CVE-2026-53189

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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%
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
Patch available.
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

Patch Availability(14)

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (146 versions)
  • every version up to 7.0.13-1: fixed in 7.0.13-1
—

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 7× in last 7d / 37× 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 266 total refreshes for this CVE.

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

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 on June 25, 2026, with the most recent update on August 5, 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 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53189?
CVE-2026-53189 has a CVSS base score of 7.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2026-53189?
A fix for CVE-2026-53189 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53189 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-53189

Explore →

Is Your Infrastructure Affected by CVE-2026-53189?

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