Skip to main content
VulnerabilityPublished Updated

CVE-2026-23091: Linux kernel · intel_th: fix device leak on output open()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f9b059bda4276f2bb72cb98ec7875a747f042ea2 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in f9b059bda4276f2bb72cb98ec7875a747f042ea2, bf7785434b5d05d940d936b78925080950bd54dd, b71e64ef7ff9443835d1333e3e80ab1e49e5209f +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 39f4034693b7c7bd1fe4cb58c93259d600f55561, < f9b059bda4276f2bb72cb98ec7875a747f042ea2
Fixed in
  • f9b059bda4276f2bb72cb98ec7875a747f042ea2
LinuxLinuxAffected
  • ≥ 39f4034693b7c7bd1fe4cb58c93259d600f55561, < bf7785434b5d05d940d936b78925080950bd54dd
Fixed in
  • bf7785434b5d05d940d936b78925080950bd54dd
LinuxLinuxAffected
  • ≥ 39f4034693b7c7bd1fe4cb58c93259d600f55561, < b71e64ef7ff9443835d1333e3e80ab1e49e5209f
Fixed in
  • b71e64ef7ff9443835d1333e3e80ab1e49e5209f
LinuxLinuxAffected
  • ≥ 39f4034693b7c7bd1fe4cb58c93259d600f55561, < af4b9467296b9a16ebc008147238070236982b6d
Fixed in
  • af4b9467296b9a16ebc008147238070236982b6d
LinuxLinuxAffected
  • ≥ 39f4034693b7c7bd1fe4cb58c93259d600f55561, < 64015cbf06e8bb75b81ae95b997e847b55280f7f
Fixed in
  • 64015cbf06e8bb75b81ae95b997e847b55280f7f
LinuxLinuxAffected
  • ≥ 39f4034693b7c7bd1fe4cb58c93259d600f55561, < 95fc36a234da24bbc5f476f8104a5a15f99ed3e3
Fixed in
  • 95fc36a234da24bbc5f476f8104a5a15f99ed3e3

Description

In the Linux kernel, the following vulnerability has been resolved: intel_th: fix device leak on output open() Make sure to drop the reference taken when looking up the th device during output device open() on errors and on close(). Note that a recent commit fixed the leak in a couple of open() error paths but not all of them, and the reference is still leaking on successful open().

References

Community reviews

Loading reviews…