CVE-2026-80923

xhci: dbgtty: Fix unregister on tty_register_driver() failure

N/A
Published: September 9, 2026 at 04:19 PM UTC
Updated: October 19, 2026 at 09: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: xhci: dbgtty: Fix unregister on tty_register_driver() failure If tty_register_driver() fails, it drops the reference, but fails to set the global dbc_tty_driver to NULL, causing the unregister to be called again when module exits. On module unload dbc_tty_exit() only gates its cleanup on the driver pointer being non-NULL, so it operates on the already-freed driver: module_init(xhci_hcd_init) xhci_hcd_init() xhci_dbc_init() [return value ignored] dbc_tty_init() tty_register_driver() fails tty_driver_kref_put() -> driver freed (dbc_tty_driver left dangling) ... module_exit(xhci_hcd_fini) xhci_hcd_fini() xhci_dbc_exit() dbc_tty_exit() if (dbc_tty_driver) -> true (dangling) tty_unregister_driver() -> use-after-free

Affected

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

4521f16139409cdf9462c7325d43454462cff6c35.9
Vendor states this is fixed in 01b7bc0938061f2fd46e0094f6483d8c6c02f7d3 (fixed)
Vendor states this is fixed in 0d0faf3cc44c4d86fc6faf5cea972c0fbe00b922 (fixed)
Vendor states this is fixed in 0e469b94fbba8eb03666da41dd1082b793c50c1a (fixed)
Vendor states this is fixed in 33ed35ca629477f57e0dd1d77d6df96cf5a9eb55 (fixed)
Vendor states this is fixed in 43635ff6401ca0e0ed21875379eeded921321525 (fixed)
Vendor states this is fixed in 943f976c93e70563b132f5585ff68b08c89641a2 (fixed)
Vendor states this is fixed in a916fa66a43e10f63198b6ce978badffc678821a (fixed)
Vendor states this is fixed in eaca2814f32b9872a332326324b9e83e01f156d2 (fixed)
Vendor states this is fixed in 5.15.220 (unaffected)
Vendor states this is fixed in 5.9 (unaffected)
Vendor states this is fixed in 6.1.187 (unaffected)
Vendor states this is fixed in 6.12.108 (unaffected)
Vendor states this is fixed in 6.18.49 (unaffected)
Vendor states this is fixed in 6.6.156 (unaffected)
Vendor states this is fixed in 7.1.13 (unaffected)
Vendor states this is fixed in 7.2.3 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (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