Linux: Improper Validation of Array Index
CVE-2026-45839 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 c8e49b79c4b48bd687706ff6e9c82638dc81ef80, a9e777f856cd2f1efc106afc7bf21aef868509d5, 669349b4612c26b3d7aacfa99d7174681bd19223 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.14% 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 c8e49b79c4b48bd687706ff6e9c82638dc81ef80 or a9e777f856cd2f1efc106afc7bf21aef868509d5 or 669349b4612c26b3d7aacfa99d7174681bd19223 or 3ff85ae79e1a74baeb916b78a63d821f6d19a994, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.15.209 or 6.1.175 or 6.6.141 or 6.12.91, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | ddc7c3042614e273044f698d2beab25cc3842d45 up to, but not including, c8e49b79c4b48bd687706ff6e9c82638dc81ef80; ddc7c3042614e273044f698d2beab25cc3842d45 up to, but not including, a9e777f856cd2f1efc106afc7bf21aef868509d5; ddc7c3042614e273044f698d2beab25cc3842d45 up to, but not including, 669349b4612c26b3d7aacfa99d7174681bd19223; ddc7c3042614e273044f698d2beab25cc3842d45 up to, but not including, 3ff85ae79e1a74baeb916b78a63d821f6d19a994; ddc7c3042614e273044f698d2beab25cc3842d45 up to, but not including, 36a9012f76ba8d9189ae56a1f8bb7c87c07a1f3a; ddc7c3042614e273044f698d2beab25cc3842d45 up to, but not including, 76f2ebaf79a9ae6d0737b87f045fe769e425d78f; ddc7c3042614e273044f698d2beab25cc3842d45 up to, but not including, 99dbab7b5a12d8f58d5b0aa2f7a1fe656a70f4b2; ddc7c3042614e273044f698d2beab25cc3842d45 up to, but not including, 1c22483a2c4bbf747787f328392ca3e68619c4dc; and 1 more ranges | c8e49b79c4b48bd687706ff6e9c82638dc81ef80, a9e777f856cd2f1efc106afc7bf21aef868509d5, 669349b4612c26b3d7aacfa99d7174681bd19223, 3ff85ae79e1a74baeb916b78a63d821f6d19a994, 36a9012f76ba8d9189ae56a1f8bb7c87c07a1f3a, 76f2ebaf79a9ae6d0737b87f045fe769e425d78f |
| Siemens | SIMATIC S7-1500 TM MFP - GNU/Linux subsystem | all versions | Not stated |
| Linux | Linux Kernel | 5.4 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.141; 6.7 up to, but not including, 6.12.91; 6.13 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.10 | 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10 |
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: bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec() CO-RE accessor strings are colon-separated indices that describe a path from a root BTF type to a target field, e.g. "0:1:2" walks through nested struct members. bpf_core_parse_spec() parses each component with sscanf("%d"), so negative values like -1 are silently accepted. The subsequent bounds checks (access_idx >= btf_vlen(t)) only guard the upper bound and always pass for negative values because C integer promotion converts the __u16 btf_vlen result to int, making the comparison (int)(-1) >= (int)(N) false for any positive N. When -1 reaches btf_member_bit_offset() it gets cast to u32 0xffffffff, producing an out-of-bounds read far past the members array. A crafted BPF program with a negative CO-RE accessor on any struct that exists in vmlinux BTF (e.g. task_struct) crashes the kernel deterministically during BPF_PROG_LOAD on any system with CONFIG_DEBUG_INFO_BTF=y (default on major distributions). The bug is reachable with CAP_BPF: BUG: unable to handle page fault for address: ffffed11818b6626 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 85 Comm: poc Not tainted 7.0.0-rc6 #18 PREEMPT(full) RIP: 0010:bpf_core_parse_spec (tools/lib/bpf/relo_core.c:354) RAX: 00000000ffffffff Call Trace: <TASK> bpf_core_calc_relo_insn (tools/lib/bpf/relo_core.c:1321) bpf_core_apply (kernel/bpf/btf.c:9507) check_core_relo (kernel/bpf/verifier.c:19475) bpf_check (kernel/bpf/verifier.c:26031) bpf_prog_load (kernel/bpf/syscall.c:3089) __sys_bpf (kernel/bpf/syscall.c:6228) </TASK> CO-RE accessor indices are inherently non-negative (struct member index, array element index, or enumerator index), so reject them immediately after parsing.
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.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/1c22483a2c4bbf747787f328392ca3e68619c4dc
- git.kernel.org/stable/c/36a9012f76ba8d9189ae56a1f8bb7c87c07a1f3a
- git.kernel.org/stable/c/3ff85ae79e1a74baeb916b78a63d821f6d19a994
- git.kernel.org/stable/c/669349b4612c26b3d7aacfa99d7174681bd19223
- git.kernel.org/stable/c/76f2ebaf79a9ae6d0737b87f045fe769e425d78f
- git.kernel.org/stable/c/99dbab7b5a12d8f58d5b0aa2f7a1fe656a70f4b2
- git.kernel.org/stable/c/a9e777f856cd2f1efc106afc7bf21aef868509d5
Other references
Recent Improper Validation of Array Index vulnerabilities
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
Spotted an error? Tell us.