The Linux kernel dm-cache device‑mapper module contains a memory leak that occurs when dm_cache_metadata_abort fails to acquire the root_lock while the block_manager is created as read‑only; the temporary block_manager created outside the root_lock is not released, causing a leak that can grow with repeated aborts. This can result in gradual out‑of‑memory conditions that may destabilize or crash the kernel, leading to a denial of service. The weakness is an improper resource release, specifically a memory leak, consistent with CWE‑399. The vulnerability requires privileged manipulation of device‑mapper tables and repeated aborts in a read‑only block_manager scenario, making it an in‑kernel, local denial of service flaw.

All Linux kernel releases that provide the dm-cache device‑mapper module and have not yet incorporated the fix referenced in the provided commit history are potentially impacted. The vendor is Linux:Linux, and the affected product is the Linux kernel with the dm-cache module. No specific kernel version list is supplied, so any installation that can create and manipulate dm-cache tables prior to the patch may be affected.

No CVSS or EPSS score is available for this entry, and the vulnerability is not listed in CISA KEV. The flaw requires privileged manipulation of the device‑mapper subsystem and repeated aborts to trigger the leak, limiting exploitation to OS administrators or compromised local users. No public exploits are known, reducing the immediate threat. Nonetheless, any system under attack could suffer a denial of service if an adversary gains the ability to reload dm-cache tables while the metadata is read‑only, repeatedly causing aborts and draining kernel memory. The absence of a remote vector and limited prerequisites keep the overall risk from high to moderate.