CVE-2026-53062CWE-362CWE-667

CVE-2026-53062

High · published June 24, 2026

CVSS v3.1
7.8
EPSS
0%
Percentile
0.7
In the wild
Unconfirmed
What it is

In the Linux kernel, the following vulnerability has been resolved:

dm cache policy smq: fix missing locks in invalidating cache blocks

In passthrough mode, the policy invalidate_mapping operation is called

simultaneously from multiple workers, thus it should be protected by a

lock. Otherwise, we might end up with data races on the allocated blocks

counter, or even use-after-free issues with internal data structures

when doing concurrent writes.

Note that the existing FIXME in smq_invalidate_mapping() doesn't affect

passthrough mode since migration tasks don't exist there, but would need

attention if supporting fast device shrinking via suspend/resume without

target reloading.

Reproduce steps:

1. Create a cache device consisting of 1024 cache entries

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 writethrough smq 0"

2. Populate the cache, and record the number of cached blocks

fio --name=populate --filename=/dev/mapper/cache --rw=randwrite --bs=4k \

--size=64m --direct=1

nr_cached=$(dmsetup status cache | awk '{split($7, a, "/"); print a[1]}')

3. Reload the cache into passthrough mode

dmsetup suspend cache

dmsetup reload cache --table "0 262144 cache /dev/mapper/cmeta \

/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough smq 0"

dmsetup resume cache

4. Write to the passthrough cache. By setting multiple jobs with I/O

size equal to the cache block size, cache blocks are invalidated

concurrently from different workers.

fio --filename=/dev/mapper/cache --name=test --rw=randwrite --bs=64k \

--direct=1 --numjobs=2 --randrepeat=0 --size=64m

5. Check if demoted matches cached block count. These numbers should

match but may differ due to the data race.

nr_demoted=$(dmsetup status cache | awk '{print $12}')

echo "$nr_cached, $nr_demoted"

The record
Technical detail
CVSS v3.1
7.8 · HIGH
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00097 · 0.7th percentile
Weaknesses
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'); CWE-667 · Improper Locking
Published
2026-06-24T21:17Z
Affected products (7)
ProductVersionsFixed in
linux/linux_kernel≥ 4.12, < 5.10.2585.10.258
linux/linux_kernel≥ 5.11, < 5.15.2095.15.209
linux/linux_kernel≥ 5.16, < 6.1.1756.1.175
linux/linux_kernel≥ 6.2, < 6.6.1416.6.141
linux/linux_kernel≥ 6.7, < 6.12.916.12.91
linux/linux_kernel≥ 6.13, < 6.18.336.18.33
linux/linux_kernel≥ 6.19, < 7.0.107.0.10
References (8)
EPSS history
Timeline
  • 24 JUN 16:30Z
    dm cache policy smq: fix missing locks in invalidating cache blocks
    cvelistv5