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 ]
Published: 2026-08-15
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A firmware node allocated on the stack or heap with a non‑zeroing allocator and initialized by fwnode_init() leaves the fwnode_handle->secondary pointer uninitialized. When an API later dereferences this pointer, such as dev_to_swnode(), the kernel can crash or exhibit undefined behavior, leading to a denial‑of‑service condition.

Affected Systems

All Linux kernel releases that have not incorporated the commit that sets fwnode_handle->secondary to NULL and fully initializes the structure are potentially affected. The exact version range is not specified, so any kernel lacking this patch is at risk.

Risk and Exploitability

Because the vulnerability requires the creation or manipulation of a firmware node, it is likely limited to local exploitation by code running in kernel mode (for example, a malicious driver or firmware). The CVSS score of 7.8 indicates high severity, while the EPSS score is less than 1%, suggesting a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog, indicating no publicly known exploits yet. Nevertheless, a kernel crash is a high‑risk outcome, and the lack of zeroing makes the bug trivially exploitable in a local context.

Generated by OpenCVE AI on August 18, 2026 at 05:29 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the fwnode_init() fix that zeroes the secondary pointer and initializes all remaining fields.
  • If a kernel upgrade cannot be performed immediately, restrict or disable drivers and modules that create temporary firmware nodes to reduce the chance of a non‑zero‑ed node being allocated.
  • Monitor kernel logs (e.g., dmesg, /var/log/kern.log) for Oops or panic events that may indicate the vulnerability is triggered, and investigate any suspicious firmware node activity.
  • When developing custom kernel modules that allocate firmware nodes, use zero‑initializing allocation functions such as kzalloc and explicitly set the secondary field to NULL before use.

Generated by OpenCVE AI on August 18, 2026 at 05:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 18 Aug 2026 04:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-788

Tue, 18 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-824
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 17 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-788

Mon, 17 Aug 2026 08:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-457
CWE-665

Mon, 17 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Sat, 15 Aug 2026 08:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-457
CWE-665

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
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 ]
Title device property: initialize the remaining fields of fwnode_handle in fwnode_init()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:39:08.142Z

Reserved: 2026-07-30T09:28:09.395Z

Link: CVE-2026-68461

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:18:34.113

Modified: 2026-08-17T06:17:55.380

Link: CVE-2026-68461

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-68461 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T05:30:08Z

Weaknesses
  • CWE-824

    Access of Uninitialized Pointer