CVE-2026-53060: dm cache metadata: fix memory leak on metadata abort retry
Published Jun 24, 2026
·Updated
dm cache metadata: fix memory leak on metadata abort retry
Affected Software
14 affected componentsFixes available
Linux dm-cache (device-mapper)
Microsoft azl3 kernel 6.6.139.1-1<6.6.143.1-1
6.6.143.1-1
Linux Linux kernel>=4.9.337<4.10
Linux Linux kernel>=4.14.303<4.15
Linux Linux kernel>=4.19.270<4.20
Linux Linux kernel>=5.4.229<5.5
Linux Linux kernel>=5.10.163<5.10.258
Linux Linux kernel>=5.15.87<5.15.209
Linux Linux kernel>=6.0.18<6.1
Linux Linux kernel>=6.1.4<6.1.175
Linux Linux kernel>=6.2<6.6.141
Linux Linux kernel>=6.7<6.12.91
Linux Linux kernel>=6.13<6.18.33
Linux Linux kernel>=6.19<7.0.10
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.143.1-1
Event History
Jun 24, 2026
CVE Published
via MITRE·04:30 PM
Data Sourced
via MITRE·04:30 PM
Description
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 27, 2026
Data Sourced
via Microsoft·08:10 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:10 AM
Affected Software
Updated
via Microsoft·08:10 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-53060?
CVE-2026-53060 has a risk rating of 2, indicating a low severity level.
2
How does CVE-2026-53060 affect the Linux dm-cache?
CVE-2026-53060 is a memory leak vulnerability that affects the dm-cache component of the Linux kernel.
3
What is the impact of CVE-2026-53060 when using dm-cache?
The impact of CVE-2026-53060 can lead to increased memory usage and potential performance degradation in systems utilizing dm-cache.
4
How do I fix CVE-2026-53060?
To fix CVE-2026-53060, update your Linux kernel to the latest version where the vulnerability has been addressed.
5
When was CVE-2026-53060 published?
CVE-2026-53060 was published on June 24, 2026.