Linux: Improper Validation of Array Index
CVE-2024-49931 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 d0e4274d9dc9f8409d56d622cd3ecf7b6fd49e2f, a4aef827a41cdaf6201bbaf773c1eae4e20e967b, ad791e3ec60cb66c1e4dc121ffbf872df312427d 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 d0e4274d9dc9f8409d56d622cd3ecf7b6fd49e2f or a4aef827a41cdaf6201bbaf773c1eae4e20e967b or ad791e3ec60cb66c1e4dc121ffbf872df312427d or e106b7ad13c1d246adaa57df73edb8f8b8acb240, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.55 or 6.10.14 or 6.11.3, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, d0e4274d9dc9f8409d56d622cd3ecf7b6fd49e2f; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, a4aef827a41cdaf6201bbaf773c1eae4e20e967b; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, ad791e3ec60cb66c1e4dc121ffbf872df312427d; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, e106b7ad13c1d246adaa57df73edb8f8b8acb240; 6.3 | d0e4274d9dc9f8409d56d622cd3ecf7b6fd49e2f, a4aef827a41cdaf6201bbaf773c1eae4e20e967b, ad791e3ec60cb66c1e4dc121ffbf872df312427d, e106b7ad13c1d246adaa57df73edb8f8b8acb240 |
| Linux | Linux Kernel | before 6.6.55; 6.7 up to, but not including, 6.10.14; 6.11 up to, but not including, 6.11.3 | 6.6.55, 6.10.14, 6.11.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.
Official description
In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix array out-of-bound access in SoC stats Currently, the ath12k_soc_dp_stats::hal_reo_error array is defined with a maximum size of DP_REO_DST_RING_MAX. However, the ath12k_dp_rx_process() function access ath12k_soc_dp_stats::hal_reo_error using the REO destination SRNG ring ID, which is incorrect. SRNG ring ID differ from normal ring ID, and this usage leads to out-of-bounds array access. To fix this issue, modify ath12k_dp_rx_process() to use the normal ring ID directly instead of the SRNG ring ID to avoid out-of-bounds array access. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1
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: partial).
- 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.1 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.