# CVE-2022-1116: Integer overflow in Kernel

> A local attacker can exploit an integer overflow in the Linux Kernel's io_uring to cause memory corruption and escalate privileges to root.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 May 2022
- **Updated:** 21 Apr 2025
- **Also known as:** A-234020136, GHSA-rjw7-cp46-vrpf, PUB-A-234020136, SUSE-SU-2022:3080-1, UBUNTU-CVE-2022-1116

## What is CVE-2022-1116?

CVE-2022-1116 is a high-severity vulnerability in Linux kernel, published on 17 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer Overflow or Wraparound vulnerability in io_uring of Linux Kernel allows local attacker to cause memory corruption and escalate privileges to root. This issue affects: Linux Kernel versions prior to 5.4.189; version 5.4.24 and later versions.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2022-1116?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-livepatch-SLE15-SP3_Update_23` | SUSE:Linux Enterprise Live Patching 15 SP3 | All versions | 2-150300.2.1 |

Products: Linux kernel, Netapp H300s Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware.

## How do I fix CVE-2022-1116?

Apply the vendor's patch.

## Is CVE-2022-1116 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1116 exists.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1116 and fix it if it is affected.

What it is: CVE-2022-1116 is a high-severity vulnerability in Linux kernel, published on 17 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1116 exists.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1116/ (Markdown: https://insights.sbomify.com/CVE-2022-1116/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1116
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1116
- OSV: https://osv.dev/vulnerability/CVE-2022-1116

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1116/
Summaries are generated and may contain mistakes; the official description above is the record.