CVE-2026-53108

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.7 from GitHub Security Advisory (severity: MODERATE) published 2026-06-24. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-38976 (ENISA EUVD) · GHSA-2377-3vvp-rhhq (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
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.1%CVSS: 4.7Exploit: None knownExposed services: Not assessed

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.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation<0.1% × 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.1%
EPSS %ILE
below the 1st
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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

June 24, 2026

Last Modified

November 6, 2026

Advisory Details (2)

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

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
Web page

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(13)

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 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 (376 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (144 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 7× in last 7d / 39× 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 226 rows 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. None are among the latest 100 rows. The 126 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-53108?
CVE-2026-53108 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-53108 published?
The CVE record for CVE-2026-53108 was published on June 24, 2026. 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 6, 2026; the record at its source may have been updated since.
Is CVE-2026-53108 actively exploited?
CVE-2026-53108 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-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?
A fix for CVE-2026-53108 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53108 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-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.