CyberSecBulletin
CVE-2024-47695NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-47695 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 0429a4e972082e3a2351da414b1c017daaf8aed2, 5ac73f8191f3de41fef4f934d84d97f3aadb301f, 01b9be936ee8839ab9f83a7e84ee02ac6c8303c4 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.69% chance of exploitation within 30 days, higher than 53% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 0429a4e972082e3a2351da414b1c017daaf8aed2 or 5ac73f8191f3de41fef4f934d84d97f3aadb301f or 01b9be936ee8839ab9f83a7e84ee02ac6c8303c4 or 1c50e0265fa332c94a4a182e4efa0fc70d8fad94, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.15.168 or 6.1.113 or 6.6.54 or 6.10.13, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux6a98d71daea186247005099758af549e6afdd244 up to, but not including, 0429a4e972082e3a2351da414b1c017daaf8aed2; 6a98d71daea186247005099758af549e6afdd244 up to, but not including, 5ac73f8191f3de41fef4f934d84d97f3aadb301f; 6a98d71daea186247005099758af549e6afdd244 up to, but not including, 01b9be936ee8839ab9f83a7e84ee02ac6c8303c4; 6a98d71daea186247005099758af549e6afdd244 up to, but not including, 1c50e0265fa332c94a4a182e4efa0fc70d8fad94; 6a98d71daea186247005099758af549e6afdd244 up to, but not including, c8b7f3d9fada0d4b4b7db86bf7345cd61f1d972e; 6a98d71daea186247005099758af549e6afdd244 up to, but not including, 3e4289b29e216a55d08a89e126bc0b37cbad9f38; 5.80429a4e972082e3a2351da414b1c017daaf8aed2, 5ac73f8191f3de41fef4f934d84d97f3aadb301f, 01b9be936ee8839ab9f83a7e84ee02ac6c8303c4, 1c50e0265fa332c94a4a182e4efa0fc70d8fad94, c8b7f3d9fada0d4b4b7db86bf7345cd61f1d972e, 3e4289b29e216a55d08a89e126bc0b37cbad9f38
LinuxLinux Kernel5.8 up to, but not including, 5.15.168; 5.16 up to, but not including, 6.1.113; 6.2 up to, but not including, 6.6.54; 6.7 up to, but not including, 6.10.13; 6.11 up to, but not including, 6.11.25.15.168, 6.1.113, 6.6.54, 6.10.13, 6.11.2

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.19.8CriticalCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path->s.con_num. This commits resets the cid to clt_path->s.con_num - 1, to stay in bounds in the cleanup loop later.

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.