CVE-2025-71157

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-01-23. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

January 23, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

RDMA/core: always drop device refcount in ib_del_sub_device_and_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fe8d456080423b9ed410469fbd1e2098d3acce2b
generic

RDMA/core: always drop device refcount in ib_del_sub_device_and_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fa3c411d21ebc26ffd175c7256c37cefa35020aa
generic

RDMA/core: always drop device refcount in ib_del_sub_device_and_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/20436f2742a92b7afeb2504eb559a98d2196b001

Patch Availability(7)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)6.12.69-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (95 versions)6.18.5-1

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 7× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 157 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-19 19:33 UTCOSV refresh
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-17 19:30 UTCEPSS rescore
  5. 2026-09-16 14:07 UTCEPSS rescore
  6. 2026-09-16 05:14 UTCEPSS rescore
  7. 2026-09-15 03:10 UTCEPSS rescore
  8. 2026-09-12 15:00 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-11 09:36 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:00 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-08-31 23:04 UTCOSV refresh
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-27 14:24 UTCEPSS rescore
  21. 2026-08-25 13:48 UTCEPSS rescore
  22. 2026-08-24 14:16 UTCEPSS rescore
  23. 2026-08-23 00:18 UTCEPSS rescore
  24. 2026-08-21 23:48 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:46 UTCEPSS rescore
  4. 2026-08-16 14:55 UTCEPSS rescore
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-15 00:23 UTCVendor advisory
  8. 2026-08-15 00:23 UTCGHSA enrichment
  9. 2026-08-14 12:44 UTCEG score recompute
  10. 2026-08-14 12:44 UTCVendor advisory
  11. 2026-08-14 12:44 UTCGHSA enrichment
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-12 13:50 UTCEPSS rescore
  14. 2026-08-11 13:42 UTCEPSS rescore
  15. 2026-08-10 23:59 UTCEPSS rescore
  16. 2026-08-09 18:34 UTCEG score recompute
  17. 2026-08-09 18:34 UTCVendor advisory
  18. 2026-08-09 18:34 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-08 16:36 UTCEPSS rescore
  21. 2026-08-07 23:43 UTCEG score recompute
  22. 2026-08-07 23:43 UTCVendor advisory
  23. 2026-08-07 23:43 UTCGHSA enrichment
  24. 2026-08-07 16:27 UTCEPSS rescore
  25. 2026-08-06 13:46 UTCEPSS rescore
  26. 2026-08-06 05:05 UTCEG score recompute
  27. 2026-08-06 05:05 UTCVendor advisory
  28. 2026-08-06 05:05 UTCGHSA enrichment
  29. 2026-08-05 19:17 UTCEPSS rescore
  30. 2026-08-04 10:37 UTCEPSS rescore
  31. 2026-08-03 10:35 UTCEPSS rescore
  32. 2026-08-02 22:15 UTCEG score recompute
  33. 2026-08-02 22:15 UTCVendor advisory
  34. 2026-08-02 22:15 UTCGHSA enrichment
  35. 2026-08-02 02:26 UTCEPSS rescore
  36. 2026-07-31 08:42 UTCOSV refresh
  37. 2026-07-30 16:27 UTCEPSS rescore
  38. 2026-07-30 01:30 UTCEPSS rescore
  39. 2026-07-27 14:13 UTCEPSS rescore
  40. 2026-07-25 14:17 UTCEPSS rescore
  41. 2026-07-25 14:17 UTCEPSS rescore
  42. 2026-07-24 14:17 UTCEPSS rescore
  43. 2026-07-23 03:03 UTCEG score recompute
  44. 2026-07-22 14:08 UTCEPSS rescore
  45. 2026-07-21 15:24 UTCEPSS rescore
  46. 2026-07-20 17:08 UTCEPSS rescore
  47. 2026-07-19 14:30 UTCEPSS rescore
  48. 2026-07-19 14:30 UTCEPSS rescore
  49. 2026-07-19 02:28 UTCEPSS rescore
  50. 2026-07-19 02:28 UTCEPSS rescore
  51. 2026-07-18 10:04 UTCEPSS rescore
  52. 2026-07-18 10:04 UTCEPSS rescore
  53. 2026-07-16 17:02 UTCEPSS rescore
  54. 2026-07-16 17:02 UTCEPSS rescore
  55. 2026-07-15 16:57 UTCEPSS rescore
  56. 2026-07-15 16:57 UTCEPSS rescore
  57. 2026-07-15 02:00 UTCEPSS rescore
  58. 2026-07-15 01:59 UTCEPSS rescore
  59. 2026-07-13 15:38 UTCOSV refresh
  60. 2026-07-13 06:12 UTCEPSS rescore
  61. 2026-07-12 05:46 UTCEPSS rescore
  62. 2026-07-12 05:46 UTCEPSS rescore
  63. 2026-07-11 08:27 UTCEPSS rescore
  64. 2026-07-11 08:27 UTCEPSS rescore
  65. 2026-07-09 19:10 UTCEPSS rescore
  66. 2026-07-08 15:15 UTCEPSS rescore
  67. 2026-07-07 13:46 UTCEPSS rescore
  68. 2026-07-06 16:27 UTCEPSS rescore
  69. 2026-07-05 02:30 UTCEPSS rescore
  70. 2026-07-05 02:30 UTCEPSS rescore
  71. 2026-07-04 06:31 UTCEPSS rescore
  72. 2026-07-04 06:31 UTCEPSS rescore
  73. 2026-07-01 15:06 UTCEPSS rescore
  74. 2026-06-30 23:22 UTCEPSS rescore
  75. 2026-06-30 23:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-71157?
CVE-2025-71157 is a high vulnerability published on January 23, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/core: always drop device refcount in ibdelsubdeviceand_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…
When was CVE-2025-71157 disclosed?
CVE-2025-71157 was first published in the National Vulnerability Database on January 23, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71157 actively exploited?
CVE-2025-71157 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.4% of all scored CVEs.
What is the CVSS score of CVE-2025-71157?
CVE-2025-71157 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-71157?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71157, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71157

Explore →

Is Your Infrastructure Affected by CVE-2025-71157?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.