CVE-2026-64131

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. NVD baseline CVSS 5.5; sources differ by 0.0.

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

A fix is available — apply it.

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

mm/memory: fix spurious warning when unmapping device-private/exclusive pages

Device private and exclusive entries are only supported for anonymous folios. This condition is tested in __migrate_device_pages() and make_device_exclusive() using folio_test_anon(). However the unmap path tests this assumption using vma_is_anonymous().

This is wrong because whilst anonymous VMAs can only contain folios where folio_test_anon() is true the opposite relation does not hold. A folio for which folio_test_anon() is true does not imply vma_is_anonymous() is true. Such a condition can occur if for example a folio is part of a private filebacked mapping.

In this case vma_is_anonymous() is false as the mapping is filebacked, but folio_test_anon() may be true, thus permitting devices to migrate the folio to device private memory. This can lead to the following spurious warnings during process teardown:

[ 772.737706] ------------[ cut here ]------------ [ 772.739201] WARNING: mm/memory.c:1754 at unmap_page_range.cold+0x26/0x18a, CPU#17: hmm-tests/2041 [ 772.742050] Modules linked in: test_hmm nvidia_uvm(O) nvidia(O) [ 772.743959] CPU: 17 UID: 0 PID: 2041 Comm: hmm-tests Tainted: G W O 7.0.0+ #387 PREEMPT(full) [ 772.747104] Tainted: [W]=WARN, [O]=OOT_MODULE [ 772.748509] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 [ 772.752117] RIP: 0010:unmap_page_range.cold+0x26/0x18a [ 772.753780] Code: 7e fe ff ff 48 89 4c 24 78 4c 89 44 24 38 e8 f2 ff b1 00 48 8b 4c 24 78 4c 8b 44 24 38 48 8b 44 24 18 48 83 78 48 00 74 04 90 <0f> 0b 90 48 89 ca b8 ff ff 37 00 48 c1 ea 03 48 c1 e0 2a 80 3c 02 [ 772.759602] RSP: 0018:ffff888112607550 EFLAGS: 00010286 [ 772.761310] RAX: ffff88811bbf4dc0 RBX: dffffc0000000000 RCX: ffffea03e9bfffd8 [ 772.763583] RDX: 1ffff1102377e9c1 RSI: 0000000000000008 RDI: ffff88811bbf4e08 [ 772.765914] RBP: 0000000000000006 R08: ffff8881059f7448 R09: ffffed10224c0e68 [ 772.768184] R10: ffff888112607347 R11: 0000000000000001 R12: 0000000000000001 [ 772.770461] R13: ffffea03e9bfffc0 R14: ffff888112607908 R15: ffffea03e9bfffc0 [ 772.772782] FS: 00007f327caa2780(0000) GS:ffff888427b7d000(0000) knlGS:0000000000000000 [ 772.775328] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 772.777187] CR2: 00007f327ca89000 CR3: 00000001994d5000 CR4: 00000000000006f0 [ 772.779135] Call Trace: [ 772.779792] [ 772.780317] ? dmirror_interval_invalidate+0x1a3/0x290 [test_hmm] [ 772.781873] ? vm_normal_page_pud+0x2b0/0x2b0 [ 772.782992] ? __rwlock_init+0x150/0x150 [ 772.784006] ? lock_release+0x216/0x2b0 [ 772.785008] ? __mmu_notifier_invalidate_range_start+0x505/0x6e0 [ 772.786522] ? lock_release+0x216/0x2b0 [ 772.787498] ? unmap_single_vma+0xb6/0x210 [ 772.788573] unmap_vmas+0x27d/0x520 [ 772.789506] ? unmap_single_vma+0x210/0x210 [ 772.790607] ? mas_update_gap.part.0+0x620/0x620 [ 772.791834] unmap_region+0x19e/0x350 [ 772.792769] ? remove_vma+0x130/0x130 [ 772.793684] ? mas_alloc_nodes+0x1f2/0x300 [ 772.794730] vms_complete_munmap_vmas+0x8c1/0xe20 [ 772.795926] ? unmap_region+0x350/0x350 [ 772.796917] do_vmi_align_munmap+0x36a/0x4e0 [ 772.798018] ? lock_release+0x216/0x2b0 [ 772.799024] ? vma_shrink+0x620/0x620 [ 772.799983] do_vmi_munmap+0x150/0x2c0 [ 772.800939] __vm_munmap+0x161/0x2c0 [ 772.801872] ? expand_downwards+0xd60/0xd60 [ 772.802948] ? clockevents_program_event+0x1ef/0x540 [ 772.804217] ? lock_release+0x216/0x2b0 [ 772.805158] __x64_sys_munmap+0x59/0x80 [ 772.805776] do_syscall_64+0xfc/0x670 [ 772.806336] ? irqentry_exit+0xda/0x580 [ 772.806976] entry_SYSCALL_64_after_hwframe+0x4b/0x53 [ 772.807772] RIP: 0033:0x7f327cbb2717 [ 772.808323] Code: 73 01 c3 48 8b 0d f9 76 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 0b 00 00 00 0f 05 <48> 3d 01 f0 ff ---truncated---

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (6)

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

mm/memory: fix spurious warning when unmapping device-private/exclusive pages - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/memory: fix spurious warning when unmapping device-private/exclusive pages - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/memory: fix spurious warning when unmapping device-private/exclusive pages - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/memory: fix spurious warning when unmapping device-private/exclusive pages - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/memory: fix spurious warning when unmapping device-private/exclusive pages - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52f72b3f8f6fa64abb71b711962b97f1f6aced1c
generic

mm/memory: fix spurious warning when unmapping device-private/exclusive pages - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2fff0cdd942261497fb8922a194b4da3315ae864

Vendor Advisories for CVE-2026-64131(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

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 21× in last 7d / 83× 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 113 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64131?
CVE-2026-64131 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/memory: fix spurious warning when unmapping device-private/exclusive pages Device private and exclusive entries are only supported for anonymous folios. This condition is tested in migratedevicepages() and makedeviceexclusive()…
When was CVE-2026-64131 disclosed?
CVE-2026-64131 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64131 actively exploited?
CVE-2026-64131 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 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64131?
CVE-2026-64131 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64131?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64131, 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-2026-64131

Explore →

Is Your Infrastructure Affected by CVE-2026-64131?

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

Start Free Scan →Browse All CVEs