Linux Kernel up to 7.0.10 Device Property fwnode_init secondary stack-based overflow

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.8$0-$5k6.22

Summaryinfo

A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 7.0.10. This vulnerability affects the function fwnode_init of the component Device Property. This manipulation of the argument secondary causes stack-based overflow. This vulnerability is tracked as CVE-2026-64220. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.0.10. It has been declared as very critical. Affected by this vulnerability is the function fwnode_init of the component Device Property. The manipulation of the argument secondary with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-64220 since 07/19/2026. The exploitation appears to be easy. An attack has to be approached locally. Additional levels of successful authentication are required for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/24/2026).

Upgrading to version 5.15.209, 6.1.175, 6.6.142, 6.12.92, 6.18.34 or 7.0.11 eliminates this vulnerability. Applying the patch f0e211d6539fae800217c10797993b7592d6ab01/3f1024deeab3b5443c29b3de4fe475e87309b8fa/371f53925a6714d0aa35f1aefdffc3e8cd62f480/34bf74b1fd2e4a44e27821a329204caf09df2976/508fd8ab158abd04b7f7d0f707cd6d6c405df4ea/f59e686c778cb41b8f7aa8fab2afd6a01afb3d47/215c90ee656114f5e8c32408228d97082f8e0eef is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.2
VulDB Meta Temp Score: 7.8

VulDB Base Score: 8.2
VulDB Temp Score: 7.8
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Stack-based overflow
CWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.209/6.1.175/6.6.142/6.12.92/6.18.34/7.0.11
Patch: f0e211d6539fae800217c10797993b7592d6ab01/3f1024deeab3b5443c29b3de4fe475e87309b8fa/371f53925a6714d0aa35f1aefdffc3e8cd62f480/34bf74b1fd2e4a44e27821a329204caf09df2976/508fd8ab158abd04b7f7d0f707cd6d6c405df4ea/f59e686c778cb41b8f7aa8fab2afd6a01afb3d47/215c90ee656114f5e8c32408228d97082f8e0eef

Timelineinfo

07/19/2026 CVE reserved
07/24/2026 +5 days Advisory disclosed
07/24/2026 +0 days VulDB entry created
07/24/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64220 (🔒)
GCVE (CVE): GCVE-0-2026-64220
GCVE (VulDB): GCVE-100-382957

Entryinfo

Created: 07/24/2026 18:23
Changes: 07/24/2026 18:23 (60)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!