Local service interruption via leaked device references
Published Aug 10, 2026 · Updated Aug 10, 2026
Reference-counting flaw in the Linux kernel Intel Trace Hub driver allows local users to exhaust resources by opening MSC outputs. The MSC release callback removes its per-file iterator but fails to drop the device reference acquired when the output is opened, so every successful open leaks one reference. Exploitation requires local access to Intel Trace Hub MSC device nodes; repeated opens can exhaust kernel resources and interrupt service.
Summary
What happened
Reference-counting flaw in the Linux kernel Intel Trace Hub driver allows local users to exhaust resources by opening MSC outputs. The MSC release callback removes its per-file iterator but fails to drop the device reference acquired when the output is opened, so every successful open leaks one reference. Exploitation requires local access to Intel Trace Hub MSC device nodes; repeated opens can exhaust kernel resources and interrupt service.
The record
- CVE
- CVE-2026-68180
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-911, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0fca16c5591534cc1fec8b6181277ee3a3d0f26c <26e27b8dcef1e4df6f30d8f25b3304a506d482b3
- Affected versionversion=5.10.249 <5.11
- Affected versionversion=5.15.199 <5.16
- Affected versionversion=6.1.162 <6.2
- Affected versionversion=6.12.68 <6.12.101
- Affected versionversion=6.18.8 <6.18.42
- Affected versionversion=6.19
- Affected versionversion=64015cbf06e8bb75b81ae95b997e847b55280f7f
- Affected versionversion=6.6.122 <6.6.148
- Affected versionversion=95fc36a234da24bbc5f476f8104a5a15f99ed3e3 <761b785a0cfbce43761227bc42a7f984f31f8921
- Affected versionversion=95fc36a234da24bbc5f476f8104a5a15f99ed3e3 <c3a28f9cb82425fe0835048ed3677f321e780691
- Affected versionversion=af4b9467296b9a16ebc008147238070236982b6d
- Affected versionversion=b71e64ef7ff9443835d1333e3e80ab1e49e5209f
- Affected versionversion=bf7785434b5d05d940d936b78925080950bd54dd <ddcf2064d7ec5a8c9afa7cb74442320e443502bc
- Affected versionversion=f9b059bda4276f2bb72cb98ec7875a747f042ea2 <caba30eb8bd321c465ecfc7d850ee85f5b353496
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo