dbcve.org
Ethernet 800 Series Controllers DriverApplication · Intel

CVE-2024-23981

HIGH · 8.8 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 28.3 or later.
See remediation →
90/100
Remediation priority · Urgent
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
Wrap-around error in Linux kernel mode driver for some Intel(R) Ethernet Network Controllers and Adapters before version 28.3 may allow an authenticated user to potentially enable escalation of privilege 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 · high confidence

A wrap-around error in the Linux kernel mode driver for Intel(R) Ethernet Network Controllers and Adapters before version 28.3 allows an authenticated local user to potentially escalate privileges. The integer wrap-around vulnerability likely exists in the driver's memory handling, buffer allocation, or calculation logic within the kernel space.

MitigationUpdate the Intel Ethernet network driver to version 28.3 or later to remediate the vulnerability.

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 800 Series Controllers DriverApplication
Affected:< 28.3

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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. Identify if Intel Ethernet 800 Series driver is loaded
    Run 'lsmod | grep -E "ice|igc|e1000"' to list loaded network drivers, or check 'lspci -k | grep -A5 Ethernet' to see network controller and its driver
    Affected if The system uses an Intel Ethernet 800 Series controller with the ice driver loaded
  2. Retrieve the installed driver version
    Run 'modinfo ice' and look for the 'version:' field, or check 'cat /sys/module/ice/version' if the module is loaded
    Affected if The displayed version number is less than 28.3 (for example, 28.2, 28.1, or any version below 28.3)
  3. Confirm the driver applies to affected hardware
    Run 'lspci | grep -i ethernet' to identify the network controller model, then cross-reference with Intel Ethernet 800 Series documentation
    Affected if The hardware is an Intel Ethernet 800 Series controller (such as E810, E810-C, E810-X, or related variants) and the driver version is below 28.3
  4. Check if kernel mode driver is in use
    Verify the driver is running in kernel mode - this is default for Linux network drivers; confirm with 'ethtool -i <interface>' showing 'driver: ice' and 'version:' field
    Affected if The driver is active in kernel mode with version below 28.3 on an affected Intel Ethernet 800 Series controller

The system is affected if it runs an Intel Ethernet 800 Series controller with the ice driver version below 28.3 on Linux.

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

Update the Intel Ethernet network driver to version 28.3 or later to remediate the vulnerability.

Recommended fix High confidence

28.3

  1. Check the current version of the Intel Ethernet driver installed on the system using 'ethtool -i <interface>' or by checking '/sys/class/net/<interface>/device/driver'
  2. Download the Intel Ethernet 800 Series Controllers Driver version 28.3 or later from Intel's official support website (www.intel.com)
  3. Extract the downloaded driver package and follow Intel's installation instructions for Linux kernel mode drivers
  4. Install the new driver module using 'make install' or the provided installer script as documented by Intel
  5. Reboot the system to load the new driver
  6. Verify the driver version has been updated to 28.3 or later using 'ethtool -i <interface>'
Caveat No breaking changes mentioned in the provided material; upgrade appears to be a straightforward version update

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

Fix this in Ethernet 800 Series Controllers Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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