CVE-2025-38590

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-08-19. NVD baseline CVSS 5.5; 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-27919 (ENISA EUVD) · GHSA-wgrh-wq84-j2xm (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:

net/mlx5e: Remove skb secpath if xfrm state is not found

Hardware returns a unique identifier for a decrypted packet's xfrm state, this state is looked up in an xarray. However, the state might have been freed by the time of this lookup.

Currently, if the state is not found, only a counter is incremented. The secpath (sp) extension on the skb is not removed, resulting in sp->len becoming 0.

Subsequently, functions like __xfrm_policy_check() attempt to access fields such as xfrm_input_state(skb)->xso.type (which dereferences sp->xvec[sp->len - 1]) without first validating sp->len. This leads to a crash when dereferencing an invalid state pointer.

This patch prevents the crash by explicitly removing the secpath extension from the skb if the xfrm state is not found after hardware decryption. This ensures downstream functions do not operate on a zero-length secpath.

BUG: unable to handle page fault for address: ffffffff000002c8 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 282e067 P4D 282e067 PUD 0 Oops: Oops: 0000 [#1] SMP CPU: 12 UID: 0 PID: 0 Comm: swapper/12 Not tainted 6.15.0-rc7_for_upstream_min_debug_2025_05_27_22_44 #1 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:__xfrm_policy_check+0x61a/0xa30 Code: b6 77 7f 83 e6 02 74 14 4d 8b af d8 00 00 00 41 0f b6 45 05 c1 e0 03 48 98 49 01 c5 41 8b 45 00 83 e8 01 48 98 49 8b 44 c5 10 <0f> b6 80 c8 02 00 00 83 e0 0c 3c 04 0f 84 0c 02 00 00 31 ff 80 fa RSP: 0018:ffff88885fb04918 EFLAGS: 00010297 RAX: ffffffff00000000 RBX: 0000000000000002 RCX: 0000000000000000 RDX: 0000000000000002 RSI: 0000000000000002 RDI: 0000000000000000 RBP: ffffffff8311af80 R08: 0000000000000020 R09: 00000000c2eda353 R10: ffff88812be2bbc8 R11: 000000001faab533 R12: ffff88885fb049c8 R13: ffff88812be2bbc8 R14: 0000000000000000 R15: ffff88811896ae00 FS: 0000000000000000(0000) GS:ffff8888dca82000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffff000002c8 CR3: 0000000243050002 CR4: 0000000000372eb0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? try_to_wake_up+0x108/0x4c0 ? udp4_lib_lookup2+0xbe/0x150 ? udp_lib_lport_inuse+0x100/0x100 ? __udp4_lib_lookup+0x2b0/0x410 __xfrm_policy_check2.constprop.0+0x11e/0x130 udp_queue_rcv_one_skb+0x1d/0x530 udp_unicast_rcv_skb+0x76/0x90 __udp4_lib_rcv+0xa64/0xe90 ip_protocol_deliver_rcu+0x20/0x130 ip_local_deliver_finish+0x75/0xa0 ip_local_deliver+0xc1/0xd0 ? ip_protocol_deliver_rcu+0x130/0x130 ip_sublist_rcv+0x1f9/0x240 ? ip_rcv_finish_core+0x430/0x430 ip_list_rcv+0xfc/0x130 __netif_receive_skb_list_core+0x181/0x1e0 netif_receive_skb_list_internal+0x200/0x360 ? mlx5e_build_rx_skb+0x1bc/0xda0 [mlx5_core] gro_receive_skb+0xfd/0x210 mlx5e_handle_rx_cqe_mpwrq+0x141/0x280 [mlx5_core] mlx5e_poll_rx_cq+0xcc/0x8e0 [mlx5_core] ? mlx5e_handle_rx_dim+0x91/0xd0 [mlx5_core] mlx5e_napi_poll+0x114/0xab0 [mlx5_core] __napi_poll+0x25/0x170 net_rx_action+0x32d/0x3a0 ? mlx5_eq_comp_int+0x8d/0x280 [mlx5_core] ? notifier_call_chain+0x33/0xa0 handle_softirqs+0xda/0x250 irq_exit_rcu+0x6d/0xc0 common_interrupt+0x81/0xa0

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
35th
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

August 19, 2025

Last Modified

October 30, 2026

Advisory Details (5)

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

net/mlx5e: Remove skb secpath if xfrm state is not found - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/781a0bbf377443ef06f3248221f06cb555935530
Web page

net/mlx5e: Remove skb secpath if xfrm state is not found - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6d19c44b5c6dd72f9a357d0399604ec16a77de3c
Web page

net/mlx5e: Remove skb secpath if xfrm state is not found - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a5782431d84716b66302b07ff1b32fea1023bd5
Web page

net/mlx5e: Remove skb secpath if xfrm state is not found - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/314f568b84b01f6eac1e4313ca47f9ade4349443
Web page

net/mlx5e: Remove skb secpath if xfrm state is not found - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/137b12a4900eb6971b889839eab6036f72cbb217

Vendor Advisories for CVE-2025-38590(2)

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

Patch Availability(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-36.36) @ plucky2026-10-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1016.16~24.04.1) @ noble2026-10-30ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1016.16) @ noble2026-10-30ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1017.17~24.04.1) @ noble2026-10-30ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1018.18) @ plucky2026-10-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1017.17) @ plucky2026-10-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-30ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-30ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-30ubuntu
linuxKernel @ 6.6.102 (fixes >=5.9.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1~bpo12+1
  • every version up to 6.12.43-1: fixed in 6.12.43-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (62 versions)
  • every version up to 6.16.3-1: fixed in 6.16.3-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(22)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 45× 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 98 of 197 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38590?
CVE-2025-38590 is a medium-severity vulnerability; its CVE record was published on August 19, 2025. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Remove skb secpath if xfrm state is not found Hardware returns a unique identifier for a decrypted packet's xfrm state, this state is looked up in an xarray. However, the state might have been freed by the time of this…
When was the CVE record for CVE-2025-38590 published?
The CVE record for CVE-2025-38590 was published on August 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 October 30, 2026; the record at its source may have been updated since.
Is CVE-2025-38590 actively exploited?
CVE-2025-38590 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38590?
CVE-2025-38590 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38590?
A fix for CVE-2025-38590 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38590 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-38590

Explore →

Is Your Infrastructure Affected by CVE-2025-38590?

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

Book a Demo →Browse All CVEs