Strix
26.1K

CVE-2026-68180

Unknown

Last modified

CVE-2026-68180 is a vulnerability of currently unknown severity. 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().

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= bf7785434b5d05d940d936b78925080950bd54dd, < ddcf2064d7ec5a8c9afa7cb74442320e443502bc; >= 0fca16c5591534cc1fec8b6181277ee3a3d0f26c, < 26e27b8dcef1e4df6f30d8f25b3304a506d482b3; >= f9b059bda4276f2bb72cb98ec7875a747f042ea2, < caba30eb8bd321c465ecfc7d850ee85f5b353496; >= 95fc36a234da24bbc5f476f8104a5a15f99ed3e3, < c3a28f9cb82425fe0835048ed3677f321e780691; >= 95fc36a234da24bbc5f476f8104a5a15f99ed3e3, < 761b785a0cfbce43761227bc42a7f984f31f8921; af4b9467296b9a16ebc008147238070236982b6d; 64015cbf06e8bb75b81ae95b997e847b55280f7f; b71e64ef7ff9443835d1333e3e80ab1e49e5209f; >= 6.6.122, < 6.6.148; >= 6.12.68, < 6.12.101; >= 6.18.8, < 6.18.42; >= 5.10.249, < 5.11; >= 5.15.199, < 5.16; >= 6.1.162, < 6.2
LinuxLinux6.19

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-68180?
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.
How severe is CVE-2026-68180?
Severity scoring for CVE-2026-68180 is pending analysis.
How do I fix CVE-2026-68180?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-68180?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST