CVE-2026-53109

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy

powerpc uses pt_frag_refcount as a reference counter for tracking it's pte and pmd page table fragments. For PTE table, in case of Hash with 64K pagesize, we have 16 fragments of 4K size in one 64K page.

Patch series [1] "mm: free retracted page table by RCU" added pte_free_defer() to defer the freeing of PTE tables when retract_page_tables() is called for madvise MADV_COLLAPSE on shmem range. [1]: https://lore.kernel.org/all/[email protected]/

pte_free_defer() sets the active flag on the corresponding fragment's folio & calls pte_fragment_free(), which reduces the pt_frag_refcount. When pt_frag_refcount reaches 0 (no active fragment using the folio), it checks if the folio active flag is set, if set, it calls call_rcu to free the folio, it the active flag is unset then it calls pte_free_now().

Now, this can lead to following problem in a corner case...

[ 265.351553][ T183] BUG: Bad page state in process a.out pfn:20d62 [ 265.353555][ T183] page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x20d62 [ 265.355457][ T183] flags: 0x3ffff800000100(active|node=0|zone=0|lastcpupid=0x7ffff) [ 265.358719][ T183] raw: 003ffff800000100 0000000000000000 5deadbeef0000122 0000000000000000 [ 265.360177][ T183] raw: 0000000000000000 c0000000119caf58 00000000ffffffff 0000000000000000 [ 265.361438][ T183] page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set [ 265.362572][ T183] Modules linked in: [ 265.364622][ T183] CPU: 0 UID: 0 PID: 183 Comm: a.out Not tainted 6.18.0-rc3-00141-g1ddeaaace7ff-dirty #53 VOLUNTARY [ 265.364785][ T183] Hardware name: IBM pSeries (emulated by qemu) POWER10 (architected) 0x801200 0xf000006 of:SLOF,git-ee03ae pSeries [ 265.364908][ T183] Call Trace: [ 265.364955][ T183] [c000000011e6f7c0] [c000000001cfaa18] dump_stack_lvl+0x130/0x148 (unreliable) [ 265.365202][ T183] [c000000011e6f7f0] [c000000000794758] bad_page+0xb4/0x1c8 [ 265.365384][ T183] [c000000011e6f890] [c00000000079c020] __free_frozen_pages+0x838/0xd08 [ 265.365554][ T183] [c000000011e6f980] [c0000000000a70ac] pte_frag_destroy+0x298/0x310 [ 265.365729][ T183] [c000000011e6fa30] [c0000000000aa764] arch_exit_mmap+0x34/0x218 [ 265.365912][ T183] [c000000011e6fa80] [c000000000751698] exit_mmap+0xb8/0x820 [ 265.366080][ T183] [c000000011e6fc30] [c0000000001b1258] __mmput+0x98/0x300 [ 265.366244][ T183] [c000000011e6fc80] [c0000000001c81f8] do_exit+0x470/0x1508 [ 265.366421][ T183] [c000000011e6fd70] [c0000000001c95e4] do_group_exit+0x88/0x148 [ 265.366602][ T183] [c000000011e6fdc0] [c0000000001c96ec] pid_child_should_wake+0x0/0x178 [ 265.366780][ T183] [c000000011e6fdf0] [c00000000003a270] system_call_exception+0x1b0/0x4e0 [ 265.366958][ T183] [c000000011e6fe50] [c00000000000d05c] system_call_vectored_common+0x15c/0x2ec

The bad page state error occurs when such a folio gets freed (with active flag set), from do_exit() path in parallel.

... this can happen when the pte fragment was allocated from this folio, but when all the fragments get freed, the pte_frag_refcount still had some unused fragments. Now, if this process exits, with such folio as it's cached pte_frag in mm->context, then during pte_frag_destroy(), we simply call pagetable_dtor() and pagetable_free(), meaning it doesn't clear the active flag. This, can lead to the above bug. Since we are anyway in do_exit() path, then if the refcount is 0, then I guess it should be ok to simply clear the folio active flag before calling pagetable_dtor() & pagetable_free().

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

Published

June 24, 2026

Last Modified

July 23, 2026

Advisory Details (3)

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

powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a32db6fca3c74b4eb8bae5470f0680deb4cbac6f

Vendor Advisories for CVE-2026-53109(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-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ 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-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-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-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

(2 across 2 ecosystems)
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 5× in last 7d / 88× 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 237 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53109?
CVE-2026-53109 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: powerpc/pgtable-frag: Fix bad page state in ptefragdestroy powerpc uses ptfragrefcount as a reference counter for tracking it's pte and pmd page table fragments. For PTE table, in case of Hash with 64K pagesize, we have 16…
When was CVE-2026-53109 disclosed?
CVE-2026-53109 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-53109 actively exploited?
CVE-2026-53109 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53109?
CVE-2026-53109 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53109?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53109, 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-53109

Explore →

Is Your Infrastructure Affected by CVE-2026-53109?

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

Start Free Scan →Browse All CVEs