CyberSecBulletin
CVE-2024-50230NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-50230 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 994b2fa13a6c9cf3feca93090a9c337d48e3d60d, 64afad73e4623308d8943645e5631f2c7a2d7971, aa0cee46c5d3fd9a39575a4c8a4f65f25f095b89 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 994b2fa13a6c9cf3feca93090a9c337d48e3d60d or 64afad73e4623308d8943645e5631f2c7a2d7971 or aa0cee46c5d3fd9a39575a4c8a4f65f25f095b89 or f05dbebb8ee34882505d53d83af7d18f28a49248, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.19.323 or 5.4.285 or 5.10.229 or 5.15.171, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux8c26c4e2694a163d525976e804d81cd955bbb40c up to, but not including, 994b2fa13a6c9cf3feca93090a9c337d48e3d60d; 8c26c4e2694a163d525976e804d81cd955bbb40c up to, but not including, 64afad73e4623308d8943645e5631f2c7a2d7971; 8c26c4e2694a163d525976e804d81cd955bbb40c up to, but not including, aa0cee46c5d3fd9a39575a4c8a4f65f25f095b89; 8c26c4e2694a163d525976e804d81cd955bbb40c up to, but not including, f05dbebb8ee34882505d53d83af7d18f28a49248; 8c26c4e2694a163d525976e804d81cd955bbb40c up to, but not including, cd0cdb51b15203fa27d4b714be83b7dfffa0b752; 8c26c4e2694a163d525976e804d81cd955bbb40c up to, but not including, f2f1fa446676c21edb777e6d2bc4fa8f956fab68; 8c26c4e2694a163d525976e804d81cd955bbb40c up to, but not including, 56c6171932a7fb267ac6cb4ff8759b93ee1d0e2e; 8c26c4e2694a163d525976e804d81cd955bbb40c up to, but not including, 41e192ad2779cae0102879612dfe46726e4396aa; and 1 more ranges994b2fa13a6c9cf3feca93090a9c337d48e3d60d, 64afad73e4623308d8943645e5631f2c7a2d7971, aa0cee46c5d3fd9a39575a4c8a4f65f25f095b89, f05dbebb8ee34882505d53d83af7d18f28a49248, cd0cdb51b15203fa27d4b714be83b7dfffa0b752, f2f1fa446676c21edb777e6d2bc4fa8f956fab68
LinuxLinux Kernel3.10 up to, but not including, 4.19.323; 4.20 up to, but not including, 5.4.285; 5.5 up to, but not including, 5.10.229; 5.11 up to, but not including, 5.15.171; 5.16 up to, but not including, 6.1.116; 6.2 up to, but not including, 6.6.60; 6.7 up to, but not including, 6.11.7; 6.124.19.323, 5.4.285, 5.10.229, 5.15.171, 6.1.116, 6.6.60

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: nilfs2: fix kernel bug due to missing clearing of checked flag Syzbot reported that in directory operations after nilfs2 detects filesystem corruption and degrades to read-only, __block_write_begin_int(), which is called to prepare block writes, may fail the BUG_ON check for accesses exceeding the folio/page size, triggering a kernel bug. This was found to be because the "checked" flag of a page/folio was not cleared when it was discarded by nilfs2's own routine, which causes the sanity check of directory entries to be skipped when the directory page/folio is reloaded. So, fix that. This was necessary when the use of nilfs2's own page discard routine was applied to more than just metadata files.

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.