CVE-2025-24325
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 · uneditedImproper 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 confidenceImproper input validation in the Linux kernel-mode driver for Intel(R) 800 Series Ethernet controllers before version 1.17.2 allows an authenticated local user to potentially escalate privileges. The vulnerability stems from insufficient validation of input data handled by the kernel driver, which could be exploited to gain elevated privileges.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Intel 800 Series Ethernet controllers presentRun 'lspci | grep -i "800 Series"' or 'lspci -nn | grep -i ethernet' to list network devices. Look for Intel Ethernet Controller 800 Series entries.Affected if No Intel 800 Series Ethernet controller is found on the system, then this CVE does not apply.
-
Locate the kernel driver moduleFor each identified Intel 800 Series controller, check the loaded driver by running 'lspci -k -s <bus-address>' or checking '/sys/bus/pci/drivers/' for driver bindings.Affected if No kernel driver is bound to the Intel 800 Series controller.
-
Retrieve the driver versionRun 'ethtool -i <interface-name>' where <interface-name> is the network interface (e.g., eth0, enp0s1) corresponding to the Intel 800 Series controller. The 'driver' and 'version' fields will show the driver name and version.Affected if Unable to retrieve driver version via ethtool; the interface may be down or not configured.
-
Compare driver version against 1.17.2Compare the version retrieved from ethtool to the fixed version 1.17.2. Versions earlier than 1.17.2 (such as 1.x.y where x < 17, or 1.17.0, 1.17.1) are considered vulnerable.Affected if The installed driver version is before 1.17.2 (e.g., 1.16.0, 1.17.1, etc.), indicating the system is affected by this vulnerability.
A system is affected only if it has an Intel 800 Series Ethernet controller with a kernel driver version earlier than 1.17.2; otherwise, it is not vulnerable to CVE-2025-24325.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the Intel 800 Series Ethernet driver to version 1.17.2 or later. Verify the current driver version and apply the vendor patch through standard Linux distribution kernel or driver update mechanisms.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24325 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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