Linux: Out-of-bounds Write
CVE-2022-50040 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 7983e1e44cb322eba6af84160b6d18df80603fb8, e84c6321f3578c38cb3c24258db91a92672b17a8, 79f86b862416126a2e826cb74224180d6625a32f 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.29% 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 7983e1e44cb322eba6af84160b6d18df80603fb8 or e84c6321f3578c38cb3c24258db91a92672b17a8 or 79f86b862416126a2e826cb74224180d6625a32f or fd8e899cdb5ecaf8e8ee73854a99e10807eef1de, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.10.138 or 5.15.63 or 5.19.4, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | bf425b82059e0b0752c0026353c1902112200837 up to, but not including, 7983e1e44cb322eba6af84160b6d18df80603fb8; bf425b82059e0b0752c0026353c1902112200837 up to, but not including, e84c6321f3578c38cb3c24258db91a92672b17a8; bf425b82059e0b0752c0026353c1902112200837 up to, but not including, 79f86b862416126a2e826cb74224180d6625a32f; bf425b82059e0b0752c0026353c1902112200837 up to, but not including, fd8e899cdb5ecaf8e8ee73854a99e10807eef1de; 5.10 | 7983e1e44cb322eba6af84160b6d18df80603fb8, e84c6321f3578c38cb3c24258db91a92672b17a8, 79f86b862416126a2e826cb74224180d6625a32f, fd8e899cdb5ecaf8e8ee73854a99e10807eef1de |
| Linux | Linux Kernel | 5.10 up to, but not including, 5.10.138; 5.11 up to, but not including, 5.15.63; 5.16 up to, but not including, 5.19.4; 6.0 | 5.10.138, 5.15.63, 5.19.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 NVD.
Official description
In the Linux kernel, the following vulnerability has been resolved: net: dsa: sja1105: fix buffer overflow in sja1105_setup_devlink_regions() If an error occurs in dsa_devlink_region_create(), then 'priv->regions' array will be accessed by negative index '-1'. Found by Linux Verification Center (linuxtesting.org) with SVACE.
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
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.8 High severity
Spotted an error? Tell us.