Homepage

CVE-2026-80923 Affecting linux-6.12 package, versions <6.12.111-1~deb12u1

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.17% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN12-LINUX612-20506991
  • published5 Oct 2026
  • disclosed9 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 9 Sep 2026

NewCVE-2026-80923  (opens in a new tab)

How to fix?

Upgrade Debian:12 linux-6.12 to version 6.12.111-1~deb12u1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream linux-6.12 package and not the linux-6.12 package as distributed by Debian. See How to fix? for Debian:12 relevant fixed versions and status.

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()           -&gt; 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)               -&gt; true (dangling)
          tty_unregister_driver()         -&gt; use-after-free