CyberSecBulletin
CVE-2024-26664NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-26664 is a high-severity out-of-bounds write 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 93f0f4e846fcb682c3ec436e3b2e30e5a3a8ee6a, 1eb74c00c9c3b13cb65e508c5d5a2f11afb96b8b, f0da068c75c20ffc5ba28243ff577531dc2af1fd 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 93f0f4e846fcb682c3ec436e3b2e30e5a3a8ee6a or 1eb74c00c9c3b13cb65e508c5d5a2f11afb96b8b or f0da068c75c20ffc5ba28243ff577531dc2af1fd or a16afec8e83c56b14a4a73d2e3fb8eec3a8a057e, 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 6.1.78, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux4f9dcadc55c21b39b072bb0882362c7edc4340bc up to, but not including, 93f0f4e846fcb682c3ec436e3b2e30e5a3a8ee6a; c00cdfc9bd767ee743ad3a4054de17aeb0afcbca up to, but not including, 1eb74c00c9c3b13cb65e508c5d5a2f11afb96b8b; d9f0159da05df869071164edf0c6d7302efc5eca up to, but not including, f0da068c75c20ffc5ba28243ff577531dc2af1fd; 30cf0dee372baf9b515f2d9c7218f905fddf3cdb up to, but not including, a16afec8e83c56b14a4a73d2e3fb8eec3a8a057e; 7108b80a542b9d65e44b36d64a700a83658c0b73 up to, but not including, 9bce69419271eb8b2b3ab467387cb59c99d80deb; 7108b80a542b9d65e44b36d64a700a83658c0b73 up to, but not including, 853a6503c586a71abf27e60a7f8c4fb28092976d; 7108b80a542b9d65e44b36d64a700a83658c0b73 up to, but not including, 3a7753bda55985dc26fae17795cb10d825453ad1; 7108b80a542b9d65e44b36d64a700a83658c0b73 up to, but not including, 4e440abc894585a34c2904a32cd54af1742311b3; and 7 more ranges93f0f4e846fcb682c3ec436e3b2e30e5a3a8ee6a, 1eb74c00c9c3b13cb65e508c5d5a2f11afb96b8b, f0da068c75c20ffc5ba28243ff577531dc2af1fd, a16afec8e83c56b14a4a73d2e3fb8eec3a8a057e, 9bce69419271eb8b2b3ab467387cb59c99d80deb, 853a6503c586a71abf27e60a7f8c4fb28092976d
LinuxLinux Kernel4.19.264 up to, but not including, 4.19.307; 5.4.221 up to, but not including, 5.4.269; 5.10.152 up to, but not including, 5.10.210; 6.1 up to, but not including, 6.1.78; 6.2 up to, but not including, 6.6.17; 6.7 up to, but not including, 6.7.5; 6.84.19.307, 5.4.269, 5.10.210, 6.1.78, 6.6.17, 6.7.5
DebianDebian Linux10.0Not stated

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.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.1HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) Fix out-of-bounds memory access Fix a bug that pdata->cpu_map[] is set before out-of-bounds check. The problem might be triggered on systems with more than 128 cores per package.

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

The underlying weakness: Out-of-bounds Write

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

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

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 Write vulnerabilities

Spotted an error? Tell us.