CVE-2025-37738

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
7.8EG
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.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ext4: ignore xattrs past end

Once inside 'ext4_xattr_inode_dec_ref_all' we should ignore xattrs entries past the 'end' entry.

This fixes the following KASAN reported issue:

================================================================== BUG: KASAN: slab-use-after-free in ext4_xattr_inode_dec_ref_all+0xb8c/0xe90 Read of size 4 at addr ffff888012c120c4 by task repro/2065

CPU: 1 UID: 0 PID: 2065 Comm: repro Not tainted 6.13.0-rc2+ #11 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Call Trace: dump_stack_lvl+0x1fd/0x300 ? tcp_gro_dev_warn+0x260/0x260 ? _printk+0xc0/0x100 ? read_lock_is_recursive+0x10/0x10 ? irq_work_queue+0x72/0xf0 ? __virt_addr_valid+0x17b/0x4b0 print_address_description+0x78/0x390 print_report+0x107/0x1f0 ? __virt_addr_valid+0x17b/0x4b0 ? __virt_addr_valid+0x3ff/0x4b0 ? __phys_addr+0xb5/0x160 ? ext4_xattr_inode_dec_ref_all+0xb8c/0xe90 kasan_report+0xcc/0x100 ? ext4_xattr_inode_dec_ref_all+0xb8c/0xe90 ext4_xattr_inode_dec_ref_all+0xb8c/0xe90 ? ext4_xattr_delete_inode+0xd30/0xd30 ? __ext4_journal_ensure_credits+0x5f0/0x5f0 ? __ext4_journal_ensure_credits+0x2b/0x5f0 ? inode_update_timestamps+0x410/0x410 ext4_xattr_delete_inode+0xb64/0xd30 ? ext4_truncate+0xb70/0xdc0 ? ext4_expand_extra_isize_ea+0x1d20/0x1d20 ? __ext4_mark_inode_dirty+0x670/0x670 ? ext4_journal_check_start+0x16f/0x240 ? ext4_inode_is_fast_symlink+0x2f2/0x3a0 ext4_evict_inode+0xc8c/0xff0 ? ext4_inode_is_fast_symlink+0x3a0/0x3a0 ? do_raw_spin_unlock+0x53/0x8a0 ? ext4_inode_is_fast_symlink+0x3a0/0x3a0 evict+0x4ac/0x950 ? proc_nr_inodes+0x310/0x310 ? trace_ext4_drop_inode+0xa2/0x220 ? _raw_spin_unlock+0x1a/0x30 ? iput+0x4cb/0x7e0 do_unlinkat+0x495/0x7c0 ? try_break_deleg+0x120/0x120 ? 0xffffffff81000000 ? __check_object_size+0x15a/0x210 ? strncpy_from_user+0x13e/0x250 ? getname_flags+0x1dc/0x530 __x64_sys_unlinkat+0xc8/0xf0 do_syscall_64+0x65/0x110 entry_SYSCALL_64_after_hwframe+0x67/0x6f RIP: 0033:0x434ffd Code: 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 8 RSP: 002b:00007ffc50fa7b28 EFLAGS: 00000246 ORIG_RAX: 0000000000000107 RAX: ffffffffffffffda RBX: 00007ffc50fa7e18 RCX: 0000000000434ffd RDX: 0000000000000000 RSI: 0000000020000240 RDI: 0000000000000005 RBP: 00007ffc50fa7be0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007ffc50fa7e08 R14: 00000000004bbf30 R15: 0000000000000001

The buggy address belongs to the object at ffff888012c12000 which belongs to the cache filp of size 360 The buggy address is located 196 bytes inside of freed 360-byte region [ffff888012c12000, ffff888012c12168)

The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x12c12 head: order:1 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0 flags: 0x40(head|node=0|zone=0) page_type: f5(slab) raw: 0000000000000040 ffff888000ad7640 ffffea0000497a00 dead000000000004 raw: 0000000000000000 0000000000100010 00000001f5000000 0000000000000000 head: 0000000000000040 ffff888000ad7640 ffffea0000497a00 dead000000000004 head: 0000000000000000 0000000000100010 00000001f5000000 0000000000000000 head: 0000000000000001 ffffea00004b0481 ffffffffffffffff 0000000000000000 head: 0000000000000002 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff888012c11f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888012c12000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb > ffff888012c12080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888012c12100: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc ffff888012c12180: fc fc fc fc fc fc fc fc fc ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
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

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.

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

August 5, 2026

Advisory Details (10)

Auto-updated Jul 30, 2026
Patch available.
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

ext4: ignore xattrs past end - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: ignore xattrs past end - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: ignore xattrs past end - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: ignore xattrs past end - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: ignore xattrs past end - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/836e625b03a666cf93ff5be328c8cb30336db872
Web page

ext4: ignore xattrs past end - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/76c365fa7e2a8bb85f0190cdb4b8cdc99b2fdce3
Web page

ext4: ignore xattrs past end - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: ignore xattrs past end - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: ignore xattrs past end - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/362a90cecd36e8a5c415966d0b75b04a0270e4dd

Vendor Advisories for CVE-2025-37738(13)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-edge (5.15.0.1094.103~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1094.79) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-30ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1043.44~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-05-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-05-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-05-30ubuntu
redhatkernel-0:4.18.0-372.155.1.el8_62025-08-06redhat
redhatkernel-0:4.18.0-477.104.1.el8_82025-08-05redhat
redhatkernel-0:4.18.0-193.162.1.el8_22025-08-04redhat
redhatkernel-0:4.18.0-305.165.1.el8_42025-07-30redhat
redhatkernel-0:4.18.0-553.62.1.el8_102025-07-16redhat
redhatkernel-rt-0:4.18.0-553.62.1.rt7.403.el8_102025-07-16redhat
redhatkernel-0:5.14.0-427.77.1.el9_42025-07-15redhat
redhatkernel-0:5.14.0-70.138.1.el9_02025-07-14redhat
redhatkernel-rt-0:5.14.0-70.138.1.rt21.210.el9_02025-07-14redhat
redhatkernel-0:5.14.0-284.124.1.el9_22025-07-09redhat
redhatkernel-rt-0:5.14.0-284.124.1.rt14.409.el9_22025-07-09redhat
redhatkernel-0:6.12.0-55.18.1.el10_02025-06-23redhat
redhatkernel-0:5.14.0-570.23.1.el9_62025-06-23redhat
linuxKernel @ 5.4.293 (fixes >=4.13.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

(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

(12)

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 11× in last 7d / 29× 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 91 of 165 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. 9 repeat rows among the latest 100 are merged into the row they repeat. The 74 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-37738?
CVE-2025-37738 is a high-severity vulnerability; its CVE record was published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: ext4: ignore xattrs past end Once inside 'ext4xattrinodedecref_all' we should ignore xattrs entries past the 'end' entry. This fixes the following KASAN reported issue:…
When was the CVE record for CVE-2025-37738 published?
The CVE record for CVE-2025-37738 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-37738 actively exploited?
CVE-2025-37738 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-37738?
CVE-2025-37738 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-37738?
A fix for CVE-2025-37738 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-37738 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-37738

Explore →

Is Your Infrastructure Affected by CVE-2025-37738?

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

Book a Demo →Browse All CVEs