kernel: Out-of-bounds Write
CVE-2022-0435 is a high-severity out-of-bounds write vulnerability in kernel, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected kernel versions: kernel 5.17-rc4. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 67.8% chance of exploitation within 30 days, which is in the top 0.67% of all scored CVEs.
Exploitation in the next 30 days is more likely than not, according to EPSS.
What to do
- Update Linux Kernel to 4.9.301 or 4.14.266 or 4.19.229 or 5.4.179, whichever matches your release line, or a later version.
Affected products and versions
Version data comes from the organisation that assigned the CVE; 6 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- 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:N/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 | 8.8 | High | NVD |
| CVSS 2.0 | 9.0 | High | NVD |
Official description
A stack overflow flaw was found in the Linux kernel's TIPC protocol functionality in the way a user sends a packet with malicious content where the number of domain member nodes is higher than the 64 allowed. This flaw allows a remote user to crash the system or possibly escalate their privileges if they have access to the TIPC network.
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
- bugzilla.redhat.com/show_bug.cgi?id=2048738Issue Tracking, Third Party Advisory
- openwall.com/lists/oss-security/2022/02/10/1Exploit, Mailing List, Mitigation, Third Party Advisory
Third-party and government advisories
- security.netapp.com/advisory/ntap-20220602-0001/Third Party Advisory
Other vulnerabilities in kernel
- 7.5 High severity
- 7.8 High severity
- 8.1 High severity
- 7.1 High severity
- 8.1 High severity
- 8.1 High severity
Recent Out-of-bounds Write vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
Linux Kernel Out-of-Bounds Write Exploited
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.