dbcve.org
Linux KernelOperating system · Linux

CVE-2022-34918

HIGH · 7.8 CVSS v3.1 Published 2022-07-04
Fix available
A fix is available. Upgrade to 4.14.316 / 4.19.284 or later.
See remediation →
80/100
Remediation priority · High
Public exploit Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-843

A resource is accessed as one type when it was actually allocated as another, so the code misreads memory layout — in interpreters and language runtimes this is frequently a direct path to code execution. It often arises from unchecked casts on attacker-influenced objects. The fix is strict type checks before casts and memory-safe access patterns.

General guidance for the type confusion class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.1, < 4.14.316>= 4.15, < 4.19.284>= 4.20, < 5.4.244>= 5.5, < 5.10.130>= 5.11, < 5.15.54>= 5.16, < 5.18.11
Debian LinuxOperating system
Affected:= 11.0
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 18.04= 20.04= 22.04
H300s FirmwareOperating system
Affected:all versions
H500s FirmwareOperating system
Affected:all versions
H700s FirmwareOperating system
Affected:all versions
H410s FirmwareOperating system
Affected:all versions
H410c FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.14.316 / 4.19.284 / 5.4.244 or later
Fixed in 4.14.3164.19.2845.4.244
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to Linux kernel >= 5.10.130, or >= 5.4.244, or >= 4.19.284, or >= 4.14.316 depending on your stable branch; for Ubuntu use 5.10.0-131 or later from updates; for Debian use 5.10.0-10+deb11u1 or later

  1. 1. Identify the current running kernel version using 'uname -r'
  2. 2. Check if your distribution has released a kernel update that includes the fix for CVE-2022-34918
  3. 3. For Debian 11 (Bullseye): Update kernel packages via 'apt update && apt install linux-image-$(uname -r | sed 's/-.*//')' or 'apt full-upgrade'
  4. 4. For Ubuntu: Apply available kernel updates via 'sudo apt update && sudo apt upgrade linux-image-generic'
  5. 5. Reboot the system to load the fixed kernel: 'sudo reboot'
  6. 6. After reboot, verify the kernel version includes the fix by checking 'cat /proc/version' or 'uname -a'
  7. 7. Confirm the kernel version is >= 5.10.130 (or >= 5.4.244, >= 4.19.284, or >= 4.14.316 depending on your major version series)
Caveat Kernel upgrades may require rebooting services; ensure compatibility with kernel modules and drivers; some container runtimes may require restart after kernel update

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34918 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data