CyberSecBulletin
CVE-2026-46163NVD status: Modified

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2026-46163 is a high-severity improper validation of array index vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions a92bd0503df2488f2cc040f329ebccff1c1934cb, df805c1d085b7a96077f0964185764c87060950d, 4242db36de99de734cc1f60e5edd86cda7e598c6 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.13% 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 a92bd0503df2488f2cc040f329ebccff1c1934cb or df805c1d085b7a96077f0964185764c87060950d or 4242db36de99de734cc1f60e5edd86cda7e598c6 or 1baaeb6adecb9691748c0253dab6ddd19a2b4e9e, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.258 or 5.15.209 or 6.1.175 or 6.6.140, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux75388acd0cd827dc1498043daa7d1c760902cd67 up to, but not including, a92bd0503df2488f2cc040f329ebccff1c1934cb; 75388acd0cd827dc1498043daa7d1c760902cd67 up to, but not including, df805c1d085b7a96077f0964185764c87060950d; 75388acd0cd827dc1498043daa7d1c760902cd67 up to, but not including, 4242db36de99de734cc1f60e5edd86cda7e598c6; 75388acd0cd827dc1498043daa7d1c760902cd67 up to, but not including, 1baaeb6adecb9691748c0253dab6ddd19a2b4e9e; 75388acd0cd827dc1498043daa7d1c760902cd67 up to, but not including, 6ee946077607d7783ae6709a899213fc4fe08f35; 75388acd0cd827dc1498043daa7d1c760902cd67 up to, but not including, 9d1bc155802943e92c57a5fb923d23edfbf0b525; 75388acd0cd827dc1498043daa7d1c760902cd67 up to, but not including, fdd4e51979f42ca8b1ab7e6176b607e1caabf2a5; 75388acd0cd827dc1498043daa7d1c760902cd67 up to, but not including, a035766f970bde2d4298346a31a80685be5c0205; and 1 more rangesa92bd0503df2488f2cc040f329ebccff1c1934cb, df805c1d085b7a96077f0964185764c87060950d, 4242db36de99de734cc1f60e5edd86cda7e598c6, 1baaeb6adecb9691748c0253dab6ddd19a2b4e9e, 6ee946077607d7783ae6709a899213fc4fe08f35, 9d1bc155802943e92c57a5fb923d23edfbf0b525
SiemensSIMATIC S7-1500 TM MFP - GNU/Linux subsystemall versionsNot stated
LinuxLinux Kernel2.6.24 up to, but not including, 5.10.258; 5.11 up to, but not including, 5.15.209; 5.16 up to, but not including, 6.1.175; 6.2 up to, but not including, 6.6.140; 6.7 up to, but not including, 6.12.88; 6.13 up to, but not including, 6.18.30; 6.19 up to, but not including, 7.0.7; 7.15.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30

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
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Official description

In the Linux kernel, the following vulnerability has been resolved: wifi: b43legacy: enforce bounds check on firmware key index in RX path Same fix as b43: the firmware-controlled key index in b43legacy_rx() can exceed dev->max_nr_keys. The existing B43legacy_WARN_ON is non-enforcing in production builds, allowing an out-of-bounds read of dev->key[]. Make the check enforcing by dropping the frame for invalid indices.

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.