dbcve.org
Linux KernelOperating system · Linux

CVE-2026-43092

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 6.6.136 / 6.12.83 or later.
See remediation →
57/100
Remediation priority · Elevated
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
In the Linux kernel, the following vulnerability has been resolved: xsk: validate MTU against usable frame size on bind AF_XDP bind currently accepts zero-copy pool configurations without verifying that the device MTU fits into the usable frame space provided by the UMEM chunk. This becomes a problem since we started to respect tailroom which is subtracted from chunk_size (among with headroom). 2k chunk size might not provide enough space for standard 1500 MTU, so let us catch such settings at bind time. Furthermore, validate whether underlying HW will be able to satisfy configured MTU wrt XSK's frame size multiplied by supported Rx buffer chain length (that is exposed via net_device::xdp_zc_max_segs).

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

A detailed technical summary for this CVE is being prepared.

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:>= 6.6, < 6.6.136>= 6.7, < 6.12.83>= 6.13, < 6.18.24>= 6.19, < 6.19.14= 7.0

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 6.6.136 / 6.12.83 / 6.18.24 or later
Fixed in 6.6.1366.12.836.18.24
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux kernel 6.6.136, 6.12.83, 6.18.24, or 6.19.14 (or later stable releases) depending on which branch you're on

  1. 1. Identify current kernel version: run `uname -r`
  2. 2. Determine which stable branch you need based on your current version (6.6.x → 6.6.136+, 6.7-6.12.x → 6.12.83+, 6.13-6.18.x → 6.18.24+, 6.19.x → 6.19.14+)
  3. 3. For Debian/Ubuntu: run `apt update && apt upgrade linux-image-generic` to pull the latest stable kernel
  4. 4. For RHEL/CentOS/Fedora: run `dnf update kernel` or `yum update kernel`
  5. 5. For other distributions: obtain the fixed kernel from your vendor or kernel.org (https://www.kernel.org/)
  6. 6. Reboot into the new kernel: `systemctl reboot`
  7. 7. Verify the fix is applied: check that `uname -r` shows a version at or above the appropriate fix version for your branch
  8. 8. Test AF_XDP functionality: ensure any zero-copy XDP sockets work correctly with your MTU settings
Caveat Kernel upgrades may require system reboot and could introduce subtle behavior changes; test in non-production environment first. Some AF_XDP configurations that previously worked with mismatched MTU/chunk_size may now be rejected at bind time.

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,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43092 — 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-2026-43092 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