CVE-2026-68461: device property: initialize the remaining fields of fwnode_handle in fwnode_init()
In the Linux kernel, the following vulnerability has been resolved:
device property: initialize the remaining fields of fwnodehandle in fwnodeinit()
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 fwnodeinit(), its secondary pointer will contain uninitialized memory which likely will be neither NULL nor ISERR() and so may end up being dereferenced (for example: in devtoswnode()). Set fwnode->secondary to NULL on initialization. While at it: initialize the remaining fields of struct fwnodehandle too just to be sure.
[ Fix typo in commit message. - Danilo ]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Set fwnode->secondary to NULL (and in fwnode_init(), initialize the remaining fields of struct fwnode_handle / fwnode_handle too) to prevent uninitialized memory from being dereferenced.
Linux kernel fwnode_handle / firmware node handling fwnode->secondary = NULL
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68461?
CVE-2026-68461 has a risk rating of 34, indicating a medium severity level.
How do I fix CVE-2026-68461?
To fix CVE-2026-68461, update your Linux kernel to the latest version where this vulnerability has been resolved.
What systems are affected by CVE-2026-68461?
CVE-2026-68461 affects the Linux kernel where device properties are managed.
What are the potential impacts of CVE-2026-68461?
The potential impact of CVE-2026-68461 includes security risks related to improper initialization of firmware nodes.
Is there a workaround for CVE-2026-68461 before applying a patch?
While applying a patch is the recommended approach, minimizing the use of stack-allocated firmware nodes may help mitigate risks.