CVE-2026-99308 · Runtime
NO FIX YET
The Linux kernel's xHCI USB driver allocates a 512-byte bounce buffer for high-speed bulk endpoints that report a 1024-byte packet size, so a device with such an endpoint can write past the buffer. An attacker with a malicious or out-of-spec USB device could corrupt kernel memory.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Systems running a Linux kernel with the xHCI host controller driver, where a USB device with an out-of-spec 1024-byte bulk endpoint can be attached. Machines with no untrusted USB devices attached are less exposed. The sources do not give affected kernel version ranges.
Not affected if no-untrusted-usb-devices
Who cares linux-kernel, usb, xhci
Unknown from the sources.
Unknown from the sources.
In the Linux kernel, the following vulnerability has been resolved:
usb: xhci: Fix bounce buffer overflow
High-speed devices with out of spec 1024 byte bulk endpoints exist and are allowed by USB core, but xhci-hcd always sets packet size to 512. The exact nature of these devices isn't documented, commit fb5ee84ea72c ("USB: Accept bulk endpoints with 1024-byte maxpacket") only states that they "don't work with xHCI host controllers", whatever it means.
But somebody (or a malicious device) can try, and then the driver will allocate a 512 byte bounce buffer for this endpoint and may write up to 1024 bytes into it if particular scatter-gather URBs are used, because xhci_align_td() obtains packet size from the descriptor. Fix this.
As a side effect, TRBs will be aligned to the packet size chosen by the driver on all endpoints of all speeds. Alignment serves the xHC, not device, so this is fine. Only out of spec devices are affected anyway.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.