CVE-2026-53061

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.

• https://git.kernel.org/stable/c/01b22656d8a68dbeae59f8b80866e7b11936b20aPatch
• https://git.kernel.org/stable/c/12105c7f18375d7615dad7605d89eadae7eb12a6Patch
• https://git.kernel.org/stable/c/1443c32f24d6d8bcdf4beceef2afc09290b98717Patch
• https://git.kernel.org/stable/c/21c503d60a257e54ca3ac58e2721bd24501d5bdePatch
• https://git.kernel.org/stable/c/322586745bd1a0e5f3559fd1635fdeb4dbd1d6b8Patch
• https://git.kernel.org/stable/c/5c98a3f1d7a554c9e920aa31daf92af6b5bbb8ccPatch
• https://git.kernel.org/stable/c/bd5a2c1018938e6b32670728bdb32a3f0efff00fPatch
• https://git.kernel.org/stable/c/c2e86f647561fcf5e1c6eba7d75e9e0c4299c94dPatch

Published

Jun 24, 2026

Last Modified

Jul 21, 2026

Status

Analyzed

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

• 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-53060In 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
• CVE-2026-53067In the Linux kernel, the following vulnerability has been re…7.8