Expired Pointer Dereference Affecting kernel-debug-modules-internal package, versions *


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

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-CENTOS8-KERNELDEBUGMODULESINTERNAL-21496608
  • published23 Oct 2026
  • disclosed9 Sept 2026

Introduced: 9 Sep 2026

CVE-2026-80923  (opens in a new tab)
CWE-825  (opens in a new tab)

How to fix?

There is no fixed version for Centos:8 kernel-debug-modules-internal.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-debug-modules-internal package and not the kernel-debug-modules-internal package as distributed by Centos. See How to fix? for Centos:8 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()           -> 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

CVSS Base Scores

version 3.1