CVE-2023-25775
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 access control in the Intel(R) Ethernet Controller RDMA driver for linux before version 1.9.30 may allow an unauthenticated user to potentially enable escalation of privilege via network 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 · moderate confidenceImproper access control in the Intel Ethernet Controller RDMA driver for Linux allows unauthenticated network attackers to potentially escalate privileges. The vulnerability exists in versions prior to 1.9.30 and could be exploited via network access to the affected interface.
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< 1.9.30CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 Ethernet RDMA driver is presentList loaded kernel modules or installed driver packages related to Intel network/RDMA functionality using 'lsmod' or package manager queries. Look for Intel Ethernet RDMA driver modules.Affected if The Intel Ethernet Controller RDMA driver is loaded or installed on the system
-
Retrieve the installed RDMA driver versionQuery the driver version via 'modinfo' on the relevant Intel RDMA module, or check the driver package version if installed via a package manager. Compare the version number against the 1.9.30 threshold.Affected if The driver version is found to be lower than 1.9.30
-
Check for active network interfaces using the affected driverIdentify network interfaces managed by the Intel Ethernet RDMA driver using 'ip link show' or 'ip addr'. Note which interfaces correspond to the affected driver.Affected if There are active network interfaces using the Intel Ethernet RDMA driver and the driver version is below 1.9.30
A system is affected if the Intel Ethernet Controller RDMA driver for Linux is installed with a version lower than 1.9.30 and has active network interfaces using that driver.
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 · scoped1.9.30
Upgrade the Intel Ethernet Controller RDMA driver for Linux to version 1.9.30 or later to remediate this vulnerability.
1.9.30
- Verify the current driver version by running: modinfo irdma or checking /sys/class/infiniband/*/device/driver/version
- Download the Intel Ethernet Controller RDMA driver version 1.9.30 or later from Intel's official support website or your Linux distribution's package repository
- If using a distribution package manager (apt, yum, dnf), update the driver package: sudo apt-get update && sudo apt-get install irdma (Debian/Ubuntu) or sudo yum/dnf update irdma (RHEL/CentOS)
- If building from source, ensure you have kernel-devel and build dependencies installed, then follow Intel's installation guide for the driver
- Reboot the system or unload/reload the driver module: sudo modprobe -r irdma && sudo modprobe irdma
- Verify the new version is loaded: modinfo irdma | grep version
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-2023-25775 — 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-2023-25775 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