CVE-2026-53129
Last modified
CVE-2026-53129 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.6, < 6.12.91 |
| Linux | Linux Kernel | >= 6.13, < 6.18.33 |
| Linux | Linux Kernel | >= 6.19, < 7.0.10 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53129?
How severe is CVE-2026-53129?
How do I fix CVE-2026-53129?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53123In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53124In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53125In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53126In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53127In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53128In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5313A vulnerability has been found in Nothings stb up to 2.30. T…4.3
- CVE-2026-53130In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53131In the Linux kernel, the following vulnerability has been re…9.4
- CVE-2026-53132In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53133In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53134In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53129?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
