Skip to main content
VulnerabilityPublished Updated

CVE-2026-68402: Linux kernel · Out-of-bounds Read

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High · fixed in ddf2773bcc8e49a43c561f22ec1e7924215d7947 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in ddf2773bcc8e49a43c561f22ec1e7924215d7947, cb8afea4655ff004fa7feee825d5c79783525383, 24154c172246ae3f0e69bb17c9111095685ceedc +5
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f7dacfb11475ba777e1e84ccec2e14b0ba5a17a3, < ddf2773bcc8e49a43c561f22ec1e7924215d7947
Fixed in
  • ddf2773bcc8e49a43c561f22ec1e7924215d7947
LinuxLinuxAffected
  • ≥ f7dacfb11475ba777e1e84ccec2e14b0ba5a17a3, < cb8afea4655ff004fa7feee825d5c79783525383
Fixed in
  • cb8afea4655ff004fa7feee825d5c79783525383
LinuxLinuxAffected
  • ≥ f7dacfb11475ba777e1e84ccec2e14b0ba5a17a3, < 24154c172246ae3f0e69bb17c9111095685ceedc
Fixed in
  • 24154c172246ae3f0e69bb17c9111095685ceedc
LinuxLinuxAffected
  • ≥ f7dacfb11475ba777e1e84ccec2e14b0ba5a17a3, < 521dd5fe6d12b0d3c275f919738dc3a07117f4a5
Fixed in
  • 521dd5fe6d12b0d3c275f919738dc3a07117f4a5
LinuxLinuxAffected
  • ≥ f7dacfb11475ba777e1e84ccec2e14b0ba5a17a3, < 84bd907361c56fbd5523eceb2682cb39da059bd5
Fixed in
  • 84bd907361c56fbd5523eceb2682cb39da059bd5
LinuxLinuxAffected
  • ≥ f7dacfb11475ba777e1e84ccec2e14b0ba5a17a3, < 20c308d9a57722801961f816395bf825f7bde6bc
Fixed in
  • 20c308d9a57722801961f816395bf825f7bde6bc

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.

References

Community reviews

Loading reviews…