CyberSecBulletin
CVE-2026-53386NVD status: Analyzed

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2026-53386 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 d5793975fc3b1780ba576812158ef22e3104e60e, d08d82d83ed45fd8c001a9df66ad7ebb86c9d6c6, abe0854e356b1bb814393ca884cb42b3eb12ce10 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.18% 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 d5793975fc3b1780ba576812158ef22e3104e60e or d08d82d83ed45fd8c001a9df66ad7ebb86c9d6c6 or abe0854e356b1bb814393ca884cb42b3eb12ce10 or abd776ded3e256889610595290f6ca46cb6e91ab, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.12.95 or 6.18.37 or 7.0.14 or 7.1.2, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux00ef7708fa6073a84f6898fdcdfe965d903b0378 up to, but not including, d5793975fc3b1780ba576812158ef22e3104e60e; 00ef7708fa6073a84f6898fdcdfe965d903b0378 up to, but not including, d08d82d83ed45fd8c001a9df66ad7ebb86c9d6c6; 00ef7708fa6073a84f6898fdcdfe965d903b0378 up to, but not including, abe0854e356b1bb814393ca884cb42b3eb12ce10; 00ef7708fa6073a84f6898fdcdfe965d903b0378 up to, but not including, abd776ded3e256889610595290f6ca46cb6e91ab; 00ef7708fa6073a84f6898fdcdfe965d903b0378 up to, but not including, 95e8a48d7a85d4226934020e57815a3316d3a14b; 6.9d5793975fc3b1780ba576812158ef22e3104e60e, d08d82d83ed45fd8c001a9df66ad7ebb86c9d6c6, abe0854e356b1bb814393ca884cb42b3eb12ce10, abd776ded3e256889610595290f6ca46cb6e91ab, 95e8a48d7a85d4226934020e57815a3316d3a14b
LinuxLinux Kernel6.9 up to, but not including, 6.12.95; 6.13 up to, but not including, 6.18.37; 6.19 up to, but not including, 7.0.14; 7.1 up to, but not including, 7.1.26.12.95, 6.18.37, 7.0.14, 7.1.2

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 CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: iio: adc: ti-ads1298: add bounds check to pga_settings index ads1298_pga_settings has 7 elements but ADS1298_MASK_CH_PGA can yield values 0-7. If it yields a value >= 7, this causes an out-of-bounds array access. Add a bounds check and return -EINVAL if the index is out of range. Note that the remaining value b111 is reserved so should not be seen in a correctly functioning system.

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.