Local system crash via uninitialized secondary pointer
Published Jul 24, 2026 · Updated Jul 24, 2026
Use of an uninitialized pointer in Linux Kernel allows local users to crash the system through firmware-node handling. fwnode_init leaves fwnode->secondary unchanged for stack objects or memory from non-zeroing allocators, so dev_to_swnode can dereference an indeterminate address. Reaching the flaw requires local low-privileged access and a path that creates such a firmware node; the documented consequence is a system crash.
Summary
What happened
Use of an uninitialized pointer in Linux Kernel allows local users to crash the system through firmware-node handling. fwnode_init leaves fwnode->secondary unchanged for stack objects or memory from non-zeroing allocators, so dev_to_swnode can dereference an indeterminate address. Reaching the flaw requires local low-privileged access and a path that creates such a firmware node; the documented consequence is a system crash.
The record
- CVE
- CVE-2026-64220
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-908, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 24, 2026CVE publishedPublication date reported by the CVE source.
- Jul 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=01bb86b380a306bd937c96da36f66429f3362137 <215c90ee656114f5e8c32408228d97082f8e0eef
- Affected versionversion=01bb86b380a306bd937c96da36f66429f3362137 <34bf74b1fd2e4a44e27821a329204caf09df2976
- Affected versionversion=01bb86b380a306bd937c96da36f66429f3362137 <371f53925a6714d0aa35f1aefdffc3e8cd62f480
- Affected versionversion=01bb86b380a306bd937c96da36f66429f3362137 <3f1024deeab3b5443c29b3de4fe475e87309b8fa
- Affected versionversion=01bb86b380a306bd937c96da36f66429f3362137 <508fd8ab158abd04b7f7d0f707cd6d6c405df4ea
- Affected versionversion=01bb86b380a306bd937c96da36f66429f3362137 <f0e211d6539fae800217c10797993b7592d6ab01
- Affected versionversion=01bb86b380a306bd937c96da36f66429f3362137 <f59e686c778cb41b8f7aa8fab2afd6a01afb3d47
- Affected versionversion=5.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo