CyberSecBulletin
CVE-2024-35905NVD status: Modified

Linux: Improper Validation of Array Index

CVE-2024-35905 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 9970e059af471478455f9534e8c3db82f8c5496d, 37dc1718dc0c4392dbfcb9adec22a776e745dd69, 98cdac206b112bec63852e94802791e316acc2c1 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.22% 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 9970e059af471478455f9534e8c3db82f8c5496d or 37dc1718dc0c4392dbfcb9adec22a776e745dd69 or 98cdac206b112bec63852e94802791e316acc2c1 or 3f0784b2f1eb9147973d8c43ba085c5fdf44ff69, whichever matches your release line, or a later version.
  2. Update SIMATIC S7-1500 TM MFP - GNU/Linux subsystem to V1.1.1 or a later version.
  3. Update Linux Kernel to 5.10.215 or 5.15.154 or 6.1.85 or 6.6.26, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxafea95d319ccb4ad2060dece9ac5e2e364dec543 up to, but not including, 9970e059af471478455f9534e8c3db82f8c5496d; 02962684258eb53f414a8a59854767be526e6abb up to, but not including, 37dc1718dc0c4392dbfcb9adec22a776e745dd69; b1d4d54d32ce6342f5faffe71bae736540ce7cb5 up to, but not including, 98cdac206b112bec63852e94802791e316acc2c1; 08b91babccbb168353f8d43fea0ed28a4cad568c up to, but not including, 3f0784b2f1eb9147973d8c43ba085c5fdf44ff69; a833a17aeac73b33f79433d7cee68d5cafd71e4f up to, but not including, 203a68151e8eeb331d4a64ab78303f3a15faf103; a833a17aeac73b33f79433d7cee68d5cafd71e4f up to, but not including, ecc6a2101840177e57c925c102d2d29f260d37c8; 1858b8a331937f3976d8482cd5f6e1f945294ad3; 5.10.209 up to, but not including, 5.10.215; and 5 more ranges9970e059af471478455f9534e8c3db82f8c5496d, 37dc1718dc0c4392dbfcb9adec22a776e745dd69, 98cdac206b112bec63852e94802791e316acc2c1, 3f0784b2f1eb9147973d8c43ba085c5fdf44ff69, 203a68151e8eeb331d4a64ab78303f3a15faf103, ecc6a2101840177e57c925c102d2d29f260d37c8
SiemensSIMATIC S7-1500 TM MFP - GNU/Linux subsystembefore V1.1.1V1.1.1
LinuxLinux Kernel5.10.209 up to, but not including, 5.10.215; 5.15.148 up to, but not including, 5.15.154; 6.1.75 up to, but not including, 6.1.85; 6.6.14 up to, but not including, 6.6.26; 6.7.2 up to, but not including, 6.8.5; 6.95.10.215, 5.15.154, 6.1.85, 6.6.26, 6.8.5
DebianDebian Linux10.0Not stated

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: bpf: Protect against int overflow for stack access size This patch re-introduces protection against the size of access to stack memory being negative; the access size can appear negative as a result of overflowing its signed int representation. This should not actually happen, as there are other protections along the way, but we should protect against it anyway. One code path was missing such protections (fixed in the previous patch in the series), causing out-of-bounds array accesses in check_stack_range_initialized(). This patch causes the verification of a program with such a non-sensical access size to fail. This check used to exist in a more indirect way, but was inadvertendly removed in a833a17aeac7.

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.