Linux: Out-of-bounds Read
CVE-2024-50074 is a high-severity out-of-bounds read 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 8aadef73ba3b325704ed5cfc4696a25c350182cf, b0641e53e6cb937487b6cfb15772374f0ba149b3, 1826b6d69bbb7f9ae8711827facbb2ad7f8d0aaa 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 8aadef73ba3b325704ed5cfc4696a25c350182cf or b0641e53e6cb937487b6cfb15772374f0ba149b3 or 1826b6d69bbb7f9ae8711827facbb2ad7f8d0aaa or 440311903231c6e6c9bcf8acb6a2885a422e00bc, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.10.228 or 5.15.169 or 6.1.114 or 6.6.58, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 166a0bddcc27de41fe13f861c8348e8e53e988c8 up to, but not including, 8aadef73ba3b325704ed5cfc4696a25c350182cf; 47b3dce100778001cd76f7e9188944b5cb27a76d up to, but not including, b0641e53e6cb937487b6cfb15772374f0ba149b3; a44f88f7576bc1916d8d6293f5c62fbe7cbe03e0 up to, but not including, 1826b6d69bbb7f9ae8711827facbb2ad7f8d0aaa; c719b393374d3763e64900ee19aaed767d5a08d6 up to, but not including, 440311903231c6e6c9bcf8acb6a2885a422e00bc; 7f4da759092a1a6ce35fb085182d02de8cc4cc84 up to, but not including, fca048f222ce9dcbde5708ba2bf81d85a4a27952; b579ea3516c371ecf59d073772bc45dfd28c8a0e up to, but not including, 66029078fee00646e2e9dbb8f41ff7819f8e7569; ab11dac93d2d568d151b1918d7b84c2d02bacbd5 up to, but not including, 2a8b26a09c8e3ea03da1ef3cd0ef6b96e559fba6; ab11dac93d2d568d151b1918d7b84c2d02bacbd5 up to, but not including, 02ac3a9ef3a18b58d8f3ea2b6e46de657bf6c4f9; and 9 more ranges | 8aadef73ba3b325704ed5cfc4696a25c350182cf, b0641e53e6cb937487b6cfb15772374f0ba149b3, 1826b6d69bbb7f9ae8711827facbb2ad7f8d0aaa, 440311903231c6e6c9bcf8acb6a2885a422e00bc, fca048f222ce9dcbde5708ba2bf81d85a4a27952, 66029078fee00646e2e9dbb8f41ff7819f8e7569 |
| Linux | Linux Kernel | 5.10.224 up to, but not including, 5.10.228; 5.11 up to, but not including, 5.15.169; 5.16 up to, but not including, 6.1.114; 6.2 up to, but not including, 6.6.58; 6.7 up to, but not including, 6.11.5; 6.12 | 5.10.228, 5.15.169, 6.1.114, 6.6.58, 6.11.5 |
| Red Hat | Enterprise Linux | 8.0; 9.0 | Not stated |
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.8 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: parport: Proper fix for array out-of-bounds access The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf(). However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit. Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/02ac3a9ef3a18b58d8f3ea2b6e46de657bf6c4f9
- git.kernel.org/stable/c/1826b6d69bbb7f9ae8711827facbb2ad7f8d0aaa
- git.kernel.org/stable/c/2a8b26a09c8e3ea03da1ef3cd0ef6b96e559fba6
- git.kernel.org/stable/c/440311903231c6e6c9bcf8acb6a2885a422e00bc
- git.kernel.org/stable/c/66029078fee00646e2e9dbb8f41ff7819f8e7569
- git.kernel.org/stable/c/fca048f222ce9dcbde5708ba2bf81d85a4a27952
Other references
Recent Out-of-bounds Read vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.