Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68461device property: initialize the remaining fields of fwnode_handle in fwnode_init()

Description

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 ]

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-68461, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < 0198d579948322cda5178b9672d448375a32f947
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < 173b61c9276c7b3a5fbcc63ae7aafc897fee1e18
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < f0b4e1cc8ad76baf49d898727eb52e91a4ef0544
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < c8542b68ba6ef4f61072098893a3f5b71c569b6c
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < 9c86a1f930bb2ddb85f867b4736716e82a4a4683
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < c81e2af41de6a159837c7129a4fc444ac6e48046
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < 7eba000621fff223dd7bab484d48918c7c77a307
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68461 badge
[![CVE-2026-68461](https://cveledger.app/badge/CVE-2026-68461.svg)](https://cveledger.app/cve/CVE-2026-68461)

Record last updated .