CVE-2025-21652

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-2601 (ENISA EUVD) · GHSA-p277-wqpc-75vw (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ipvlan: Fix use-after-free in ipvlan_get_iflink().

syzbot presented an use-after-free report [0] regarding ipvlan and linkwatch.

ipvlan does not hold a refcnt of the lower device unlike vlan and macvlan.

If the linkwatch work is triggered for the ipvlan dev, the lower dev might have already been freed, resulting in UAF of ipvlan->phy_dev in ipvlan_get_iflink().

We can delay the lower dev unregistration like vlan and macvlan by holding the lower dev's refcnt in dev->netdev_ops->ndo_init() and releasing it in dev->priv_destructor().

Jakub pointed out calling .ndo_XXX after unregister_netdevice() has returned is error prone and suggested [1] addressing this UAF in the core by taking commit 750e51603395 ("net: avoid potential UAF in default_operstate()") further.

Let's assume unregistering devices DOWN and use RCU protection in default_operstate() not to race with the device unregistration.

[0]: BUG: KASAN: slab-use-after-free in ipvlan_get_iflink+0x84/0x88 drivers/net/ipvlan/ipvlan_main.c:353 Read of size 4 at addr ffff0000d768c0e0 by task kworker/u8:35/6944

CPU: 0 UID: 0 PID: 6944 Comm: kworker/u8:35 Not tainted 6.13.0-rc2-g9bc5c9515b48 #12 4c3cb9e8b4565456f6a355f312ff91f4f29b3c47 Hardware name: linux,dummy-virt (DT) Workqueue: events_unbound linkwatch_event Call trace: show_stack+0x38/0x50 arch/arm64/kernel/stacktrace.c:484 (C) __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xbc/0x108 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x16c/0x6f0 mm/kasan/report.c:489 kasan_report+0xc0/0x120 mm/kasan/report.c:602 __asan_report_load4_noabort+0x20/0x30 mm/kasan/report_generic.c:380 ipvlan_get_iflink+0x84/0x88 drivers/net/ipvlan/ipvlan_main.c:353 dev_get_iflink+0x7c/0xd8 net/core/dev.c:674 default_operstate net/core/link_watch.c:45 [inline] rfc2863_policy+0x144/0x360 net/core/link_watch.c:72 linkwatch_do_dev+0x60/0x228 net/core/link_watch.c:175 __linkwatch_run_queue+0x2f4/0x5b8 net/core/link_watch.c:239 linkwatch_event+0x64/0xa8 net/core/link_watch.c:282 process_one_work+0x700/0x1398 kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x8c4/0xe10 kernel/workqueue.c:3391 kthread+0x2b0/0x360 kernel/kthread.c:389 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862

Allocated by task 9303: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x30/0x68 mm/kasan/common.c:68 kasan_save_alloc_info+0x44/0x58 mm/kasan/generic.c:568 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0x84/0xa0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __do_kmalloc_node mm/slub.c:4283 [inline] __kmalloc_node_noprof+0x2a0/0x560 mm/slub.c:4289 __kvmalloc_node_noprof+0x9c/0x230 mm/util.c:650 alloc_netdev_mqs+0xb4/0x1118 net/core/dev.c:11209 rtnl_create_link+0x2b8/0xb60 net/core/rtnetlink.c:3595 rtnl_newlink_create+0x19c/0x868 net/core/rtnetlink.c:3771 __rtnl_newlink net/core/rtnetlink.c:3896 [inline] rtnl_newlink+0x122c/0x15c0 net/core/rtnetlink.c:4011 rtnetlink_rcv_msg+0x61c/0x918 net/core/rtnetlink.c:6901 netlink_rcv_skb+0x1dc/0x398 net/netlink/af_netlink.c:2542 rtnetlink_rcv+0x34/0x50 net/core/rtnetlink.c:6928 netlink_unicast_kernel net/netlink/af_netlink.c:1321 [inline] netlink_unicast+0x618/0x838 net/netlink/af_netlink.c:1347 netlink_sendmsg+0x5fc/0x8b0 net/netlink/af_netlink.c:1891 sock_sendmsg_nosec net/socket.c:711 [inline] __sock_sendmsg net/socket.c:726 [inline] __sys_sendto+0x2ec/0x438 net/socket.c:2197 __do_sys_sendto net/socket.c:2204 [inline] __se_sys_sendto net/socket.c:2200 [inline] __arm64_sys_sendto+0xe4/0x110 net/socket.c:2200 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x90/0x278 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x13c/0x250 arch/arm64/kernel/syscall.c:132 do_el0_svc+0x54/0x70 arch/arm64/kernel/syscall.c:151 el ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 19, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 30, 2026
Patch available.
Web page

ipvlan: Fix use-after-free in ipvlan_get_iflink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cb358ff94154774d031159b018adf45e17673941
Web page

ipvlan: Fix use-after-free in ipvlan_get_iflink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52a24538d569f48e79d1a169a5d359d384152950
Web page

ipvlan: Fix use-after-free in ipvlan_get_iflink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba9f7c16ec879c83bb4f80406773a911aace8267

Vendor Advisories for CVE-2025-21652(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(18)

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 rangeFix by version rangeDependents
linux—
  • every version up to 6.12.10-1: fixed in 6.12.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.10-1: fixed in 6.12.10-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 202 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-21652?
CVE-2025-21652 is a high-severity vulnerability; its CVE record was published on January 19, 2025. In the Linux kernel, the following vulnerability has been resolved: ipvlan: Fix use-after-free in ipvlan_get_iflink(). syzbot presented an use-after-free report [0] regarding ipvlan and linkwatch. ipvlan does not hold a refcnt of the lower device unlike vlan and macvlan. If the linkwatch work is…
When was the CVE record for CVE-2025-21652 published?
The CVE record for CVE-2025-21652 was published on January 19, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-21652 actively exploited?
CVE-2025-21652 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21652?
CVE-2025-21652 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-21652?
A fix for CVE-2025-21652 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-21652 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-21652?

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