Skip to main content
VulnerabilityPublished Updated

CVE-2026-53061: Linux kernel · dm cache: fix dirty mapping checking in passthrough mode switching

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c2e86f647561fcf5e1c6eba7d75e9e0c4299c94d : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in c2e86f647561fcf5e1c6eba7d75e9e0c4299c94d, bd5a2c1018938e6b32670728bdb32a3f0efff00f, 322586745bd1a0e5f3559fd1635fdeb4dbd1d6b8 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 2ee57d587357f0d752af6c2e3e46434a74b1bee3, < c2e86f647561fcf5e1c6eba7d75e9e0c4299c94d
Fixed in
  • c2e86f647561fcf5e1c6eba7d75e9e0c4299c94d
LinuxLinuxAffected
  • ≥ 2ee57d587357f0d752af6c2e3e46434a74b1bee3, < bd5a2c1018938e6b32670728bdb32a3f0efff00f
Fixed in
  • bd5a2c1018938e6b32670728bdb32a3f0efff00f
LinuxLinuxAffected
  • ≥ 2ee57d587357f0d752af6c2e3e46434a74b1bee3, < 322586745bd1a0e5f3559fd1635fdeb4dbd1d6b8
Fixed in
  • 322586745bd1a0e5f3559fd1635fdeb4dbd1d6b8
LinuxLinuxAffected
  • ≥ 2ee57d587357f0d752af6c2e3e46434a74b1bee3, < 12105c7f18375d7615dad7605d89eadae7eb12a6
Fixed in
  • 12105c7f18375d7615dad7605d89eadae7eb12a6
LinuxLinuxAffected
  • ≥ 2ee57d587357f0d752af6c2e3e46434a74b1bee3, < 1443c32f24d6d8bcdf4beceef2afc09290b98717
Fixed in
  • 1443c32f24d6d8bcdf4beceef2afc09290b98717
LinuxLinuxAffected
  • ≥ 2ee57d587357f0d752af6c2e3e46434a74b1bee3, < 21c503d60a257e54ca3ac58e2721bd24501d5bde
Fixed in
  • 21c503d60a257e54ca3ac58e2721bd24501d5bde

Description

In the Linux kernel, the following vulnerability has been resolved: dm cache: fix dirty mapping checking in passthrough mode switching As mentioned in commit 9b1cc9f251af ("dm cache: share cache-metadata object across inactive and active DM tables"), dm-cache assumed table reload occurs after suspension, while LVM's table preload breaks this assumption. The dirty mapping check for passthrough mode was designed around this assumption and is performed during table creation, causing the check to fail with preload while metadata updates are ongoing. This risks loading dirty mappings into passthrough mode, resulting in data loss. Reproduce steps: 1. Create a writeback cache with zero migration_threshold to produce dirty mappings dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" 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 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writeback smq \ 2 migration_threshold 0" 2. Preload a table in passthrough mode dmsetup reload cache --table "0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough smq 0" 3. Write to the first cache block to make it dirty fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k 4. Resume the inactive table. Now it's possible to load the dirty block into passthrough mode. dmsetup resume cache Fix by moving the checks to the preresume phase to support table preloading. Also remove the unused function dm_cache_metadata_all_clean.

References

Community reviews

Loading reviews…