CyberSecBulletin
CVE-2024-26982NVD status: Modified

Linux: Out-of-bounds Read

Published Updated By the CyberSecBulletin desk

CVE-2024-26982 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 32c114a58236fe67141634774559f21f1dc96fd7, 4a1b6f89825e267e156ccaeba3d235edcac77f94, cf46f88b92cfc0e32bd8a21ba1273cff13b8745f 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.28% 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 32c114a58236fe67141634774559f21f1dc96fd7 or 4a1b6f89825e267e156ccaeba3d235edcac77f94 or cf46f88b92cfc0e32bd8a21ba1273cff13b8745f or 5b99dea79650b50909c50aba24fbae00f203f013, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.30 or 6.8.8, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux6545b246a2c815a8fcd07d58240effb6ec3481b1 up to, but not including, 32c114a58236fe67141634774559f21f1dc96fd7; 6545b246a2c815a8fcd07d58240effb6ec3481b1 up to, but not including, 4a1b6f89825e267e156ccaeba3d235edcac77f94; 6545b246a2c815a8fcd07d58240effb6ec3481b1 up to, but not including, cf46f88b92cfc0e32bd8a21ba1273cff13b8745f; 6545b246a2c815a8fcd07d58240effb6ec3481b1 up to, but not including, 5b99dea79650b50909c50aba24fbae00f203f013; 6545b246a2c815a8fcd07d58240effb6ec3481b1 up to, but not including, be383effaee3d89034f0828038f95065b518772e; 6545b246a2c815a8fcd07d58240effb6ec3481b1 up to, but not including, 7def00ebc9f2d6a581ddf46ce4541f84a10680e5; 6545b246a2c815a8fcd07d58240effb6ec3481b1 up to, but not including, 9253c54e01b6505d348afbc02abaa4d9f8a01395; 2.6.2932c114a58236fe67141634774559f21f1dc96fd7, 4a1b6f89825e267e156ccaeba3d235edcac77f94, cf46f88b92cfc0e32bd8a21ba1273cff13b8745f, 5b99dea79650b50909c50aba24fbae00f203f013, be383effaee3d89034f0828038f95065b518772e, 7def00ebc9f2d6a581ddf46ce4541f84a10680e5
SiemensSIMATIC S7-1500 TM MFP - BIOSall versionsNot stated
SiemensSIMATIC S7-1500 TM MFP - GNU/Linux subsystemall versionsNot stated
LinuxLinux Kernelbefore 6.6.30; 6.7 up to, but not including, 6.8.8; 6.96.6.30, 6.8.8

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: Squashfs: check the inode number is not the invalid value of zero Syskiller has produced an out of bounds access in fill_meta_index(). That out of bounds access is ultimately caused because the inode has an inode number with the invalid value of zero, which was not checked. The reason this causes the out of bounds access is due to following sequence of events: 1. Fill_meta_index() is called to allocate (via empty_meta_index()) and fill a metadata index. It however suffers a data read error and aborts, invalidating the newly returned empty metadata index. It does this by setting the inode number of the index to zero, which means unused (zero is not a valid inode number). 2. When fill_meta_index() is subsequently called again on another read operation, locate_meta_index() returns the previous index because it matches the inode number of 0. Because this index has been returned it is expected to have been filled, and because it hasn't been, an out of bounds access is performed. This patch adds a sanity check which checks that the inode number is not zero when the inode is created and returns -EINVAL if it is. [[email protected]: whitespace fix]

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

Other references

Recent Out-of-bounds Read vulnerabilities

Spotted an error? Tell us.