CyberSecBulletin
CVE-2024-26884NVD status: Modified

Linux: Improper Restriction of Operations within the Bounds of a Memory Buffer

Published Updated By the CyberSecBulletin desk

CVE-2024-26884 is a high-severity improper restriction of operations within the bounds of a memory buffer 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 33ec04cadb77605b71d9298311919303d390c4d5, 92c81fbb3ed2e0dfc33a4183a67135e1ab566ace, 64f00b4df0597590b199b62a37a165473bf658a6 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 33ec04cadb77605b71d9298311919303d390c4d5 or 92c81fbb3ed2e0dfc33a4183a67135e1ab566ace or 64f00b4df0597590b199b62a37a165473bf658a6 or 3b08cfc65f07b1132c1979d73f014ae6e04de55d, whichever matches your release line, or a later version.
  2. Update SIMATIC S7-1500 TM MFP - GNU/Linux subsystem to V1.1.1 or a later version.
  3. Update Linux Kernel to 4.19.311 or 5.4.273 or 5.10.214 or 5.15.153, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxdaaf427c6ab392bedcd018e326b2ffa1e1110cd6 up to, but not including, 33ec04cadb77605b71d9298311919303d390c4d5; daaf427c6ab392bedcd018e326b2ffa1e1110cd6 up to, but not including, 92c81fbb3ed2e0dfc33a4183a67135e1ab566ace; daaf427c6ab392bedcd018e326b2ffa1e1110cd6 up to, but not including, 64f00b4df0597590b199b62a37a165473bf658a6; daaf427c6ab392bedcd018e326b2ffa1e1110cd6 up to, but not including, 3b08cfc65f07b1132c1979d73f014ae6e04de55d; daaf427c6ab392bedcd018e326b2ffa1e1110cd6 up to, but not including, a83fdaeaea3677b83a53f72ace2d73a19bcd6d93; daaf427c6ab392bedcd018e326b2ffa1e1110cd6 up to, but not including, 8435f0961bf3dc65e204094349bd9aeaac1f8868; daaf427c6ab392bedcd018e326b2ffa1e1110cd6 up to, but not including, d817f0d34d927f2deb17dadbfe212c9a6a32ac3e; daaf427c6ab392bedcd018e326b2ffa1e1110cd6 up to, but not including, a6fa75b5096c0f9826a4fabe22d907b0a5bb1016; and 2 more ranges33ec04cadb77605b71d9298311919303d390c4d5, 92c81fbb3ed2e0dfc33a4183a67135e1ab566ace, 64f00b4df0597590b199b62a37a165473bf658a6, 3b08cfc65f07b1132c1979d73f014ae6e04de55d, a83fdaeaea3677b83a53f72ace2d73a19bcd6d93, 8435f0961bf3dc65e204094349bd9aeaac1f8868
SiemensSIMATIC S7-1500 TM MFP - GNU/Linux subsystembefore V1.1.1V1.1.1
LinuxLinux Kernel3.19 up to, but not including, 4.19.311; 4.20 up to, but not including, 5.4.273; 5.5 up to, but not including, 5.10.214; 5.11 up to, but not including, 5.15.153; 5.16 up to, but not including, 6.1.83; 6.2 up to, but not including, 6.6.23; 6.7 up to, but not including, 6.7.11; 6.8 up to, but not including, 6.8.24.19.311, 5.4.273, 5.10.214, 5.15.153, 6.1.83, 6.6.23

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.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.8HighNVD
CVSS 3.17.8HighCISA (ADP)

Official description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix hashtab overflow check on 32-bit arches The hashtab code relies on roundup_pow_of_two() to compute the number of hash buckets, and contains an overflow check by checking if the resulting value is 0. However, on 32-bit arches, the roundup code itself can overflow by doing a 32-bit left-shift of an unsigned long value, which is undefined behaviour, so it is not guaranteed to truncate neatly. This was triggered by syzbot on the DEVMAP_HASH type, which contains the same check, copied from the hashtab code. So apply the same fix to hashtab, by moving the overflow check to before the roundup.

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

The underlying weakness: Improper Restriction of Operations within the Bounds of a Memory Buffer

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.

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 Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities (CWE-119)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities

Spotted an error? Tell us.