CVE-2026-64521

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

A fix is available — apply it.

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

pinctrl: meson: amlogic-a4: fix deadlock issue

Accessing the pinconf-pins sysfs node may deadlock.

pinconf_pins_show() holds pctldev->mutex, and the platform driver calls pinctrl_find_gpio_range_from_pin(), which tries to acquire the same mutex again, leading to a deadlock.

Use pinctrl_find_gpio_range_from_pin_nolock() to fix this issue.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 25, 2026

Last Modified

July 25, 2026

Vendor Advisories for CVE-2026-64521(1)

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

Patch Availability(4)

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 (141 versions)7.0.12-1

All Vendor Advisories

(4)

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 6× in last 7d / 36× 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.

  1. 2026-09-12 15:22 UTCVendor advisory
  2. 2026-09-12 15:21 UTCGHSA enrichment
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-09 08:29 UTCVendor advisory
  6. 2026-09-09 08:29 UTCGHSA enrichment
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-05 15:31 UTCEPSS rescore
  11. 2026-09-05 05:59 UTCVendor advisory
  12. 2026-09-05 05:59 UTCGHSA enrichment
  13. 2026-09-04 05:07 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 23:06 UTCVendor advisory
  16. 2026-09-01 23:06 UTCGHSA enrichment
  17. 2026-09-01 13:54 UTCEPSS rescore
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:42 UTCEPSS rescore
  22. 2026-08-28 01:28 UTCVendor advisory
  23. 2026-08-28 01:28 UTCGHSA enrichment
  24. 2026-08-26 14:47 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 52 more
  1. 2026-08-24 18:00 UTCVendor advisory
  2. 2026-08-24 18:00 UTCGHSA enrichment
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 09:43 UTCVendor advisory
  5. 2026-08-21 09:43 UTCGHSA enrichment
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 02:50 UTCVendor advisory
  10. 2026-08-18 02:50 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 19:58 UTCVendor advisory
  15. 2026-08-14 19:58 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-11 13:06 UTCVendor advisory
  18. 2026-08-11 13:06 UTCGHSA enrichment
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-09 13:47 UTCEPSS rescore
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-08 06:14 UTCVendor advisory
  23. 2026-08-08 06:14 UTCGHSA enrichment
  24. 2026-08-06 13:47 UTCEPSS rescore
  25. 2026-08-05 19:17 UTCEPSS rescore
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-04 23:22 UTCVendor advisory
  28. 2026-08-04 23:22 UTCGHSA enrichment
  29. 2026-08-04 15:10 UTCEPSS rescore
  30. 2026-08-04 10:39 UTCEPSS rescore
  31. 2026-08-03 10:36 UTCEPSS rescore
  32. 2026-08-02 02:27 UTCEPSS rescore
  33. 2026-08-01 16:30 UTCEG score recompute
  34. 2026-08-01 16:30 UTCVendor advisory
  35. 2026-08-01 16:30 UTCGHSA enrichment
  36. 2026-08-01 04:16 UTCEPSS rescore
  37. 2026-07-30 16:28 UTCEPSS rescore
  38. 2026-07-30 01:30 UTCEPSS rescore
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-29 09:38 UTCEG score recompute
  41. 2026-07-29 09:38 UTCGHSA enrichment
  42. 2026-07-28 15:37 UTCEPSS rescore
  43. 2026-07-27 14:14 UTCEPSS rescore
  44. 2026-07-26 14:54 UTCEPSS rescore
  45. 2026-07-26 14:54 UTCEPSS rescore
  46. 2026-07-26 02:45 UTCEG score recompute
  47. 2026-07-26 02:45 UTCGHSA enrichment
  48. 2026-07-25 14:18 UTCEPSS rescore
  49. 2026-07-25 14:18 UTCEPSS rescore
  50. 2026-07-25 10:39 UTCNVD update
  51. 2026-07-25 09:22 UTCEG score recompute
  52. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64521?
CVE-2026-64521 is a publicly disclosed vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: pinctrl: meson: amlogic-a4: fix deadlock issue Accessing the pinconf-pins sysfs node may deadlock. pinconfpinsshow() holds pctldev->mutex, and the platform driver calls pinctrlfindgpiorangefrom_pin(), which tries to acquire the…
When was CVE-2026-64521 disclosed?
CVE-2026-64521 was first published in the National Vulnerability Database on July 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64521 actively exploited?
CVE-2026-64521 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 93.8% of all scored CVEs.
How do I remediate CVE-2026-64521?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64521, 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-64521

Explore →

Is Your Infrastructure Affected by CVE-2026-64521?

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