dbcve.org
Use After FreeWeakness · CWE-416

CVE-2025-27723

MEDIUM · 6.8 CVSS v4.0 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
Use after free for some Linux kernel driver for the Intel(R) Ethernet 800 series before version 2.3.14 within Ring 0: Kernel may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (high) impacts.

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 confidence

Use-after-free vulnerability in the Linux kernel driver for Intel(R) Ethernet 800 series network adapters allows a local, authenticated unprivileged user to cause a denial of service by accessing memory that has been freed. The vulnerability exists in Ring 0 (kernel space) and requires low complexity with no user interaction or special internal knowledge.

MitigationUpdate the Intel Ethernet 800 series driver to version 2.3.14 or later to patch the use-after-free vulnerability. Follow principle of least privilege to limit local user access.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Ethernet 800 series adapters
    Run 'lspci | grep -i ethernet' to list network adapters. Look for Intel Ethernet 800 series (often shown as Ethernet 800 or similar naming with 800 series)
    Affected if No Intel Ethernet 800 series adapter is present in the system
  2. Determine the kernel driver in use
    Run 'ls /sys/class/net/' to list network interfaces, then 'ethtool -i <interface>' or check '/sys/class/net/<interface>/device/driver' to identify the driver name (typically ice or iegb for Intel Ethernet 800 series)
    Affected if The driver is not ice or another Intel Ethernet 800 series driver
  3. Retrieve the installed driver version
    Run 'modinfo ice' or 'ethtool -i <interface>' (replace ice with the actual driver name found). Extract the 'version' or 'driver_version' field from the output
    Affected if Unable to retrieve driver version information
  4. Compare driver version to fixed release
    Compare the version number from the previous step to 2.3.14. Ensure proper numeric comparison (e.g., 2.3.13 or earlier is older, 2.3.14 or later includes the fix)
    Affected if The installed driver version is earlier than 2.3.14

A system is affected if it has an Intel Ethernet 800 series network adapter running a kernel driver version earlier than 2.3.14.

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 Ethernet 800 series driver to version 2.3.14 or later to patch the use-after-free vulnerability. Follow principle of least privilege to limit local user access.

Recommended fix Moderate confidence

Intel Ethernet 800 series Linux kernel driver version 2.3.14 or later

  1. Identify the current Intel Ethernet 800 series driver version using 'ethtool -i <interface>' or checking the ice driver version via 'modinfo ice'
  2. If running a version before 2.3.14, update the kernel or driver package to a version containing driver version 2.3.14 or later
  3. For enterprise distributions, apply the latest kernel security updates which typically include driver updates: 'sudo yum update' or 'sudo apt-get update && sudo apt-get upgrade' for RHEL-based or Debian-based systems respectively
  4. For direct Intel driver installation, download the latest ice driver from Intel's support website and follow the installation instructions
  5. Reboot the system to load the updated driver
  6. Verify the driver version post-update using 'modinfo ice' or 'ethtool -i <interface>' to confirm version 2.3.14 or later is installed

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27723 — 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-27723 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