Data corruption via lost xHCI bounce buffers
Published Sep 16, 2026 · Updated Sep 16, 2026
Data corruption in the Linux kernel xHCI driver allows local users to retain stale bytes in completed large fragmented USB IN transfers. xhci_unmap_td_bounce_buffer() follows only td->bounce_seg, so earlier segment bounce buffers are neither copied into the URB nor DMA-unmapped. The condition requires a bulk transfer spanning at least three ring segments with boundary data misaligned to wMaxPacketSize; affected reads can silently consume stale data while each dropped bounce also leaks a DMA mapping.
Summary
What happened
Data corruption in the Linux kernel xHCI driver allows local users to retain stale bytes in completed large fragmented USB IN transfers. xhci_unmap_td_bounce_buffer() follows only td->bounce_seg, so earlier segment bounce buffers are neither copied into the URB nor DMA-unmapped. The condition requires a bulk transfer spanning at least three ring segments with boundary data misaligned to wMaxPacketSize; affected reads can silently consume stale data while each dropped bounce also leaks a DMA mapping.
The record
- CVE
- CVE-2026-90015
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.8
- Affected versionversion=f9c589e142d04b8a19eb382162f804d17102b5ed <3c9a2b5a4f1183696f02ac280ced1d34afb409b1
- Affected versionversion=f9c589e142d04b8a19eb382162f804d17102b5ed <43239fc6dfb62c50ae1b9c0e82bac0f8cd2e285c
- Affected versionversion=f9c589e142d04b8a19eb382162f804d17102b5ed <7236bbd2cb7d9fc0eda896bbd34790341e2a4377
- Affected versionversion=f9c589e142d04b8a19eb382162f804d17102b5ed <a1629dfb011446d02905778f6df19f14c5f4f3b3
- Affected versionversion=f9c589e142d04b8a19eb382162f804d17102b5ed <c8124b28f12dbdd126118e63d0ebf8093a01fb81
- Affected versionversion=f9c589e142d04b8a19eb382162f804d17102b5ed <e04d5304a248e5d2a7f4faa87541644bdd320cfb
- Affected versionversion=f9c589e142d04b8a19eb382162f804d17102b5ed <efaab8938fb92979be6df359f7d1a43fb7e4717d
- Affected versionversion=f9c589e142d04b8a19eb382162f804d17102b5ed <ff44dfb03a293bf30e31f98772a1dd316a6071d1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- xhci-verity reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo