CVE-2024-57929CWE-672

CVE-2024-57929

High · published January 19, 2025

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

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

dm array: fix releasing a faulty array block twice in dm_array_cursor_end

When dm_bm_read_lock() fails due to locking or checksum errors, it

releases the faulty block implicitly while leaving an invalid output

pointer behind. The caller of dm_bm_read_lock() should not operate on

this invalid dm_block pointer, or it will lead to undefined result.

For example, the dm_array_cursor incorrectly caches the invalid pointer

on reading a faulty array block, causing a double release in

dm_array_cursor_end(), then hitting the BUG_ON in dm-bufio cache_put().

Reproduce steps:

1. initialize a cache device

dmsetup create cmeta --table "0 8192 linear /dev/sdc 0"

dmsetup create cdata --table "0 65536 linear /dev/sdc 8192"

dmsetup create corig --table "0 524288 linear /dev/sdc $262144"

dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1

dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \

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

2. wipe the second array block offline

dmsteup remove cache cmeta cdata corig

mapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \

2>/dev/null | hexdump -e '1/8 "%u\n"')

ablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \

2>/dev/null | hexdump -e '1/8 "%u\n"')

dd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock

3. try reopen the cache device

dmsetup create cmeta --table "0 8192 linear /dev/sdc 0"

dmsetup create cdata --table "0 65536 linear /dev/sdc 8192"

dmsetup create corig --table "0 524288 linear /dev/sdc $262144"

dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \

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

Kernel logs:

(snip)

device-mapper: array: array_block_check failed: blocknr 0 != wanted 10

device-mapper: block manager: array validator check failed for block 10

device-mapper: array: get_ablock failed

device-mapper: cache metadata: dm_array_cursor_next for mapping failed

------------[ cut here ]------------

kernel BUG at drivers/md/dm-bufio.c:638!

Fix by setting the cached block pointer to NULL on errors.

In addition to the reproducer described above, this fix can be

verified using the "array_cursor/damaged" test in dm-unit:

dm-unit run /pdata/array_cursor/damaged --kernel-dir <KERNEL_DIR>

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.00260 · 16.8th percentile
Weakness
CWE-672 · Operation on a Resource after Expiration or Release
Published
2025-01-19T17:15Z
Affected products (12)
ProductVersionsFixed in
linux/linux_kernel≥ 4.9, < 5.4.2905.4.290
linux/linux_kernel≥ 5.5, < 5.10.2345.10.234
linux/linux_kernel≥ 5.11, < 5.15.1775.15.177
linux/linux_kernel≥ 5.16, < 6.1.1256.1.125
linux/linux_kernel≥ 6.2, < 6.6.726.6.72
linux/linux_kernel≥ 6.7, < 6.12.106.12.10
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
References (10)
EPSS history
Timeline
  • 19 JAN 11:52Z
    dm array: fix releasing a faulty array block twice in dm_array_cursor_end
    cvelistv5