CVE-2026-80923
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 versions
Linux kernel versions
5.9
and later are affected. Fixed in
5.15.220,
6.1.187,
6.6.156,
6.12.108,
6.18.49,
7.1.13,
7.2.3,
7.3-rc1
and their respective stable series.
References
8 totalFrequently asked questions
-
What is CVE-2026-80923?
CVE-2026-80923 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.9 onward and has been patched in 5.15.220, 6.1.187, 6.6.156 and others. CVE-2026-80923 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-80923?
Yes. CVE-2026-80923 has been patched. Fixed versions include 5.15.220, 6.1.187, 6.6.156 and others. If you are running Linux kernel 5.9 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-80923 actively exploited?
No. CVE-2026-80923 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.