CVE-2026-99308
usb: xhci: Fix bounce buffer overflow
What happened?
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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: f9c589e142d04b8a19eb382162f804d17102b5ed to < dab2792e136385bd34b36d2b95db94862ed902cc; affected: f9c589e142d04b8a19eb382162f804d17102b5ed to < d0d15d7a11f2a45e5d29ab4780a094992d7a26a2; affected: f9c589e142d04b8a19eb382162f804d17102b5ed to < e95ace4abebd564b50b856513e24853d35be06cd; affected: f9c589e142d04b8a19eb382162f804d17102b5ed to < 68c5cb7574c567e83ba95258cb146db95e069a87 | See vendor advisory |
| LinuxLinux | affected: 4.8; unaffected: 0 to < 4.8; unaffected: 6.12.118 to ≤ 6.12.*; unaffected: 6.18.63 to ≤ 6.18.*; unaffected: 7.3.4 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99308
- https://git.kernel.org/stable/c/dab2792e136385bd34b36d2b95db94862ed902cc
- https://git.kernel.org/stable/c/d0d15d7a11f2a45e5d29ab4780a094992d7a26a2
- https://git.kernel.org/stable/c/e95ace4abebd564b50b856513e24853d35be06cd
- https://git.kernel.org/stable/c/68c5cb7574c567e83ba95258cb146db95e069a87