LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference

In the Linux kernel, the following vulnerability has been resolved: RDMA/cm: Fix leaking the multicast GID table reference If the CM ID is destroyed while the CM event for multicast creating is still queued the cancel_work_sync() will prevent the work from running which also prevents destroying the ah_attr. This leaks a refcount and triggers a WARN: GID entry ref leak for dev syz1 index 2 ref=573 WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline] WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886 Destroy the ah_attr after canceling the work, it is safe to call this twice.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel RDMA connection manager bug that can leak an internal multicast GID table reference when cleanup races with queued multicast work. The source describes a kernel warning and reference leak, not data theft or code execution. Exposure is mainly relevant to systems using RDMA, InfiniBand, or RoCE functionality.

Executive priority

Treat this as a targeted Linux kernel maintenance issue, not an emergency based on current evidence. Prioritize patch validation for RDMA-enabled infrastructure because resource leaks in kernel subsystems can affect reliability, even without confirmed exploitation.

Technical view

In RDMA/cm multicast handling, destroying a CM ID while the multicast creation event is still queued can make cancel_work_sync prevent work execution and skip ah_attr destruction. That leaks a GID table reference and can trigger a WARN. The referenced stable commits fix cleanup by destroying ah_attr after work cancellation.

Likely exposure

Linux systems with RDMA-capable kernel support are the relevant population, especially hosts using InfiniBand, RoCE, or RDMA multicast paths. The source bundle lists Linux kernel versions and stable commits, but distro-specific exposure requires mapping vendor kernel packages to those fixes.

Exploitation context

No active exploitation is reported in the provided sources, and KEV is false. The public description points to a cleanup race causing a reference leak and WARN. It does not establish remote exploitation, privilege escalation, or a complete denial-of-service path.

Researcher notes

The evidence supports a race in RDMA/cm multicast cleanup involving queued work, ah_attr lifetime, and GID table reference management. The bundle lacks CVSS, CWE, exploit evidence, and distro package status. Avoid broad claims beyond RDMA-capable Linux kernels until vendor mappings are confirmed.

Mitigation direction

  • Identify systems running Linux kernels with RDMA, InfiniBand, or RoCE enabled.
  • Map deployed kernel packages to vendor advisories or the referenced stable commits.
  • Prioritize updates for RDMA-capable servers and high-availability infrastructure.
  • Apply vendor kernel updates when available rather than hand-patching production kernels.
  • Monitor kernel logs for GID entry reference leak warnings.

Validation and detection

  • Inventory kernel versions and enabled RDMA-related modules on Linux hosts.
  • Check whether vendor kernel builds include the referenced stable fixes.
  • Review kernel logs for GID entry ref leak or related WARN messages.
  • Confirm RDMA workloads remain stable after applying kernel updates.
  • Track vendor advisories for distro-specific affected and fixed package versions.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2025-71084 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux60d613b39e8d0c9f3b526e9c96445422b4562d76, fe454dc31e84f8c14cb8942fcb61666c9f40745b, fe454dc31e84f8c14cb8942fcb61666c9f40745b, fe454dc31e84f8c14cb8942fcb61666c9f40745b, fe454dc31e84f8c14cb8942fcb61666c9f40745b, fe454dc31e84f8c14cb8942fcb61666c9f40745b, fe454dc31e84f8c14cb8942fcb61666c9f40745b, a3262b3884dd67b4c5632ce7cdf9cff9d1a575d4, 5.10.20, 5.11.3unaffected
LinuxLinux5.12, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.