CyberSecBulletin
CVE-2024-50007NVD status: Analyzed

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2024-50007 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 a6bdb691cf7b66dcd929de1a253c5c42edd2e522, ce2953e44829ec54bcbb57e9d890fc8af0900c80, 219587bca2678e31700ef09ecec178ba1f735674 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.25% 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 a6bdb691cf7b66dcd929de1a253c5c42edd2e522 or ce2953e44829ec54bcbb57e9d890fc8af0900c80 or 219587bca2678e31700ef09ecec178ba1f735674 or 36ee4021bcc37b834996e79740d095d6f8dd948f, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.19.323 or 5.4.285 or 5.10.227 or 5.15.168, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux719f82d3987aad4cc9f46d19c35f362672545cad up to, but not including, a6bdb691cf7b66dcd929de1a253c5c42edd2e522; 719f82d3987aad4cc9f46d19c35f362672545cad up to, but not including, ce2953e44829ec54bcbb57e9d890fc8af0900c80; 719f82d3987aad4cc9f46d19c35f362672545cad up to, but not including, 219587bca2678e31700ef09ecec178ba1f735674; 719f82d3987aad4cc9f46d19c35f362672545cad up to, but not including, 36ee4021bcc37b834996e79740d095d6f8dd948f; 719f82d3987aad4cc9f46d19c35f362672545cad up to, but not including, e658227d9d4f4e122d81690fdbc0d438b10288f5; 719f82d3987aad4cc9f46d19c35f362672545cad up to, but not including, 7a55740996701f7b2bc46dc988b60ef2e416a747; 719f82d3987aad4cc9f46d19c35f362672545cad up to, but not including, ad7248a5e92587b9266c62db8bcc4e58de53e372; 719f82d3987aad4cc9f46d19c35f362672545cad up to, but not including, 876d04bf5a8ac1d6af5afd258cd37ab83ab2cf3d; and 2 more rangesa6bdb691cf7b66dcd929de1a253c5c42edd2e522, ce2953e44829ec54bcbb57e9d890fc8af0900c80, 219587bca2678e31700ef09ecec178ba1f735674, 36ee4021bcc37b834996e79740d095d6f8dd948f, e658227d9d4f4e122d81690fdbc0d438b10288f5, 7a55740996701f7b2bc46dc988b60ef2e416a747
DebianDebian Linux11.0Not stated
LinuxLinux Kernelbefore 4.19.323; 4.20 up to, but not including, 5.4.285; 5.5 up to, but not including, 5.10.227; 5.11 up to, but not including, 5.15.168; 5.16 up to, but not including, 6.1.113; 6.2 up to, but not including, 6.6.55; 6.7 up to, but not including, 6.10.14; 6.11 up to, but not including, 6.11.34.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, 6.6.55

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: ALSA: asihpi: Fix potential OOB array access ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware. We shouldn't trust it blindly. This patch adds a sanity check of the array index to fit in the array size.

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. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Improper Validation of Array Index vulnerabilities

Spotted an error? Tell us.