Linux: Out-of-bounds Write
CVE-2024-50262 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 e8494ac079814a53fbc2258d2743e720907488ed, 91afbc0eb3c90258ae378ae3c6ead3d2371e926d, 590976f921723d53ac199c01d5b7b73a94875e68 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.27% 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 e8494ac079814a53fbc2258d2743e720907488ed or 91afbc0eb3c90258ae378ae3c6ead3d2371e926d or 590976f921723d53ac199c01d5b7b73a94875e68 or 86c8ebe02d8806dd8878d0063e8e185622ab6ea6, whichever matches your release line, or a later version.
- Update SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 or a later version.
- Update SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to V3.1.5 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | b471f2f1de8b816f1e799b80aa92588f3566e4bd up to, but not including, e8494ac079814a53fbc2258d2743e720907488ed; b471f2f1de8b816f1e799b80aa92588f3566e4bd up to, but not including, 91afbc0eb3c90258ae378ae3c6ead3d2371e926d; b471f2f1de8b816f1e799b80aa92588f3566e4bd up to, but not including, 590976f921723d53ac199c01d5b7b73a94875e68; b471f2f1de8b816f1e799b80aa92588f3566e4bd up to, but not including, 86c8ebe02d8806dd8878d0063e8e185622ab6ea6; b471f2f1de8b816f1e799b80aa92588f3566e4bd up to, but not including, a035df0b98df424559fd383e8e1a268f422ea2ba; b471f2f1de8b816f1e799b80aa92588f3566e4bd up to, but not including, 90a6e0e1e151ef7a9282e78f54c3091de2dcc99c; b471f2f1de8b816f1e799b80aa92588f3566e4bd up to, but not including, c4b4f9a9ab82238cb158fa4fe61a8c0ae21a4980; b471f2f1de8b816f1e799b80aa92588f3566e4bd up to, but not including, 13400ac8fb80c57c2bfb12ebd35ee121ce9b4d21; and 1 more ranges | e8494ac079814a53fbc2258d2743e720907488ed, 91afbc0eb3c90258ae378ae3c6ead3d2371e926d, 590976f921723d53ac199c01d5b7b73a94875e68, 86c8ebe02d8806dd8878d0063e8e185622ab6ea6, a035df0b98df424559fd383e8e1a268f422ea2ba, 90a6e0e1e151ef7a9282e78f54c3091de2dcc99c |
| Siemens | SIMATIC S7-1500 CPU 1518-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Siemens | SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Siemens | SIMATIC S7-1500 TM MFP - GNU/Linux subsystem | before V1.1.1 | V1.1.1 |
| Siemens | SIPLUS S7-1500 CPU 1518-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Siemens | RUGGEDCOM RST2428P | before V3.2 | V3.2 |
| Siemens | SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family | before V3.2 | V3.2 |
| Siemens | SCALANCE XCM-/XRM-/XCH-/XRH-300 family | before V3.2 | V3.2 |
| Linux | Linux Kernel | 4.16 up to, but not including, 4.19.323; 4.20 up to, but not including, 5.4.285; 5.5 up to, but not including, 5.10.229; 5.11 up to, but not including, 5.15.171; 5.16 up to, but not including, 6.1.116; 6.2 up to, but not including, 6.6.60; 6.7 up to, but not including, 6.11.7; 6.12 | 4.19.323, 5.4.285, 5.10.229, 5.15.171, 6.1.116, 6.6.60 |
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 |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix out-of-bounds write in trie_get_next_key() trie_get_next_key() allocates a node stack with size trie->max_prefixlen, while it writes (trie->max_prefixlen + 1) nodes to the stack when it has full paths from the root to leaves. For example, consider a trie with max_prefixlen is 8, and the nodes with key 0x00/0, 0x00/1, 0x00/2, ... 0x00/8 inserted. Subsequent calls to trie_get_next_key with _key with .prefixlen = 8 make 9 nodes be written on the node stack with size 8.
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
- git.kernel.org/stable/c/13400ac8fb80c57c2bfb12ebd35ee121ce9b4d21
- git.kernel.org/stable/c/590976f921723d53ac199c01d5b7b73a94875e68
- git.kernel.org/stable/c/86c8ebe02d8806dd8878d0063e8e185622ab6ea6
- git.kernel.org/stable/c/90a6e0e1e151ef7a9282e78f54c3091de2dcc99c
- git.kernel.org/stable/c/91afbc0eb3c90258ae378ae3c6ead3d2371e926d
- git.kernel.org/stable/c/a035df0b98df424559fd383e8e1a268f422ea2ba
- git.kernel.org/stable/c/c4b4f9a9ab82238cb158fa4fe61a8c0ae21a4980
- git.kernel.org/stable/c/e8494ac079814a53fbc2258d2743e720907488ed
Other references
Recent Out-of-bounds Write vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.3 High severity
Spotted an error? Tell us.