CVE-2026-68461

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM 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 — 4 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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (7)

Auto-updated Aug 17, 2026
Patch available.
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.

Patch Availability(12)

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 rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)
  • every version up to 6.12.96-1: fixed in 6.12.96-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 27× in last 7d / 132× 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 216 total refreshes for this CVE.

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

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 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.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68461?
CVE-2026-68461 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68461?
A fix for CVE-2026-68461 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68461 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.