CVE-2025-71084: Linux kernel · RDMA/cm: Fix leaking the multicast GID table reference
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d5ce588a9552878859a4d44b70b724216c188a5f : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-06-10.
- Patch
- Available – fixed in d5ce588a9552878859a4d44b70b724216c188a5f, c0acdee513239e1d6e1b490f56be0e6837dfd162, abf38398724ecc888f62c678d288da40d11878af +6
Exploitation evidence
Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/d5ce588a9552878859a4d44b70b724216c188a5f (opens in a new tab)
- git.kernel.org/stable/c/abf38398724ecc888f62c678d288da40d11878af (opens in a new tab)
- git.kernel.org/stable/c/ab668a58c4a2ccb6d54add7a76f2f955d15d0196 (opens in a new tab)
- git.kernel.org/stable/c/c0acdee513239e1d6e1b490f56be0e6837dfd162 (opens in a new tab)
- git.kernel.org/stable/c/5cb34bb5fd726491b809efbeb5cfd63ae5bf9cf3 (opens in a new tab)
- git.kernel.org/stable/c/3ba6d01c4b3c584264dc733c6a2ecc5bbc8e0bb5 (opens in a new tab)
- git.kernel.org/stable/c/57f3cb6c84159d12ba343574df2115fb18dd83ca (opens in a new tab)