dbcve.org
Linux KernelOperating system · Linux

CVE-2018-1000026

HIGH · 7.7 CVSS v3.1 Published 2018-02-09
Fix available
A fix is available. Upgrade to 4.4.181 / 4.9.159 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable 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
Linux Linux kernel version at least v4.8 onwards, probably well before contains a Insufficient input validation vulnerability in bnx2x network card driver that can result in DoS: Network card firmware assertion takes card off-line. This attack appear to be exploitable via An attacker on a must pass a very large, specially crafted packet to the bnx2x card. This can be done from an untrusted guest VM..

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

Insufficient input validation in the bnx2x network card driver allows an attacker on an untrusted guest VM to send a specially crafted large packet that triggers a firmware assertion, causing the network card to go offline (Denial of Service). The driver fails to properly validate packet size or format before passing it to the firmware.

MitigationApply Linux kernel updates that include the bnx2x driver fix for proper input validation; in virtualized environments, restrict or monitor untrusted guest VM network access to reduce attack surface.

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:>= 2.6.12, < 4.4.181>= 4.5.0, < 4.9.159>= 4.10, < 4.14.102>= 4.15, < 4.16
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 16.04= 17.10
Enterprise LinuxOperating system
Affected:= 7.0
Enterprise Linux DesktopOperating system
Affected:= 7.0
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux WorkstationOperating system
Affected:= 7.0
Debian LinuxOperating system
Affected:= 8.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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. Determine if bnx2x driver is loaded
    Run 'lsmod | grep bnx2x' to see if the bnx2x kernel module is currently loaded in memory
    Affected if The bnx2x module is loaded and running
  2. Identify the running Linux kernel version
    Run 'uname -r' to get the kernel version, then compare it against the affected ranges: < 4.4.181, 4.5.0 to < 4.9.159, 4.10 to < 4.14.102, 4.15 to < 4.16
    Affected if The kernel version falls within any of the affected version ranges
  3. Confirm bnx2x driver file exists
    Check for the presence of the driver file using 'ls /lib/modules/$(uname -r)/kernel/drivers/net/ethernet/broadcom/bnx2x*' or similar path under /lib/modules
    Affected if The bnx2x driver binary exists in the kernel modules directory for the running kernel
  4. Determine if system is running as a virtualization host
    Run 'systemd-detect-virt' or check 'lspci | grep -i network' to see if bnx2x network hardware is physically present or passed through to VMs
    Affected if The bnx2x driver is handling network traffic from virtual machines (the attack vector requires untrusted guest VMs to send packets to the physical network card)

A system is affected if it runs a vulnerable kernel version with the bnx2x driver loaded and exposes the network interface to untrusted guest virtual machines.

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
Upgrade available Upgrade to 4.4.181 / 4.9.159 / 4.14.102 or later
Fixed in 4.4.1814.9.1594.14.102
Interim mitigation

Apply Linux kernel updates that include the bnx2x driver fix for proper input validation; in virtualized environments, restrict or monitor untrusted guest VM network access to reduce attack surface.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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