CyberSecBulletin
CVE-2024-47670NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-47670 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 b49a786beb11ff740cb9e0c20b999c2a0e1729c2, 60c0d36189bad58b1a8e69af8781d90009559ea1, 34759b7e4493d7337cbc414c132cef378c492a2c 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.24% 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 b49a786beb11ff740cb9e0c20b999c2a0e1729c2 or 60c0d36189bad58b1a8e69af8781d90009559ea1 or 34759b7e4493d7337cbc414c132cef378c492a2c or 5bbe51eaf01a5dd6fb3f0dea81791e5dbc6dc6dd, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.112 or 6.6.53 or 6.10.12, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxcf1d6c763fbcb115263114302485ad17e7933d87 up to, but not including, b49a786beb11ff740cb9e0c20b999c2a0e1729c2; cf1d6c763fbcb115263114302485ad17e7933d87 up to, but not including, 60c0d36189bad58b1a8e69af8781d90009559ea1; cf1d6c763fbcb115263114302485ad17e7933d87 up to, but not including, 34759b7e4493d7337cbc414c132cef378c492a2c; cf1d6c763fbcb115263114302485ad17e7933d87 up to, but not including, 5bbe51eaf01a5dd6fb3f0dea81791e5dbc6dc6dd; cf1d6c763fbcb115263114302485ad17e7933d87 up to, but not including, 9b32539590a8e6400ac2f6e7cf9cbb8e08711a2f; cf1d6c763fbcb115263114302485ad17e7933d87 up to, but not including, 1f6e167d6753fe3ea493cdc7f7de8d03147a4d39; cf1d6c763fbcb115263114302485ad17e7933d87 up to, but not including, 8e7bef408261746c160853fc27df3139659f5f77; cf1d6c763fbcb115263114302485ad17e7933d87 up to, but not including, 9e3041fecdc8f78a5900c3aa51d3d756e73264d6; and 1 more rangesb49a786beb11ff740cb9e0c20b999c2a0e1729c2, 60c0d36189bad58b1a8e69af8781d90009559ea1, 34759b7e4493d7337cbc414c132cef378c492a2c, 5bbe51eaf01a5dd6fb3f0dea81791e5dbc6dc6dd, 9b32539590a8e6400ac2f6e7cf9cbb8e08711a2f, 1f6e167d6753fe3ea493cdc7f7de8d03147a4d39
LinuxLinux Kernelbefore 6.1.112; 6.2 up to, but not including, 6.6.53; 6.7 up to, but not including, 6.10.126.1.112, 6.6.53, 6.10.12

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

Official description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: add bounds checking to ocfs2_xattr_find_entry() Add a paranoia check to make sure it doesn't stray beyond valid memory region containing ocfs2 xattr entries when scanning for a match. It will prevent out-of-bound access in case of crafted images.

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.