CVE-2026-53060
Last modified
CVE-2026-53060 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
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>
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53060?
How severe is CVE-2026-53060?
How do I fix CVE-2026-53060?
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-53055In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53056In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53057In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53058In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53059In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5306The Check & Log Email WordPress plugin before 2.0.13 does n…5.4
- CVE-2026-53061In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53062In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53063In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53064In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53065In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53066In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53060?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
