LiveActive security incident?Get immediate response
CVE Record

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

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().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a reference leak in the Intel Trace Hub output open path. It can leave device references unreleased after errors or normal close. The public record does not provide CVSS, CWE, exploitability, or impact detail, so business urgency should be driven by kernel exposure and vendor update availability.

Executive priority

Track and patch through normal Linux kernel maintenance unless your environment relies on Intel Trace Hub devices. There is not enough public evidence to justify emergency action, but kernel fixes should not be deferred indefinitely.

Technical view

The flaw is in the Linux kernel intel_th driver. During output device open(), a th device reference taken during lookup was not dropped on all error paths and was still leaked after successful open and close. Upstream stable commits are referenced as the resolution, but the source bundle does not describe practical exploitation or concrete impact.

Likely exposure

Potential exposure is limited to Linux systems running affected kernel versions or branches with the intel_th Intel Trace Hub driver present. The source bundle lists Linux as affected but does not map distro packages, configurations, or device-node access requirements.

Exploitation context

The bundle does not report active exploitation, public exploit code, or KEV listing. It only states the kernel bug has been resolved. Treat exploitation status as unconfirmed and avoid assuming remote reachability or privilege impact without vendor analysis.

Researcher notes

Key unknowns are impact, trigger conditions, permissions needed to open the output device, and whether repeated opens can cause meaningful resource exhaustion. The commit message supports a device reference leak, not broader memory corruption or code execution.

Mitigation direction

  • Apply Linux kernel vendor updates that include the referenced stable intel_th fix.
  • Map the referenced upstream commits to your distribution kernel packages.
  • Follow your Linux distributor guidance if fixed packages are not yet available.
  • Prioritize hosts where Intel Trace Hub or intel_th devices are enabled.

Validation and detection

  • Inventory running Linux kernel versions across managed systems.
  • Check whether installed kernels include one of the referenced stable fixes.
  • Review distribution advisories for CVE-2026-23091 package status.
  • Confirm whether intel_th support is built, loaded, or exposed on relevant hosts.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23091 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux39f4034693b7c7bd1fe4cb58c93259d600f55561, 39f4034693b7c7bd1fe4cb58c93259d600f55561, 39f4034693b7c7bd1fe4cb58c93259d600f55561, 39f4034693b7c7bd1fe4cb58c93259d600f55561, 39f4034693b7c7bd1fe4cb58c93259d600f55561, 39f4034693b7c7bd1fe4cb58c93259d600f55561, 39f4034693b7c7bd1fe4cb58c93259d600f55561unaffected
LinuxLinux4.4, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.