---
id: "CVE-2026-99308"
page: "https://infrastack.ai/live/CVE-2026-99308"
kind: "vulnerability"
aliases: ["CVE-2026-99308"]
title: "Linux kernel: xHCI bounce buffer overflow from malicious USB bulk endpoint"
severity: "unknown"
cvss: null
epss: 0.00223
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["linux-kernel", "runtime", "usb", "xhci"]
not_affected_if: ["no-untrusted-usb-devices"]
published_at: "2026-11-16T10:17:05+00:00"
first_seen_at: "2026-11-16T10:39:27+00:00"
updated_at: "2026-11-16T18:53:18+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99308", "first_seen_at": "2026-11-16T10:39:27+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-99308", "first_seen_at": "2026-11-16T18:53:18+00:00"}]
exploit_sources: [{"type": "epss", "score": 0.00223, "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-99308"}]
---

# Linux kernel: xHCI bounce buffer overflow from malicious USB bulk endpoint

Link for people: https://infrastack.ai/live/CVE-2026-99308 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-11-16T10:39:27+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99308
- 2026-11-16T18:53:18+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-99308

## 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
