CyberSecBulletin
CVE-2024-46821NVD status: Analyzed

Linux: Improper Validation of Array Index

CVE-2024-46821 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 befd1dc693c98bad69a701ede3a298698f0f9436, e549cd6da1f21c34ba0f65adeca6a8aa9860b381, 60f4a4bc3329e5cb8c4df0cc961f0d5ffd96e22d 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.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to befd1dc693c98bad69a701ede3a298698f0f9436 or e549cd6da1f21c34ba0f65adeca6a8aa9860b381 or 60f4a4bc3329e5cb8c4df0cc961f0d5ffd96e22d or 4711b1347cb9f0c3083da6d87c624d75f9bd1d50, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.236 or 5.15.180 or 6.1.109 or 6.6.50, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux1a195ed5f197fcfd1d99ceedd469857fcd7d8c4f up to, but not including, befd1dc693c98bad69a701ede3a298698f0f9436; 1a195ed5f197fcfd1d99ceedd469857fcd7d8c4f up to, but not including, e549cd6da1f21c34ba0f65adeca6a8aa9860b381; 1a195ed5f197fcfd1d99ceedd469857fcd7d8c4f up to, but not including, 60f4a4bc3329e5cb8c4df0cc961f0d5ffd96e22d; 1a195ed5f197fcfd1d99ceedd469857fcd7d8c4f up to, but not including, 4711b1347cb9f0c3083da6d87c624d75f9bd1d50; 1a195ed5f197fcfd1d99ceedd469857fcd7d8c4f up to, but not including, 06a3810010b525b9958424e344f0c25b09e128fa; 1a195ed5f197fcfd1d99ceedd469857fcd7d8c4f up to, but not including, c8c19ebf7c0b202a6a2d37a52ca112432723db5f; 5.3befd1dc693c98bad69a701ede3a298698f0f9436, e549cd6da1f21c34ba0f65adeca6a8aa9860b381, 60f4a4bc3329e5cb8c4df0cc961f0d5ffd96e22d, 4711b1347cb9f0c3083da6d87c624d75f9bd1d50, 06a3810010b525b9958424e344f0c25b09e128fa, c8c19ebf7c0b202a6a2d37a52ca112432723db5f
DebianDebian Linux11.0Not stated
LinuxLinux Kernelbefore 5.10.236; 5.11 up to, but not including, 5.15.180; 5.16 up to, but not including, 6.1.109; 6.2 up to, but not including, 6.6.50; 6.7 up to, but not including, 6.10.95.10.236, 5.15.180, 6.1.109, 6.6.50, 6.10.9

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: drm/amd/pm: Fix negative array index read Avoid using the negative values for clk_idex as an index into an array pptable->DpmDescriptor. V2: fix clk_index return check (Tim Huang)

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.