Linux Kernel: Out-of-bounds Write
CVE-2022-27666 is a high-severity out-of-bounds write vulnerability in Linux Kernel from 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 4.14.274, 4.19.237, 5.4.188 as the first without the flaw, so updating Linux Kernel to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 5.52% chance of exploitation within 30 days, which is in the top 7.06% of all scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux Kernel to 4.14.274 or 4.19.237 or 5.4.188 or 5.10.108, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux Kernel | 4.11 up to, but not including, 4.14.274; 4.15 up to, but not including, 4.19.237; 4.20 up to, but not including, 5.4.188; 5.5 up to, but not including, 5.10.108; 5.11 up to, but not including, 5.15.29; 5.16 up to, but not including, 5.16.15; 5.17 | 4.14.274, 4.19.237, 5.4.188, 5.10.108, 5.15.29, 5.16.15 |
| Fedora Project | Fedora | 34; 35 | Not stated |
| Red Hat | Virtualization | 4.0 | Not stated |
| Red Hat | Enterprise Linux | 8.0 | Not stated |
| NetApp | H300s Firmware | Not specified in the record | Not stated |
| NetApp | H500s Firmware | Not specified in the record | Not stated |
| NetApp | H700s Firmware | Not specified in the record | Not stated |
| NetApp | H300e Firmware | Not specified in the record | Not stated |
| NetApp | H500e Firmware | Not specified in the record | Not stated |
| NetApp | H700e Firmware | Not specified in the record | Not stated |
| NetApp | H410s Firmware | Not specified in the record | Not stated |
| NetApp | H410c Firmware | Not specified in the record | Not stated |
| Debian | Debian Linux | 9.0; 10.0; 11.0 | Not stated |
Version data comes from NVD's product matching. 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 | NVD |
| CVSS 2.0 | 4.6 | Medium | NVD |
Official description
A heap buffer overflow flaw was found in IPsec ESP transformation code in net/ipv4/esp4.c and net/ipv6/esp6.c. This flaw allows a local attacker with a normal user privilege to overwrite kernel heap objects and may cause a local privilege escalation threat.
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=2061633Issue Tracking, Third Party Advisory
- github.com/torvalds/linux/commit/ebe48d368e97d007bfeb76fcb065d6cfc4c96645Third Party Advisory
Third-party and government advisories
- security.netapp.com/advisory/ntap-20220429-0001/Third Party Advisory
- debian.org/security/2022/dsa-5127Third Party Advisory
- debian.org/security/2022/dsa-5173Third Party Advisory
Other vulnerabilities in Linux Kernel
- 9.8 Critical severity
- 7.0 High severity
- 7.8 High severity
- 7.1 High severity
- 7.0 High severity
- 7.8 High severity
Recent Out-of-bounds Write vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 9.3 High severity
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
Spotted an error? Tell us.