CVE-2025-21720

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-02-27. 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-5215 (ENISA EUVD) · GHSA-vcp2-pcm5-4hq8 (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.4%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

xfrm: delete intermediate secpath entry in packet offload mode

Packets handled by hardware have added secpath as a way to inform XFRM core code that this path was already handled. That secpath is not needed at all after policy is checked and it is removed later in the stack.

However, in the case of IP forwarding is enabled (/proc/sys/net/ipv4/ip_forward), that secpath is not removed and packets which already were handled are reentered to the driver TX path with xfrm_offload set.

The following kernel panic is observed in mlx5 in such case:

mlx5_core 0000:04:00.0 enp4s0f0np0: Link up mlx5_core 0000:04:00.1 enp4s0f1np1: Link up Initializing XFRM netlink socket IPsec XFRM device driver BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page PGD 0 P4D 0 Oops: Oops: 0010 [#1] PREEMPT SMP CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.13.0-rc1-alex #3 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. RSP: 0018:ffffb87380003800 EFLAGS: 00010206 RAX: ffff8df004e02600 RBX: ffffb873800038d8 RCX: 00000000ffff98cf RDX: ffff8df00733e108 RSI: ffff8df00521fb80 RDI: ffff8df001661f00 RBP: ffffb87380003850 R08: ffff8df013980000 R09: 0000000000000010 R10: 0000000000000002 R11: 0000000000000002 R12: ffff8df001661f00 R13: ffff8df00521fb80 R14: ffff8df00733e108 R15: ffff8df011faf04e FS: 0000000000000000(0000) GS:ffff8df46b800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffffffffd6 CR3: 0000000106384000 CR4: 0000000000350ef0 Call Trace: ? show_regs+0x63/0x70 ? __die_body+0x20/0x60 ? __die+0x2b/0x40 ? page_fault_oops+0x15c/0x550 ? do_user_addr_fault+0x3ed/0x870 ? exc_page_fault+0x7f/0x190 ? asm_exc_page_fault+0x27/0x30 mlx5e_ipsec_handle_tx_skb+0xe7/0x2f0 [mlx5_core] mlx5e_xmit+0x58e/0x1980 [mlx5_core] ? __fib_lookup+0x6a/0xb0 dev_hard_start_xmit+0x82/0x1d0 sch_direct_xmit+0xfe/0x390 __dev_queue_xmit+0x6d8/0xee0 ? __fib_lookup+0x6a/0xb0 ? internal_add_timer+0x48/0x70 ? mod_timer+0xe2/0x2b0 neigh_resolve_output+0x115/0x1b0 __neigh_update+0x26a/0xc50 neigh_update+0x14/0x20 arp_process+0x2cb/0x8e0 ? __napi_build_skb+0x5e/0x70 arp_rcv+0x11e/0x1c0 ? dev_gro_receive+0x574/0x820 __netif_receive_skb_list_core+0x1cf/0x1f0 netif_receive_skb_list_internal+0x183/0x2a0 napi_complete_done+0x76/0x1c0 mlx5e_napi_poll+0x234/0x7a0 [mlx5_core] __napi_poll+0x2d/0x1f0 net_rx_action+0x1a6/0x370 ? atomic_notifier_call_chain+0x3b/0x50 ? irq_int_handler+0x15/0x20 [mlx5_core] handle_softirqs+0xb9/0x2f0 ? handle_irq_event+0x44/0x60 irq_exit_rcu+0xdb/0x100 common_interrupt+0x98/0xc0 asm_common_interrupt+0x27/0x40 RIP: 0010:pv_native_safe_halt+0xb/0x10 Code: 09 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 22 0f 1f 84 00 00 00 00 00 90 eb 07 0f 00 2d 7f e9 36 00 fb 40 00 83 ff 07 77 21 89 ff ff 24 fd 88 3d a1 bd 0f 21 f8 RSP: 0018:ffffffffbe603de8 EFLAGS: 00000202 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000f92f46680 RDX: 0000000000000037 RSI: 00000000ffffffff RDI: 00000000000518d4 RBP: ffffffffbe603df0 R08: 000000cd42e4dffb R09: ffffffffbe603d70 R10: 0000004d80d62680 R11: 0000000000000001 R12: ffffffffbe60bf40 R13: 0000000000000000 R14: 0000000000000000 R15: ffffffffbe60aff8 ? default_idle+0x9/0x20 arch_cpu_idle+0x9/0x10 default_idle_call+0x29/0xf0 do_idle+0x1f2/0x240 cpu_startup_entry+0x2c/0x30 rest_init+0xe7/0x100 start_kernel+0x76b/0xb90 x86_64_start_reservations+0x18/0x30 x86_64_start_kernel+0xc0/0x110 ? setup_ghcb+0xe/0x130 common_startup_64+0x13e/0x141 Modules linked in: esp4_offload esp4 xfrm_interface xfrm6_tunnel tunnel4 tunnel6 xfrm_user xfrm_algo binf ---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.4% × 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.4%
EPSS %ILE
30th
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.4% 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 (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

February 27, 2025

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 5, 2026
Patch available.
Web page

xfrm: delete intermediate secpath entry in packet offload mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/600258d555f0710b9c47fb78d2d80a4aecd608cc
Web page

xfrm: delete intermediate secpath entry in packet offload mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/981ad4c882096e7375b8c2181dd4c3ee58ea5bae
Web page

xfrm: delete intermediate secpath entry in packet offload mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6945701ca1572f81bc9bb46f624b02eabb3eaf3e
Web page

xfrm: delete intermediate secpath entry in packet offload mode - kernel/git/stable/linux.git - Linux kernel stable tree

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-26.26) @ oracular2026-10-24ubuntu
ubuntulinux-tools-oracle-64k (6.11.0-1016.17) @ oracular2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1029.30) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1022.23) @ noble2026-10-24ubuntu
ubuntulinux-virtual-6.8 (6.8.0-64.67) @ noble2026-10-24ubuntu
ubuntulinux-tools-gcp-lts-24.04 (6.8.0-1033.35) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-64.67~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-64.67.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-aws (6.11.0-1014.15) @ oracular2026-10-24ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1025.26) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1031.35) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2026.27) @ noble2026-10-24ubuntu
linuxKernel @ 6.6.76 (fixes >=6.2.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.13-1: fixed in 6.12.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—

Weakness Classification(1)

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

All Vendor Advisories

(12)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-21720?
CVE-2025-21720 is a medium-severity vulnerability; its CVE record was published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: xfrm: delete intermediate secpath entry in packet offload mode Packets handled by hardware have added secpath as a way to inform XFRM core code that this path was already handled. That secpath is not needed at all after policy is…
When was the CVE record for CVE-2025-21720 published?
The CVE record for CVE-2025-21720 was published on February 27, 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-21720 actively exploited?
CVE-2025-21720 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21720?
CVE-2025-21720 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21720?
A fix for CVE-2025-21720 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-21720

Explore →

Is Your Infrastructure Affected by CVE-2025-21720?

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

Book a Demo →Browse All CVEs