CVE-2026-98773

USB: cdc-acm: skip URB restart in port_shutdown if disconnected

N/A
Published: October 18, 2026 at 03:48 PM UTC
Updated: October 30, 2026 at 01:21 PM 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: cdc-acm: skip URB restart in port_shutdown if disconnected acm_port_shutdown() is called from the tty-port machinery whenever the last user closes the port. acm_disconnect() sets acm->disconnected and calls tty_port_tty_vhangup(), which eventually triggers port_shutdown(). At that point acm_disconnect() has already called acm_poison_urbs() and is about to free the control and read URBs. However, acm_port_shutdown() unconditionally calls acm_unpoison_urbs() and, when the ALWAYS_POLL_CTRL quirk is set, immediately re-submits the ctrlurb and all read URBs. If the concurrent acm_disconnect() then frees those URBs and their DMA buffers while they are in-flight, the result is a use-after-free in acm_ctrl_irq() or acm_read_bulk_callback() accessing the freed DMA memory. Fix by checking acm->disconnected after draining the delayed anchor and returning early: if we are in a disconnect path the URBs must remain poisoned and must not be resubmitted. The early return is placed after the delayed-anchor drain loop because that loop only cancels write-side accounting (wb->use = false and autopm counter) and does not touch the hardware path.

Affected

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

283f8162cc3c82086537cbc7dc01870dbeb07a915d29d7ff8679e5a525f22da467ba33c042e8029b6.1.1756.12.836.18.246.19.146.6.136603d5a7110832e10165d21f9a1486399457177de7.0.17.18fb82e3555a7d56a05d8ef0edee9859f889c0860d826061aa64cb28089bf4c73e301dd7928662b84f58752ebcb35e156c85cd1a82d6579c7af3b9023f77f10bc76c2da86b4248269472f6d971e37828b
Vendor states this is fixed in 6.12.113 (unaffected)
Vendor states this is fixed in 6.18.56 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.2.10 (unaffected)
Vendor states this is fixed in 7.3 (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