dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53216

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to 5.15.210 / 6.1.176 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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: net: mvpp2: limit XDP frame size to the RX buffer mvpp2 has short and long BM pools, and short pool buffers can be smaller than PAGE_SIZE. The XDP path nevertheless initializes every xdp_buff with PAGE_SIZE as frame size. XDP helpers use frame_sz to validate tail growth and to derive the hard end of the data area. Advertising PAGE_SIZE for short buffers can let bpf_xdp_adjust_tail() grow a packet past the real allocation, corrupting memory or later tripping skb tailroom checks. Initialize the XDP buffer with bm_pool->frag_size so XDP tailroom matches the actual buffer backing the packet.

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 · high confidence

The mvpp2 network driver incorrectly initializes XDP buffers with PAGE_SIZE as frame size regardless of actual buffer pool allocation. Since short BM pool buffers can be smaller than PAGE_SIZE, XDP helpers using frame_sz to validate tail growth allow bpf_xdp_adjust_tail() to extend packets past actual buffer boundaries, causing memory corruption or skb tailroom check failures.

MitigationApply the kernel patch to initialize XDP buffers with bm_pool->frag_size instead of PAGE_SIZE. Until the fix is deployed, avoid using XDP on short-buffer pools or disable XDP entirely for affected mvpp2 interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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:>= 5.9, < 5.15.210>= 5.16, < 6.1.176>= 6.2, < 6.6.143>= 6.7, < 6.12.94>= 6.13, < 6.18.36>= 6.19, < 7.0.13= 7.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if mvpp2 driver is in use
    Run 'lsmod | grep mvpp2' or check 'ip link' output for interfaces using this driver (e.g., 'ethtool -i <interface>' shows driver: mvpp2)
    Affected if No mvpp2 interfaces are present in the system
  2. Verify kernel version against affected ranges
    Run 'uname -r' and compare to: >= 5.9, < 5.15.210; >= 5.16, < 6.1.176; >= 6.2, < 6.6.143; >= 6.7, < 6.12.94; >= 6.13, < 6.18.36; >= 6.19, < 7.0.13; = 7.1
    Affected if Kernel version falls within any of the affected ranges listed
  3. Check if XDP is enabled on mvpp2 interfaces
    Run 'ip link show' and look for 'xdp' flags on mvpp2 interfaces, or check 'cat /sys/class/net/<iface>/xdp/'
    Affected if No XDP programs are attached to mvpp2 interfaces
  4. Check for short buffer manager pool configuration
    Inspect mvpp2 driver configuration or hardware/firmware settings that define buffer pool frag_size values (typically smaller than PAGE_SIZE, e.g., 1536 or 2048 bytes)
    Affected if Buffer manager pools use standard PAGE_SIZE allocations (typically 4096 bytes) rather than smaller frag_size values

The system is affected if running a vulnerable kernel version AND using mvpp2 driver with XDP enabled AND short buffer manager pools are configured with allocations smaller than PAGE_SIZE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 5.15.210 / 6.1.176 / 6.6.143 or later
Fixed in 5.15.2106.1.1766.6.143
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch to initialize XDP buffers with bm_pool->frag_size instead of PAGE_SIZE. Until the fix is deployed, avoid using XDP on short-buffer pools or disable XDP entirely for affected mvpp2 interfaces.

Recommended fix High confidence

Upgrade to kernel 5.15.210, 6.1.176, 6.6.143, or 6.12.94 (depending on your current branch)

  1. 1. Check the current running kernel version using 'uname -r'
  2. 2. Determine which kernel branch you are running (e.g., 5.15.x, 6.1.x, 6.6.x, or 6.7-6.12.x)
  3. 3. For kernel 5.15.x: upgrade to version 5.15.210 or later
  4. 4. For kernel 6.1.x: upgrade to version 6.1.176 or later
  5. 5. For kernel 6.2-6.6.x: upgrade to version 6.6.143 or later
  6. 6. For kernel 6.7-6.12.x: upgrade to version 6.12.94 or later
  7. 7. Reboot the system to load the fixed kernel
  8. 8. Verify the fix is applied by checking the mvpp2 driver source for the frame_sz fix or running 'modinfo mvpp2'
Caveat Kernel upgrades may require matching system utilities and drivers; ensure compatibility with userspace tools and hardware drivers before upgrading

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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