CyberSecBulletin
CVE-2024-42092NVD status: Modified

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2024-42092 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 a8d78984fdc105bc1a38b73e98d32b1bc4222684, cd75721984337c38a12aeca33ba301d31ca4b3fd, e44a83bf15c4db053ac6dfe96a23af184c9136d9 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 a8d78984fdc105bc1a38b73e98d32b1bc4222684 or cd75721984337c38a12aeca33ba301d31ca4b3fd or e44a83bf15c4db053ac6dfe96a23af184c9136d9 or 70b48899f3f23f98a52c5b1060aefbdc7ba7957b, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.19.317 or 5.4.279 or 5.10.221 or 5.15.162, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxeb3744a2dd01cb07ce9f556d56d6fe451f0c313a up to, but not including, a8d78984fdc105bc1a38b73e98d32b1bc4222684; eb3744a2dd01cb07ce9f556d56d6fe451f0c313a up to, but not including, cd75721984337c38a12aeca33ba301d31ca4b3fd; eb3744a2dd01cb07ce9f556d56d6fe451f0c313a up to, but not including, e44a83bf15c4db053ac6dfe96a23af184c9136d9; eb3744a2dd01cb07ce9f556d56d6fe451f0c313a up to, but not including, 70b48899f3f23f98a52c5b1060aefbdc7ba7957b; eb3744a2dd01cb07ce9f556d56d6fe451f0c313a up to, but not including, 89d7008af4945808677662a630643b5ea89c6e8d; eb3744a2dd01cb07ce9f556d56d6fe451f0c313a up to, but not including, 2d83492259ad746b655f196cd5d1be4b3d0a3782; eb3744a2dd01cb07ce9f556d56d6fe451f0c313a up to, but not including, c542e51306d5f1eba3af84daa005826223382470; eb3744a2dd01cb07ce9f556d56d6fe451f0c313a up to, but not including, 7aa9b96e9a73e4ec1771492d0527bd5fc5ef9164; and 1 more rangesa8d78984fdc105bc1a38b73e98d32b1bc4222684, cd75721984337c38a12aeca33ba301d31ca4b3fd, e44a83bf15c4db053ac6dfe96a23af184c9136d9, 70b48899f3f23f98a52c5b1060aefbdc7ba7957b, 89d7008af4945808677662a630643b5ea89c6e8d, 2d83492259ad746b655f196cd5d1be4b3d0a3782
LinuxLinux Kernel4.19 up to, but not including, 4.19.317; 4.20 up to, but not including, 5.4.279; 5.5 up to, but not including, 5.10.221; 5.11 up to, but not including, 5.15.162; 5.16 up to, but not including, 6.1.97; 6.2 up to, but not including, 6.6.37; 6.7 up to, but not including, 6.9.8; 6.104.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.97, 6.6.37

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: gpio: davinci: Validate the obtained number of IRQs Value of pdata->gpio_unbanked is taken from Device Tree. In case of broken DT due to any error this value can be any. Without this value validation there can be out of chips->irqs array boundaries access in davinci_gpio_probe(). Validate the obtained nirq value so that it won't exceed the maximum number of IRQs per bank. Found by Linux Verification Center (linuxtesting.org) with SVACE.

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.