CVE-2025-37780

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-05-01. NVD baseline CVSS 7.1; 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-13027 (ENISA EUVD) · GHSA-w595-4hr6-r5fv (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

isofs: Prevent the use of too small fid

syzbot reported a slab-out-of-bounds Read in isofs_fh_to_parent. [1]

The handle_bytes value passed in by the reproducing program is equal to 12. In handle_to_path(), only 12 bytes of memory are allocated for the structure file_handle->f_handle member, which causes an out-of-bounds access when accessing the member parent_block of the structure isofs_fid in isofs, because accessing parent_block requires at least 16 bytes of f_handle. Here, fh_len is used to indirectly confirm that the value of handle_bytes is greater than 3 before accessing parent_block.

[1] BUG: KASAN: slab-out-of-bounds in isofs_fh_to_parent+0x1b8/0x210 fs/isofs/export.c:183 Read of size 4 at addr ffff0000cc030d94 by task syz-executor215/6466 CPU: 1 UID: 0 PID: 6466 Comm: syz-executor215 Not tainted 6.14.0-rc7-syzkaller-ga2392f333575 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:466 (C) __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0x198/0x550 mm/kasan/report.c:521 kasan_report+0xd8/0x138 mm/kasan/report.c:634 __asan_report_load4_noabort+0x20/0x2c mm/kasan/report_generic.c:380 isofs_fh_to_parent+0x1b8/0x210 fs/isofs/export.c:183 exportfs_decode_fh_raw+0x2dc/0x608 fs/exportfs/expfs.c:523 do_handle_to_path+0xa0/0x198 fs/fhandle.c:257 handle_to_path fs/fhandle.c:385 [inline] do_handle_open+0x8cc/0xb8c fs/fhandle.c:403 __do_sys_open_by_handle_at fs/fhandle.c:443 [inline] __se_sys_open_by_handle_at fs/fhandle.c:434 [inline] __arm64_sys_open_by_handle_at+0x80/0x94 fs/fhandle.c:434 __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+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600

Allocated by task 6466: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x40/0x78 mm/kasan/common.c:68 kasan_save_alloc_info+0x40/0x50 mm/kasan/generic.c:562 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0xac/0xc4 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __do_kmalloc_node mm/slub.c:4294 [inline] __kmalloc_noprof+0x32c/0x54c mm/slub.c:4306 kmalloc_noprof include/linux/slab.h:905 [inline] handle_to_path fs/fhandle.c:357 [inline] do_handle_open+0x5a4/0xb8c fs/fhandle.c:403 __do_sys_open_by_handle_at fs/fhandle.c:443 [inline] __se_sys_open_by_handle_at fs/fhandle.c:434 [inline] __arm64_sys_open_by_handle_at+0x80/0x94 fs/fhandle.c:434 __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+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 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
11th
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 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 (model v2026.06.15, score date 2026-10-26). 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

May 1, 2025

Last Modified

November 6, 2025

Advisory Details (10)

Auto-updated Oct 18, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4193-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4178-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
Web page

isofs: Prevent the use of too small fid - kernel/git/stable/linux.git - Linux kernel stable tree

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

isofs: Prevent the use of too small fid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/952e7a7e317f126d0a2b879fc531b716932d5ffa
Web page

isofs: Prevent the use of too small fid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63d5a3e207bf315a32c7d16de6c89753a759f95a
Web page

isofs: Prevent the use of too small fid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e7de55602c61c8ff28db075cc49c8dd6989d7e0
Web page

isofs: Prevent the use of too small fid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56dfffea9fd3be0b3795a9ca6401e133a8427e0b
Web page

isofs: Prevent the use of too small fid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fdafdaef796816a9ed0fd7ac812932d569d9beb
Web page

isofs: Prevent the use of too small fid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0405d4b63d082861f4eaff9d39c78ee9dc34f845
Web page

isofs: Prevent the use of too small fid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/007124c896e7d4614ac1f6bd4dedb975c35a2a8e

Vendor Advisories for CVE-2025-37780(1)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-10-27ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1084.80) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1087.77) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.144.141) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1088.92) @ jammy2026-10-27ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1083.89~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-10-27ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1052.56) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1083.81) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1094.92) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1094.79) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1094.103~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-27ubuntu
linuxKernel @ 5.4.293 (fixes >=2.6.12)—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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (45 versions)
  • every version up to 5.10.237-1: fixed in 5.10.237-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.129-1~deb11u1 (7 versions)
  • every version up to 6.1.137-1~deb11u1: fixed in 6.1.137-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (37 versions)
  • every version up to 6.1.135-1: fixed in 6.1.135-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-37780?
CVE-2025-37780 is a high-severity vulnerability; its CVE record was published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: isofs: Prevent the use of too small fid syzbot reported a slab-out-of-bounds Read in isofs_fh_to_parent. [1] The handle_bytes value passed in by the reproducing program is equal to 12. In handle_to_path(), only 12 bytes of memory…
When was the CVE record for CVE-2025-37780 published?
The CVE record for CVE-2025-37780 was published on May 1, 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 November 6, 2025; the record at its source may have been updated since.
Is CVE-2025-37780 actively exploited?
CVE-2025-37780 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-37780?
CVE-2025-37780 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2025-37780?
A fix for CVE-2025-37780 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-37780 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-37780

Explore →

Is Your Infrastructure Affected by CVE-2025-37780?

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

Book a Demo →Browse All CVEs