Linux Kernel up to 7.1.4 Device Property fwnode_init uninitialized pointer

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.
9.5$0-$5k0.47+

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.1.4. It has been rated as very critical. The affected element is the function fwnode_init of the component Device Property. This manipulation causes uninitialized pointer. This vulnerability is tracked as CVE-2026-68461. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability classified as very critical was found in Linux Kernel up to 7.1.4. Affected by this vulnerability is the function fwnode_init of the component Device Property. The manipulation with an unknown input leads to a uninitialized pointer vulnerability. The CWE definition for the vulnerability is CWE-824. The product accesses or uses a pointer that has not been initialized. 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: initialize the remaining fields of fwnode_handle 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 uninitialized 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. While at it: initialize the remaining fields of struct fwnode_handle too just to be sure. [ Fix typo in commit message. - Danilo ]

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-68461 since 07/30/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/15/2026).

Upgrading to version 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.5 or 7.2-rc1 eliminates this vulnerability. Applying the patch 0198d579948322cda5178b9672d448375a32f947/173b61c9276c7b3a5fbcc63ae7aafc897fee1e18/f0b4e1cc8ad76baf49d898727eb52e91a4ef0544/c8542b68ba6ef4f61072098893a3f5b71c569b6c/9c86a1f930bb2ddb85f867b4736716e82a4a4683/c81e2af41de6a159837c7129a4fc444ac6e48046/7eba000621fff223dd7bab484d48918c7c77a307 is able to eliminate this problem.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 9.5

VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Uninitialized pointer
CWE: CWE-824 / CWE-908
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

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.212/6.1.178/6.6.145/6.12.96/6.18.39/7.1.5/7.2-rc1
Patch: 0198d579948322cda5178b9672d448375a32f947/173b61c9276c7b3a5fbcc63ae7aafc897fee1e18/f0b4e1cc8ad76baf49d898727eb52e91a4ef0544/c8542b68ba6ef4f61072098893a3f5b71c569b6c/9c86a1f930bb2ddb85f867b4736716e82a4a4683/c81e2af41de6a159837c7129a4fc444ac6e48046/7eba000621fff223dd7bab484d48918c7c77a307

Timelineinfo

07/30/2026 CVE reserved
08/15/2026 +16 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-68461 (🔒)
GCVE (CVE): GCVE-0-2026-68461
GCVE (VulDB): GCVE-100-390187

Entryinfo

Created: 08/15/2026 08:11
Changes: 08/15/2026 08:11 (59)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!