dbcve.org
CWE-130Weakness · CWE-130

CVE-2026-9054

CRITICAL · 9.2 CVSS v4.0 Published 2026-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 attacker sending tcp, il, rudp, rudp, or gre packets with a length less than the header size would trigger a kernel panic.

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

A kernel panic occurs when processing malformed network packets (tcp, il, rudp, or gre protocols) where the packet length is smaller than the required header size. The vulnerability stems from missing length validation before header parsing, allowing an attacker to trigger a denial of service by sending specially crafted packets.

MitigationImplement packet length validation checks in the affected protocol handlers to verify sufficient data is present before processing headers; apply kernel patches from the vendor when available.

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

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
Authentication
Y
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:A/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:A/V:X/RE:X/U:X

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. Identify kernel version
    Run 'uname -r' or 'cat /proc/version' to obtain the running kernel version
    Affected if The kernel version is lower than the version that includes the vendor patch for CVE-2026-9054 (compare against vendor security advisory)
  2. Check TCP protocol support
    Verify if TCP protocol handling is enabled - run 'lsmod | grep tcp' or check /proc/net/protocols for TCP presence
    Affected if TCP protocol stack is loaded and processing network traffic
  3. Check IL protocol support
    Run 'lsmod | grep il' or check /proc/net/protocols to see if the IL protocol module is loaded
    Affected if IL protocol module is loaded and active
  4. Check RUDP protocol support
    Run 'lsmod | grep rudp' or check /proc/net/protocols for RUDP presence
    Affected if RUDP protocol module is loaded and active
  5. Check GRE protocol support
    Run 'lsmod | grep gre' or check /proc/net/protocols for GRE tunnel support
    Affected if GRE protocol module is loaded and active
  6. Verify patch status
    Check if vendor-specific kernel patches for this CVE are applied - consult vendor documentation or check kernel patch alignment
    Affected if No vendor patch for CVE-2026-9054 has been applied to the kernel

The environment is affected if the kernel version is unpatched for CVE-2026-9059 and any of the TCP, IL, RUDP, or GRE network protocols are enabled and processing traffic.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement packet length validation checks in the affected protocol handlers to verify sufficient data is present before processing headers; apply kernel patches from the vendor when available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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