Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53061, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (20 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 2ee57d587357f0d752af6c2e3e46434a74b1bee3 – < c2e86f647561fcf5e1c6eba7d75e9e0c4299c94d
    • affected 2ee57d587357f0d752af6c2e3e46434a74b1bee3 – < 5c98a3f1d7a554c9e920aa31daf92af6b5bbb8cc
    • affected 2ee57d587357f0d752af6c2e3e46434a74b1bee3 – < 1443c32f24d6d8bcdf4beceef2afc09290b98717
    • affected 2ee57d587357f0d752af6c2e3e46434a74b1bee3 – < 12105c7f18375d7615dad7605d89eadae7eb12a6
    • affected 2ee57d587357f0d752af6c2e3e46434a74b1bee3 – < bd5a2c1018938e6b32670728bdb32a3f0efff00f
    • affected 2ee57d587357f0d752af6c2e3e46434a74b1bee3 – < 21c503d60a257e54ca3ac58e2721bd24501d5bde
    • affected 2ee57d587357f0d752af6c2e3e46434a74b1bee3 – < 01b22656d8a68dbeae59f8b80866e7b11936b20a
    • affected 2ee57d587357f0d752af6c2e3e46434a74b1bee3 – < 322586745bd1a0e5f3559fd1635fdeb4dbd1d6b8
  • Linux · Linux

    • affected 3.13
    • unaffected < 3.13
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.141 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53061 badge
[![CVE-2026-53061](https://cveledger.app/badge/CVE-2026-53061.svg)](https://cveledger.app/cve/CVE-2026-53061)

Record last updated .