Linux: Out-of-bounds Write
CVE-2022-48632 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 48ee0a864d1af02eea98fc825cc230d61517a71e, dc2a0c587006f29b724069740c48654b9dcaebd2, 3b5ab5fbe69ebbee5692c72b05071a43fc0655d8 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.26% 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 48ee0a864d1af02eea98fc825cc230d61517a71e or dc2a0c587006f29b724069740c48654b9dcaebd2 or 3b5ab5fbe69ebbee5692c72b05071a43fc0655d8 or de24aceb07d426b6f1c59f33889d6a964770547b, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.10.146 or 5.15.71 or 5.19.12, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | b5b5b32081cd206baa6e58cca7f112d9723785d6 up to, but not including, 48ee0a864d1af02eea98fc825cc230d61517a71e; b5b5b32081cd206baa6e58cca7f112d9723785d6 up to, but not including, dc2a0c587006f29b724069740c48654b9dcaebd2; b5b5b32081cd206baa6e58cca7f112d9723785d6 up to, but not including, 3b5ab5fbe69ebbee5692c72b05071a43fc0655d8; b5b5b32081cd206baa6e58cca7f112d9723785d6 up to, but not including, de24aceb07d426b6f1c59f33889d6a964770547b; 5.10 | 48ee0a864d1af02eea98fc825cc230d61517a71e, dc2a0c587006f29b724069740c48654b9dcaebd2, 3b5ab5fbe69ebbee5692c72b05071a43fc0655d8, de24aceb07d426b6f1c59f33889d6a964770547b |
| Linux | Linux Kernel | 5.10 up to, but not including, 5.10.146; 5.11 up to, but not including, 5.15.71; 5.16 up to, but not including, 5.19.12; 6.0 | 5.10.146, 5.15.71, 5.19.12 |
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: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() memcpy() is called in a loop while 'operation->length' upper bound is not checked and 'data_idx' also increments.
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: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/3b5ab5fbe69ebbee5692c72b05071a43fc0655d8Mailing List
- git.kernel.org/stable/c/48ee0a864d1af02eea98fc825cc230d61517a71eMailing List
- git.kernel.org/stable/c/dc2a0c587006f29b724069740c48654b9dcaebd2Mailing List
- git.kernel.org/stable/c/de24aceb07d426b6f1c59f33889d6a964770547bMailing List
Recent Out-of-bounds Write vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.