CVE-2026-53129

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:

fs/mbcache: cancel shrink work before destroying the cache

mb_cache_destroy() calls shrinker_free() and then frees all cache entries and the cache itself, but it does not cancel the pending c_shrink_work work item first.

If mb_cache_entry_create() schedules c_shrink_work via schedule_work() and the work item is still pending or running when mb_cache_destroy() runs, mb_cache_shrink_worker() will access the cache after its memory has been freed, causing a use-after-free.

This is only reachable by a privileged user (root or CAP_SYS_ADMIN) who can trigger the last put of a mounted ext2/ext4/ocfs2 filesystem.

Cancel the work item with cancel_work_sync() before calling shrinker_free(), ensuring the worker has finished and will not be rescheduled before the cache is torn down.

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
2%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 6, 2026

Advisory Details (4)

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

fs/mbcache: cancel shrink work before destroying the cache - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/mbcache: cancel shrink work before destroying the cache - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/mbcache: cancel shrink work before destroying the cache - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/mbcache: cancel shrink work before destroying the cache - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e4eff315d799f5842b95872199b0f0fb8ef5f51

Vendor Advisories for CVE-2026-53129(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-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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53129?
CVE-2026-53129 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: fs/mbcache: cancel shrink work before destroying the cache mbcachedestroy() calls shrinker_free() and then frees all cache entries and the cache itself, but it does not cancel the pending cshrinkwork work item first. If…
When was CVE-2026-53129 disclosed?
CVE-2026-53129 was first published in the National Vulnerability Database on June 24, 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-53129 actively exploited?
CVE-2026-53129 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 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53129?
CVE-2026-53129 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53129?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53129, 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-53129

Explore →

Is Your Infrastructure Affected by CVE-2026-53129?

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

Start Free Scan →Browse All CVEs