CVE-2025-21759

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-27. NVD baseline CVSS 7.8; sources differ by 0.0.

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ipv6: mcast: extend RCU protection in igmp6_send()

igmp6_send() can be called without RTNL or RCU being held.

Extend RCU protection so that we can safely fetch the net pointer and avoid a potential UAF.

Note that we no longer can use sock_alloc_send_skb() because ipv6.igmp_sk uses GFP_KERNEL allocations which can sleep.

Instead use alloc_skb() and charge the net->ipv6.igmp_sk socket under RCU protection.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
38(Track)
EG Risk 38/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%
Exploitation7% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
93.6%
KEV
Not listed

Published

February 27, 2025

Last Modified

March 24, 2025

Patch Availability(22)

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 11× in last 7d / 42× 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.

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

Frequently asked(5)

What is CVE-2025-21759?
CVE-2025-21759 is a high vulnerability published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: extend RCU protection in igmp6_send() igmp6_send() can be called without RTNL or RCU being held. Extend RCU protection so that we can safely fetch the net pointer and avoid a potential UAF. Note that we no longer can…
When was CVE-2025-21759 disclosed?
CVE-2025-21759 was first published in the National Vulnerability Database on February 27, 2025, with the most recent update on March 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-21759 actively exploited?
CVE-2025-21759 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-21759?
CVE-2025-21759 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-21759?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-21759, 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

Explore the affected products and dependency analysis for CVE-2025-21759

Explore →

Is Your Infrastructure Affected by CVE-2025-21759?

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