CVE-2025-32003
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 · uneditedOut-of-bounds read in the firmware for some 100GbE Intel(R) Ethernet Network Adapter E810 before version cvl fw 1.7.6, cpk 1.3.7 within Ring 0: Bare Metal OS may allow a denial of service. Network adversary with an authenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via network access when attack requirements are present with 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 (none) 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 confidenceAn out-of-bounds read vulnerability exists in the firmware of Intel E810 100GbE Ethernet Network Adapters running versions prior to cvl fw 1.7.6 or cpk 1.3.7. An authenticated network attacker with low complexity and special internal knowledge can trigger this vulnerability in Ring 0 (bare metal OS context), causing a denial of service with high availability impact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 30.3CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 E810 adapter presenceRun 'lspci | grep -i intel' or 'lspci | grep -i E810' to list network adapters. Look for Intel Ethernet Controller E810 in the output.Affected if No Intel E810 adapter is found in the system PCI device list, then this CVE does not apply.
-
Check cvl firmware versionRun 'ethtool -i <interface>' where <interface> is the network interface name (e.g., eth0) associated with the E810 adapter. Look for the 'firmware-version' field in the output.Affected if The firmware version shown is less than 1.7.6 (e.g., 1.7.5, 1.6.x, etc.).
-
Check cpk firmware versionRun 'ethtool -i <interface>' for the E810 interface. Some E810 variants use 'cpk' firmware. Check if the firmware string contains 'cpk' and compare the version number.Affected if The cpk firmware version is less than 1.3.7.
-
Check Intel Ethernet Controller versionRun 'lspci -nn | grep -i ethernet' to find the controller. Look for the device ID indicating Intel Ethernet Controller and check if the controller revision/version number displayed is less than 30.3.Affected if The Intel Ethernet Controller version is 30.2 or earlier.
A system is affected if it contains an Intel E810 100GbE adapter running cvl firmware prior to 1.7.6, cpk firmware prior to 1.3.7, or an Intel Ethernet Controller version below 30.3.
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 · scoped30.3
Upgrade Intel E810 Ethernet Network Adapter firmware to version cvl fw 1.7.6 or cpk 1.3.7 or later to resolve the out-of-bounds read vulnerability.
cvl fw 1.7.6 or cpk 1.3.7 (or later) for Intel(R) Ethernet Network Adapter E810
- Identify the current firmware version of the Intel(R) Ethernet Network Adapter E810 using system inventory or Intel firmware tools
- Download the updated firmware version cvl fw 1.7.6 or cpk 1.3.7 (or later) from the Intel support website (intel.com)
- Schedule a maintenance window as firmware updates may require system downtime
- Apply the firmware update to the E810 adapter using Intel's firmware update utilities or bootable firmware update media
- Verify the firmware version has been successfully updated post-update
- Test network connectivity and adapter functionality to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32003 — 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-32003 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