Strix
63.4K

CVE-2026-80923

Unknown

Last modified

CVE-2026-80923 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 4521f16139409cdf9462c7325d43454462cff6c3, < 01b7bc0938061f2fd46e0094f6483d8c6c02f7d3; >= 4521f16139409cdf9462c7325d43454462cff6c3, < 43635ff6401ca0e0ed21875379eeded921321525; >= 4521f16139409cdf9462c7325d43454462cff6c3, < eaca2814f32b9872a332326324b9e83e01f156d2; >= 4521f16139409cdf9462c7325d43454462cff6c3, < 943f976c93e70563b132f5585ff68b08c89641a2; >= 4521f16139409cdf9462c7325d43454462cff6c3, < 0d0faf3cc44c4d86fc6faf5cea972c0fbe00b922; >= 4521f16139409cdf9462c7325d43454462cff6c3, < 33ed35ca629477f57e0dd1d77d6df96cf5a9eb55; >= 4521f16139409cdf9462c7325d43454462cff6c3, < 0e469b94fbba8eb03666da41dd1082b793c50c1a; >= 4521f16139409cdf9462c7325d43454462cff6c3, < a916fa66a43e10f63198b6ce978badffc678821a
LinuxLinux5.9

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is 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
How severe is CVE-2026-80923?
Severity scoring for CVE-2026-80923 is pending analysis.
How do I fix CVE-2026-80923?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-80923?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST