From: Markus Rechberger <linuxusb.ml@sundtek.de>
To: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Highly critical bug in XHCI Controller
Date: Sun, 17 Nov 2024 15:33:28 +0800 [thread overview]
Message-ID: <3905c1c88695e0ffcfabf700c06dd7223decef8d.camel@sundtek.de> (raw)
Hi,
the issue was first reported at vdr-portal.de
https://www-vdr--portal-de.translate.goog/forum/index.php?thread/136541-empfehlung-dvb-s2-tuner-oder-satip/&postID=1376196&_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp#post1376196
we've got around a highly critical bug in the xhci driver.
https://sundtek.de/support/uxvd32.txt
In xhci.c
The bug is still active in Mainline:
https://github.com/torvalds/linux/blob/master/drivers/usb/host/xhci.c#L2382
static int xhci_check_bw_table(struct xhci_hcd *xhci,
struct xhci_virt_device *virt_dev,
int old_active_eps)
bw_table can end up with a NULL pointer.
This problem will lead to a complete kernel crash, rendering the entire
system unusable without any access to the actual linux system.
How to trigger the problem?
Short D+/D- or pull them to ground on a USB device while connecting the
device.
The problem can happen due to following cases:
* a device is getting suddenly disconnected during enumeration
* a faulty cable
* a faulty device
* a malicious device triggers this issue on purpose
* if there are electrical issues during connecting a device.
A quick hotfix would be to check if bw_table is NULL in
xhci_check_bw_table, however the check should be performed earlier - in
the area where bw_table is supposed to be assigned.
Best Regards,
Markus
next reply other threads:[~2024-11-17 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 7:33 Markus Rechberger [this message]
2024-11-17 12:44 ` Markus Rechberger
2024-11-17 13:12 ` Greg KH
2024-11-17 14:35 ` Michał Pecio
2024-11-17 15:03 ` Markus Rechberger
2024-11-17 15:18 ` Alan Stern
2024-11-17 15:47 ` Markus Rechberger
2024-11-17 21:02 ` Alan Stern
2024-11-18 5:14 ` Markus Rechberger
2024-11-18 16:03 ` Alan Stern
2024-11-18 21:23 ` Michał Pecio
2024-11-17 13:12 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3905c1c88695e0ffcfabf700c06dd7223decef8d.camel@sundtek.de \
--to=linuxusb.ml@sundtek.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®