dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-24484

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 input validation in the Linux kernel-mode driver for some Intel(R) 800 Series Ethernet before version 1.17.2 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 · moderate confidence

Improper input validation in the Intel 800 Series Ethernet kernel-mode driver allows an authenticated local user to escalate privileges. This is a kernel-level driver vulnerability where insufficient validation of input data enables a local attacker to gain elevated (likely root) privileges on the system.

MitigationUpdate the Intel 800 Series Ethernet driver to version 1.17.2 or later to address the input validation flaw.

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

CVSS:3.1/AV:L/AC:H/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 Intel 800 Series Ethernet adapter
    Run 'lspci | grep -i ethernet' or check device manager to list installed network adapters. Look for Intel 800 Series controller (e.g., Intel Ethernet 800 Series).
    Affected if No Intel 800 Series Ethernet adapter is present in the system
  2. Locate the kernel-mode driver
    On Linux, check /sys/class/net/*/device/driver or use 'ls -la /sys/bus/pci/drivers/'. On Windows, check Device Manager under Network adapters and view driver details. Identify the driver associated with the Intel 800 Series adapter.
    Affected if No Intel 800 Series driver is loaded or installed
  3. Retrieve the installed driver version
    On Linux, use 'modinfo e1000e' or check the driver file properties. On Windows, right-click the adapter in Device Manager, go to Driver tab, and note the Driver Version field. This version corresponds to the Intel Ethernet driver.
    Affected if Unable to determine driver version from the installed driver
  4. Compare version to 1.17.2
    Compare the installed driver version number to 1.17.2. Any version lower than 1.17.2 (e.g., 1.16.x, 1.15.x, etc.) is considered vulnerable.
    Affected if Installed version is below 1.17.2 (e.g., 1.16.1, 1.15.0, etc.)

The system is affected if it has an Intel 800 Series Ethernet adapter running a kernel-mode driver version earlier than 1.17.2, as the input validation flaw exists in those versions and can enable local privilege escalation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Intel 800 Series Ethernet driver to version 1.17.2 or later to address the input validation flaw.

Recommended fix High confidence

Intel(R) 800 Series Ethernet Linux kernel-mode driver version 1.17.2

  1. Identify the Intel 800 Series Ethernet adapter in use
  2. Download the latest Intel network driver package from intel.com/support or your system vendor
  3. Extract the driver files and locate the kernel module (e.g., ice.ko or iavf.ko)
  4. Compile and install the driver module matching kernel version 1.17.2 or later
  5. Reboot the system to load the updated driver
  6. Verify the driver version loaded matches 1.17.2 or later using 'modinfo ice' or 'ethtool -i <interface>'

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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-2025-24484 — 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-2025-24484 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