CVE-2026-68180 — intel_th: fix MSC output device reference leak
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ af4b9467296b9a16ebc008147238070236982b6d and < 12ad4fad748e6e563ff4480f03b89134a41b5c37≥ 64015cbf06e8bb75b81ae95b997e847b55280f7f and < df55842fddbcdb80e6dd16680439c0f780ed592e≥ b71e64ef7ff9443835d1333e3e80ab1e49e5209f and < 141641a70ed337e54487f766ede745fc2ce44c42≥ bf7785434b5d05d940d936b78925080950bd54dd and < ddcf2064d7ec5a8c9afa7cb74442320e443502bc≥ 0fca16c5591534cc1fec8b6181277ee3a3d0f26c and < 26e27b8dcef1e4df6f30d8f25b3304a506d482b3≥ f9b059bda4276f2bb72cb98ec7875a747f042ea2 and < caba30eb8bd321c465ecfc7d850ee85f5b353496≥ 95fc36a234da24bbc5f476f8104a5a15f99ed3e3 and < c3a28f9cb82425fe0835048ed3677f321e780691≥ 95fc36a234da24bbc5f476f8104a5a15f99ed3e3 and < 761b785a0cfbce43761227bc42a7f984f31f8921 and 7 more≥ 5.10.249 and < 5.10.265≥ 5.15.199 and < 5.15.216≥ 6.1.162 and < 6.1.183≥ 6.6.122 and < 6.6.148≥ 6.12.68 and < 6.12.101≥ 6.18.8 and < 6.18.42version 6.19 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/141641a70ed337e54487f766ede745fc2ce44c42
- git.kernel.org/stable/c/caba30eb8bd321c465ecfc7d850ee85f5b353496
- git.kernel.org/stable/c/26e27b8dcef1e4df6f30d8f25b3304a506d482b3
- git.kernel.org/stable/c/c3a28f9cb82425fe0835048ed3677f321e780691
- git.kernel.org/stable/c/ddcf2064d7ec5a8c9afa7cb74442320e443502bc
- git.kernel.org/stable/c/df55842fddbcdb80e6dd16680439c0f780ed592e
- git.kernel.org/stable/c/761b785a0cfbce43761227bc42a7f984f31f8921
- git.kernel.org/stable/c/12ad4fad748e6e563ff4480f03b89134a41b5c37
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 3d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 3d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 3d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 3d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 3d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-68180 is "intel_th: fix MSC output device reference leak", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.