CyberSecBulletin
CVE-2024-49969NVD status: Modified

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2024-49969 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 7ab69af56a23859b647dee69fa1052c689343621, c13f9c62015c56a938304cef6d507227ea3e0039, 0f1e222a4b41d77c442901d166fbdca967af0d86 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.27% 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 7ab69af56a23859b647dee69fa1052c689343621 or c13f9c62015c56a938304cef6d507227ea3e0039 or 0f1e222a4b41d77c442901d166fbdca967af0d86 or 929506d5671419cffd8d01e9a7f5eae53682a838, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.227 or 5.15.168 or 6.1.113 or 6.6.55, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux03f54d7d3448dc1668568d1adb69b43c1d1dc79f up to, but not including, 7ab69af56a23859b647dee69fa1052c689343621; 03f54d7d3448dc1668568d1adb69b43c1d1dc79f up to, but not including, c13f9c62015c56a938304cef6d507227ea3e0039; 03f54d7d3448dc1668568d1adb69b43c1d1dc79f up to, but not including, 0f1e222a4b41d77c442901d166fbdca967af0d86; 03f54d7d3448dc1668568d1adb69b43c1d1dc79f up to, but not including, 929506d5671419cffd8d01e9a7f5eae53682a838; 03f54d7d3448dc1668568d1adb69b43c1d1dc79f up to, but not including, 578422ddae3d13362b64e77ef9bab98780641631; 03f54d7d3448dc1668568d1adb69b43c1d1dc79f up to, but not including, b9d8b94ec7e67f0cae228c054f77b73967c389a3; 03f54d7d3448dc1668568d1adb69b43c1d1dc79f up to, but not including, d81873f9e715b72d4f8d391c8eb243946f784dfc; 5.97ab69af56a23859b647dee69fa1052c689343621, c13f9c62015c56a938304cef6d507227ea3e0039, 0f1e222a4b41d77c442901d166fbdca967af0d86, 929506d5671419cffd8d01e9a7f5eae53682a838, 578422ddae3d13362b64e77ef9bab98780641631, b9d8b94ec7e67f0cae228c054f77b73967c389a3
LinuxLinux Kernelbefore 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.35.10.227, 5.15.168, 6.1.113, 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.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix index out of bounds in DCN30 color transformation This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_hw_format` function in the DCN30 color management module. The issue could occur when the index 'i' exceeds the number of transfer function points (TRANSFER_FUNC_POINTS). The fix adds a check to ensure 'i' is within bounds before accessing the transfer function points. If 'i' is out of bounds, the function returns false to indicate an error. drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:180 cm3_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.red' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:181 cm3_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.green' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:182 cm3_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.blue' 1025 <= s32max

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

Recent Improper Validation of Array Index vulnerabilities

Spotted an error? Tell us.