CVE-2025-22836
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 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 confidenceAn integer overflow vulnerability exists in the Linux kernel-mode driver for Intel 800 Series Ethernet controllers before version 1.17.2. The flaw allows a local authenticated user to potentially escalate privileges via the integer wraparound condition.
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 if Intel 800 Series Ethernet driver is loadedRun 'lsmod | grep -E "igc|ice"' to check if the Intel Ethernet driver module is loaded. The 800 series typically uses the 'igc' driver for I225/I226 controllers.Affected if No matching driver module is found - the system may not be using affected hardware.
-
Retrieve the driver versionRun 'modinfo igc 2>/dev/null | grep -i version' or check '/sys/module/igc/version' if it exists. For ice driver, run 'modinfo ice | grep -i version'.Affected if Version information cannot be retrieved or the driver is not present.
-
Compare installed version to 1.17.2Compare the version output from the previous step to the affected range. Versions before 1.17.2 are vulnerable. Format may vary (e.g., 1.17.1, 1.16.0, etc.).Affected if The installed version is a release prior to 1.17.2.
-
Verify the driver is in use with affected hardwareRun 'ip link show' and 'ethtool -i <interface>' to identify active Intel 800 Series interfaces using the vulnerable driver.Affected if An interface is actively using the igc or ice driver with a vulnerable version.
The system is affected if an Intel 800 Series Ethernet controller is in use with the igc or ice driver version prior to 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 patch the integer overflow vulnerability.
Intel(R) 800 Series Ethernet Linux kernel-mode driver version 1.17.2 or later
- 1. Identify the current version of the Intel(R) 800 Series Ethernet Linux kernel-mode driver installed on the system
- 2. Download the latest version of the Intel Ethernet driver from the official Intel support website (intel.com/support)
- 3. Ensure the driver version is 1.17.2 or later to obtain the security fix
- 4. Follow Intel's documentation for driver installation, which typically involves: a) Unload the current driver module if running, b) Install the new driver package, c) Reboot the system to load the updated driver
- 5. Verify the installed driver version matches the expected fixed version (1.17.2 or later) using ethtool or similar diagnostic tools
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-22836 — 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-22836 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