CVE-2026-68180

intel_th: fix MSC output device reference leak

N/A
Published: August 10, 2026 at 11:59 AM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.249 ≤ v < 5.10.2655.15.199 ≤ v < 5.15.2166.1.162 ≤ v < 6.1.1836.12.68 ≤ v < 6.12.1016.18.8 ≤ v < 6.18.426.19 ≤ v < 7.1.66.19 ≤ v < 7.26.6.122 ≤ v < 6.6.1480fca16c5591534cc1fec8b6181277ee3a3d0f26c5.10.2495.15.1996.1.1626.12.686.18.86.196.6.12264015cbf06e8bb75b81ae95b997e847b55280f7f95fc36a234da24bbc5f476f8104a5a15f99ed3e3af4b9467296b9a16ebc008147238070236982b6db71e64ef7ff9443835d1333e3e80ab1e49e5209fbf7785434b5d05d940d936b78925080950bd54ddf9b059bda4276f2bb72cb98ec7875a747f042ea2
Vendor states this is fixed in 12ad4fad748e6e563ff4480f03b89134a41b5c37 (fixed)
Vendor states this is fixed in 141641a70ed337e54487f766ede745fc2ce44c42 (fixed)
Vendor states this is fixed in 26e27b8dcef1e4df6f30d8f25b3304a506d482b3 (fixed)
Vendor states this is fixed in 761b785a0cfbce43761227bc42a7f984f31f8921 (fixed)
Vendor states this is fixed in c3a28f9cb82425fe0835048ed3677f321e780691 (fixed)
Vendor states this is fixed in caba30eb8bd321c465ecfc7d850ee85f5b353496 (fixed)
Vendor states this is fixed in ddcf2064d7ec5a8c9afa7cb74442320e443502bc (fixed)
Vendor states this is fixed in df55842fddbcdb80e6dd16680439c0f780ed592e (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.19 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card