# CVE-2022-2639: Integer overflow in kernel

> A local attacker can exploit an integer coercion error in the Open vSwitch kernel module to cause an out-of-bounds write, leading to system crashes or privilege escalation.

- **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:** 1 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-2639, GHSA-w6wh-qr7x-h932, OESA-2024-1384, RHSA-2022:8765, RHSA-2022:8767, RHSA-2022:8768, RHSA-2023:0058, RHSA-2023:0059, UBUNTU-CVE-2022-2639

## What is CVE-2022-2639?

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

### Official description

An integer coercion error was found in the openvswitch kernel module. Given a sufficiently large number of actions, while copying and reserving memory for a new action of a new flow, the reserve_sfa_size() function does not return -EMSGSIZE as expected, potentially leading to an out-of-bounds write access. This flaw allows a local user to crash or potentially escalate their privileges on the system.

Weakness: CWE-681 (Incorrect Conversion between Numeric Types), CWE-192 (Integer Coercion Error)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bpftool` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `bpftool-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-abi-whitelists` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-core` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-debug` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-debug-core` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-debug-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-debug-devel` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-debug-modules` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-debug-modules-extra` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-debuginfo-common-ppc64le` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-debuginfo-common-x86_64` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-devel` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-doc` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-modules` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-modules-extra` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-tools` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-tools-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kernel-tools-libs` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `kpatch-patch-4_18_0-147_70_1` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-2.el8_1 |
| `kpatch-patch-4_18_0-147_70_1-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-2.el8_1 |
| `kpatch-patch-4_18_0-147_70_1-debugsource` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-2.el8_1 |
| `kpatch-patch-4_18_0-147_74_1` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-2.el8_1 |
| `kpatch-patch-4_18_0-147_74_1-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-2.el8_1 |
| `kpatch-patch-4_18_0-147_74_1-debugsource` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-2.el8_1 |
| `kpatch-patch-4_18_0-147_76_1` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-1.el8_1 |
| `kpatch-patch-4_18_0-147_76_1-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-1.el8_1 |
| `kpatch-patch-4_18_0-147_76_1-debugsource` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-1.el8_1 |
| `kpatch-patch-4_18_0-147_77_1` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-1.el8_1 |
| `kpatch-patch-4_18_0-147_77_1-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-1.el8_1 |
| `kpatch-patch-4_18_0-147_77_1-debugsource` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-1.el8_1 |
| `perf` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `perf-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `python3-perf` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `python3-perf-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.78.1.el8_1 |
| `bpftool` | Red Hat:rhel_eus:8.4::baseos | All versions | 0:4.18.0-305.72.1.el8_4 |
| `bpftool-debuginfo` | Red Hat:rhel_eus:8.4::baseos | All versions | 0:4.18.0-305.72.1.el8_4 |
| `kernel` | Red Hat:rhel_eus:8.4::baseos | All versions | 0:4.18.0-305.72.1.el8_4 |

Products: Linux kernel, Redhat Enterprise Linux.

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

Apply the vendor's patch.

## Is CVE-2022-2639 being exploited?

There is no known exploitation of CVE-2022-2639 in the wild and no public exploit code.

Public exploit code:

- https://github.com/EkamSinghWalia/Detection-and-Mitigation-for-CVE-2022-2639 (github_poc): https://github.com/EkamSinghWalia/Detection-and-Mitigation-for-CVE-2022-2639
- https://github.com/letsr00t/-2022-LOCALROOT-CVE-2022-2639 (github_poc): https://github.com/letsr00t/-2022-LOCALROOT-CVE-2022-2639
- https://github.com/devetop/CVE-2022-2639-PipeVersion (github_poc): https://github.com/devetop/CVE-2022-2639-PipeVersion
- CVE-2022-2639: Linux kernel openvswitch local privilege escalation. (github_poc): https://github.com/aix567/Aurora

## 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-2639 and fix it if it is affected.

What it is: CVE-2022-2639 is a high-severity vulnerability in Linux kernel, published on 1 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2639 in the wild and no public exploit code.

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-2639/ (Markdown: https://insights.sbomify.com/CVE-2022-2639/index.md)
```

## Sources

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

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