CyberSecBulletin
CVE-2024-27045NVD status: Modified

Linux: Buffer Copy without Checking Size of Input

Published Updated By the CyberSecBulletin desk

CVE-2024-27045 is a high-severity buffer copy without checking size of input 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 ff28893c96c5e0927a4da10cd24a3522ca663515, 440f059837418fac1695b65d3ebc6080d33be877, d346b3e5b25c95d504478507eb867cd3818775ab 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.31% 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 ff28893c96c5e0927a4da10cd24a3522ca663515 or 440f059837418fac1695b65d3ebc6080d33be877 or d346b3e5b25c95d504478507eb867cd3818775ab or ad76fd30557d6a106c481e4606a981221ca525f7, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.214 or 5.15.153 or 6.1.83 or 6.6.23, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxc06e09b76639657f284bfaf1cce29557a2515e85 up to, but not including, ff28893c96c5e0927a4da10cd24a3522ca663515; c06e09b76639657f284bfaf1cce29557a2515e85 up to, but not including, 440f059837418fac1695b65d3ebc6080d33be877; c06e09b76639657f284bfaf1cce29557a2515e85 up to, but not including, d346b3e5b25c95d504478507eb867cd3818775ab; c06e09b76639657f284bfaf1cce29557a2515e85 up to, but not including, ad76fd30557d6a106c481e4606a981221ca525f7; c06e09b76639657f284bfaf1cce29557a2515e85 up to, but not including, eb9327af3621d26b1d83f767c97a3fe8191a3a65; c06e09b76639657f284bfaf1cce29557a2515e85 up to, but not including, cf114d8d4a8d78df272116a745bb43b48cef65f4; c06e09b76639657f284bfaf1cce29557a2515e85 up to, but not including, 4b09715f1504f1b6e8dff0e9643630610bc05141; 5.9ff28893c96c5e0927a4da10cd24a3522ca663515, 440f059837418fac1695b65d3ebc6080d33be877, d346b3e5b25c95d504478507eb867cd3818775ab, ad76fd30557d6a106c481e4606a981221ca525f7, eb9327af3621d26b1d83f767c97a3fe8191a3a65, cf114d8d4a8d78df272116a745bb43b48cef65f4
LinuxLinux Kernel5.9 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.25.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.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.17.0HighCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix a potential buffer overflow in 'dp_dsc_clock_en_read()' Tell snprintf() to store at most 10 bytes in the output buffer instead of 30. Fixes the below: drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_debugfs.c:1508 dp_dsc_clock_en_read() error: snprintf() is printing too much 30 vs 10

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

The underlying weakness: Buffer Copy without Checking Size of Input

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output 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 Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)

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 Buffer Copy without Checking Size of Input vulnerabilities

Spotted an error? Tell us.