CVE-2026-64238

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-24. 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:

gpio: shared: fix deadlock on shared proxy's parent removal

Commit 710abda58055 ("gpio: shared: call gpio_chip::of_xlate() if set") used the mutex embedded in struct gpio_shared_entry to protect the offset field which now can be modified after assignment. The critical section however is too wide and introduced a potential deadlock on the removal of the shared GPIO proxy's parent.

Make the critical section shorter - only protect the offset when it's being read.

While at it: mention the fact that the entry lock is now also used to protect against concurrent access to the offset field in the structure's documentation.

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 24, 2026

Last Modified

August 13, 2026

Advisory Details (2)

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

gpio: shared: fix deadlock on shared proxy's parent removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a554dfcd30dd5e41d1d67387b3bb85cea83e12e1
generic

gpio: shared: fix deadlock on shared proxy's parent removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a1b836607304f71051f9f9dcccf8b5097b86a1fb

Vendor Advisories for CVE-2026-64238(1)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-26ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-08-26ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-26ubuntu

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

(3)

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

Frequently asked(5)

What is CVE-2026-64238?
CVE-2026-64238 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: gpio: shared: fix deadlock on shared proxy's parent removal Commit 710abda58055 ("gpio: shared: call gpiochip::ofxlate() if set") used the mutex embedded in struct gpiosharedentry to protect the offset field which now can be…
When was CVE-2026-64238 disclosed?
CVE-2026-64238 was first published in the National Vulnerability Database on July 24, 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-64238 actively exploited?
CVE-2026-64238 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-64238?
CVE-2026-64238 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64238?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64238, 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-64238

Explore →

Is Your Infrastructure Affected by CVE-2026-64238?

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

Start Free Scan →Browse All CVEs