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-64220device property: set fwnode->secondary to NULL in fwnode_init()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 4 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-64220, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < f0e211d6539fae800217c10797993b7592d6ab01
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < 3f1024deeab3b5443c29b3de4fe475e87309b8fa
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < 371f53925a6714d0aa35f1aefdffc3e8cd62f480
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < 34bf74b1fd2e4a44e27821a329204caf09df2976
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < 508fd8ab158abd04b7f7d0f707cd6d6c405df4ea
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < f59e686c778cb41b8f7aa8fab2afd6a01afb3d47
    • affected 01bb86b380a306bd937c96da36f66429f3362137 – < 215c90ee656114f5e8c32408228d97082f8e0eef
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.34 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .