CyberSecBulletin
CVE-2024-46871NVD status: Analyzed

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2024-46871 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 e1896f381d27466c26cb44b4450eae05cd59dfd0, 9f404b0bc2df3880758fb3c3bc7496f596f347d7, 800a5ab673c4a61ca220cce177386723d91bdb37 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.21% 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 e1896f381d27466c26cb44b4450eae05cd59dfd0 or 9f404b0bc2df3880758fb3c3bc7496f596f347d7 or 800a5ab673c4a61ca220cce177386723d91bdb37 or c592b6355b9b57b8e59fc5978ce1e14f64488a98, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.15.174 or 6.1.109 or 6.6.50 or 6.10.9, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c up to, but not including, e1896f381d27466c26cb44b4450eae05cd59dfd0; 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c up to, but not including, 9f404b0bc2df3880758fb3c3bc7496f596f347d7; 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c up to, but not including, 800a5ab673c4a61ca220cce177386723d91bdb37; 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c up to, but not including, c592b6355b9b57b8e59fc5978ce1e14f64488a98; 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c up to, but not including, ad28d7c3d989fc5689581664653879d664da76f0; 4.15e1896f381d27466c26cb44b4450eae05cd59dfd0, 9f404b0bc2df3880758fb3c3bc7496f596f347d7, 800a5ab673c4a61ca220cce177386723d91bdb37, c592b6355b9b57b8e59fc5978ce1e14f64488a98, ad28d7c3d989fc5689581664653879d664da76f0
DebianDebian Linux11.0Not stated
LinuxLinux Kernel4.15 up to, but not including, 5.15.174; 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.15.174, 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/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX [Why & How] It actually exposes '6' types in enum dmub_notification_type. Not 5. Using smaller number to create array dmub_callback & dmub_thread_offload has potential to access item out of array bound. Fix it.

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.