# CVE-2022-34918: Memory corruption in n/a

> A local attacker can escalate privileges to root via a type confusion bug in the Linux kernel's nft_set_elem_init function, requiring an unprivileged user namespace.

- **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:** 4 Jul 2022
- **Updated:** 14 Oct 2026
- **Also known as:** AZL-10075, DEBIAN-CVE-2022-34918, GHSA-9v26-h3ph-p8v7, RHSA-2022:6592, UBUNTU-CVE-2022-34918, USN-5545-1, openSUSE-SU-2024:12181-1

## What is CVE-2022-34918?

CVE-2022-34918 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 4 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in the Linux kernel through 5.18.9. A type confusion bug in nft_set_elem_init (leading to a buffer overflow) could be used by a local attacker to escalate privileges, a different vulnerability than CVE-2022-32250. (The attacker can obtain root access, but must start with an unprivileged user namespace to obtain CAP_NET_ADMIN access.) This can be fixed in nft_setelem_parse_data in net/netfilter/nf_tables_api.c.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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

It affects 8 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kpatch-patch-5_14_0-70_13_1` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-2.el9_0 |
| `kpatch-patch-5_14_0-70_13_1-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-2.el9_0 |
| `kpatch-patch-5_14_0-70_13_1-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-2.el9_0 |
| `kpatch-patch-5_14_0-70_17_1` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-1.el9_0 |
| `kpatch-patch-5_14_0-70_17_1-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-1.el9_0 |
| `kpatch-patch-5_14_0-70_17_1-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-1.el9_0 |
| `kpatch-patch-5_14_0-70_22_1` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-1.el9_0 |
| `kpatch-patch-5_14_0-70_22_1-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-1.el9_0 |
| `kpatch-patch-5_14_0-70_22_1-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-1.el9_0 |
| `kernel-source` | openSUSE:Tumbleweed | All versions | 5.18.9-2.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Linux kernel, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware.

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

Apply the vendor's patch.

## Is CVE-2022-34918 being exploited?

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

Public exploit code:

- https://github.com/randorisec/CVE-2022-34918-LPE-PoC (github_poc): https://github.com/randorisec/CVE-2022-34918-LPE-PoC
- CVE-2022-34918 netfilter nf_tables 本地提权 POC (github_poc): https://github.com/veritas501/CVE-2022-34918
- https://github.com/merlinepedra25/CVE-2022-34918-LPE-PoC (github_poc): https://github.com/merlinepedra25/CVE-2022-34918-LPE-PoC
- https://github.com/merlinepedra/CVE-2022-34918-LPE-PoC (github_poc): https://github.com/merlinepedra/CVE-2022-34918-LPE-PoC
- Netfilter nft_set_elem_init Heap Overflow Privilege Escalation (metasploit)
- https://github.com/linulinu/CVE-2022-34918 (github_poc): https://github.com/linulinu/CVE-2022-34918

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34918 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 4 Jul 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-34918 exists.

Affected product: Canonical Ubuntu Linux. 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-34918/ (Markdown: https://insights.sbomify.com/CVE-2022-34918/index.md)
```

## Sources

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

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