Linux: Improper Validation of Array Index
CVE-2024-38562 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 ed74398642fcb19f6ff385c35a7d512c6663e17b, 4e2a5566462b53db7d4c4722da86eedf0b8f546c, 8fa4d56564ee7cc2ee348258d88efe191d70dd7f 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.24% 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 ed74398642fcb19f6ff385c35a7d512c6663e17b or 4e2a5566462b53db7d4c4722da86eedf0b8f546c or 8fa4d56564ee7cc2ee348258d88efe191d70dd7f or 838c7b8f1f278404d9d684c34a8cb26dc41aaaa1, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.33 or 6.8.12 or 6.9.3, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | e3eac9f32ec04112b39e01b574ac739382469bf9 up to, but not including, ed74398642fcb19f6ff385c35a7d512c6663e17b; e3eac9f32ec04112b39e01b574ac739382469bf9 up to, but not including, 4e2a5566462b53db7d4c4722da86eedf0b8f546c; e3eac9f32ec04112b39e01b574ac739382469bf9 up to, but not including, 8fa4d56564ee7cc2ee348258d88efe191d70dd7f; e3eac9f32ec04112b39e01b574ac739382469bf9 up to, but not including, 838c7b8f1f278404d9d684c34a8cb26dc41aaaa1; 6.6 | ed74398642fcb19f6ff385c35a7d512c6663e17b, 4e2a5566462b53db7d4c4722da86eedf0b8f546c, 8fa4d56564ee7cc2ee348258d88efe191d70dd7f, 838c7b8f1f278404d9d684c34a8cb26dc41aaaa1 |
| Linux | Linux Kernel | 6.6 up to, but not including, 6.6.33; 6.7 up to, but not including, 6.8.12; 6.9 up to, but not including, 6.9.3 | 6.6.33, 6.8.12, 6.9.3 |
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: wifi: nl80211: Avoid address calculations via out of bounds array indexing Before request->channels[] can be used, request->n_channels must be set. Additionally, address calculations for memory after the "channels" array need to be calculated from the allocation base ("request") rather than via the first "out of bounds" index of "channels", otherwise run-time bounds checking will throw a warning.
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.