CyberSecBulletin
CVE-2024-46859NVD status: Modified

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2024-46859 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 b7c2f692307fe704be87ea80d7328782b33c3cef, 9291fadbd2720a869b1d2fcf82305648e2e62a16, 6821a82616f60aa72c5909b3e252ad97fb9f7e2a 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 b7c2f692307fe704be87ea80d7328782b33c3cef or 9291fadbd2720a869b1d2fcf82305648e2e62a16 or 6821a82616f60aa72c5909b3e252ad97fb9f7e2a or b38c19783286a71693c2194ed1b36665168c09c4, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.15.168 or 6.1.111 or 6.6.52 or 6.10.11, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxe424fb8cc4e6634c10f8159b1ff5618cf7bab9c6 up to, but not including, b7c2f692307fe704be87ea80d7328782b33c3cef; e424fb8cc4e6634c10f8159b1ff5618cf7bab9c6 up to, but not including, 9291fadbd2720a869b1d2fcf82305648e2e62a16; e424fb8cc4e6634c10f8159b1ff5618cf7bab9c6 up to, but not including, 6821a82616f60aa72c5909b3e252ad97fb9f7e2a; e424fb8cc4e6634c10f8159b1ff5618cf7bab9c6 up to, but not including, b38c19783286a71693c2194ed1b36665168c09c4; e424fb8cc4e6634c10f8159b1ff5618cf7bab9c6 up to, but not including, f52e98d16e9bd7dd2b3aef8e38db5cbc9899d6a4; 3.3b7c2f692307fe704be87ea80d7328782b33c3cef, 9291fadbd2720a869b1d2fcf82305648e2e62a16, 6821a82616f60aa72c5909b3e252ad97fb9f7e2a, b38c19783286a71693c2194ed1b36665168c09c4, f52e98d16e9bd7dd2b3aef8e38db5cbc9899d6a4
DebianDebian Linux11.0Not stated
LinuxLinux Kernel3.3 up to, but not including, 5.15.168; 5.16 up to, but not including, 6.1.111; 6.2 up to, but not including, 6.6.52; 6.7 up to, but not including, 6.10.11; 6.115.15.168, 6.1.111, 6.6.52, 6.10.11

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: platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses The panasonic laptop code in various places uses the SINF array with index values of 0 - SINF_CUR_BRIGHT(0x0d) without checking that the SINF array is big enough. Not all panasonic laptops have this many SINF array entries, for example the Toughbook CF-18 model only has 10 SINF array entries. So it only supports the AC+DC brightness entries and mute. Check that the SINF array has a minimum size which covers all AC+DC brightness entries and refuse to load if the SINF array is smaller. For higher SINF indexes hide the sysfs attributes when the SINF array does not contain an entry for that attribute, avoiding show()/store() accessing the array out of bounds and add bounds checking to the probe() and resume() code accessing these.

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.