# intel_th: fix MSC output device reference leak

CVE record · `CVE-2026-68180`

- **Identifiers:** `CVE-2026-68180`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 10 Aug 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 10 Aug 2026, 11:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `af4b9467296b9a16ebc008147238070236982b6d to before 12ad4fad748e6e563ff4480f03b89134a41b5c37` (git)
  - affected: `64015cbf06e8bb75b81ae95b997e847b55280f7f to before df55842fddbcdb80e6dd16680439c0f780ed592e` (git)
  - affected: `b71e64ef7ff9443835d1333e3e80ab1e49e5209f to before 141641a70ed337e54487f766ede745fc2ce44c42` (git)
  - affected: `bf7785434b5d05d940d936b78925080950bd54dd to before ddcf2064d7ec5a8c9afa7cb74442320e443502bc` (git)
  - affected: `0fca16c5591534cc1fec8b6181277ee3a3d0f26c to before 26e27b8dcef1e4df6f30d8f25b3304a506d482b3` (git)
  - affected: `f9b059bda4276f2bb72cb98ec7875a747f042ea2 to before caba30eb8bd321c465ecfc7d850ee85f5b353496` (git)
  - affected: `95fc36a234da24bbc5f476f8104a5a15f99ed3e3 to before c3a28f9cb82425fe0835048ed3677f321e780691` (git)
  - affected: `95fc36a234da24bbc5f476f8104a5a15f99ed3e3 to before 761b785a0cfbce43761227bc42a7f984f31f8921` (git)
  - affected: `5.10.249 to before 5.10.265` (semver)
  - affected: `5.15.199 to before 5.15.216` (semver)
  - affected: `6.1.162 to before 6.1.183` (semver)
  - affected: `6.6.122 to before 6.6.148` (semver)
  - and 2 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.19`
  - unaffected: `before 6.19` (semver)
  - unaffected: `5.10.265 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.216 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.183 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.148 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.101 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.42 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.6 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0022, the 12th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 10 Aug 2026, 11:59 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-68180)
- 10 Aug 2026, 13:20 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-68180)

## Sources

- [CVE List: CVE-2026-68180](https://www.cve.org/CVERecord?id=CVE-2026-68180)
- [NVD: CVE-2026-68180](https://nvd.nist.gov/vuln/detail/CVE-2026-68180)

### References from the CNA

- <https://git.kernel.org/stable/c/12ad4fad748e6e563ff4480f03b89134a41b5c37>
- <https://git.kernel.org/stable/c/df55842fddbcdb80e6dd16680439c0f780ed592e>
- <https://git.kernel.org/stable/c/141641a70ed337e54487f766ede745fc2ce44c42>
- <https://git.kernel.org/stable/c/ddcf2064d7ec5a8c9afa7cb74442320e443502bc>
- <https://git.kernel.org/stable/c/26e27b8dcef1e4df6f30d8f25b3304a506d482b3>
- <https://git.kernel.org/stable/c/caba30eb8bd321c465ecfc7d850ee85f5b353496>
- <https://git.kernel.org/stable/c/c3a28f9cb82425fe0835048ed3677f321e780691>
- <https://git.kernel.org/stable/c/761b785a0cfbce43761227bc42a7f984f31f8921>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-68180>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-68180/>. Everything for agents: <https://agentprime.io/llms.txt>.
