CVE-2025-38066
Severity CVSS v4.0:
Pending analysis
Type:
Unavailable / Other
Publication date:
18/06/2025
Last modified:
17/12/2025
Description
In the Linux kernel, the following vulnerability has been resolved:<br />
<br />
dm cache: prevent BUG_ON by blocking retries on failed device resumes<br />
<br />
A cache device failing to resume due to mapping errors should not be<br />
retried, as the failure leaves a partially initialized policy object.<br />
Repeating the resume operation risks triggering BUG_ON when reloading<br />
cache mappings into the incomplete policy object.<br />
<br />
Reproduce steps:<br />
<br />
1. create a cache metadata consisting of 512 or more cache blocks,<br />
with some mappings stored in the first array block of the mapping<br />
array. Here we use cache_restore v1.0 to build the metadata.<br />
<br />
cat cmeta.xml<br />
<br />
<br />
<br />
<br />
<br />
EOF<br />
dmsetup create cmeta --table "0 8192 linear /dev/sdc 0"<br />
cache_restore -i cmeta.xml -o /dev/mapper/cmeta --metadata-version=2<br />
dmsetup remove cmeta<br />
<br />
2. wipe the second array block of the mapping array to simulate<br />
data degradations.<br />
<br />
mapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \<br />
2>/dev/null | hexdump -e &#39;1/8 "%u\n"&#39;)<br />
ablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \<br />
2>/dev/null | hexdump -e &#39;1/8 "%u\n"&#39;)<br />
dd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock<br />
<br />
3. try bringing up the cache device. The resume is expected to fail<br />
due to the broken array block.<br />
<br />
dmsetup create cmeta --table "0 8192 linear /dev/sdc 0"<br />
dmsetup create cdata --table "0 65536 linear /dev/sdc 8192"<br />
dmsetup create corig --table "0 524288 linear /dev/sdc 262144"<br />
dmsetup create cache --notable<br />
dmsetup load cache --table "0 524288 cache /dev/mapper/cmeta \<br />
/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0"<br />
dmsetup resume cache<br />
<br />
4. try resuming the cache again. An unexpected BUG_ON is triggered<br />
while loading cache mappings.<br />
<br />
dmsetup resume cache<br />
<br />
Kernel logs:<br />
<br />
(snip)<br />
------------[ cut here ]------------<br />
kernel BUG at drivers/md/dm-cache-policy-smq.c:752!<br />
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI<br />
CPU: 0 UID: 0 PID: 332 Comm: dmsetup Not tainted 6.13.4 #3<br />
RIP: 0010:smq_load_mapping+0x3e5/0x570<br />
<br />
Fix by disallowing resume operations for devices that failed the<br />
initial attempt.
Impact
Base Score 3.x
5.50
Severity 3.x
MEDIUM
Vulnerable products and versions
| CPE | From | Up to |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 5.4.294 (excluding) | |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 5.5 (including) | 5.10.238 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 5.11 (including) | 5.15.185 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 5.16 (including) | 6.1.141 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.2 (including) | 6.6.93 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.7 (including) | 6.12.31 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.13 (including) | 6.14.9 (excluding) |
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* |
To consult the complete list of CPE names with products and versions, see this page
References to Advisories, Solutions, and Tools
- https://git.kernel.org/stable/c/00586b78eeb7c626a14ca13453a1631f88a7cf36
- https://git.kernel.org/stable/c/025c8f477625eb39006ded650e7d027bcfb20e79
- https://git.kernel.org/stable/c/3986ef4a9b6a0d9c28bc325d8713beba5e67586f
- https://git.kernel.org/stable/c/5da692e2262b8f81993baa9592f57d12c2703dea
- https://git.kernel.org/stable/c/c5356a5e80442131e2714d0d26bb110590e4e568
- https://git.kernel.org/stable/c/c614584c2a66b538f469089ac089457a34590c14
- https://git.kernel.org/stable/c/cc80a5cc520939d0a7d071cc4ae4b3c55ef171d0
- https://git.kernel.org/stable/c/f3128e3074e8af565cc6a66fe3384a56df87f803
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html



