Linux: Buffer Copy without Checking Size of Input
CVE-2024-56557 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 6e4d236d9c4b38571c394d3ab6e85dfb71c33ed3, 00663d3e000c31d0d49ef86a809f5c107c2d09cd, e5cac32721997cb8bcb208a29f4598b3faf46338 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.25% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 6e4d236d9c4b38571c394d3ab6e85dfb71c33ed3 or 00663d3e000c31d0d49ef86a809f5c107c2d09cd or e5cac32721997cb8bcb208a29f4598b3faf46338 or 218ecc35949129171ca39bcc0d407c8dc4cd0bbc, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.1.120 or 6.6.64 or 6.12.4, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 851644a60d200c9a294de5a5594004bcf13d34c7 up to, but not including, 6e4d236d9c4b38571c394d3ab6e85dfb71c33ed3; 851644a60d200c9a294de5a5594004bcf13d34c7 up to, but not including, 00663d3e000c31d0d49ef86a809f5c107c2d09cd; 851644a60d200c9a294de5a5594004bcf13d34c7 up to, but not including, e5cac32721997cb8bcb208a29f4598b3faf46338; 851644a60d200c9a294de5a5594004bcf13d34c7 up to, but not including, 218ecc35949129171ca39bcc0d407c8dc4cd0bbc; 851644a60d200c9a294de5a5594004bcf13d34c7 up to, but not including, 3a4187ec454e19903fd15f6e1825a4b84e59a4cd; 5.6 | 6e4d236d9c4b38571c394d3ab6e85dfb71c33ed3, 00663d3e000c31d0d49ef86a809f5c107c2d09cd, e5cac32721997cb8bcb208a29f4598b3faf46338, 218ecc35949129171ca39bcc0d407c8dc4cd0bbc, 3a4187ec454e19903fd15f6e1825a4b84e59a4cd |
| Linux | Linux Kernel | 5.6 up to, but not including, 6.1.120; 6.2 up to, but not including, 6.6.64; 6.7 up to, but not including, 6.12.4 | 6.1.120, 6.6.64, 6.12.4 |
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 CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 5.5 | Medium | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad7923: Fix buffer overflow for tx_buf and ring_xfer The AD7923 was updated to support devices with 8 channels, but the size of tx_buf and ring_xfer was not increased accordingly, leading to a potential buffer overflow in ad7923_update_scan_mode().
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
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Buffer Copy without Checking Size of Input vulnerabilities
- 7.8 High severity
- 9.3 Critical severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.