cve.bz

CVE-2026-68461 linux linux: Improper Initialization

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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 ]

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-665 Improper Initialization
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.15.212
  • Linux Linux: fixed in 6.1.178
  • Linux Linux: fixed in 6.6.145
  • Linux Linux: fixed in 6.12.96
  • Linux Linux: fixed in 6.18.39
  • Linux Linux: fixed in 7.1.5
  • Linux Linux: fixed in 7.2
  • Debian, Ubuntu, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-68461 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-68461?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-68461?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-68461 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.11 and later

Fixed in

ProductRelease lineFixed in
Linux5.155.15.212
Linux6.16.1.178
Linux6.66.6.145
Linux6.126.12.96
Linux6.186.18.39
Linux7.17.1.5
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.180-1DEBIAN-CVE-2026-68461
Debian13linux6.12.96-1DEBIAN-CVE-2026-68461
Debian14linux7.1.5-1DEBIAN-CVE-2026-68461
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-68461
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-68461
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-68461
Ubuntu22.04:LTSlinux5.15.0-198.208UBUNTU-CVE-2026-68461 USN-8875-1
Ubuntu22.04:LTSlinux-aws5.15.0-1117.124UBUNTU-CVE-2026-68461 USN-8875-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-68461 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1123.132UBUNTU-CVE-2026-68461 USN-8875-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-68461 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1122.131UBUNTU-CVE-2026-68461 USN-8876-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-68461 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1118.128UBUNTU-CVE-2026-68461 USN-8877-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-68461 USN-9024-1
74 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquita23linux-lts6.1.182-r0BELL-CVE-2026-68461
Alpaquita25linux-lts6.12.103-r0BELL-CVE-2026-68461
Alpaquitastreamlinux-lts6.18.43-r0BELL-CVE-2026-68461

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as having Moderate impact because exploitation is constrained to local environments and results in a kernel crash without directly compromising system confidentiality or integrity. In standard Red Hat Enterprise Linux deployments, an attacker requires local access to trigger operations that allocate uninitialized firmware node structures. Because the defect leads to an invalid pointer dereference within kernel device management rather than arbitrary code execution or privilege escalation, the primary risk is limited to a local denial of service.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-68461.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON