CyberSecBulletin
CVE-2023-52594NVD status: Analyzed

Linux: Improper Validation of Array Index

CVE-2023-52594 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 f44f073c78112ff921a220d01b86d09f2ace59bc, f11f0fd1ad6c11ae7856d4325fe9d05059767225, 84770a996ad8d7f121ff2fb5a8d149aad52d64c1 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.25% 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 f44f073c78112ff921a220d01b86d09f2ace59bc or f11f0fd1ad6c11ae7856d4325fe9d05059767225 or 84770a996ad8d7f121ff2fb5a8d149aad52d64c1 or 9003fa9a0198ce004b30738766c67eb7373479c9, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.19.307 or 5.4.269 or 5.10.210 or 5.15.149, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux27876a29de221186c9d5883e5fe5f6da18ef9a45 up to, but not including, f44f073c78112ff921a220d01b86d09f2ace59bc; 27876a29de221186c9d5883e5fe5f6da18ef9a45 up to, but not including, f11f0fd1ad6c11ae7856d4325fe9d05059767225; 27876a29de221186c9d5883e5fe5f6da18ef9a45 up to, but not including, 84770a996ad8d7f121ff2fb5a8d149aad52d64c1; 27876a29de221186c9d5883e5fe5f6da18ef9a45 up to, but not including, 9003fa9a0198ce004b30738766c67eb7373479c9; 27876a29de221186c9d5883e5fe5f6da18ef9a45 up to, but not including, 25c6f49ef59b7a9b80a3f7ab9e95268a1b01a234; 27876a29de221186c9d5883e5fe5f6da18ef9a45 up to, but not including, e4f4bac7d3b64eb75f70cd3345712de6f68a215d; 27876a29de221186c9d5883e5fe5f6da18ef9a45 up to, but not including, be609c7002dd4504b15b069cb7582f4c778548d1; 27876a29de221186c9d5883e5fe5f6da18ef9a45 up to, but not including, 2adc886244dff60f948497b59affb6c6ebb3c348; and 1 more rangesf44f073c78112ff921a220d01b86d09f2ace59bc, f11f0fd1ad6c11ae7856d4325fe9d05059767225, 84770a996ad8d7f121ff2fb5a8d149aad52d64c1, 9003fa9a0198ce004b30738766c67eb7373479c9, 25c6f49ef59b7a9b80a3f7ab9e95268a1b01a234, e4f4bac7d3b64eb75f70cd3345712de6f68a215d
LinuxLinux Kernelbefore 4.19.307; 4.20 up to, but not including, 5.4.269; 5.5 up to, but not including, 5.10.210; 5.11 up to, but not including, 5.15.149; 5.16 up to, but not including, 6.1.77; 6.2 up to, but not including, 6.6.16; 6.7 up to, but not including, 6.7.44.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.77, 6.6.16

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: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() Fix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug occurs when txs->cnt, data from a URB provided by a USB device, is bigger than the size of the array txs->txstatus, which is HTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug handling code after the check. Make the function return if that is the case. Found by a modified version of syzkaller. UBSAN: array-index-out-of-bounds in htc_drv_txrx.c index 13 is out of range for type '__wmi_event_txstatus [12]' Call Trace: ath9k_htc_txstatus ath9k_wmi_event_tasklet tasklet_action_common __do_softirq irq_exit_rxu sysvec_apic_timer_interrupt

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.