CVE-2026-68180: intel_th: fix MSC output device reference leak
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 12ad4fad748e6e563ff4480f03b89134a41b5c37, 141641a70ed337e54487f766ede745fc2ce44c42, 26e27b8dcef1e4df6f30d8f25b3304a506d482b3; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 12ad4fad748e6e563ff4480f03b89134a41b5c37, 141641a70ed337e54487f766ede745fc2ce44c42, 26e27b8dcef1e4df6f30d8f25b3304a506d482b3; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: intel_th: fix MSC output device reference leak intel_th_output_open() looks up the output device with bus_find_device_by_devt(), which returns the device with a reference that must be dropped after use. commit 95fc36a234da ("intel_th: fix device leak on output open()") attempted to drop the reference from intel_th_output_release(). However, a successful open replaces file->f_op with the output driver file operations before returning, so close runs the output driver release callback instead. For MSC outputs, close runs intel_th_msc_release(), which only removes the per-file iterator and does not drop the device reference taken by intel_th_output_open(). Consequently, every successful MSC output open leaks one device reference. Drop the device reference from intel_th_msc_release(), which is the release path actually used for MSC output files. Remove the now-unused intel_th_output_release() callback from intel_th_output_fops.
- Published
- Aug 10, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.19affected
- af4b9467296b9a16ebc008147238070236982b6d and later · before 12ad4fad748e6e563ff4480f03b89134a41b5c37affected · git
- 64015cbf06e8bb75b81ae95b997e847b55280f7f and later · before df55842fddbcdb80e6dd16680439c0f780ed592eaffected · git
- b71e64ef7ff9443835d1333e3e80ab1e49e5209f and later · before 141641a70ed337e54487f766ede745fc2ce44c42affected · git
- bf7785434b5d05d940d936b78925080950bd54dd and later · before ddcf2064d7ec5a8c9afa7cb74442320e443502bcaffected · git
- 0fca16c5591534cc1fec8b6181277ee3a3d0f26c and later · before 26e27b8dcef1e4df6f30d8f25b3304a506d482b3affected · git
- f9b059bda4276f2bb72cb98ec7875a747f042ea2 and later · before caba30eb8bd321c465ecfc7d850ee85f5b353496affected · git
- 95fc36a234da24bbc5f476f8104a5a15f99ed3e3 and later · before c3a28f9cb82425fe0835048ed3677f321e780691affected · git
- 95fc36a234da24bbc5f476f8104a5a15f99ed3e3 and later · before 761b785a0cfbce43761227bc42a7f984f31f8921affected · git
- 5.10.249 and later · before 5.10.265affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68178Aug 10, 2026 · misc: nsm: pin the module while the device is open31Monitor
- ← EarlierCVE-2026-68179Aug 10, 2026 · misc: nsm: only unlock nsm_dev on post-lock error paths33Monitor
- Later →CVE-2026-68184Aug 10, 2026 · cdrom: fix stack out-of-bounds read in CDROMVOLCTRL0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12ad4fad748e6e563ff4480f03b89134a41b5c37 | Vendor (CNA) |
| Linux Linux | 141641a70ed337e54487f766ede745fc2ce44c42 | Vendor (CNA) |
| Linux Linux | 26e27b8dcef1e4df6f30d8f25b3304a506d482b3 | Vendor (CNA) |
| Linux Linux | 5.10.265 | Vendor (CNA) |
| Linux Linux | 5.15.216 | Vendor (CNA) |
| Linux Linux | 6.1.183 | Vendor (CNA) |
| Linux Linux | 6.12.101 | Vendor (CNA) |
| Linux Linux | 6.18.42 | Vendor (CNA) |
| Linux Linux | 6.6.148 | Vendor (CNA) |
| Linux Linux | 761b785a0cfbce43761227bc42a7f984f31f8921 | Vendor (CNA) |
| Linux Linux | c3a28f9cb82425fe0835048ed3677f321e780691 | Vendor (CNA) |
| Linux Linux | caba30eb8bd321c465ecfc7d850ee85f5b353496 | Vendor (CNA) |
| Linux Linux | ddcf2064d7ec5a8c9afa7cb74442320e443502bc | Vendor (CNA) |
| Linux Linux | df55842fddbcdb80e6dd16680439c0f780ed592e | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/141641a70ed337e54487f766ede745fc2ce44c42
- git.kernel.org/stable/c/26e27b8dcef1e4df6f30d8f25b3304a506d482b3
- git.kernel.org/stable/c/761b785a0cfbce43761227bc42a7f984f31f8921
- git.kernel.org/stable/c/c3a28f9cb82425fe0835048ed3677f321e780691
- git.kernel.org/stable/c/caba30eb8bd321c465ecfc7d850ee85f5b353496
- git.kernel.org/stable/c/ddcf2064d7ec5a8c9afa7cb74442320e443502bc
- git.kernel.org/stable/c/df55842fddbcdb80e6dd16680439c0f780ed592e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.