CVE-2026-64220
Received Received - Intake

Linux Kernel NULL Pointer Dereference in Device Property Handling

Publication date: 2026-07-24

Last updated on: 2026-07-24

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-24
Last Modified
2026-07-24
Generated
2026-07-24
AI Q&A
2026-07-24
EPSS Evaluated
N/A
NVD
CVE-2026-64220
EUVD
EUVD-2026-48628

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves uninitialized memory in firmware nodes. When a firmware node is created on the stack or heap using a non-zeroing allocation function and initialized with fwnode_init(), its secondary pointer may contain uninitialized memory. This could lead to dereferencing invalid or unexpected values, potentially causing system instability or crashes.

Detection Guidance

This vulnerability requires kernel code inspection to detect. Check if your kernel uses fwnode_init() on stack or non-zeroing heap allocations without setting secondary to NULL. Review kernel patches or compile logs for fixes related to this issue.

Impact Analysis

If exploited, this vulnerability could allow attackers to cause denial-of-service conditions, system crashes, or unexpected behavior by manipulating uninitialized memory in firmware nodes. Systems relying on firmware nodes for device properties may be particularly affected.

Compliance Impact

The vulnerability involves uninitialized memory in firmware node initialization, which could lead to memory corruption or unintended behavior. This may impact compliance with standards like GDPR or HIPAA if it affects data integrity or security in systems handling sensitive information. However, specific compliance impacts are not detailed in the provided context.

Mitigation Strategies

Apply the latest kernel patches from your Linux distribution. If patches are unavailable, recompile the kernel with the fix: ensure fwnode_init() sets secondary to NULL. Monitor vendor advisories for updates.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64220. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart