CVE-2025-38241

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-09. 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-20820 (ENISA EUVD) · GHSA-j5v8-prgm-3f4c (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.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

mm/shmem, swap: fix softlockup with mTHP swapin

Following softlockup can be easily reproduced on my test machine with:

echo always > /sys/kernel/mm/transparent_hugepage/hugepages-64kB/enabled swapon /dev/zram0 # zram0 is a 48G swap device mkdir -p /sys/fs/cgroup/memory/test echo 1G > /sys/fs/cgroup/test/memory.max echo $BASHPID > /sys/fs/cgroup/test/cgroup.procs while true; do dd if=/dev/zero of=/tmp/test.img bs=1M count=5120 cat /tmp/test.img > /dev/null rm /tmp/test.img done

Then after a while: watchdog: BUG: soft lockup - CPU#0 stuck for 763s! [cat:5787] Modules linked in: zram virtiofs CPU: 0 UID: 0 PID: 5787 Comm: cat Kdump: loaded Tainted: G L 6.15.0.orig-gf3021d9246bc-dirty #118 PREEMPT(voluntary)· Tainted: [L]=SOFTLOCKUP Hardware name: Red Hat KVM/RHEL-AV, BIOS 0.0.0 02/06/2015 RIP: 0010:mpol_shared_policy_lookup+0xd/0x70 Code: e9 b8 b4 ff ff 31 c0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44 00 00 41 54 55 53 <48> 8b 1f 48 85 db 74 41 4c 8d 67 08 48 89 fb 48 89 f5 4c 89 e7 e8 RSP: 0018:ffffc90002b1fc28 EFLAGS: 00000202 RAX: 00000000001c20ca RBX: 0000000000724e1e RCX: 0000000000000001 RDX: ffff888118e214c8 RSI: 0000000000057d42 RDI: ffff888118e21518 RBP: 000000000002bec8 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000bf4 R11: 0000000000000000 R12: 0000000000000001 R13: 00000000001c20ca R14: 00000000001c20ca R15: 0000000000000000 FS: 00007f03f995c740(0000) GS:ffff88a07ad9a000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f03f98f1000 CR3: 0000000144626004 CR4: 0000000000770eb0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: shmem_alloc_folio+0x31/0xc0 shmem_swapin_folio+0x309/0xcf0 ? filemap_get_entry+0x117/0x1e0 ? xas_load+0xd/0xb0 ? filemap_get_entry+0x101/0x1e0 shmem_get_folio_gfp+0x2ed/0x5b0 shmem_file_read_iter+0x7f/0x2e0 vfs_read+0x252/0x330 ksys_read+0x68/0xf0 do_syscall_64+0x4c/0x1c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f03f9a46991 Code: 00 48 8b 15 81 14 10 00 f7 d8 64 89 02 b8 ff ff ff ff eb bd e8 20 ad 01 00 f3 0f 1e fa 80 3d 35 97 10 00 00 74 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 4f c3 66 0f 1f 44 00 00 55 48 89 e5 48 83 ec RSP: 002b:00007fff3c52bd28 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 0000000000040000 RCX: 00007f03f9a46991 RDX: 0000000000040000 RSI: 00007f03f98ba000 RDI: 0000000000000003 RBP: 00007fff3c52bd50 R08: 0000000000000000 R09: 00007f03f9b9a380 R10: 0000000000000022 R11: 0000000000000246 R12: 0000000000040000 R13: 00007f03f98ba000 R14: 0000000000000003 R15: 0000000000000000

The reason is simple, readahead brought some order 0 folio in swap cache, and the swapin mTHP folio being allocated is in conflict with it, so swapcache_prepare fails and causes shmem_swap_alloc_folio to return -EEXIST, and shmem simply retries again and again causing this loop.

Fix it by applying a similar fix for anon mTHP swapin.

The performance change is very slight, time of swapin 10g zero folios with shmem (test for 12 times): Before: 2.47s After: 2.48s

[kasong@tencent.com: add comment]

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.1% × 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.1%
EPSS %ILE
1st
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.1% 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 9, 2025

Last Modified

November 19, 2025

Advisory Details (2)

Auto-updated Oct 23, 2026
Patch available.
Web page

mm/shmem, swap: fix softlockup with mTHP swapin - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/shmem, swap: fix softlockup with mTHP swapin - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1283dfc1e0cd52cf525c2cb1b59a6f9183aab7ca

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1014.14~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1014.14) @ plucky2026-05-30ubuntu
ubuntulinux-tools-aws-edge (6.14.0-1015.15~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34) @ plucky2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.14.0-1018.19~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34~24.04.1) @ noble2026-05-30ubuntu
linuxKernel @ 6.15.5 (fixes >=6.14.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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38241?
CVE-2025-38241 is a medium-severity vulnerability; its CVE record was published on July 9, 2025. In the Linux kernel, the following vulnerability has been resolved: mm/shmem, swap: fix softlockup with mTHP swapin Following softlockup can be easily reproduced on my test machine with: echo always > /sys/kernel/mm/transparent_hugepage/hugepages-64kB/enabled swapon /dev/zram0 # zram0 is a 48G swap…
When was the CVE record for CVE-2025-38241 published?
The CVE record for CVE-2025-38241 was published on July 9, 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 19, 2025; the record at its source may have been updated since.
Is CVE-2025-38241 actively exploited?
CVE-2025-38241 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38241?
CVE-2025-38241 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38241?
A fix for CVE-2025-38241 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-38241

Explore →

Is Your Infrastructure Affected by CVE-2025-38241?

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

Book a Demo →Browse All CVEs