CVE-2026-68402

wifi: cfg80211: bound element ID read when checking non-inheritance

HIGH
7.1
CVSS Score
Published: August 10, 2026 at 12:04 PM UTC
Updated: October 19, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: bound element ID read when checking non-inheritance cfg80211_is_element_inherited() reads the first data octet of the candidate element (id = elem->data[0]) to look it up in an extension non-inheritance list. It does so after testing elem->id, but without verifying that the element actually has a data octet. A zero-length extension element (WLAN_EID_EXTENSION with length 0) therefore makes it read one octet past the end of the element. _ieee802_11_parse_elems_full() runs this check for every element of a frame once a non-inheritance context exists -- e.g. while parsing a per-STA profile of a Multi-Link element in a (re)association response, or a non-transmitted BSS profile -- so a crafted frame from an AP can trigger a one-octet slab-out-of-bounds read during element parsing: BUG: KASAN: slab-out-of-bounds in cfg80211_is_element_inherited Read of size 1 ... in net/wireless/scan.c Return early (treat the element as inherited) when an extension element carries no data, mirroring the existing handling of empty ID lists. The bug was found by fuzzing ieee802_11_parse_elems_full() under KASAN.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.2f7dacfb11475ba777e1e84ccec2e14b0ba5a17a3
Vendor states this is fixed in 11ac7a5e75f5132f1778e0c60981d30dc29fb869 (fixed)
Vendor states this is fixed in 20c308d9a57722801961f816395bf825f7bde6bc (fixed)
Vendor states this is fixed in 24154c172246ae3f0e69bb17c9111095685ceedc (fixed)
Vendor states this is fixed in 2d31ebb26a14f103c9cdc5287fb20cb2d4bde901 (fixed)
Vendor states this is fixed in 521dd5fe6d12b0d3c275f919738dc3a07117f4a5 (fixed)
Vendor states this is fixed in 84bd907361c56fbd5523eceb2682cb39da059bd5 (fixed)
Vendor states this is fixed in cb8afea4655ff004fa7feee825d5c79783525383 (fixed)
Vendor states this is fixed in ddf2773bcc8e49a43c561f22ec1e7924215d7947 (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.2 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card