Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2026-53060

medium

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 ro…

Vendor / product: Linux — linux kernel

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 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

CVSS
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2026-06-24 17:17
Modified: 2026-11-06 17:18
NVD status: Analyzed
Last synced 1 week ago
Verified against the source API 2026-11-06 17:46 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥4.9.337 <4.10, ≥4.14.303 <4.15, ≥4.19.270 <4.20, ≥5.4.229 <5.5, ≥5.10.163 <5.10.258, ≥5.15.87 <5.15.209

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/044ca491d4086dc5bf233e9fcb71db52df32f633
Patch / mitigation: https://git.kernel.org/stable/c/14f60e957f34f95a626caec76a8fae88cf4c397f
Patch / mitigation: https://git.kernel.org/stable/c/15c30997dca681f90dbf2d45ee629c1828bf0c0d
Patch / mitigation: https://git.kernel.org/stable/c/322a3b70368d49e39591fe9fc6c07d262128b05f
Patch / mitigation: https://git.kernel.org/stable/c/4311ca59a1891d33c4c8b7946f98c34f167fe833
Patch / mitigation: https://git.kernel.org/stable/c/6b97cc7a42905755c56bbddc33aa8b792205caee
Patch / mitigation: https://git.kernel.org/stable/c/b0bd35535bdb6f58505f3a30ee5793986943997a
Patch / mitigation: https://git.kernel.org/stable/c/d1a79620c419a0af1911f99c873014b30740e303

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-06 17:46 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs