CVE-2025-23241
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 · uneditedInteger overflow or wraparound 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 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 · high confidenceInteger overflow or wraparound vulnerability 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 cause a denial of service.
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
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/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 controller in the systemRun lspci or check /sys/class/net to list network controllers and look for Intel 800 Series devices (e.g., device IDs in the 800 Series family)Affected if The system has an Intel 800 Series Ethernet controller present
-
Locate the active network interfaceCheck /sys/class/net for interfaces corresponding to the Intel 800 Series controller, or use ip link show to list interfacesAffected if An interface is mapped to the Intel 800 Series controller
-
Retrieve the driver version for the interfaceUse ethtool -i <interface> or read /sys/class/net/<interface>/device/driver/version to obtain the installed driver versionAffected if The driver version is exposed and can be compared
-
Compare installed version against 1.17.2Compare the retrieved driver version number to the threshold version 1.17.2 using standard version comparisonAffected if The installed version is lower than 1.17.2 (for example, 1.17.1, 1.16.x, or any version below 1.17.2)
-
Confirm the driver is a Linux kernel-mode driverVerify from ethtool -i output or driver metadata that this is a Linux kernel driver for Intel 800 Series EthernetAffected if The driver is a Linux kernel-mode driver for the affected product
The user is affected if their system contains an Intel 800 Series Ethernet controller running a Linux kernel-mode driver version lower than 1.17.2.
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 · scopedUpgrade the Intel 800 Series Ethernet driver to version 1.17.2 or later to remediate this vulnerability.
Linux kernel driver for Intel(R) 800 Series Ethernet version 1.17.2 or later
- Identify the specific Intel 800 Series Ethernet driver in use (e.g., i40e, ice) using 'lsmod | grep -E "i40e|ice"' or 'ethtool -i <interface>'
- Check current driver version using 'modinfo i40e' or 'modinfo ice'
- Update the kernel or driver package to obtain version 1.17.2 or later. This is typically done via: 'sudo apt-get update && sudo apt-get upgrade' (Debian/Ubuntu) or 'sudo yum update' (RHEL/CentOS)
- Reboot the system to load the updated driver
- Verify the fixed version is loaded using 'modinfo i40e' or 'modinfo ice' and confirm version 1.17.2 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23241 — 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-23241 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