CVE-2026-53060: dm cache metadata: fix memory leak on metadata abort retry
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 044ca491d4086dc5bf233e9fcb71db52df32f633, 14f60e957f34f95a626caec76a8fae88cf4c397f, 15c30997dca681f90dbf2d45ee629c1828bf0c0d; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 044ca491d4086dc5bf233e9fcb71db52df32f633, 14f60e957f34f95a626caec76a8fae88cf4c397f, 15c30997dca681f90dbf2d45ee629c1828bf0c0d; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: dm cache metadata: fix memory leak on metadata abort retry When failing to acquire the root_lock in dm_cache_metadata_abort because the block_manager is read-only, the temporary block_manager created outside the root_lock is not properly released, causing a memory leak. Reproduce steps: This can be reproduced by reloading a new table while the metadata is read-only. While the second call to dm_cache_metadata_abort is caused by lack of support for table preload in dm-cache, mentioned in commit 9b1cc9f251af ("dm cache: share cache-metadata object across inactive and active DM tables"), it exposes the memory leak in dm_cache_metadata_abort when the function is called multiple times. Specifically, dm-cache fails to sync the new cache object's mode during preresume, creating the reproducer condition. This issue could also occur through concurrent metadata_operation_failed calls due to races in cache mode updates, but the table preload scenario below provides a reliable reproducer. 1. Create a cache device with some faulty trailing metadata blocks dmsetup create cmeta <<EOF 0 200 linear /dev/sdc 0 200 7992 error EOF dmsetup create cdata --table "0 131072 linear /dev/sdc 8192" dmsetup create corig --table "0 262144 linear /dev/sdc 262144" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct dmsetup create cache --table "0 131072 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 1 writethrough smq 0" 2. Suspend and resume the cache to start a new metadata transaction and trigger metadata io errors on the next metadata commit. dmsetup suspend cache dmsetup resume cache 3. Write to the cache device to update metadata fio --filename=/dev/mapper/cache --name test --rw=randwrite --bs=4k \ --randrepeat=0 --direct=1 --size 64k 4. Preload the same table dmsetup reload cache --table "$(dmsetup table cache)" 5. Resume the new table. This triggers the memory leak. dmsetup suspend cache dmsetup resume cache kmemleak logs: <snip> unreferenced object 0xffff8880080c2010 (size 16): comm "dmsetup", pid 132, jiffies 4294982580 hex dump (first 16 bytes): 00 38 b9 07 80 88 ff ff 6a 6b 6b 6b 6b 6b 6b a5 ... backtrace (crc 3118f31c): kmemleak_alloc+0x28/0x40 __kmalloc_cache_noprof+0x3d9/0x510 dm_block_manager_create+0x51/0x140 dm_cache_metadata_abort+0x85/0x320 metadata_operation_failed+0x103/0x1e0 cache_preresume+0xacd/0xe70 dm_table_resume_targets+0xd3/0x320 __dm_resume+0x1b/0xf0 dm_resume+0x127/0x170 <snip>
- Published
- Jun 24, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-401
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6e237cacda8b4e976849e7bff9fe7dff0e968586, 3972ae47d0ee9b5b434af5d0cca6cdfd1e239d4f, 9958f5ffc44530b650fb4cc9038a4d167fa4f5c1, f472bfc95d9c9653172dbdad39219b32fabf9b92, bdd4e106929ac943f3226d8f03754b480701e97b, 6.2affected
- b45e77b79215405bd039a690f5b06cc03e8ed27d and later · before 14f60e957f34f95a626caec76a8fae88cf4c397faffected · git
- 28d307f380df88a598bc0186d527462902d9bda1 and later · before 6b97cc7a42905755c56bbddc33aa8b792205caeeaffected · git
- f74b7c5a85e22cd9091845e0d62a1dd89d0f855f and later · before d1a79620c419a0af1911f99c873014b30740e303affected · git
- 352b837a5541690d4f843819028cf2b8be83d424 and later · before 15c30997dca681f90dbf2d45ee629c1828bf0c0daffected · git
- 352b837a5541690d4f843819028cf2b8be83d424 and later · before b0bd35535bdb6f58505f3a30ee5793986943997aaffected · git
- 352b837a5541690d4f843819028cf2b8be83d424 and later · before 322a3b70368d49e39591fe9fc6c07d262128b05faffected · git
- 352b837a5541690d4f843819028cf2b8be83d424 and later · before 4311ca59a1891d33c4c8b7946f98c34f167fe833affected · git
- 352b837a5541690d4f843819028cf2b8be83d424 and later · before 044ca491d4086dc5bf233e9fcb71db52df32f633affected · git
- 5.10.163 and later · before 5.10.258affected · semver
Affected versions · NVD (12)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.9.337 and later · before 4.10
- linux linux kernel4.14.303 and later · before 4.15
- linux linux kernel4.19.270 and later · before 4.20
- linux linux kernel5.4.229 and later · before 5.5
- linux linux kernel5.10.163 and later · before 5.10.258
- linux linux kernel5.15.87 and later · before 5.15.209
- linux linux kernel6.0.18 and later · before 6.1
- linux linux kernel6.1.4 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.141
- linux linux kernel6.7 and later · before 6.12.91
- linux linux kernel6.13 and later · before 6.18.33
- linux linux kernel6.19 and later · before 7.0.10
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.10-1 | 7.0.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-53055Jun 24, 2026 · crypto: hisilicon/sec2 - prevent req used-after-free for sec39Monitor
- ← EarlierCVE-2026-53059Jun 24, 2026 · dm log: fix out-of-bounds write due to region_count overflow31Monitor
- Later →CVE-2026-53061Jun 24, 2026 · dm cache: fix dirty mapping checking in passthrough mode switching22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 044ca491d4086dc5bf233e9fcb71db52df32f633 | Vendor (CNA) |
| Linux Linux | 14f60e957f34f95a626caec76a8fae88cf4c397f | Vendor (CNA) |
| Linux Linux | 15c30997dca681f90dbf2d45ee629c1828bf0c0d | Vendor (CNA) |
| Linux Linux | 322a3b70368d49e39591fe9fc6c07d262128b05f | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 4311ca59a1891d33c4c8b7946f98c34f167fe833 | Vendor (CNA) |
| Linux Linux | 5.10.258 | Vendor (CNA) |
| Linux Linux | 5.15.209 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 6.1 | Vendor (CNA) |
| Linux Linux | 6.1.175 | Vendor (CNA) |
| Linux Linux | 6b97cc7a42905755c56bbddc33aa8b792205caee | Vendor (CNA) |
| Linux Linux | b0bd35535bdb6f58505f3a30ee5793986943997a | Vendor (CNA) |
| Linux Linux | d1a79620c419a0af1911f99c873014b30740e303 | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.143.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0440 · Jun 25, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/14f60e957f34f95a626caec76a8fae88cf4c397f
- git.kernel.org/stable/c/15c30997dca681f90dbf2d45ee629c1828bf0c0d
- git.kernel.org/stable/c/322a3b70368d49e39591fe9fc6c07d262128b05f
- git.kernel.org/stable/c/4311ca59a1891d33c4c8b7946f98c34f167fe833
- git.kernel.org/stable/c/6b97cc7a42905755c56bbddc33aa8b792205caee
- git.kernel.org/stable/c/b0bd35535bdb6f58505f3a30ee5793986943997a
- git.kernel.org/stable/c/d1a79620c419a0af1911f99c873014b30740e303
Vendor advisories and official records. Exploit/PoC links are deliberately left out.