CyberSecBulletin
CVE-2026-23246NVD status: Analyzed

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2026-23246 is a high-severity improper validation of array index vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions 650981e718e68005ca2760a6358134b8a98ebea4, bfde158d5d1322c0c2df398a8d1ccce04943be2e, f35ceec54d48e227fa46f8f97fd100a77b8eab15 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.31% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 650981e718e68005ca2760a6358134b8a98ebea4 or bfde158d5d1322c0c2df398a8d1ccce04943be2e or f35ceec54d48e227fa46f8f97fd100a77b8eab15 or d58d71c2167601762351962b9604808d3be94400, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.130 or 6.12.77 or 6.18.17 or 6.19.7, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux8eb8dd2ffbbb6b0b8843b66754ee9f129f1b2d6c up to, but not including, 650981e718e68005ca2760a6358134b8a98ebea4; 8eb8dd2ffbbb6b0b8843b66754ee9f129f1b2d6c up to, but not including, bfde158d5d1322c0c2df398a8d1ccce04943be2e; 8eb8dd2ffbbb6b0b8843b66754ee9f129f1b2d6c up to, but not including, f35ceec54d48e227fa46f8f97fd100a77b8eab15; 8eb8dd2ffbbb6b0b8843b66754ee9f129f1b2d6c up to, but not including, d58d71c2167601762351962b9604808d3be94400; 8eb8dd2ffbbb6b0b8843b66754ee9f129f1b2d6c up to, but not including, 162d331d833dc73a3e905a24c44dd33732af1fc5; 6.5650981e718e68005ca2760a6358134b8a98ebea4, bfde158d5d1322c0c2df398a8d1ccce04943be2e, f35ceec54d48e227fa46f8f97fd100a77b8eab15, d58d71c2167601762351962b9604808d3be94400, 162d331d833dc73a3e905a24c44dd33732af1fc5
LinuxLinux Kernel6.5.1 up to, but not including, 6.6.130; 6.7 up to, but not including, 6.12.77; 6.13 up to, but not including, 6.18.17; 6.19 up to, but not including, 6.19.7; 6.5; 7.06.6.130, 6.12.77, 6.18.17, 6.19.7

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration link_id is taken from the ML Reconfiguration element (control & 0x000f), so it can be 0..15. link_removal_timeout[] has IEEE80211_MLD_MAX_NUM_LINKS (15) elements, so index 15 is out-of-bounds. Skip subelements with link_id >= IEEE80211_MLD_MAX_NUM_LINKS to avoid a stack out-of-bounds write.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Validation of Array Index

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

How developers prevent this class of flaw

  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, Ada allows the programmer to constrain the values of a variable and languages such as Java and Ruby will allow the programmer to handle exceptions when an out-of-bounds index is accessed.
  • Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND.

More Improper Validation of Array Index vulnerabilities (CWE-129)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Improper Validation of Array Index vulnerabilities

Spotted an error? Tell us.