Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-53129fs/mbcache: cancel shrink work before destroying the cache

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53129, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected c2f3140fe2eceb3a6c1615b2648b9471544881c6 – < 40148c615687c1692712e50a6de53d62dfbfc20f
    • affected c2f3140fe2eceb3a6c1615b2648b9471544881c6 – < cbdd6f0fb19a0ce8a013acd80ac87a62f57fa20d
    • affected c2f3140fe2eceb3a6c1615b2648b9471544881c6 – < a88d39a74a208e197c03bffaa2df34de732af19f
    • affected c2f3140fe2eceb3a6c1615b2648b9471544881c6 – < 0e4eff315d799f5842b95872199b0f0fb8ef5f51
    • affected c2f3140fe2eceb3a6c1615b2648b9471544881c6 – < b25fd3523bef88fb7ffd4c5b63bbe9c08f73bb4c
    • affected c2f3140fe2eceb3a6c1615b2648b9471544881c6 – < d227786ab1119669df4dc333a61510c52047cce4
  • Linux · Linux

    • affected 4.6
    • unaffected < 4.6
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53129 badge
[![CVE-2026-53129](https://cveledger.app/badge/CVE-2026-53129.svg)](https://cveledger.app/cve/CVE-2026-53129)

Record last updated .