[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251028080043.27760-1-uttkarsh.aggarwal@oss.qualcomm.com>
Date: Tue, 28 Oct 2025 13:30:43 +0530
From: Uttkarsh Aggarwal <uttkarsh.aggarwal@....qualcomm.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Mathias Nyman <mathias.nyman@...el.com>
Cc: linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
wesley.cheng@....qualcomm.com,
Uttkarsh Aggarwal <uttkarsh.aggarwal@....qualcomm.com>
Subject: [PATCH] xhci: sideband: Fix race condition in sideband unregister
A kernel panic was observed due to a race condition between un-registering
sideband and creating sideband interrupters. The issue occurrs when thread
T1 runs uaudio_disconnect() and released sb->xhci via sideband_unregister,
while thread T2 simultaneously accessed the now-NULL sb->xhci in
xhci_sideband_create_interrupter() resulting in a crash.
By locking the mutex before modifying sb->xhci, any thread calling
xhci_sideband_create_interrupter() will either see a valid sb->xhci or wait
until xhci_sideband_unregister() completes.
Signed-off-by: Uttkarsh Aggarwal <uttkarsh.aggarwal@....qualcomm.com>
---
drivers/usb/host/xhci-sideband.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/host/xhci-sideband.c b/drivers/usb/host/xhci-sideband.c
index e771a476fef2..74a58f759cee 100644
--- a/drivers/usb/host/xhci-sideband.c
+++ b/drivers/usb/host/xhci-sideband.c
@@ -481,10 +481,12 @@ xhci_sideband_unregister(struct xhci_sideband *sb)
xhci_sideband_remove_interrupter(sb);
+ mutex_lock(&sb->mutex);
spin_lock_irq(&xhci->lock);
sb->xhci = NULL;
sb->vdev->sideband = NULL;
spin_unlock_irq(&xhci->lock);
+ mutex_unlock(&sb->mutex);
kfree(sb);
}
--
2.17.1
Powered by blists - more mailing lists