Linux: Integer Overflow or Wraparound
CVE-2022-49289 is a high-severity integer overflow or wraparound vulnerability in Linux, with a CVSS 3.1 base score of 7.1 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 e65d28d4e9bf90a35ba79c06661a572a38391dec, 99801e2f457824955da4aadaa035913a6dede03a, a1ad747fc1a0e06d1bf26b996ee8a56b5c8d02d8 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 e65d28d4e9bf90a35ba79c06661a572a38391dec or 99801e2f457824955da4aadaa035913a6dede03a or a1ad747fc1a0e06d1bf26b996ee8a56b5c8d02d8 or 222ca305c9fd39e5ed8104da25c09b2b79a516a8, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.15.32 or 5.16.18, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 7567746e1c0d66ac0ef8a9d8816ca694462c7370 up to, but not including, e65d28d4e9bf90a35ba79c06661a572a38391dec; 7567746e1c0d66ac0ef8a9d8816ca694462c7370 up to, but not including, 99801e2f457824955da4aadaa035913a6dede03a; 7567746e1c0d66ac0ef8a9d8816ca694462c7370 up to, but not including, a1ad747fc1a0e06d1bf26b996ee8a56b5c8d02d8; 7567746e1c0d66ac0ef8a9d8816ca694462c7370 up to, but not including, 222ca305c9fd39e5ed8104da25c09b2b79a516a8; 3.2 | e65d28d4e9bf90a35ba79c06661a572a38391dec, 99801e2f457824955da4aadaa035913a6dede03a, a1ad747fc1a0e06d1bf26b996ee8a56b5c8d02d8, 222ca305c9fd39e5ed8104da25c09b2b79a516a8 |
| Linux | Linux Kernel | 3.2 up to, but not including, 5.15.32; 5.16 up to, but not including, 5.16.18; 5.17 | 5.15.32, 5.16.18 |
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
- NoneNothing can be modified.
- 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:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.1 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: uaccess: fix integer overflow on access_ok() Three architectures check the end of a user access against the address limit without taking a possible overflow into account. Passing a negative length or another overflow in here returns success when it should not. Use the most common correct implementation here, which optimizes for a constant 'size' argument, and turns the common case into a single comparison.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Integer Overflow or Wraparound
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How developers prevent this class of flaw
- Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).
More Integer Overflow or Wraparound vulnerabilities (CWE-190)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Integer Overflow or Wraparound vulnerabilities
- 9.8 Critical severity
- 7.1 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.3 High severity
- 8.4 High severity
Spotted an error? Tell us.