CyberSecBulletin
CVE-2024-46729NVD status: Analyzed

Linux: Incorrect Calculation of Buffer Size

CVE-2024-46729 is a high-severity incorrect calculation of buffer size 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 712be65b3b372a82bff0865b9c090147764bf1c4, 3941a3aa4b653b69876d894d08f3fff1cc965267 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.21% 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 712be65b3b372a82bff0865b9c090147764bf1c4 or 3941a3aa4b653b69876d894d08f3fff1cc965267, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.10.9 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c up to, but not including, 712be65b3b372a82bff0865b9c090147764bf1c4; 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c up to, but not including, 3941a3aa4b653b69876d894d08f3fff1cc965267; 4.15712be65b3b372a82bff0865b9c090147764bf1c4, 3941a3aa4b653b69876d894d08f3fff1cc965267
LinuxLinux Kernel4.15 up to, but not including, 6.10.96.10.9

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.

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix incorrect size calculation for loop [WHY] fe_clk_en has size of 5 but sizeof(fe_clk_en) has byte size 20 which is lager than the array size. [HOW] Divide byte size 20 by its element size. This fixes 2 OVERRUN issues reported by Coverity.

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

The underlying weakness: Incorrect Calculation of Buffer Size

The product does not correctly calculate the size to be used when allocating a buffer.

How developers prevent this class of flaw

  • When allocating a buffer for the purpose of transforming, converting, or encoding an input, allocate enough memory to handle the largest possible encoding. For example, in a routine that converts & characters to & for HTML entity encoding, the output buffer needs to be at least 5 times as large as the input buffer.
  • Understand the programming language's underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, not-a-number calculations, and how the language handles numbers that are too large or too small for its underlying representation. Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.
  • Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.

More Incorrect Calculation of Buffer Size vulnerabilities (CWE-131)

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 Incorrect Calculation of Buffer Size vulnerabilities

Spotted an error? Tell us.