CyberSecBulletin
CVE-2024-57850NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-57850 is a high-severity out-of-bounds write 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 421f9e9f0fae9f8e721ffa07f22d9765fa1214d5, f6fc251baefc3cdc4f41f2f5a47940d7d4a67332, bd384b04ad1995441b18fe6c1366d02de8c5d5eb 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.26% 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 421f9e9f0fae9f8e721ffa07f22d9765fa1214d5 or f6fc251baefc3cdc4f41f2f5a47940d7d4a67332 or bd384b04ad1995441b18fe6c1366d02de8c5d5eb or 47c9a7f81027a78afea9d2e9a54bfd8fabb6b3d0, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.4.287 or 5.10.231 or 5.15.174 or 6.1.120, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 421f9e9f0fae9f8e721ffa07f22d9765fa1214d5; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, f6fc251baefc3cdc4f41f2f5a47940d7d4a67332; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, bd384b04ad1995441b18fe6c1366d02de8c5d5eb; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 47c9a7f81027a78afea9d2e9a54bfd8fabb6b3d0; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 6808a1812a3419542223e7fe9e2de577e99e45d1; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, dc39b08fcc3831b0bc46add91ba93cd2aab50716; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, fe051552f5078fa02d593847529a3884305a6ffe; 2.6.12421f9e9f0fae9f8e721ffa07f22d9765fa1214d5, f6fc251baefc3cdc4f41f2f5a47940d7d4a67332, bd384b04ad1995441b18fe6c1366d02de8c5d5eb, 47c9a7f81027a78afea9d2e9a54bfd8fabb6b3d0, 6808a1812a3419542223e7fe9e2de577e99e45d1, dc39b08fcc3831b0bc46add91ba93cd2aab50716
LinuxLinux Kernelbefore 5.4.287; 5.5 up to, but not including, 5.10.231; 5.11 up to, but not including, 5.15.174; 5.16 up to, but not including, 6.1.120; 6.2 up to, but not including, 6.6.66; 6.7 up to, but not including, 6.12.55.4.287, 5.10.231, 5.15.174, 6.1.120, 6.6.66, 6.12.5

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: jffs2: Prevent rtime decompress memory corruption The rtime decompression routine does not fully check bounds during the entirety of the decompression pass and can corrupt memory outside the decompression buffer if the compressed data is corrupted. This adds the required check to prevent this failure mode.

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: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.