CVE-2025-38203

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-04. 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-20053 (ENISA EUVD) · GHSA-3rjx-hm66-mfp3 (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: Fix null-ptr-deref in jfs_ioc_trim

[ Syzkaller Report ]

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000087: 0000 [#1 KASAN: null-ptr-deref in range [0x0000000000000438-0x000000000000043f] CPU: 2 UID: 0 PID: 10614 Comm: syz-executor.0 Not tainted 6.13.0-rc6-gfbfd64d25c7a-dirty #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Sched_ext: serialise (enabled+all), task: runnable_at=-30ms RIP: 0010:jfs_ioc_trim+0x34b/0x8f0 Code: e7 e8 59 a4 87 fe 4d 8b 24 24 4d 8d bc 24 38 04 00 00 48 8d 93 90 82 fe ff 4c 89 ff 31 f6 RSP: 0018:ffffc900055f7cd0 EFLAGS: 00010206 RAX: 0000000000000087 RBX: 00005866a9e67ff8 RCX: 000000000000000a RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000001 RBP: dffffc0000000000 R08: ffff88807c180003 R09: 1ffff1100f830000 R10: dffffc0000000000 R11: ffffed100f830001 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000438 FS: 00007fe520225640(0000) GS:ffff8880b7e80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005593c91b2c88 CR3: 000000014927c000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:

? __die_body+0x61/0xb0 ? die_addr+0xb1/0xe0 ? exc_general_protection+0x333/0x510 ? asm_exc_general_protection+0x26/0x30 ? jfs_ioc_trim+0x34b/0x8f0 jfs_ioctl+0x3c8/0x4f0 ? __pfx_jfs_ioctl+0x10/0x10 ? __pfx_jfs_ioctl+0x10/0x10 __se_sys_ioctl+0x269/0x350 ? __pfx___se_sys_ioctl+0x10/0x10 ? do_syscall_64+0xfb/0x210 do_syscall_64+0xee/0x210 ? syscall_exit_to_user_mode+0x1e0/0x330 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fe51f4903ad Code: c3 e8 a7 2b 00 00 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d RSP: 002b:00007fe5202250c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fe51f5cbf80 RCX: 00007fe51f4903ad RDX: 0000000020000680 RSI: 00000000c0185879 RDI: 0000000000000005 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fe520225640 R13: 000000000000000e R14: 00007fe51f44fca0 R15: 00007fe52021d000

Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:jfs_ioc_trim+0x34b/0x8f0 Code: e7 e8 59 a4 87 fe 4d 8b 24 24 4d 8d bc 24 38 04 00 00 48 8d 93 90 82 fe ff 4c 89 ff 31 f6 RSP: 0018:ffffc900055f7cd0 EFLAGS: 00010206 RAX: 0000000000000087 RBX: 00005866a9e67ff8 RCX: 000000000000000a RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000001 RBP: dffffc0000000000 R08: ffff88807c180003 R09: 1ffff1100f830000 R10: dffffc0000000000 R11: ffffed100f830001 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000438 FS: 00007fe520225640(0000) GS:ffff8880b7e80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005593c91b2c88 CR3: 000000014927c000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Kernel panic - not syncing: Fatal exception

[ Analysis ]

We believe that we have found a concurrency bug in the fs/jfs module that results in a null pointer dereference. There is a closely related issue which has been fixed:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d6c1b3599b2feb5c7291f5ac3a36e5fa7cedb234

... but, unfortunately, the accepted patch appears to still be susceptible to a null pointer dereference under some interleavings.

To trigger the bug, we think that JFS_SBI(ipbmap->i_sb)->bmap is set to NULL in dbFreeBits and then dereferenced in jfs_ioc_trim. This bug manifests quite rarely under normal circumstances, but is triggereable from a syz-program.

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
8th
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-24). 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 4, 2025

Last Modified

September 2, 2026

Advisory Details (8)

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

jfs: Fix null-ptr-deref in jfs_ioc_trim - kernel/git/stable/linux.git - Linux kernel stable tree

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

jfs: Fix null-ptr-deref in jfs_ioc_trim - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9806ae34d7d661c372247cd36f83bfa0523d60ed
Web page

jfs: Fix null-ptr-deref in jfs_ioc_trim - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/233340626cf1b1887dca181f9f811db60c73f802
Web page

jfs: Fix null-ptr-deref in jfs_ioc_trim - kernel/git/stable/linux.git - Linux kernel stable tree

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

jfs: Fix null-ptr-deref in jfs_ioc_trim - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a2de0f5b8d7f218bea5bd43d30b466e8b272b8d
Web page

jfs: Fix null-ptr-deref in jfs_ioc_trim - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a8cb9908b51500a76f5156423bd295df53bff89
Web page

jfs: Fix null-ptr-deref in jfs_ioc_trim - kernel/git/stable/linux.git - Linux kernel stable tree

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

jfs: Fix null-ptr-deref in jfs_ioc_trim - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d50231d473f89024158dc62624930de45d13718

Vendor Advisories for CVE-2025-38203(2)

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

Patch Availability(16)

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:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (46 versions)
  • every version up to 5.10.244-1: fixed in 5.10.244-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (63 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

(15)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2025-38203?
CVE-2025-38203 is a medium-severity vulnerability; its CVE record was published on July 4, 2025. In the Linux kernel, the following vulnerability has been resolved: jfs: Fix null-ptr-deref in jfs_ioc_trim [ Syzkaller Report ] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000087: 0000 [#1 KASAN: null-ptr-deref in range [0x0000000000000438-0x000000000000043f]…
When was the CVE record for CVE-2025-38203 published?
The CVE record for CVE-2025-38203 was published on July 4, 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 September 2, 2026; the record at its source may have been updated since.
Is CVE-2025-38203 actively exploited?
CVE-2025-38203 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38203?
CVE-2025-38203 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38203?
A fix for CVE-2025-38203 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38203 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-38203

Explore →

Is Your Infrastructure Affected by CVE-2025-38203?

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