CVE-2025-21984

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2025-04-01. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

A fix is available — apply it.

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

mm: fix kernel BUG when userfaultfd_move encounters swapcache

userfaultfd_move() checks whether the PTE entry is present or a swap entry.

  • If the PTE entry is present, move_present_pte() handles folio
migration by setting:

src_folio->index = linear_page_index(dst_vma, dst_addr);

  • If the PTE entry is a swap entry, move_swap_pte() simply copies
the PTE to the new dst_addr.

This approach is incorrect because, even if the PTE is a swap entry, it can still reference a folio that remains in the swap cache.

This creates a race window between steps 2 and 4.

  • add_to_swap: The folio is added to the swapcache.
  • try_to_unmap: PTEs are converted to swap entries.
  • pageout: The folio is written back.
  • Swapcache is cleared.
If userfaultfd_move() occurs in the window between steps 2 and 4, after the swap PTE has been moved to the destination, accessing the destination triggers do_swap_page(), which may locate the folio in the swapcache. However, since the folio's index has not been updated to match the destination VMA, do_swap_page() will detect a mismatch.

This can result in two critical issues depending on the system configuration.

If KSM is disabled, both small and large folios can trigger a BUG during the add_rmap operation due to:

page_pgoff(folio, page) != linear_page_index(vma, address)

[ 13.336953] page: refcount:6 mapcount:1 mapping:00000000f43db19c index:0xffffaf150 pfn:0x4667c [ 13.337520] head: order:2 mapcount:1 entire_mapcount:0 nr_pages_mapped:1 pincount:0 [ 13.337716] memcg:ffff00000405f000 [ 13.337849] anon flags: 0x3fffc0000020459(locked|uptodate|dirty|owner_priv_1|head|swapbacked|node=0|zone=0|lastcpupid=0xffff) [ 13.338630] raw: 03fffc0000020459 ffff80008507b538 ffff80008507b538 ffff000006260361 [ 13.338831] raw: 0000000ffffaf150 0000000000004000 0000000600000000 ffff00000405f000 [ 13.339031] head: 03fffc0000020459 ffff80008507b538 ffff80008507b538 ffff000006260361 [ 13.339204] head: 0000000ffffaf150 0000000000004000 0000000600000000 ffff00000405f000 [ 13.339375] head: 03fffc0000000202 fffffdffc0199f01 ffffffff00000000 0000000000000001 [ 13.339546] head: 0000000000000004 0000000000000000 00000000ffffffff 0000000000000000 [ 13.339736] page dumped because: VM_BUG_ON_PAGE(page_pgoff(folio, page) != linear_page_index(vma, address)) [ 13.340190] ------------[ cut here ]------------ [ 13.340316] kernel BUG at mm/rmap.c:1380! [ 13.340683] Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP [ 13.340969] Modules linked in: [ 13.341257] CPU: 1 UID: 0 PID: 107 Comm: a.out Not tainted 6.14.0-rc3-gcf42737e247a-dirty #299 [ 13.341470] Hardware name: linux,dummy-virt (DT) [ 13.341671] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 13.341815] pc : __page_check_anon_rmap+0xa0/0xb0 [ 13.341920] lr : __page_check_anon_rmap+0xa0/0xb0 [ 13.342018] sp : ffff80008752bb20 [ 13.342093] x29: ffff80008752bb20 x28: fffffdffc0199f00 x27: 0000000000000001 [ 13.342404] x26: 0000000000000000 x25: 0000000000000001 x24: 0000000000000001 [ 13.342575] x23: 0000ffffaf0d0000 x22: 0000ffffaf0d0000 x21: fffffdffc0199f00 [ 13.342731] x20: fffffdffc0199f00 x19: ffff000006210700 x18: 00000000ffffffff [ 13.342881] x17: 6c203d2120296567 x16: 6170202c6f696c6f x15: 662866666f67705f [ 13.343033] x14: 6567617028454741 x13: 2929737365726464 x12: ffff800083728ab0 [ 13.343183] x11: ffff800082996bf8 x10: 0000000000000fd7 x9 : ffff80008011bc40 [ 13.343351] x8 : 0000000000017fe8 x7 : 00000000fffff000 x6 : ffff8000829eebf8 [ 13.343498] x5 : c0000000fffff000 x4 : 0000000000000000 x3 : 0000000000000000 [ 13.343645] x2 : 0000000000000000 x1 : ffff0000062db980 x0 : 000000000000005f [ 13.343876] Call trace: [ 13.344045] __page_check_anon_rmap+0xa0/0xb0 (P) [ 13.344234] folio_add_anon_rmap_ptes+0x22c/0x320 [ 13.344333] do_swap_page+0x1060/0x1400 [ 13.344417] __handl ---truncated---

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

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
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

April 1, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

mm: fix kernel BUG when userfaultfd_move encounters swapcache - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c50f8e6053b0503375c2975bf47f182445aebb4c
generic

mm: fix kernel BUG when userfaultfd_move encounters swapcache - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b1e11bd86c0943bb7624efebdc384340a50ad683
generic

mm: fix kernel BUG when userfaultfd_move encounters swapcache - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e9507246298fd6f1ca7bb42ef01a6e34fb93684

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-24.04b (6.11.0-1024.24) @ noble2026-07-30ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1015.16) @ oracular2026-07-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-28.28) @ oracular2026-07-30ubuntu
ubuntulinux-tools-azure-6.11 (6.11.0-1018.18) @ oracular2026-07-30ubuntu
linuxKernel @ 6.12.20osv

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.20-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.20-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(4)

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 5× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:06 UTCEPSS rescore
  4. 2026-09-16 05:13 UTCEPSS rescore
  5. 2026-09-15 03:09 UTCEPSS rescore
  6. 2026-09-13 16:46 UTCEPSS rescore
  7. 2026-09-12 15:00 UTCEPSS rescore
  8. 2026-09-11 14:51 UTCEPSS rescore
  9. 2026-09-11 09:35 UTCEPSS rescore
  10. 2026-09-10 09:33 UTCEPSS rescore
  11. 2026-09-08 21:59 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-07 13:18 UTCOSV refresh
  14. 2026-09-06 13:46 UTCEPSS rescore
  15. 2026-09-06 13:46 UTCEPSS rescore
  16. 2026-09-05 15:28 UTCEPSS rescore
  17. 2026-09-04 05:05 UTCEPSS rescore
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:52 UTCEPSS rescore
  20. 2026-09-01 04:38 UTCEPSS rescore
  21. 2026-08-30 19:16 UTCEPSS rescore
  22. 2026-08-30 01:21 UTCEPSS rescore
  23. 2026-08-28 21:40 UTCEPSS rescore
  24. 2026-08-27 14:24 UTCEPSS rescore
  25. 2026-08-25 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 00:18 UTCEPSS rescore
  2. 2026-08-21 23:48 UTCEPSS rescore
  3. 2026-08-20 22:54 UTCEPSS rescore
  4. 2026-08-20 22:31 UTCOSV refresh
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:47 UTCEPSS rescore
  7. 2026-08-17 13:46 UTCEPSS rescore
  8. 2026-08-16 14:55 UTCEPSS rescore
  9. 2026-08-16 02:13 UTCEPSS rescore
  10. 2026-08-16 02:13 UTCEPSS rescore
  11. 2026-08-15 01:29 UTCEPSS rescore
  12. 2026-08-13 21:59 UTCEPSS rescore
  13. 2026-08-12 13:50 UTCEPSS rescore
  14. 2026-08-10 23:59 UTCEPSS rescore
  15. 2026-08-09 13:45 UTCEPSS rescore
  16. 2026-08-07 16:26 UTCEPSS rescore
  17. 2026-08-06 13:46 UTCEPSS rescore
  18. 2026-08-05 19:16 UTCEPSS rescore
  19. 2026-08-05 14:00 UTCEG score recompute
  20. 2026-08-05 14:00 UTCVendor advisory
  21. 2026-08-05 13:59 UTCGHSA enrichment
  22. 2026-08-04 15:09 UTCEPSS rescore
  23. 2026-08-04 10:37 UTCEPSS rescore
  24. 2026-08-03 10:35 UTCEPSS rescore
  25. 2026-08-02 02:25 UTCEPSS rescore
  26. 2026-08-01 04:15 UTCEPSS rescore
  27. 2026-07-30 16:27 UTCEPSS rescore
  28. 2026-07-30 07:15 UTCEG score recompute
  29. 2026-07-30 07:15 UTCVendor advisory
  30. 2026-07-30 07:15 UTCGHSA enrichment
  31. 2026-07-30 01:29 UTCEPSS rescore
  32. 2026-07-28 15:35 UTCEPSS rescore
  33. 2026-07-27 14:12 UTCEPSS rescore
  34. 2026-07-26 14:53 UTCEPSS rescore
  35. 2026-07-25 14:17 UTCEPSS rescore
  36. 2026-07-24 14:17 UTCEPSS rescore
  37. 2026-07-24 10:11 UTCOSV refresh
  38. 2026-07-23 14:17 UTCEPSS rescore
  39. 2026-07-23 02:50 UTCEG score recompute
  40. 2026-07-22 14:07 UTCEPSS rescore
  41. 2026-07-22 14:07 UTCEPSS rescore
  42. 2026-07-21 15:24 UTCEPSS rescore
  43. 2026-07-20 17:07 UTCEPSS rescore
  44. 2026-07-19 14:30 UTCEPSS rescore
  45. 2026-07-19 14:30 UTCEPSS rescore
  46. 2026-07-19 02:28 UTCEPSS rescore
  47. 2026-07-19 02:28 UTCEPSS rescore
  48. 2026-07-18 10:03 UTCEPSS rescore
  49. 2026-07-16 17:02 UTCEPSS rescore
  50. 2026-07-15 16:57 UTCEPSS rescore
  51. 2026-07-15 16:57 UTCEPSS rescore
  52. 2026-07-13 22:29 UTCEPSS rescore
  53. 2026-07-13 22:29 UTCEPSS rescore
  54. 2026-07-13 06:12 UTCEPSS rescore
  55. 2026-07-13 06:12 UTCEPSS rescore
  56. 2026-07-12 05:46 UTCEPSS rescore
  57. 2026-07-12 05:46 UTCEPSS rescore
  58. 2026-07-11 08:27 UTCEPSS rescore
  59. 2026-07-11 08:26 UTCEPSS rescore
  60. 2026-07-09 19:09 UTCEPSS rescore
  61. 2026-07-08 15:14 UTCEPSS rescore
  62. 2026-07-07 13:45 UTCEPSS rescore
  63. 2026-07-07 05:51 UTCOSV refresh
  64. 2026-07-06 16:26 UTCEPSS rescore
  65. 2026-07-06 02:22 UTCEPSS rescore
  66. 2026-07-06 02:22 UTCEPSS rescore
  67. 2026-07-05 02:30 UTCEPSS rescore
  68. 2026-07-04 06:30 UTCEPSS rescore
  69. 2026-07-01 15:06 UTCEPSS rescore
  70. 2026-06-30 23:21 UTCEPSS rescore
  71. 2026-06-30 23:21 UTCEPSS rescore
  72. 2026-06-29 14:06 UTCEPSS rescore
  73. 2026-06-28 14:07 UTCEPSS rescore
  74. 2026-06-28 14:07 UTCEPSS rescore
  75. 2026-06-28 04:55 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-21984?
CVE-2025-21984 is a medium vulnerability published on April 1, 2025. In the Linux kernel, the following vulnerability has been resolved: mm: fix kernel BUG when userfaultfd_move encounters swapcache userfaultfd_move() checks whether the PTE entry is present or a swap entry. If the PTE entry is present, movepresentpte() handles folio migration by setting:…
When was CVE-2025-21984 disclosed?
CVE-2025-21984 was first published in the National Vulnerability Database on April 1, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-21984 actively exploited?
CVE-2025-21984 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.7% of all scored CVEs.
What is the CVSS score of CVE-2025-21984?
CVE-2025-21984 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2025-21984?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-21984, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-21984

Explore →

Is Your Infrastructure Affected by CVE-2025-21984?

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