Linux: Out-of-bounds Write
CVE-2024-50203 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 9e80f366ebfdfafc685fe83a84c34f7ef01cbe88, f521c2a0c0c4585f36d912bf62c852b88682c4f2, 7db1a2121f3c7903b8e397392beec563c3d00950 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.23% 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 9e80f366ebfdfafc685fe83a84c34f7ef01cbe88 or f521c2a0c0c4585f36d912bf62c852b88682c4f2 or 7db1a2121f3c7903b8e397392beec563c3d00950 or a552e2ef5fd1a6c78267cd4ec5a9b49aa11bbb1c, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.11 or 6.11.6, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 077149478497b2f00ff4fd9da2c892defa6418d8 up to, but not including, 9e80f366ebfdfafc685fe83a84c34f7ef01cbe88; d9664e6ff040798a46cdc5d401064f55b8676c83 up to, but not including, f521c2a0c0c4585f36d912bf62c852b88682c4f2; 19d3c179a37730caf600a97fed3794feac2b197b up to, but not including, 7db1a2121f3c7903b8e397392beec563c3d00950; 19d3c179a37730caf600a97fed3794feac2b197b up to, but not including, a552e2ef5fd1a6c78267cd4ec5a9b49aa11bbb1c; 6d218fcc707d6b2c3616b6cd24b948fd4825cfec; 6.10.3 up to, but not including, 6.11; 6.11 | 9e80f366ebfdfafc685fe83a84c34f7ef01cbe88, f521c2a0c0c4585f36d912bf62c852b88682c4f2, 7db1a2121f3c7903b8e397392beec563c3d00950, a552e2ef5fd1a6c78267cd4ec5a9b49aa11bbb1c, 6.11 |
| Linux | Linux Kernel | 6.10.3 up to, but not including, 6.11; 6.11 up to, but not including, 6.11.6; 6.12 | 6.11, 6.11.6 |
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: bpf, arm64: Fix address emission with tag-based KASAN enabled When BPF_TRAMP_F_CALL_ORIG is enabled, the address of a bpf_tramp_image struct on the stack is passed during the size calculation pass and an address on the heap is passed during code generation. This may cause a heap buffer overflow if the heap address is tagged because emit_a64_mov_i64() will emit longer code than it did during the size calculation pass. The same problem could occur without tag-based KASAN if one of the 16-bit words of the stack address happened to be all-ones during the size calculation pass. Fix the problem by assuming the worst case (4 instructions) when calculating the size of the bpf_tramp_image address emission.
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.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Out-of-bounds Write vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.3 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.