CVE-2026-64465

usb: xhci: Fix sleep in atomic context in xhci_free_streams()

N/A
Published: July 25, 2026 at 08:51 AM UTC
Updated: August 17, 2026 at 05:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Fix sleep in atomic context in xhci_free_streams() When a USB device with active stream endpoints is disconnected, xhci_free_streams() is called from the hub_event workqueue to free the stream resources. It calls xhci_free_stream_info() while holding xhci->lock with irqs disabled. xhci_free_stream_info() invokes xhci_free_stream_ctx(), which calls dma_free_coherent() for large stream context arrays. dma_free_coherent() can sleep (e.g. via vunmap), triggering a BUG when called from atomic context. Call trace: dma_free_attrs+0x174/0x220 xhci_free_stream_info+0xd0/0x11c xhci_free_streams+0x278/0x37c usb_free_streams+0x98/0xc0 usb_unbind_interface+0x1b8/0x2f8 device_release_driver_internal+0x1d4/0x2cc device_release_driver+0x18/0x28 bus_remove_device+0x160/0x1a4 device_del+0x1ec/0x350 usb_disable_device+0x98/0x214 usb_disconnect+0xf0/0x35c hub_event+0xab4/0x19ec process_one_work+0x278/0x63c Fix this by saving the stream_info pointers and clearing the ep references under the lock, then calling xhci_free_stream_info() outside the lock where sleeping is allowed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.35 ≤ v < 5.10.2612.6.35 ≤ v < 5.15.2122.6.35 ≤ v < 6.1.1782.6.35 ≤ v < 6.12.962.6.35 ≤ v < 6.18.392.6.35 ≤ v < 6.6.1452.6.35 ≤ v < 7.1.42.6.35 ≤ v < 7.22.6.358df75f42f8e67e2851cdcf6da91640fb881defd1
Vendor states this is fixed in 10666ac9c552990204e791af653abf8e9d9ff619 (fixed)
Vendor states this is fixed in 1e45aa722c4ce5663e987102aac18c8ad6a83fdd (fixed)
Vendor states this is fixed in 42c37c4b75d38b51d84f31a8e29427f5e06a7c2a (fixed)
Vendor states this is fixed in 93cd037da94fcb93183bfb2457e3a56d3eb4c8f4 (fixed)
Vendor states this is fixed in d107eb316144c5fb958486e7fe604cd7f1b35cda (fixed)
Vendor states this is fixed in e623e4a203f56d5c57519a9a3cb29600551534ad (fixed)
Vendor states this is fixed in f7b022ae07685e7526fc39f387ce65b5d309dd3b (fixed)
Vendor states this is fixed in f90586129cf9e1fbdb718ef602eea3f15dc1c31c (fixed)
Vendor states this is fixed in 2.6.35 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card