Security readout for executives and security teams
Plain-English summary
A Linux RDMA driver cleanup error can leave software resources in an invalid state when Mellanox mlx5 firmware fails to destroy a receive queue. A later destruction attempt may access freed memory. The supplied CVSS rating is 7.8, reflecting potentially serious local impact, but affected systems require the relevant kernel driver and RDMA exposure.
Executive priority
Prioritize remediation on multi-user compute, virtualization, AI, and high-performance systems exposing mlx5 RDMA resources. Other Linux systems have lower practical exposure. Schedule a supported kernel update promptly, while confirming exact package status with the distribution vendor because the supplied version boundaries are not sufficiently clear for reliable fleet-wide matching.
Technical view
The mlx5 RDMA receive-queue destruction path cleaned software state before confirming firmware destruction succeeded. If firmware returned an error, retrying destruction could underflow a reference count and trigger a use-after-free. The correction rolls the object back to its original state after failure. The supplied vector requires local access and low privileges, without user interaction.
Likely exposure
Exposure is concentrated in Linux systems using the mlx5 RDMA stack, including mlx5_ib, mlx5_core, ib_uverbs, and compatible hardware or virtual environments. A local user must be able to reach the relevant RDMA userspace functionality. The bundled version data is ambiguous, so administrators should confirm affected distribution builds through vendor advisories.
Exploitation context
The source bundle provides a kernel warning and call trace demonstrating the faulty condition. It does not establish public weaponization or attacks in the wild, and the CVE is not identified as being in KEV. Treat this as a potentially high-impact local vulnerability rather than a remotely exploitable issue.
Researcher notes
The failure occurs during error handling, specifically when firmware rejects final receive-queue destruction after software resources were already cleaned. Repeated destruction can reach freed state and underflow a reference count. The CVSS vector claims confidentiality, integrity, and availability impact, but the supplied evidence shows a warning trace rather than demonstrated exploitation or a confirmed security outcome.
Mitigation direction
- Install a vendor-supported kernel containing the applicable referenced stable fix.
- Prioritize shared systems where untrusted local users can access RDMA devices.
- Consult the Linux distribution vendor for exact affected and corrected package versions.
- If updating is delayed, seek vendor-supported temporary mitigations for RDMA access.
Validation and detection
- Inventory systems using mlx5 hardware and loaded mlx5 or RDMA kernel modules.
- Compare installed kernel packages with the applicable distribution security advisory.
- Confirm the updated kernel includes the relevant stable fix for its maintained branch.
- Review kernel logs for refcount underflow, use-after-free, or mlx5 receive-queue destruction failures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2025-38161 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/26d2f662d3a6655a82fd8a287e8b1ce471567f36CVE reference, Linux
- https://git.kernel.org/stable/c/f9784da76ad7be66230e829e743bdf68a2c49e56CVE reference, Linux
- https://git.kernel.org/stable/c/cf32affe6f3801cfb72a65e69c4bc7a8ee9be100CVE reference, Linux
- https://git.kernel.org/stable/c/7c4c84cdcc19e89d42f6bf117238e5471173423eCVE reference, Linux
- https://git.kernel.org/stable/c/50ac361ff8914133e3cf6ef184bac90c22cb8d79CVE reference, Linux
- https://git.kernel.org/stable/c/0a7790cbba654e925243571cf2f24d61603d3ed3CVE reference, Linux
- https://git.kernel.org/stable/c/5d2ea5aebbb2f3ebde4403f9c55b2b057e5dd2d6CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlCVE reference, CVE
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.