Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2023-54292

A critical data race exists in the Linux kernel’s RDMA/irdma driver that can corrupt memory or crash the system. The race occurs while handling CQP requests and has been fixed in recent kernel releases. Users should update their kernel to a version that includes this patch.

publishedDec 30, 2025
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
7th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 3, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel users that run the RDMA/irdma driver, such as those using InfiniBand or RDMA over Converged Ethernet (RoCE) hardware. This includes system administrators and developers on servers and high‑performance computing clusters.

02

Real-world impact

An attacker could exploit the race to corrupt memory, crash the system, or potentially execute arbitrary code, leading to loss of confidentiality, integrity, or availability.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability can be exploited without authentication or user interaction, has a low complexity, and can fully compromise confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 01Verify your current kernel version.
  2. 02Check your distribution’s security advisories for a kernel update that includes the irdma data‑race fix.
  3. 03Install the updated kernel package.
  4. 04Reboot the system to use the new kernel.

NVD description indicates the issue has been resolved in the Linux kernel.

05

Timeline

  1. Dec 30, 2025 · Dec 30, 2025
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 1d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 4, 2026 · 1d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →