CVE-2026-53189

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

mm/huge_memory: update file PMD counter before folio_put()

__split_huge_pmd_locked() updates the file/shmem RSS counter after dropping the PMD mapping's folio reference. If folio_put() drops the last reference, mm_counter_file() can later read freed folio state via folio_test_swapbacked().

Move the counter update before folio_put().

CVSS v3
7.8
EG Score
7.8(high)
EPSS
3.6%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

mm/huge_memory: update file PMD counter before folio_put() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/huge_memory: update file PMD counter before folio_put() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/huge_memory: update file PMD counter before folio_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d878059924f12c1bc24556a92ec56add74de3c8
generic

mm/huge_memory: update file PMD counter before folio_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/84b3212b166b446faea27ebebb7161405ffceef9
generic

mm/huge_memory: update file PMD counter before folio_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c29a8ba084e89499ca77b947e07ae817f9c16ce
generic

mm/huge_memory: update file PMD counter before folio_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f5b604e1e6bde4e889199168ee80fe8306d06ad
generic

mm/huge_memory: update file PMD counter before folio_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/459771c9cf30f378bdbd30fc65d17f7eb931bb59
generic

mm/huge_memory: update file PMD counter before folio_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/108963978a681c0c468d279cac2b930c27672877

Vendor Advisories for CVE-2026-53189(1)

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

Data Freshness Timeline

(refreshed 42× in last 7d / 60× 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.

  1. 2026-07-07 01:58 UTCEG score recompute
  2. 2026-07-07 01:58 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 15:08 UTCEG score recompute
  6. 2026-07-06 15:07 UTCGHSA enrichment
  7. 2026-07-06 04:10 UTCEG score recompute
  8. 2026-07-06 04:09 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 17:18 UTCEG score recompute
  12. 2026-07-05 17:18 UTCGHSA enrichment
  13. 2026-07-05 06:27 UTCEG score recompute
  14. 2026-07-05 06:27 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 19:38 UTCEG score recompute
  18. 2026-07-04 19:37 UTCGHSA enrichment
  19. 2026-07-04 08:47 UTCEG score recompute
  20. 2026-07-04 08:47 UTCGHSA enrichment
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-03 21:57 UTCEG score recompute
  24. 2026-07-03 21:57 UTCGHSA enrichment
  25. 2026-07-03 11:07 UTCEG score recompute
Show 35 more
  1. 2026-07-03 11:07 UTCGHSA enrichment
  2. 2026-07-03 00:05 UTCEG score recompute
  3. 2026-07-03 00:05 UTCGHSA enrichment
  4. 2026-07-02 13:16 UTCEG score recompute
  5. 2026-07-02 13:16 UTCGHSA enrichment
  6. 2026-07-02 02:23 UTCEG score recompute
  7. 2026-07-02 02:23 UTCGHSA enrichment
  8. 2026-07-01 15:32 UTCEG score recompute
  9. 2026-07-01 15:32 UTCGHSA enrichment
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 04:41 UTCEG score recompute
  12. 2026-07-01 04:41 UTCGHSA enrichment
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-30 17:51 UTCEG score recompute
  15. 2026-06-30 17:51 UTCGHSA enrichment
  16. 2026-06-30 07:01 UTCEG score recompute
  17. 2026-06-30 07:01 UTCGHSA enrichment
  18. 2026-06-29 20:11 UTCEG score recompute
  19. 2026-06-29 20:11 UTCGHSA enrichment
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 09:21 UTCEG score recompute
  23. 2026-06-29 09:21 UTCGHSA enrichment
  24. 2026-06-28 22:31 UTCEG score recompute
  25. 2026-06-28 22:31 UTCGHSA enrichment
  26. 2026-06-28 14:07 UTCEPSS rescore
  27. 2026-06-28 11:41 UTCEG score recompute▲ 7.80
  28. 2026-06-28 11:41 UTCGHSA enrichment
  29. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  30. 2026-06-28 04:56 UTCEPSS rescore
  31. 2026-06-28 04:56 UTCEPSS rescore
  32. 2026-06-27 03:08 UTCEPSS rescore
  33. 2026-06-25 13:49 UTCEPSS rescore
  34. 2026-06-25 10:07 UTCEG score recompute
  35. 2026-06-25 10:07 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53189?
CVE-2026-53189 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/hugememory: update file PMD counter before folioput() splithugepmd_locked() updates the file/shmem RSS counter after dropping the PMD mapping's folio reference. If folio_put() drops the last reference, mmcounterfile() can later…
When was CVE-2026-53189 disclosed?
CVE-2026-53189 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53189 actively exploited?
CVE-2026-53189 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53189?
CVE-2026-53189 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53189?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53189, 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

Explore the affected products and dependency analysis for CVE-2026-53189

Explore →

Is Your Infrastructure Affected by CVE-2026-53189?

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

Start Free Scan →Browse All CVEs