CyberSecBulletin
CVE-2024-26593NVD status: Modified

Linux: Out-of-bounds Read

Published Updated By the CyberSecBulletin desk

CVE-2024-26593 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 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 d074d5ff5ae77b18300e5079c6bda6342a4d44b7, 7a14b8a477b88607d157c24aeb23e7389ec3319f, 1f8d0691c50581ba6043f009ec9e8b9f78f09d5a 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.29% 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 d074d5ff5ae77b18300e5079c6bda6342a4d44b7 or 7a14b8a477b88607d157c24aeb23e7389ec3319f or 1f8d0691c50581ba6043f009ec9e8b9f78f09d5a or 491528935c9c48bf341d8b40eabc6c4fc5df6f2c, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.4.269 or 5.10.210 or 5.15.149 or 6.1.79, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux315cd67c945351f8a569500f8ab16b7fa94026e8 up to, but not including, d074d5ff5ae77b18300e5079c6bda6342a4d44b7; 315cd67c945351f8a569500f8ab16b7fa94026e8 up to, but not including, 7a14b8a477b88607d157c24aeb23e7389ec3319f; 315cd67c945351f8a569500f8ab16b7fa94026e8 up to, but not including, 1f8d0691c50581ba6043f009ec9e8b9f78f09d5a; 315cd67c945351f8a569500f8ab16b7fa94026e8 up to, but not including, 491528935c9c48bf341d8b40eabc6c4fc5df6f2c; 315cd67c945351f8a569500f8ab16b7fa94026e8 up to, but not including, 6be99c51829b24c914cef5bff6164877178e84d9; 315cd67c945351f8a569500f8ab16b7fa94026e8 up to, but not including, 609c7c1cc976e740d0fed4dbeec688b3ecb5dce2; 315cd67c945351f8a569500f8ab16b7fa94026e8 up to, but not including, c1c9d0f6f7f1dbf29db996bd8e166242843a5f21; 5.3d074d5ff5ae77b18300e5079c6bda6342a4d44b7, 7a14b8a477b88607d157c24aeb23e7389ec3319f, 1f8d0691c50581ba6043f009ec9e8b9f78f09d5a, 491528935c9c48bf341d8b40eabc6c4fc5df6f2c, 6be99c51829b24c914cef5bff6164877178e84d9, 609c7c1cc976e740d0fed4dbeec688b3ecb5dce2
LinuxLinux Kernel5.3.0 up to, but not including, 5.4.269; 5.5.0 up to, but not including, 5.10.210; 5.11.0 up to, but not including, 5.15.149; 5.16.0 up to, but not including, 6.1.79; 6.2.0 up to, but not including, 6.6.18; 6.7.0 up to, but not including, 6.7.65.4.269, 5.10.210, 5.15.149, 6.1.79, 6.6.18, 6.7.6

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
NoneNothing can be modified.
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:N/A:H. Scored by NVD.

Official description

In the Linux kernel, the following vulnerability has been resolved: i2c: i801: Fix block process call transactions According to the Intel datasheets, software must reset the block buffer index twice for block process call transactions: once before writing the outgoing data to the buffer, and once again before reading the incoming data from the buffer. The driver is currently missing the second reset, causing the wrong portion of the block buffer to be read.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Read

The product reads data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that provides appropriate memory abstractions.

More Out-of-bounds Read vulnerabilities (CWE-125)

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 Out-of-bounds Read vulnerabilities

Spotted an error? Tell us.