Linux: Integer Overflow or Wraparound
CVE-2022-49030 is a high-severity integer overflow or wraparound 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 8a549ab6724520aa3c07f47e0eba820293551490, 0140e079a42064680394fff1199a7b5483688dec, 535a25ab4f9a45f74ba38ab71de95e97474922ed 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.28% 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 8a549ab6724520aa3c07f47e0eba820293551490 or 0140e079a42064680394fff1199a7b5483688dec or 535a25ab4f9a45f74ba38ab71de95e97474922ed or 927cbb478adf917e0a142b94baa37f06279cc466, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.10.158 or 5.15.82 or 6.0.12, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | bf99c936f9478a05d51e9f101f90de70bee9a89c up to, but not including, 8a549ab6724520aa3c07f47e0eba820293551490; bf99c936f9478a05d51e9f101f90de70bee9a89c up to, but not including, 0140e079a42064680394fff1199a7b5483688dec; bf99c936f9478a05d51e9f101f90de70bee9a89c up to, but not including, 535a25ab4f9a45f74ba38ab71de95e97474922ed; bf99c936f9478a05d51e9f101f90de70bee9a89c up to, but not including, 927cbb478adf917e0a142b94baa37f06279cc466; 5.8 | 8a549ab6724520aa3c07f47e0eba820293551490, 0140e079a42064680394fff1199a7b5483688dec, 535a25ab4f9a45f74ba38ab71de95e97474922ed, 927cbb478adf917e0a142b94baa37f06279cc466 |
| Linux | Linux Kernel | 5.8 up to, but not including, 5.10.158; 5.11 up to, but not including, 5.15.82; 5.16 up to, but not including, 6.0.12; 6.1 | 5.10.158, 5.15.82, 6.0.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: libbpf: Handle size overflow for ringbuf mmap The maximum size of ringbuf is 2GB on x86-64 host, so 2 * max_entries will overflow u32 when mapping producer page and data pages. Only casting max_entries to size_t is not enough, because for 32-bits application on 64-bits kernel the size of read-only mmap region also could overflow size_t. So fixing it by casting the size of read-only mmap region into a __u64 and checking whether or not there will be overflow during mmap.
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.
- 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
Recent Integer Overflow or Wraparound vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
- 7.5 High severity
Spotted an error? Tell us.