In the Linux kernel, the following vulnerability has been resolved: dm cache metadata: fix memory leak on metadata abort retry When failing to… (CVE-2026-53060)
A memory leak vulnerability in the Linux kernel's device mapper cache metadata handling was resolved. The issue occurs when failing to acquire a lock during metadata abort retry due to the block manager being read-only, causing temporary resources not to be released properly. This can be triggered by reloading a new table while metadata is read-only or through concurrent metadata operation failures. The vulnerability does not affect confidentiality or integrity but can cause denial of service by exhausting memory.
AI Analysis
Technical Summary
CVE-2026-53060 addresses a memory leak in the Linux kernel's dm_cache_metadata_abort function. When the root_lock cannot be acquired because the block_manager is read-only, the temporary block_manager created outside the lock is not freed, leading to a memory leak. This condition can be reliably reproduced by reloading a dm-cache table while metadata is read-only, triggering multiple calls to dm_cache_metadata_abort. The leak is also exposed by concurrent metadata_operation_failed calls due to race conditions in cache mode updates. The issue results in unreferenced kernel memory allocations, as confirmed by kmemleak logs.
Potential Impact
The vulnerability causes a memory leak in the kernel, which can lead to resource exhaustion and potential denial of service. There is no impact on confidentiality or integrity. The CVSS 3.1 score is 5.5 (medium severity) reflecting local attack vector with low complexity and no user interaction required.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid scenarios that reload dm-cache tables while metadata is read-only or cause concurrent metadata operation failures. Monitor kernel memory usage to detect potential leaks related to dm-cache operations.
In the Linux kernel, the following vulnerability has been resolved: dm cache metadata: fix memory leak on metadata abort retry When failing to… (CVE-2026-53060)
Description
A memory leak vulnerability in the Linux kernel's device mapper cache metadata handling was resolved. The issue occurs when failing to acquire a lock during metadata abort retry due to the block manager being read-only, causing temporary resources not to be released properly. This can be triggered by reloading a new table while metadata is read-only or through concurrent metadata operation failures. The vulnerability does not affect confidentiality or integrity but can cause denial of service by exhausting memory.
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53060 addresses a memory leak in the Linux kernel's dm_cache_metadata_abort function. When the root_lock cannot be acquired because the block_manager is read-only, the temporary block_manager created outside the lock is not freed, leading to a memory leak. This condition can be reliably reproduced by reloading a dm-cache table while metadata is read-only, triggering multiple calls to dm_cache_metadata_abort. The leak is also exposed by concurrent metadata_operation_failed calls due to race conditions in cache mode updates. The issue results in unreferenced kernel memory allocations, as confirmed by kmemleak logs.
Potential Impact
The vulnerability causes a memory leak in the kernel, which can lead to resource exhaustion and potential denial of service. There is no impact on confidentiality or integrity. The CVSS 3.1 score is 5.5 (medium severity) reflecting local attack vector with low complexity and no user interaction required.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid scenarios that reload dm-cache tables while metadata is read-only or cause concurrent metadata operation failures. Monitor kernel memory usage to detect potential leaks related to dm-cache operations.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w7r8-qc4c-gqhh
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53060"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a5fcf481010f89cc21529e1
Added to database: 07/21/2026, 19:58:00 UTC
Last enriched: 09/15/2026, 06:36:23 UTC
Last updated: 09/15/2026, 06:36:23 UTC
Views: 22
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.