dbcve.org
Ethernet Controller E810 FirmwareOperating system · Intel

CVE-2021-0002

HIGH · 7.1 CVSS v3.1 Published 2021-08-11
Fix available
A fix is available. Upgrade to 1.4.11 or later.
See remediation →
73/100
Remediation priority · Elevated
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
Improper conditions check in some Intel(R) Ethernet Controllers 800 series Linux drivers before version 1.4.11 may allow an authenticated user to potentially enable information disclosure or denial of service via local access.

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

Improper conditions check vulnerability in Intel Ethernet Controllers 800 series Linux drivers before version 1.4.11. The flaw involves incorrect or missing validation in conditional logic within the driver code, allowing a locally authenticated user to potentially trigger information disclosure or denial of service conditions.

MitigationUpgrade Intel Ethernet 800 series Linux drivers to version 1.4.11 or later. Apply the vendor-provided driver update through standard Linux package management or Intel's driver repositories, and verify successful installation.

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
Ethernet Controller E810 FirmwareOperating system
Affected:< 1.4.11
FedoraOperating system
Affected:= 33= 34= 35

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Identify Intel E810 Ethernet Controller hardware
    Run 'lspci | grep -i ethernet' or 'lspci | grep -iE810' to list Ethernet controllers and confirm presence of Intel E810 series
    Affected if The system has an Intel Ethernet Controller E810 installed
  2. Check installed driver version
    Run 'ethtool -i <interface>' (replace <interface> with eth0, ens33f0, etc. found in step 1) or 'modinfo ice' to retrieve the driver version
    Affected if The driver version is earlier than 1.4.11 (for example, 1.4.10 or lower)
  3. Check firmware version of the E810 controller
    Run 'ethtool -i <interface>' and look for the firmware version field, or check 'cat /sys/class/net/<interface>/device/firmware_version'
    Affected if The firmware version is earlier than 1.4.11
  4. Verify operating system version if using Fedora
    Run 'cat /etc/fedora-release' to check the Fedora release number
    Affected if The system runs Fedora 33, Fedora 34, or Fedora 35 with the vulnerable driver version

A system is affected if it contains an Intel Ethernet Controller E810 with driver or firmware versions below 1.4.11, particularly on Fedora 33-35 where the vulnerable driver version shipped.

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 1.4.11 or later
Fixed in 1.4.11
Interim mitigation

Upgrade Intel Ethernet 800 series Linux drivers to version 1.4.11 or later. Apply the vendor-provided driver update through standard Linux package management or Intel's driver repositories, and verify successful installation.

Recommended fix High confidence

Intel E810 firmware >= 1.4.11; Fedora kernel updates containing ice driver 1.4.11+

  1. Update Intel Ethernet Controller E810 firmware to version 1.4.11 or later using Intel's firmware update utilities
  2. For Fedora systems, apply kernel updates that include the fixed ice driver (part of the upstream Linux kernel)
  3. Reboot the system after applying firmware and kernel updates to load the corrected driver
  4. Verify the driver version is 1.4.11 or later using: modinfo ice | grep version
Caveat Firmware updates require downtime and should be tested in a non-production environment first; ensure backup of previous firmware version is available for rollback if needed

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

Fix this in Ethernet Controller E810 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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