CVE-2026-68461

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

device property: initialize the remaining fields of fwnode_handle 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 uninitialized 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. While at it: initialize the remaining fields of struct fwnode_handle too just to be sure.

[ Fix typo in commit message. - Danilo ]

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (7)

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

device property: initialize the remaining fields of fwnode_handle in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

device property: initialize the remaining fields of fwnode_handle in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

device property: initialize the remaining fields of fwnode_handle in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

device property: initialize the remaining fields of fwnode_handle in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c86a1f930bb2ddb85f867b4736716e82a4a4683
generic

device property: initialize the remaining fields of fwnode_handle in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7eba000621fff223dd7bab484d48918c7c77a307
generic

device property: initialize the remaining fields of fwnode_handle in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/173b61c9276c7b3a5fbcc63ae7aafc897fee1e18
generic

device property: initialize the remaining fields of fwnode_handle in fwnode_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0198d579948322cda5178b9672d448375a32f947

Vendor Advisories for CVE-2026-68461(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 28× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 21:18 UTCGHSA enrichment
  3. 2026-08-20 08:56 UTCGHSA enrichment
  4. 2026-08-19 20:34 UTCEG score recompute
  5. 2026-08-19 20:34 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 08:11 UTCGHSA enrichment
  8. 2026-08-18 19:49 UTCEG score recompute
  9. 2026-08-18 19:49 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 07:26 UTCGHSA enrichment
  13. 2026-08-17 19:03 UTCEG score recompute
  14. 2026-08-17 19:03 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 06:30 UTCEG score recompute
  17. 2026-08-17 06:30 UTCGHSA enrichment
  18. 2026-08-17 06:01 UTCEG score recompute 7.80
  19. 2026-08-17 06:01 UTCGHSA enrichment
  20. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  21. 2026-08-17 05:35 UTCEG score recompute
  22. 2026-08-17 05:35 UTCGHSA enrichment
  23. 2026-08-17 05:24 UTCMITRE cvelistV5
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 3 more
  1. 2026-08-15 06:20 UTCNVD update
  2. 2026-08-15 06:20 UTCEG score recompute
  3. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68461?
CVE-2026-68461 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: device property: initialize the remaining fields of fwnodehandle in fwnodeinit() 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…
When was CVE-2026-68461 disclosed?
CVE-2026-68461 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68461 actively exploited?
CVE-2026-68461 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-68461?
CVE-2026-68461 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68461?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68461, 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

Explore the affected products and dependency analysis for CVE-2026-68461

Explore →

Is Your Infrastructure Affected by CVE-2026-68461?

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