CVE-2025-24486
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) 700 Series Ethernet before version 2.28.5 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 confidenceImproper input validation in the Linux kernel-mode driver for Intel 700 Series Ethernet controllers allows an authenticated local user to escalate privileges. The vulnerability stems from insufficient validation of input data processed by the driver, which could be exploited to gain elevated system 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Intel 700 Series Ethernet hardwareRun 'lspci | grep -i ethernet' or 'lspci -d :' to list Ethernet controllers. Look for Intel 700 Series (often identified by device IDs in the 15b7-15b8 range or similar 700 Series identifiers)Affected if No Intel 700 Series Ethernet controller is present in the system
-
Identify the kernel driver in useFor each Intel 700 Series adapter found, run 'ethtool -i <interface>' or check 'lspci -k' output to identify the kernel driver name (commonly 'ice' or similar for Intel Ethernet drivers)Affected if No Intel Ethernet driver is loaded for the 700 Series controller
-
Retrieve the driver versionUse 'ethtool -i <interface>' to read the driver version field, or run 'modinfo <drivername>' to get the module versionAffected if The driver version cannot be determined or is earlier than the fixed release version
-
Compare against the fixed versionCompare the installed driver version number to the known vulnerable versions. If the version is earlier than the patched release, the system is vulnerableAffected if The installed driver version is earlier than the patched version and the system has the affected hardware
A user is affected if the system contains an Intel 700 Series Ethernet controller running a Linux kernel driver with a version earlier than the patched release.
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.
dbcve · scopedUpdate the Intel 700 Series Ethernet driver to version 2.28.5 or later. Apply the patch to all affected systems and verify the update was successful.
Intel(R) 700 Series Ethernet Linux kernel-mode driver version 2.28.5 or later
- Identify the current version of the Intel(R) 700 Series Ethernet Linux kernel-mode driver using 'modinfo' or checking system logs
- Download version 2.28.5 or later of the Intel(R) 700 Series Ethernet driver from Intel's official support website (intel.com/support)
- Install the updated driver following Intel's provided installation instructions, which typically involve compiling and loading the new kernel module
- Reboot the system or reload the driver module to ensure the new version is active
- Verify the installed driver version matches 2.28.5 or later using 'modinfo'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24486 — 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-24486 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