Linux: Improper Validation of Array Index
CVE-2025-40114 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 7a40b52d4442178bee0cf1c36bc450ab951cef0f, 18a08b5632809faa671279b3cd27d5f96cc5a3f0, 9c40a68b7f97fa487e6c7e67fcf4f846a1f96692 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.26% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 7a40b52d4442178bee0cf1c36bc450ab951cef0f or 18a08b5632809faa671279b3cd27d5f96cc5a3f0 or 9c40a68b7f97fa487e6c7e67fcf4f846a1f96692 or ee735aa33db16c1fb5ebccbaf84ad38f5583f3cc, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.23 or 6.13.11 or 6.14.2, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 3b82f43238aecd73464aeacc9c73407079511533 up to, but not including, 7a40b52d4442178bee0cf1c36bc450ab951cef0f; 3b82f43238aecd73464aeacc9c73407079511533 up to, but not including, 18a08b5632809faa671279b3cd27d5f96cc5a3f0; 3b82f43238aecd73464aeacc9c73407079511533 up to, but not including, 9c40a68b7f97fa487e6c7e67fcf4f846a1f96692; 3b82f43238aecd73464aeacc9c73407079511533 up to, but not including, ee735aa33db16c1fb5ebccbaf84ad38f5583f3cc; 6.8 | 7a40b52d4442178bee0cf1c36bc450ab951cef0f, 18a08b5632809faa671279b3cd27d5f96cc5a3f0, 9c40a68b7f97fa487e6c7e67fcf4f846a1f96692, ee735aa33db16c1fb5ebccbaf84ad38f5583f3cc |
| Linux | Linux Kernel | 6.8 up to, but not including, 6.12.23; 6.13 up to, but not including, 6.13.11; 6.14 up to, but not including, 6.14.2 | 6.12.23, 6.13.11, 6.14.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 NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: iio: light: Add check for array bounds in veml6075_read_int_time_ms The array contains only 5 elements, but the index calculated by veml6075_read_int_time_index can range from 0 to 7, which could lead to out-of-bounds access. The check prevents this issue. Coverity Issue CID 1574309: (#1 of 1): Out-of-bounds read (OVERRUN) overrun-local: Overrunning array veml6075_it_ms of 5 4-byte elements at element index 7 (byte offset 31) using index int_index (which evaluates to 7) This is hardening against potentially broken hardware. Good to have but not necessary to backport.
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
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Improper Validation of Array Index vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.