CVE-2025-71157: RDMA/core: always drop device refcount in ib_del_sub_device_and_put()
In the Linux kernel, the following vulnerability has been resolved:
RDMA/core: always drop device refcount in ib_del_sub_device_and_put()
Since nldev_deldev() (introduced by commit 060c642b2ab8 ("RDMA/nldev: Add
support to add/delete a sub IB device through netlink") grabs a reference
using ib_device_get_by_index() before calling ib_del_sub_device_and_put(),
we need to drop that reference before returning -EOPNOTSUPP error.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel RDMA reference-counting flaw. In a sub-device deletion error path, the kernel could fail to release a device reference. The public record does not state confirmed exploitation, a CVSS score, or a clear business impact such as privilege escalation or data exposure.
Executive priority
Treat as a kernel maintenance item unless your environment depends on RDMA. There is not enough public evidence to justify emergency response, but kernel owners should confirm exposure and align updates with normal patch cycles.
Technical view
RDMA/core function ib_del_sub_device_and_put() did not always drop a reference acquired by nldev_deldev() through ib_device_get_by_index() before returning -EOPNOTSUPP. The fix ensures the reference is released on that path. The evidence points to a resource/lifetime-management bug in RDMA sub-device handling.
Likely exposure
Exposure appears limited to Linux systems running affected kernels where RDMA core and sub-IB device netlink functionality are present or usable. The source bundle lists Linux kernel versions and stable commit references but does not identify distributions, configurations, or reachable attack prerequisites.
Exploitation context
The bundle reports KEV false and provides no cited evidence of active exploitation, public exploit code, or weaponization. The trigger context involves RDMA netlink sub-device deletion behavior, but the sources do not document attacker privileges, locality, or practical impact.
Researcher notes
The record lacks CVSS, CWE, exploitability detail, and distribution mapping. Analysis should focus on the RDMA nldev_deldev() path, the -EOPNOTSUPP return, and whether unreleased device references can accumulate or affect object lifetime in reachable configurations.
Mitigation direction
Check Linux or distribution vendor guidance for fixed kernel packages.
Prioritize kernels containing the listed stable fixes.
Inventory systems using RDMA, InfiniBand, or related kernel modules.
If RDMA is unused, consider disabling it under vendor guidance.
Track vendor advisories for impact and severity clarification.
Validation and detection
Compare running kernel builds against vendor fixed versions.
Confirm whether RDMA core functionality is installed, loaded, or required.
Review kernel package changelogs for the referenced stable commits.
Check vulnerability scanners for CVE-2025-71157 coverage updates.
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-71157 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
4Source links
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.
Jan 23, 2026, 14:25 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.