CVE-2026-53108

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2026-06-24. 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:

powerpc/64s: Fix unmap race with PMD migration entries

The following race is possible with migration swap entries or device-private THP entries. e.g. when move_pages is called on a PMD THP page, then there maybe an intermediate state, where PMD entry acts as a migration swap entry (pmd_present() is true). Then if an munmap happens at the same time, then this VM_BUG_ON() can happen in pmdp_huge_get_and_clear_full().

This patch fixes that.

Thread A: move_pages() syscall add_folio_for_migration() mmap_read_lock(mm) folio_isolate_lru(folio) mmap_read_unlock(mm)

do_move_pages_to_node() migrate_pages() try_to_migrate_one() spin_lock(ptl) set_pmd_migration_entry() pmdp_invalidate() # PMD: _PAGE_INVALID | _PAGE_PTE | pfn set_pmd_at() # PMD: migration swap entry (pmd_present=0) spin_unlock(ptl) [page copy phase] # <--- RACE WINDOW -->

Thread B: munmap() mmap_write_downgrade(mm) unmap_vmas() -> zap_pmd_range() zap_huge_pmd() __pmd_trans_huge_lock() pmd_is_huge(): # !pmd_present && !pmd_none -> TRUE (swap entry) pmd_lock() -> # spin_lock(ptl), waits for Thread A to release ptl pmdp_huge_get_and_clear_full() VM_BUG_ON(!pmd_present(*pmdp)) # HITS!

[ 287.738700][ T1867] ------------[ cut here ]------------ [ 287.743843][ T1867] kernel BUG at arch/powerpc/mm/book3s64/pgtable.c:187! cpu 0x0: Vector: 700 (Program Check) at [c00000044037f4f0] pc: c000000000094ca4: pmdp_huge_get_and_clear_full+0x6c/0x23c lr: c000000000645dec: zap_huge_pmd+0xb0/0x868 sp: c00000044037f790 msr: 800000000282b033 current = 0xc0000004032c1a00 paca = 0xc000000004fe0000 irqmask: 0x03 irq_happened: 0x09 pid = 1867, comm = a.out kernel BUG at :187! Linux version 6.19.0-12136-g14360d4f917c-dirty (powerpc64le-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #27 SMP PREEMPT Sun Feb 22 10:38:56 IST 2026 enter ? for help [link register ] c000000000645dec zap_huge_pmd+0xb0/0x868 [c00000044037f790] c00000044037f7d0 (unreliable) [c00000044037f7d0] c000000000645dcc zap_huge_pmd+0x90/0x868 [c00000044037f840] c0000000005724cc unmap_page_range+0x176c/0x1f40 [c00000044037fa00] c000000000572ea0 unmap_vmas+0xb0/0x1d8 [c00000044037fa90] c0000000005af254 unmap_region+0xb4/0x128 [c00000044037fb50] c0000000005af400 vms_complete_munmap_vmas+0x138/0x310 [c00000044037fbe0] c0000000005b0f1c do_vmi_align_munmap+0x1ec/0x238 [c00000044037fd30] c0000000005b3688 __vm_munmap+0x170/0x1f8 [c00000044037fdf0] c000000000587f74 sys_munmap+0x2c/0x40 [c00000044037fe10] c000000000032668 system_call_exception+0x128/0x350 [c00000044037fe50] c00000000000d05c system_call_vectored_common+0x15c/0x2ec ---- Exception: 3000 (System Call Vectored) at 0000000010064a2c SP (7fff9b1ee9c0) is in userspace 0:mon> zh

commit a30b48bf1b24 ("mm/migrate_device: implement THP migration of zone device pages"), enabled migration for device-private PMD entries. Hence this is one other path where this warning could get trigger from.

------------[ cut here ]------------ WARNING: arch/powerpc/mm/book3s64/hash_pgtable.c:199 at hash__pmd_hugepage_update+0x48/0x284, CPU#3: hmm-tests/1905 Modules linked in: test_hmm CPU: 3 UID: 0 PID: 1905 Comm: hmm-tests Tainted: G B W L N 7.0.0-rc1-01438-g7e2f0ee7581c #21 PREEMPT Tainted: [B]=BAD_PAGE, [W]=WARN, [L]=SOFTLOCKUP, [N]=TEST Hardware name: IBM pSeries (emulated by qemu) POWER10 (architected) 0x801200 0xf000006 of:SLOF,git-ee03ae pSeries NIP [c000000000096b70] hash__pmd_hugepage_update+0x48/0x284 LR [c000000000096e7c] hash__pmdp_huge_get_and_clear+0xd0/0xd4 Call Trace: [c000000604707670] [c000000004e102b8] 0xc000000004e102b8 (unreliable) [c000000604707700] [c00000000064ec3c] set_pmd_migration_entry+0x414/0x498 [c000000604707760] [c00000000063e5a4] migrate_vma_col ---truncated---

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

Published

June 24, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jul 24, 2026
No patch confirmed yet.
generic

powerpc/64s: Fix unmap race with PMD migration entries - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/64s: Fix unmap race with PMD migration entries - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/829367e55012c053738ebe7db20c4a90d6609ece

Vendor Advisories for CVE-2026-53108(2)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ 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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

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 3× in last 7d / 44× 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 144 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53108?
CVE-2026-53108 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: powerpc/64s: Fix unmap race with PMD migration entries The following race is possible with migration swap entries or device-private THP entries. e.g. when move_pages is called on a PMD THP page, then there maybe an intermediate…
When was CVE-2026-53108 disclosed?
CVE-2026-53108 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53108 actively exploited?
CVE-2026-53108 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 99.9% of all scored CVEs.
What is the CVSS score of CVE-2026-53108?
CVE-2026-53108 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-53108?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53108, 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-53108

Explore →

Is Your Infrastructure Affected by CVE-2026-53108?

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

Start Free Scan →Browse All CVEs