CyberSecBulletin
CVE-2024-26791NVD status: Analyzed

Linux: Out-of-bounds Read

Published Updated By the CyberSecBulletin desk

CVE-2024-26791 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 11d7a2e429c02d51e2dc90713823ea8b8d3d3a84, c6652e20d7d783d060fe5f987eac7b5cabe31311, 2886fe308a83968dde252302884a1e63351cf16d 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 11d7a2e429c02d51e2dc90713823ea8b8d3d3a84 or c6652e20d7d783d060fe5f987eac7b5cabe31311 or 2886fe308a83968dde252302884a1e63351cf16d or ab2d68655d0f04650bef09fee948ff80597c5fb9, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.19.309 or 5.4.271 or 5.10.212 or 5.15.151, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxe93c89c1aaaaaec3487c4c18dd02360371790722 up to, but not including, 11d7a2e429c02d51e2dc90713823ea8b8d3d3a84; e93c89c1aaaaaec3487c4c18dd02360371790722 up to, but not including, c6652e20d7d783d060fe5f987eac7b5cabe31311; e93c89c1aaaaaec3487c4c18dd02360371790722 up to, but not including, 2886fe308a83968dde252302884a1e63351cf16d; e93c89c1aaaaaec3487c4c18dd02360371790722 up to, but not including, ab2d68655d0f04650bef09fee948ff80597c5fb9; e93c89c1aaaaaec3487c4c18dd02360371790722 up to, but not including, f590040ce2b712177306b03c2a63b16f7d48d3c8; e93c89c1aaaaaec3487c4c18dd02360371790722 up to, but not including, b1690ced4d2d8b28868811fb81cd33eee5aefee1; e93c89c1aaaaaec3487c4c18dd02360371790722 up to, but not including, 343eecb4ff49a7b1cc1dfe86958a805cf2341cfb; e93c89c1aaaaaec3487c4c18dd02360371790722 up to, but not including, 9845664b9ee47ce7ee7ea93caf47d39a9d4552c4; and 1 more ranges11d7a2e429c02d51e2dc90713823ea8b8d3d3a84, c6652e20d7d783d060fe5f987eac7b5cabe31311, 2886fe308a83968dde252302884a1e63351cf16d, ab2d68655d0f04650bef09fee948ff80597c5fb9, f590040ce2b712177306b03c2a63b16f7d48d3c8, b1690ced4d2d8b28868811fb81cd33eee5aefee1
LinuxLinux Kernelbefore 4.19.309; 4.20 up to, but not including, 5.4.271; 5.5 up to, but not including, 5.10.212; 5.11 up to, but not including, 5.15.151; 5.16 up to, but not including, 6.1.81; 6.2 up to, but not including, 6.6.21; 6.7 up to, but not including, 6.7.9; 6.84.19.309, 5.4.271, 5.10.212, 5.15.151, 6.1.81, 6.6.21

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: btrfs: dev-replace: properly validate device names There's a syzbot report that device name buffers passed to device replace are not properly checked for string termination which could lead to a read out of bounds in getname_kernel(). Add a helper that validates both source and target device name buffers. For devid as the source initialize the buffer to empty string in case something tries to read it later. This was originally analyzed and fixed in a different way by Edward Adam Davis (see links).

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.