CVE-2025-37741

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-05-01. 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-13074 (ENISA EUVD) · GHSA-q2h8-9338-55xq (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:

jfs: Prevent copying of nlink with value 0 from disk inode

syzbot report a deadlock in diFree. [1]

When calling "ioctl$LOOP_SET_STATUS64", the offset value passed in is 4, which does not match the mounted loop device, causing the mapping of the mounted loop device to be invalidated.

When creating the directory and creating the inode of iag in diReadSpecial(), read the page of fixed disk inode (AIT) in raw mode in read_metapage(), the metapage data it returns is corrupted, which causes the nlink value of 0 to be assigned to the iag inode when executing copy_from_dinode(), which ultimately causes a deadlock when entering diFree().

To avoid this, first check the nlink value of dinode before setting iag inode.

[1] WARNING: possible recursive locking detected 6.12.0-rc7-syzkaller-00212-g4a5df3796467 #0 Not tainted -------------------------------------------- syz-executor301/5309 is trying to acquire lock: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x37c/0x2fb0 fs/jfs/jfs_imap.c:889

but task is already holding lock: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diAlloc+0x1b6/0x1630

other info that might help us debug this: Possible unsafe locking scenario:

CPU0 ---- lock(&(imap->im_aglock[index])); lock(&(imap->im_aglock[index]));

* DEADLOCK *

May be due to missing lock nesting notation

5 locks held by syz-executor301/5309: #0: ffff8880422a4420 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:515 #1: ffff88804755b390 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:850 [inline] #1: ffff88804755b390 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x260/0x540 fs/namei.c:4026 #2: ffff888044548920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diAlloc+0x1b6/0x1630 #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diNewIAG fs/jfs/jfs_imap.c:2460 [inline] #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diAllocExt fs/jfs/jfs_imap.c:1905 [inline] #3: ffff888044548890 (&imap->im_freelock){+.+.}-{3:3}, at: diAllocAG+0x4b7/0x1e50 fs/jfs/jfs_imap.c:1669 #4: ffff88804755a618 (&jfs_ip->rdwrlock/1){++++}-{3:3}, at: diNewIAG fs/jfs/jfs_imap.c:2477 [inline] #4: ffff88804755a618 (&jfs_ip->rdwrlock/1){++++}-{3:3}, at: diAllocExt fs/jfs/jfs_imap.c:1905 [inline] #4: ffff88804755a618 (&jfs_ip->rdwrlock/1){++++}-{3:3}, at: diAllocAG+0x869/0x1e50 fs/jfs/jfs_imap.c:1669

stack backtrace: CPU: 0 UID: 0 PID: 5309 Comm: syz-executor301 Not tainted 6.12.0-rc7-syzkaller-00212-g4a5df3796467 #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_deadlock_bug+0x483/0x620 kernel/locking/lockdep.c:3037 check_deadlock kernel/locking/lockdep.c:3089 [inline] validate_chain+0x15e2/0x5920 kernel/locking/lockdep.c:3891 __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5202 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825 __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752 diFree+0x37c/0x2fb0 fs/jfs/jfs_imap.c:889 jfs_evict_inode+0x32d/0x440 fs/jfs/inode.c:156 evict+0x4e8/0x9b0 fs/inode.c:725 diFreeSpecial fs/jfs/jfs_imap.c:552 [inline] duplicateIXtree+0x3c6/0x550 fs/jfs/jfs_imap.c:3022 diNewIAG fs/jfs/jfs_imap.c:2597 [inline] diAllocExt fs/jfs/jfs_imap.c:1905 [inline] diAllocAG+0x17dc/0x1e50 fs/jfs/jfs_imap.c:1669 diAlloc+0x1d2/0x1630 fs/jfs/jfs_imap.c:1590 ialloc+0x8f/0x900 fs/jfs/jfs_inode.c:56 jfs_mkdir+0x1c5/0xba0 fs/jfs/namei.c:225 vfs_mkdir+0x2f9/0x4f0 fs/namei.c:4257 do_mkdirat+0x264/0x3a0 fs/namei.c:4280 __do_sys_mkdirat fs/namei.c:4295 [inline] __se_sys_mkdirat fs/namei.c:4293 [inline] __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:4293 do_syscall_x64 arch/x86/en ---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
5th
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 (model v2026.06.15, score date 2026-10-25). 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

August 5, 2026

Advisory Details (9)

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

jfs: Prevent copying of nlink with value 0 from disk inode - kernel/git/stable/linux.git - Linux kernel stable tree

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

jfs: Prevent copying of nlink with value 0 from disk inode - kernel/git/stable/linux.git - Linux kernel stable tree

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

jfs: Prevent copying of nlink with value 0 from disk inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/994787341358816d91b2fded288ecb7f129f2b27
Web page

jfs: Prevent copying of nlink with value 0 from disk inode - kernel/git/stable/linux.git - Linux kernel stable tree

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

jfs: Prevent copying of nlink with value 0 from disk inode - kernel/git/stable/linux.git - Linux kernel stable tree

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

jfs: Prevent copying of nlink with value 0 from disk inode - kernel/git/stable/linux.git - Linux kernel stable tree

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

jfs: Prevent copying of nlink with value 0 from disk inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86bfeaa18f9e4615b97f2d613e0fcc4ced196527
Web page

jfs: Prevent copying of nlink with value 0 from disk inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b5ce75f8bd3ddf480cc0a240d7ff5cdea0444f9
Web page

jfs: Prevent copying of nlink with value 0 from disk inode - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2025-37741(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-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1044.44~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1088.92) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1094.92) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1094.103~20.04.1) @ focal2026-10-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1083.89~20.04.1) @ focal2026-10-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1052.56) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1094.79) @ jammy2026-10-23ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1084.80) @ jammy2026-10-23ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1083.81) @ jammy2026-10-23ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-23ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-10-23ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-10-23ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-10-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-23ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1087.77) @ jammy2026-10-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-23ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.144.141) @ jammy2026-10-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-23ubuntu
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 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 192 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 94 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% · 5th percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 5th 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 UTCEG score recompute
  10. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-23 21:00 UTCEG score recompute
  13. 2026-10-23 21:00 UTCVendor advisory
  14. 2026-10-23 21:00 UTCGHSA enrichmentGHSA-q2h8-9338-55xq · 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 23: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:36 UTCEG score recompute
  23. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 73 more
  1. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-12 17:08 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-11 20:41 UTCEG score recompute
  5. 2026-10-11 18:51 UTCEG score recompute
  6. 2026-10-11 15:29 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-09-27 03:45 UTCOSV refresh
  19. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  26. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  27. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  28. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  29. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  30. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  32. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  34. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  35. 2026-09-07 12:48 UTCOSV refresh
  36. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  37. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  38. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  39. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  40. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  41. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  42. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  43. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  44. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  45. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  46. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  47. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  48. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  49. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  50. 2026-08-20 22:01 UTCOSV refresh
  51. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  52. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  53. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  54. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  55. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  56. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  57. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  58. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  59. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  60. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  61. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  62. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  63. 2026-08-05 13:57 UTCEG score recompute
  64. 2026-08-05 13:57 UTCVendor advisory
  65. 2026-08-05 13:57 UTCGHSA enrichmentGHSA-q2h8-9338-55xq · GitHub CVSS 5.5
  66. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  67. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  68. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  69. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  70. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  71. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  72. 2026-07-30 07:13 UTCEG score recompute
  73. 2026-07-30 07:13 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-37741?
CVE-2025-37741 is a medium-severity vulnerability; its CVE record was published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: jfs: Prevent copying of nlink with value 0 from disk inode syzbot report a deadlock in diFree. [1] When calling "ioctl$LOOP_SET_STATUS64", the offset value passed in is 4, which does not match the mounted loop device, causing the…
When was the CVE record for CVE-2025-37741 published?
The CVE record for CVE-2025-37741 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-37741 actively exploited?
CVE-2025-37741 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-37741?
CVE-2025-37741 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-37741?
A fix for CVE-2025-37741 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-37741 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-37741

Explore →

Is Your Infrastructure Affected by CVE-2025-37741?

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

Book a Demo →Browse All CVEs