# i2c: tegra: fix pm_runtime leak on mutex_lock failure

CVE record · `CVE-2026-64171`

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

Published by the CVE Program (CNA: Linux) at 19 Jul 2026, 15:40 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: `6077cfd716fbd4d1f2a3702e49ae8bf65c072685 to before 8f7ed203b39004c02479a9156089d87d1ac2c1d8` (git)
  - affected: `6077cfd716fbd4d1f2a3702e49ae8bf65c072685 to before 57cf4e8d6a57dc2ef5810f4852a23ba4c71b74bb` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `7.0`
  - unaffected: `before 7.0` (semver)
  - unaffected: `7.0.11 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's Tegra I2C driver leaks a runtime power management reference when mutex locking fails, so the device can never enter runtime suspend. The source gives no details on attacker access or impact beyond this. Upgrade to Linux kernel 7.0.11 or later in the 7.0 series, or to 7.1 or later.

Written 17 Nov 2026.

## 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.0011, the 1st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 19 Jul 2026, 15:40 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-64171)
- 19 Jul 2026, 16:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-64171)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/8f7ed203b39004c02479a9156089d87d1ac2c1d8>
- <https://git.kernel.org/stable/c/57cf4e8d6a57dc2ef5810f4852a23ba4c71b74bb>

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-64171>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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