0.0
NA
CVE-2026-64220
device 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.

INFO

Published Date :

July 24, 2026, 4:16 p.m.

Last Modified :

July 24, 2026, 4:16 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-64220 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Initialize firmware node secondary pointer to NULL to prevent dereferencing uninitialized memory.
  • Ensure firmware nodes are properly initialized.
  • Set fwnode->secondary to NULL during initialization.
  • Use zeroing allocation functions for firmware nodes.
  • Apply kernel patches that fix this issue.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-64220 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-64220 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-64220 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-64220 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 24, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '01bb86b380a306bd937c96da36f66429f3362137', 'lessThan': 'f0e211d6539fae800217c10797993b7592d6ab01', 'versionType': 'git'}, {'status': 'affected', 'version': '01bb86b380a306bd937c96da36f66429f3362137', 'lessThan': '3f1024deeab3b5443c29b3de4fe475e87309b8fa', 'versionType': 'git'}, {'status': 'affected', 'version': '01bb86b380a306bd937c96da36f66429f3362137', 'lessThan': '371f53925a6714d0aa35f1aefdffc3e8cd62f480', 'versionType': 'git'}, {'status': 'affected', 'version': '01bb86b380a306bd937c96da36f66429f3362137', 'lessThan': '34bf74b1fd2e4a44e27821a329204caf09df2976', 'versionType': 'git'}, {'status': 'affected', 'version': '01bb86b380a306bd937c96da36f66429f3362137', 'lessThan': '508fd8ab158abd04b7f7d0f707cd6d6c405df4ea', 'versionType': 'git'}, {'status': 'affected', 'version': '01bb86b380a306bd937c96da36f66429f3362137', 'lessThan': 'f59e686c778cb41b8f7aa8fab2afd6a01afb3d47', 'versionType': 'git'}, {'status': 'affected', 'version': '01bb86b380a306bd937c96da36f66429f3362137', 'lessThan': '215c90ee656114f5e8c32408228d97082f8e0eef', 'versionType': 'git'}], 'programFiles': ['include/linux/fwnode.h'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.11'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.11', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.15.209', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.175', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.142', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.92', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.34', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.11', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['include/linux/fwnode.h'], 'defaultStatus': 'affected'}]
    Added 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.
    Added Reference https://git.kernel.org/stable/c/215c90ee656114f5e8c32408228d97082f8e0eef
    Added Reference https://git.kernel.org/stable/c/34bf74b1fd2e4a44e27821a329204caf09df2976
    Added Reference https://git.kernel.org/stable/c/371f53925a6714d0aa35f1aefdffc3e8cd62f480
    Added Reference https://git.kernel.org/stable/c/3f1024deeab3b5443c29b3de4fe475e87309b8fa
    Added Reference https://git.kernel.org/stable/c/508fd8ab158abd04b7f7d0f707cd6d6c405df4ea
    Added Reference https://git.kernel.org/stable/c/f0e211d6539fae800217c10797993b7592d6ab01
    Added Reference https://git.kernel.org/stable/c/f59e686c778cb41b8f7aa8fab2afd6a01afb3d47
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.