CVE-2026-53060

/// Technical 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 t

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References