Linux: Out-of-bounds Write
CVE-2024-53106 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 e01aae58e818503f2ffcd34c6f7dc6f90af1057e, 8a84765c62cc0469864e2faee43aae253ad16082, 1ecf0df5205cfb0907eb7984b8671257965a5232 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.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to e01aae58e818503f2ffcd34c6f7dc6f90af1057e or 8a84765c62cc0469864e2faee43aae253ad16082 or 1ecf0df5205cfb0907eb7984b8671257965a5232 or 923168a0631bc42fffd55087b337b1b6c54dcff5, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.1.119 or 6.6.63 or 6.11.10, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 9fab303a2cb3d323ca3a32a8b4ab60b451141901 up to, but not including, e01aae58e818503f2ffcd34c6f7dc6f90af1057e; 9fab303a2cb3d323ca3a32a8b4ab60b451141901 up to, but not including, 8a84765c62cc0469864e2faee43aae253ad16082; 9fab303a2cb3d323ca3a32a8b4ab60b451141901 up to, but not including, 1ecf0df5205cfb0907eb7984b8671257965a5232; 9fab303a2cb3d323ca3a32a8b4ab60b451141901 up to, but not including, 923168a0631bc42fffd55087b337b1b6c54dcff5; 5.19 | e01aae58e818503f2ffcd34c6f7dc6f90af1057e, 8a84765c62cc0469864e2faee43aae253ad16082, 1ecf0df5205cfb0907eb7984b8671257965a5232, 923168a0631bc42fffd55087b337b1b6c54dcff5 |
| Linux | Linux Kernel | 5.19.1 up to, but not including, 6.1.119; 6.2 up to, but not including, 6.6.63; 6.7 up to, but not including, 6.11.10; 5.19; 6.12 | 6.1.119, 6.6.63, 6.11.10 |
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 system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.3 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: ima: fix buffer overrun in ima_eventdigest_init_common Function ima_eventdigest_init() calls ima_eventdigest_init_common() with HASH_ALGO__LAST which is then used to access the array hash_digest_size[] leading to buffer overrun. Have a conditional statement to handle this.
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.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Out-of-bounds Write vulnerabilities
- 8.1 High severity
- 7.8 High severity
Linux Kernel Out-of-Bounds Write Exploited
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.