CVE-2025-37834

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 (severity: MODERATE) published 2025-05-08. 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-13961 (ENISA EUVD) · GHSA-jmf7-45hm-82v2 (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:

mm/vmscan: don't try to reclaim hwpoison folio

Syzkaller reports a bug as follows:

Injecting memory failure for pfn 0x18b00e at process virtual address 0x20ffd000 Memory failure: 0x18b00e: dirty swapcache page still referenced by 2 users Memory failure: 0x18b00e: recovery action for dirty swapcache page: Failed page: refcount:2 mapcount:0 mapping:0000000000000000 index:0x20ffd pfn:0x18b00e memcg:ffff0000dd6d9000 anon flags: 0x5ffffe00482011(locked|dirty|arch_1|swapbacked|hwpoison|node=0|zone=2|lastcpupid=0xfffff) raw: 005ffffe00482011 dead000000000100 dead000000000122 ffff0000e232a7c9 raw: 0000000000020ffd 0000000000000000 00000002ffffffff ffff0000dd6d9000 page dumped because: VM_BUG_ON_FOLIO(!folio_test_uptodate(folio)) ------------[ cut here ]------------ kernel BUG at mm/swap_state.c:184! Internal error: Oops - BUG: 00000000f2000800 [#1] SMP Modules linked in: CPU: 0 PID: 60 Comm: kswapd0 Not tainted 6.6.0-gcb097e7de84e #3 Hardware name: linux,dummy-virt (DT) pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : add_to_swap+0xbc/0x158 lr : add_to_swap+0xbc/0x158 sp : ffff800087f37340 x29: ffff800087f37340 x28: fffffc00052c0380 x27: ffff800087f37780 x26: ffff800087f37490 x25: ffff800087f37c78 x24: ffff800087f377a0 x23: ffff800087f37c50 x22: 0000000000000000 x21: fffffc00052c03b4 x20: 0000000000000000 x19: fffffc00052c0380 x18: 0000000000000000 x17: 296f696c6f662865 x16: 7461646f7470755f x15: 747365745f6f696c x14: 6f6621284f494c4f x13: 0000000000000001 x12: ffff600036d8b97b x11: 1fffe00036d8b97a x10: ffff600036d8b97a x9 : dfff800000000000 x8 : 00009fffc9274686 x7 : ffff0001b6c5cbd3 x6 : 0000000000000001 x5 : ffff0000c25896c0 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 0000000000000000 x1 : ffff0000c25896c0 x0 : 0000000000000000 Call trace: add_to_swap+0xbc/0x158 shrink_folio_list+0x12ac/0x2648 shrink_inactive_list+0x318/0x948 shrink_lruvec+0x450/0x720 shrink_node_memcgs+0x280/0x4a8 shrink_node+0x128/0x978 balance_pgdat+0x4f0/0xb20 kswapd+0x228/0x438 kthread+0x214/0x230 ret_from_fork+0x10/0x20

I can reproduce this issue with the following steps:

1) When a dirty swapcache page is isolated by reclaim process and the page isn't locked, inject memory failure for the page. me_swapcache_dirty() clears uptodate flag and tries to delete from lru, but fails. Reclaim process will put the hwpoisoned page back to lru.

2) The process that maps the hwpoisoned page exits, the page is deleted the page will never be freed and will be in the lru forever.

3) If we trigger a reclaim again and tries to reclaim the page, add_to_swap() will trigger VM_BUG_ON_FOLIO due to the uptodate flag is cleared.

To fix it, skip the hwpoisoned page in shrink_folio_list(). Besides, the hwpoison folio may not be unmapped by hwpoison_user_mappings() yet, unmap it in shrink_folio_list(), otherwise the folio will fail to be unmaped by hwpoison_user_mappings() since the folio isn't in lru list.

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 SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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. 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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)60 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 Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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 8, 2025

Last Modified

November 5, 2026

Vendor Advisories for CVE-2025-37834(1)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-10-23ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-10-23ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-10-23ubuntu
linuxKernel @ 6.12.26 (fixes >=2.6.32)—osv

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc7-1~exp1 (375 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.27-1: fixed in 6.12.27-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.27-1: fixed in 6.12.27-1
—

Additional Vendor Advisories

(3)

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 6× in last 7d / 35× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 217 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-20 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-11-19 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-11-18 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-11-17 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-11-16 16:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-11-15 16:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-11-14 16:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-11-13 16:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-11-11 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-11-10 16:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-11-09 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-11-07 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-11-06 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-11-05 21:32 UTCVendor advisory
  18. 2026-11-05 21:32 UTCGHSA enrichmentGHSA-jmf7-45hm-82v2 · GitHub severity MODERATE · GitHub CVSS 5.5
  19. 2026-11-05 20:58 UTCEchelonGraph re-scored
  20. 2026-11-05 20:58 UTCVendor advisory
  21. 2026-11-05 20:58 UTCGHSA enrichmentGHSA-jmf7-45hm-82v2 · GitHub severity MODERATE · GitHub CVSS 5.5
  22. 2026-11-05 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-11-04 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-11-03 16:44 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 74 more
  1. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-31 16:31 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 UTCEchelonGraph re-scored
  9. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-23 20:58 UTCEchelonGraph re-scored
  12. 2026-10-23 20:58 UTCVendor advisory
  13. 2026-10-23 20:58 UTCGHSA enrichmentGHSA-jmf7-45hm-82v2 · GitHub CVSS 5.5
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-18 05:36 UTCEchelonGraph re-scored
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  26. 2026-10-12 17:08 UTCEchelonGraph re-scored
  27. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  28. 2026-10-11 20:41 UTCEchelonGraph re-scored
  29. 2026-10-11 18:51 UTCEchelonGraph re-scored
  30. 2026-10-11 15:28 UTCEchelonGraph re-scored
  31. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  32. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  33. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  34. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  35. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  36. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  37. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  38. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  39. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-10-02 14:41 UTCOSV refresh
  41. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  42. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  45. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  46. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  47. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  48. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  49. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  50. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  51. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  52. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  53. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  54. 2026-09-13 12:54 UTCOSV refresh
  55. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  56. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  57. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  58. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  59. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  60. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  61. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  62. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  63. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  64. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  65. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  66. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  67. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  68. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  69. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  70. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  71. 2026-08-25 14:39 UTCOSV refresh
  72. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  73. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  74. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile

Frequently asked(5)

What is CVE-2025-37834?
CVE-2025-37834 is a medium-severity vulnerability; its CVE record was published on May 8, 2025. In the Linux kernel, the following vulnerability has been resolved: mm/vmscan: don't try to reclaim hwpoison folio Syzkaller reports a bug as follows: Injecting memory failure for pfn 0x18b00e at process virtual address 0x20ffd000 Memory failure: 0x18b00e: dirty swapcache page still referenced by 2…
When was the CVE record for CVE-2025-37834 published?
The CVE record for CVE-2025-37834 was published on May 8, 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 5, 2026; the record at its source may have been updated since.
Is CVE-2025-37834 actively exploited?
CVE-2025-37834 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-37834?
CVE-2025-37834 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-37834?
A fix for CVE-2025-37834 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-37834 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-37834

Explore →

Is Your Infrastructure Affected by CVE-2025-37834?

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