CVE-2026-64220

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:

device property: set fwnode->secondary to NULL in fwnode_init()

If a firmware node is allocated on the stack (for instance: temporary software node whose life-time we control) or on the heap - but using a non-zeroing allocation function - and initialized using fwnode_init(), its secondary pointer will contain uninitalized memory which likely will be neither NULL nor IS_ERR() and so may end up being dereferenced (for example: in dev_to_swnode()). Set fwnode->secondary to NULL on initialization.

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
2%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 11, 2026

Advisory Details (7)

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

device property: set fwnode->secondary to NULL in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

device property: set fwnode->secondary to NULL in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

device property: set fwnode->secondary to NULL in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/508fd8ab158abd04b7f7d0f707cd6d6c405df4ea
generic

device property: set fwnode->secondary to NULL in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f1024deeab3b5443c29b3de4fe475e87309b8fa
generic

device property: set fwnode->secondary to NULL in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/371f53925a6714d0aa35f1aefdffc3e8cd62f480
generic

device property: set fwnode->secondary to NULL in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34bf74b1fd2e4a44e27821a329204caf09df2976
generic

device property: set fwnode->secondary to NULL in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/215c90ee656114f5e8c32408228d97082f8e0eef

Vendor Advisories for CVE-2026-64220(1)

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

Patch Availability(8)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
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

(8)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-64220?
CVE-2026-64220 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: device property: set fwnode->secondary to NULL in fwnode_init() If a firmware node is allocated on the stack (for instance: temporary software node whose life-time we control) or on the heap - but using a non-zeroing allocation…
When was CVE-2026-64220 disclosed?
CVE-2026-64220 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64220 actively exploited?
CVE-2026-64220 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 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64220?
CVE-2026-64220 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64220?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64220, 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-64220

Explore →

Is Your Infrastructure Affected by CVE-2026-64220?

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