CVE-2026-64171

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

i2c: tegra: fix pm_runtime leak on mutex_lock failure

If tegra_i2c_mutex_lock() fails, the function returns without calling pm_runtime_put(), leaking the runtime PM reference acquired by the preceding pm_runtime_get_sync(). This prevents the device from ever entering runtime suspend.

Add the missing pm_runtime_put() before returning on lock failure.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

i2c: tegra: fix pm_runtime leak on mutex_lock failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8f7ed203b39004c02479a9156089d87d1ac2c1d8
generic

i2c: tegra: fix pm_runtime leak on mutex_lock failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57cf4e8d6a57dc2ef5810f4852a23ba4c71b74bb

Vendor Advisories for CVE-2026-64171(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 21× in last 7d / 69× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 368 total refreshes for this CVE.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 20:16 UTCVendor advisory
  3. 2026-08-25 20:16 UTCGHSA enrichment
  4. 2026-08-24 20:17 UTCEG score recompute
  5. 2026-08-24 20:17 UTCVendor advisory
  6. 2026-08-24 20:16 UTCGHSA enrichment
  7. 2026-08-23 20:52 UTCEG score recompute
  8. 2026-08-23 20:52 UTCVendor advisory
  9. 2026-08-23 20:52 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 21:28 UTCVendor advisory
  12. 2026-08-22 21:28 UTCGHSA enrichment
  13. 2026-08-21 21:45 UTCEG score recompute
  14. 2026-08-21 21:45 UTCVendor advisory
  15. 2026-08-21 21:45 UTCGHSA enrichment
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 22:20 UTCVendor advisory
  18. 2026-08-20 22:20 UTCGHSA enrichment
  19. 2026-08-19 22:55 UTCEG score recompute
  20. 2026-08-19 22:55 UTCVendor advisory
  21. 2026-08-19 22:55 UTCGHSA enrichment
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-18 19:40 UTCEG score recompute
  24. 2026-08-18 19:40 UTCVendor advisory
  25. 2026-08-18 19:39 UTCGHSA enrichment
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-17 13:14 UTCVendor advisory
  3. 2026-08-17 13:14 UTCGHSA enrichment
  4. 2026-08-16 13:50 UTCVendor advisory
  5. 2026-08-16 13:50 UTCGHSA enrichment
  6. 2026-08-15 14:26 UTCEG score recompute
  7. 2026-08-15 14:26 UTCVendor advisory
  8. 2026-08-15 14:26 UTCGHSA enrichment
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 15:01 UTCEG score recompute
  11. 2026-08-14 15:01 UTCVendor advisory
  12. 2026-08-14 15:01 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 15:36 UTCEG score recompute▲ 5.50
  15. 2026-08-13 15:36 UTCVendor advisory
  16. 2026-08-13 15:36 UTCGHSA enrichment
  17. 2026-08-13 15:36 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  18. 2026-08-13 14:06 UTCVendor advisory
  19. 2026-08-13 14:06 UTCGHSA enrichment
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 00:00 UTCEPSS rescore
  22. 2026-08-10 19:25 UTCVendor advisory
  23. 2026-08-10 19:25 UTCGHSA enrichment
  24. 2026-08-09 13:47 UTCEPSS rescore
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-08 00:44 UTCVendor advisory
  27. 2026-08-08 00:44 UTCGHSA enrichment
  28. 2026-08-06 13:47 UTCEPSS rescore
  29. 2026-08-05 19:17 UTCEPSS rescore
  30. 2026-08-05 19:17 UTCEPSS rescore
  31. 2026-08-05 06:02 UTCGHSA enrichment
  32. 2026-08-04 10:39 UTCEPSS rescore
  33. 2026-08-03 10:36 UTCEPSS rescore
  34. 2026-08-02 09:59 UTCVendor advisory
  35. 2026-08-02 09:59 UTCGHSA enrichment
  36. 2026-08-02 02:27 UTCEPSS rescore
  37. 2026-08-01 04:16 UTCEPSS rescore
  38. 2026-07-30 16:28 UTCEPSS rescore
  39. 2026-07-30 15:18 UTCEG score recompute
  40. 2026-07-30 15:18 UTCGHSA enrichment
  41. 2026-07-30 01:30 UTCEPSS rescore
  42. 2026-07-30 01:30 UTCEPSS rescore
  43. 2026-07-29 05:37 UTCGHSA enrichment
  44. 2026-07-28 15:37 UTCEPSS rescore
  45. 2026-07-27 14:14 UTCEPSS rescore
  46. 2026-07-26 14:54 UTCEPSS rescore
  47. 2026-07-26 14:54 UTCEPSS rescore
  48. 2026-07-26 10:51 UTCEG score recompute
  49. 2026-07-26 10:51 UTCVendor advisory
  50. 2026-07-26 10:51 UTCGHSA enrichment
  51. 2026-07-25 14:18 UTCEPSS rescore
  52. 2026-07-25 14:18 UTCEPSS rescore
  53. 2026-07-24 14:18 UTCEPSS rescore
  54. 2026-07-24 14:18 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 14:18 UTCEPSS rescore
  57. 2026-07-23 03:22 UTCEG score recompute
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-22 14:08 UTCEPSS rescore
  60. 2026-07-21 15:25 UTCEPSS rescore
  61. 2026-07-21 15:25 UTCEPSS rescore
  62. 2026-07-20 17:15 UTCEG score recompute
  63. 2026-07-20 17:15 UTCGHSA enrichment
  64. 2026-07-20 17:08 UTCEPSS rescore
  65. 2026-07-20 16:28 UTCGHSA enrichment
  66. 2026-07-20 16:09 UTCGHSA enrichment
  67. 2026-07-20 15:58 UTCGHSA enrichment
  68. 2026-07-20 15:55 UTCGHSA enrichment
  69. 2026-07-20 15:54 UTCGHSA enrichment
  70. 2026-07-20 15:53 UTCGHSA enrichment
  71. 2026-07-20 15:52 UTCGHSA enrichment
  72. 2026-07-20 15:52 UTCGHSA enrichment
  73. 2026-07-20 15:51 UTCGHSA enrichment
  74. 2026-07-20 15:51 UTCGHSA enrichment
  75. 2026-07-20 15:50 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64171?
CVE-2026-64171 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: fix pmruntime leak on mutexlock failure If tegrai2cmutex_lock() fails, the function returns without calling pmruntimeput(), leaking the runtime PM reference acquired by the preceding pmruntimeget_sync(). This prevents…
When was CVE-2026-64171 disclosed?
CVE-2026-64171 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64171 actively exploited?
CVE-2026-64171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64171?
CVE-2026-64171 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64171?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64171, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64171

Explore →

Is Your Infrastructure Affected by CVE-2026-64171?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs