CVE-2025-38475

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-07-28. 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-22887 (ENISA EUVD) · GHSA-wfpw-m32p-qqfp (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:

smc: Fix various oops due to inet_sock type confusion.

syzbot reported weird splats [0][1] in cipso_v4_sock_setattr() while freeing inet_sk(sk)->inet_opt.

The address was freed multiple times even though it was read-only memory.

cipso_v4_sock_setattr() did nothing wrong, and the root cause was type confusion.

The cited commit made it possible to create smc_sock as an INET socket.

The issue is that struct smc_sock does not have struct inet_sock as the first member but hijacks AF_INET and AF_INET6 sk_family, which confuses various places.

In this case, inet_sock.inet_opt was actually smc_sock.clcsk_data_ready(), which is an address of a function in the text segment.

$ pahole -C inet_sock vmlinux struct inet_sock { ... struct ip_options_rcu * inet_opt; /* 784 8 */

$ pahole -C smc_sock vmlinux struct smc_sock { ... void (*clcsk_data_ready)(struct sock *); /* 784 8 */

The same issue for another field was reported before. [2][3]

At that time, an ugly hack was suggested [4], but it makes both INET and SMC code error-prone and hard to change.

Also, yet another variant was fixed by a hacky commit 98d4435efcbf3 ("net/smc: prevent NULL pointer dereference in txopt_get").

Instead of papering over the root cause by such hacks, we should not allow non-INET socket to reuse the INET infra.

Let's add inet_sock as the first member of smc_sock.

[0]: kvfree_call_rcu(): Double-freed call. rcu_head 000000006921da73 WARNING: CPU: 0 PID: 6718 at mm/slab_common.c:1956 kvfree_call_rcu+0x94/0x3f0 mm/slab_common.c:1955 Modules linked in: CPU: 0 UID: 0 PID: 6718 Comm: syz.0.17 Tainted: G W 6.16.0-rc4-syzkaller-g7482bb149b9f #0 PREEMPT Tainted: [W]=WARN Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : kvfree_call_rcu+0x94/0x3f0 mm/slab_common.c:1955 lr : kvfree_call_rcu+0x94/0x3f0 mm/slab_common.c:1955 sp : ffff8000a03a7730 x29: ffff8000a03a7730 x28: 00000000fffffff5 x27: 1fffe000184823d3 x26: dfff800000000000 x25: ffff0000c2411e9e x24: ffff0000dd88da00 x23: ffff8000891ac9a0 x22: 00000000ffffffea x21: ffff8000891ac9a0 x20: ffff8000891ac9a0 x19: ffff80008afc2480 x18: 00000000ffffffff x17: 0000000000000000 x16: ffff80008ae642c8 x15: ffff700011ede14c x14: 1ffff00011ede14c x13: 0000000000000004 x12: ffffffffffffffff x11: ffff700011ede14c x10: 0000000000ff0100 x9 : 5fa3c1ffaf0ff000 x8 : 5fa3c1ffaf0ff000 x7 : 0000000000000001 x6 : 0000000000000001 x5 : ffff8000a03a7078 x4 : ffff80008f766c20 x3 : ffff80008054d360 x2 : 0000000000000000 x1 : 0000000000000201 x0 : 0000000000000000 Call trace: kvfree_call_rcu+0x94/0x3f0 mm/slab_common.c:1955 (P) cipso_v4_sock_setattr+0x2f0/0x3f4 net/ipv4/cipso_ipv4.c:1914 netlbl_sock_setattr+0x240/0x334 net/netlabel/netlabel_kapi.c:1000 smack_netlbl_add+0xa8/0x158 security/smack/smack_lsm.c:2581 smack_inode_setsecurity+0x378/0x430 security/smack/smack_lsm.c:2912 security_inode_setsecurity+0x118/0x3c0 security/security.c:2706 __vfs_setxattr_noperm+0x174/0x5c4 fs/xattr.c:251 __vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:295 vfs_setxattr+0x158/0x2ac fs/xattr.c:321 do_setxattr fs/xattr.c:636 [inline] file_setxattr+0x1b8/0x294 fs/xattr.c:646 path_setxattrat+0x2ac/0x320 fs/xattr.c:711 __do_sys_fsetxattr fs/xattr.c:761 [inline] __se_sys_fsetxattr fs/xattr.c:758 [inline] __arm64_sys_fsetxattr+0xc0/0xdc fs/xattr.c:758 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600

[ ---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
6th
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. 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

July 28, 2025

Last Modified

August 5, 2026

Advisory Details (3)

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

smc: Fix various oops due to inet_sock type confusion. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67a167a6b8b45607bc34aa541d1c75097d18d460
Web page

smc: Fix various oops due to inet_sock type confusion. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60ada4fe644edaa6c2da97364184b0425e8aeaf5
Web page

smc: Fix various oops due to inet_sock type confusion. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5b02e397929e5b13b969ef1f8e43c7951e2864f5

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-36.36) @ plucky2026-10-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1016.16~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1016.16) @ noble2026-10-23ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1018.18) @ plucky2026-10-23ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1017.17~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1017.17) @ plucky2026-10-23ubuntu
linuxKernel @ 6.12.40 (fixes >=6.11.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
linux6.12.38-1
  • every version up to 6.12.41-1: fixed in 6.12.41-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.

All Vendor Advisories

(6)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38475?
CVE-2025-38475 is a medium-severity vulnerability; its CVE record was published on July 28, 2025. In the Linux kernel, the following vulnerability has been resolved: smc: Fix various oops due to inet_sock type confusion. syzbot reported weird splats [0][1] in cipso_v4_sock_setattr() while freeing inet_sk(sk)->inet_opt. The address was freed multiple times even though it was read-only memory.…
When was the CVE record for CVE-2025-38475 published?
The CVE record for CVE-2025-38475 was published on July 28, 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-38475 actively exploited?
CVE-2025-38475 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38475?
CVE-2025-38475 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38475?
A fix for CVE-2025-38475 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-38475

Explore →

Is Your Infrastructure Affected by CVE-2025-38475?

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

Book a Demo →Browse All CVEs