CVE-2025-21861

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-03-12. 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-7599 (ENISA EUVD) · GHSA-4r9v-vhgw-qfm4 (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/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()

If migration succeeded, we called folio_migrate_flags()->mem_cgroup_migrate() to migrate the memcg from the old to the new folio. This will set memcg_data of the old folio to 0.

Similarly, if migration failed, memcg_data of the dst folio is left unset.

If we call folio_putback_lru() on such folios (memcg_data == 0), we will add the folio to be freed to the LRU, making memcg code unhappy. Running the hmm selftests:

# ./hmm-tests ... # RUN hmm.hmm_device_private.migrate ... [ 102.078007][T14893] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7ff27d200 pfn:0x13cc00 [ 102.079974][T14893] anon flags: 0x17ff00000020018(uptodate|dirty|swapbacked|node=0|zone=2|lastcpupid=0x7ff) [ 102.082037][T14893] raw: 017ff00000020018 dead000000000100 dead000000000122 ffff8881353896c9 [ 102.083687][T14893] raw: 00000007ff27d200 0000000000000000 00000001ffffffff 0000000000000000 [ 102.085331][T14893] page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled()) [ 102.087230][T14893] ------------[ cut here ]------------ [ 102.088279][T14893] WARNING: CPU: 0 PID: 14893 at ./include/linux/memcontrol.h:726 folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.090478][T14893] Modules linked in: [ 102.091244][T14893] CPU: 0 UID: 0 PID: 14893 Comm: hmm-tests Not tainted 6.13.0-09623-g6c216bc522fd #151 [ 102.093089][T14893] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 [ 102.094848][T14893] RIP: 0010:folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.096104][T14893] Code: ... [ 102.099908][T14893] RSP: 0018:ffffc900236c37b0 EFLAGS: 00010293 [ 102.101152][T14893] RAX: 0000000000000000 RBX: ffffea0004f30000 RCX: ffffffff8183f426 [ 102.102684][T14893] RDX: ffff8881063cb880 RSI: ffffffff81b8117f RDI: ffff8881063cb880 [ 102.104227][T14893] RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000 [ 102.105757][T14893] R10: 0000000000000001 R11: 0000000000000002 R12: ffffc900236c37d8 [ 102.107296][T14893] R13: ffff888277a2bcb0 R14: 000000000000001f R15: 0000000000000000 [ 102.108830][T14893] FS: 00007ff27dbdd740(0000) GS:ffff888277a00000(0000) knlGS:0000000000000000 [ 102.110643][T14893] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 102.111924][T14893] CR2: 00007ff27d400000 CR3: 000000010866e000 CR4: 0000000000750ef0 [ 102.113478][T14893] PKRU: 55555554 [ 102.114172][T14893] Call Trace: [ 102.114805][T14893] [ 102.115397][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.116547][T14893] ? __warn.cold+0x110/0x210 [ 102.117461][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.118667][T14893] ? report_bug+0x1b9/0x320 [ 102.119571][T14893] ? handle_bug+0x54/0x90 [ 102.120494][T14893] ? exc_invalid_op+0x17/0x50 [ 102.121433][T14893] ? asm_exc_invalid_op+0x1a/0x20 [ 102.122435][T14893] ? __wake_up_klogd.part.0+0x76/0xd0 [ 102.123506][T14893] ? dump_page+0x4f/0x60 [ 102.124352][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.125500][T14893] folio_batch_move_lru+0xd4/0x200 [ 102.126577][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.127505][T14893] __folio_batch_add_and_move+0x391/0x720 [ 102.128633][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.129550][T14893] folio_putback_lru+0x16/0x80 [ 102.130564][T14893] migrate_device_finalize+0x9b/0x530 [ 102.131640][T14893] dmirror_migrate_to_device.constprop.0+0x7c5/0xad0 [ 102.133047][T14893] dmirror_fops_unlocked_ioctl+0x89b/0xc80

Likely, nothing else goes wrong: putting the last folio reference will remove the folio from the LRU again. So besides memcg complaining, adding the folio to be freed to the LRU is just an unnecessary step.

The new flow resembles what we have in migrate_folio_move(): add the dst to the lru, rem ---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 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
15th
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 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

March 12, 2025

Last Modified

October 15, 2026

Advisory Details (9)

Auto-updated Jul 17, 2026
Patch available.
Web page

SSA-019113

https://cert-portal.siemens.com/productcert/html/ssa-019113.html
Web page

mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78f579cb7d825134e071a1714d8d0c4fd0ffe459
Web page

mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/64397b0cb7c09e3ef3f9f5c7c17299c4eebd3875
Web page

mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61fa824e304ed162fe965f64999068e6fcff2059
Web page

mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/41cddf83d8b00f29fd105e7a0777366edc69a5cf
Web page

mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f9240d59e9a95d19f06120bfd1d0e681c6c0ac7
Web page

mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/20fb6fc51863fbff7868de8b5f6d249d2094df1f
Web page

mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/069dd21ea8262204f94737878389c2815a054a9e

Vendor Advisories for CVE-2025-21861(4)

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

Patch Availability(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-78.78) @ noble2026-05-30ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1033.33) @ noble2026-05-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1032.33) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1035.39) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2028.29) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1034.39~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1099.103) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1100.90) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.170.159) @ jammy2026-05-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1052.52) @ jammy2026-05-30ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1095.95) @ jammy2026-05-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1095.95) @ jammy2026-05-30ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1097.93) @ jammy2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1064 (5.15.0-1064.68) @ jammy2026-05-30ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1100.107~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1041.43) @ jammy2026-05-30ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-05-30ubuntu
redhatkernel-0:6.12.0-124.8.1.el10_12025-11-11redhat
redhatkernel-0:5.14.0-611.5.1.el9_72025-11-11redhat
linuxKernel @ 5.4.300 (fixes >=4.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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (47 versions)
  • every version up to 5.10.247-1: fixed in 5.10.247-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.153-1~deb11u1 (12 versions)
  • every version up to 6.1.158-1~deb11u1: fixed in 6.1.158-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (44 versions)
  • every version up to 6.1.158-1: fixed in 6.1.158-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.17-1: fixed in 6.12.17-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.17-1: fixed in 6.12.17-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(20)

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 8× in last 7d / 41× 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 96 of 200 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-21861?
CVE-2025-21861 is a medium-severity vulnerability; its CVE record was published on March 12, 2025. In the Linux kernel, the following vulnerability has been resolved: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() If migration succeeded, we called folio_migrate_flags()->mem_cgroup_migrate() to migrate the memcg from the old to the new folio. This will set…
When was the CVE record for CVE-2025-21861 published?
The CVE record for CVE-2025-21861 was published on March 12, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2025-21861 actively exploited?
CVE-2025-21861 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21861?
CVE-2025-21861 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21861?
A fix for CVE-2025-21861 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-21861 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-21861

Explore →

Is Your Infrastructure Affected by CVE-2025-21861?

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

Book a Demo →Browse All CVEs