CVE-2025-21677

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-01-31. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-2626 (ENISA EUVD) · GHSA-ch6g-q299-j266 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

pfcp: Destroy device along with udp socket's netns dismantle.

pfcp_newlink() links the device to a list in dev_net(dev) instead of net, where a udp tunnel socket is created.

Even when net is removed, the device stays alive on dev_net(dev). Then, removing net triggers the splat below. [0]

In this example, pfcp0 is created in ns2, but the udp socket is created in ns1.

ip netns add ns1 ip netns add ns2 ip -n ns1 link add netns ns2 name pfcp0 type pfcp ip netns del ns1

Let's link the device to the socket's netns instead.

Now, pfcp_net_exit() needs another netdev iteration to remove all pfcp devices in the netns.

pfcp_dev_list is not used under RCU, so the list API is converted to the non-RCU variant.

pfcp_net_exit() can be converted to .exit_batch_rtnl() in net-next.

[0]: ref_tracker: net notrefcnt@00000000128b34dc has 1/1 users at sk_alloc (./include/net/net_namespace.h:345 net/core/sock.c:2236) inet_create (net/ipv4/af_inet.c:326 net/ipv4/af_inet.c:252) __sock_create (net/socket.c:1558) udp_sock_create4 (net/ipv4/udp_tunnel_core.c:18) pfcp_create_sock (drivers/net/pfcp.c:168) pfcp_newlink (drivers/net/pfcp.c:182 drivers/net/pfcp.c:197) rtnl_newlink (net/core/rtnetlink.c:3786 net/core/rtnetlink.c:3897 net/core/rtnetlink.c:4012) rtnetlink_rcv_msg (net/core/rtnetlink.c:6922) netlink_rcv_skb (net/netlink/af_netlink.c:2542) netlink_unicast (net/netlink/af_netlink.c:1321 net/netlink/af_netlink.c:1347) netlink_sendmsg (net/netlink/af_netlink.c:1891) ____sys_sendmsg (net/socket.c:711 net/socket.c:726 net/socket.c:2583) ___sys_sendmsg (net/socket.c:2639) __sys_sendmsg (net/socket.c:2669) do_syscall_64 (arch/x86/entry/common.c:52 arch/x86/entry/common.c:83) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)

WARNING: CPU: 1 PID: 11 at lib/ref_tracker.c:179 ref_tracker_dir_exit (lib/ref_tracker.c:179) Modules linked in: CPU: 1 UID: 0 PID: 11 Comm: kworker/u16:0 Not tainted 6.13.0-rc5-00147-g4c1224501e9d #5 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 Workqueue: netns cleanup_net RIP: 0010:ref_tracker_dir_exit (lib/ref_tracker.c:179) Code: 00 00 00 fc ff df 4d 8b 26 49 bd 00 01 00 00 00 00 ad de 4c 39 f5 0f 85 df 00 00 00 48 8b 74 24 08 48 89 df e8 a5 cc 12 02 90 <0f> 0b 90 48 8d 6b 44 be 04 00 00 00 48 89 ef e8 80 de 67 ff 48 89 RSP: 0018:ff11000007f3fb60 EFLAGS: 00010286 RAX: 00000000000020ef RBX: ff1100000d6481e0 RCX: 1ffffffff0e40d82 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8423ee3c RBP: ff1100000d648230 R08: 0000000000000001 R09: fffffbfff0e395af R10: 0000000000000001 R11: 0000000000000000 R12: ff1100000d648230 R13: dead000000000100 R14: ff1100000d648230 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ff1100006ce80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005620e1363990 CR3: 000000000eeb2002 CR4: 0000000000771ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ? __warn (kernel/panic.c:748) ? ref_tracker_dir_exit (lib/ref_tracker.c:179) ? report_bug (lib/bug.c:201 lib/bug.c:219) ? handle_bug (arch/x86/kernel/traps.c:285) ? exc_invalid_op (arch/x86/kernel/traps.c:309 (discriminator 1)) ? asm_exc_invalid_op (./arch/x86/include/asm/idtentry.h:621) ? _raw_spin_unlock_irqrestore (./arch/x86/include/asm/irqflags.h:42 ./arch/x86/include/asm/irqflags.h:97 ./arch/x86/include/asm/irqflags.h:155 ./include/linux/spinlock_api_smp.h:151 kernel/locking/spinlock.c:194) ? ref_tracker_dir_exit (lib/ref_tracker.c:179) ? __pfx_ref_tracker_dir_exit (lib/ref_tracker.c:158) ? kfree (mm/slub.c:4613 mm/slub.c:4761) net_free (net/core/net_namespace.c:476 net/core/net_namespace.c:467) cleanup_net (net/cor ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
8th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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 (model v2026.06.15, score date 2026-10-25). 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 31, 2025

Last Modified

August 5, 2026

Advisory Details (2)

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

pfcp: Destroy device along with udp socket's netns dismantle. - kernel/git/stable/linux.git - Linux kernel stable tree

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

pfcp: Destroy device along with udp socket's netns dismantle. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c35a66e2bfea53dea3562b2575ac7fd4c38ee61

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-edge (6.11.0-1013.13~24.04.1) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-24.24+1) @ oracular2026-10-24ubuntu
linuxKernel @ 6.12.11 (fixes >=6.10.0)—osv

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 40× 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 208 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 112 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-21677?
CVE-2025-21677 is a medium-severity vulnerability; its CVE record was published on January 31, 2025. In the Linux kernel, the following vulnerability has been resolved: pfcp: Destroy device along with udp socket's netns dismantle. pfcp_newlink() links the device to a list in dev_net(dev) instead of net, where a udp tunnel socket is created. Even when net is removed, the device stays alive on…
When was the CVE record for CVE-2025-21677 published?
The CVE record for CVE-2025-21677 was published on January 31, 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-21677 actively exploited?
CVE-2025-21677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21677?
CVE-2025-21677 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21677?
A fix for CVE-2025-21677 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-21677?

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

Book a Demo →Browse All CVEs