---
id: CVE-2024-57929
title: |-
  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 …
summary: |-
  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 …
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-672
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 4.9, < 5.4.290'
  - 'linux_kernel >= 5.5, < 5.10.234'
  - 'linux_kernel >= 5.11, < 5.15.177'
  - 'linux_kernel >= 5.16, < 6.1.125'
  - 'linux_kernel >= 6.2, < 6.6.72'
  - 'linux_kernel >= 6.7, < 6.12.10'
  - linux_kernel = 6.13
patched:
  - linux_kernel 6.12.10
published: '2025-01-19'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T02:17:13.080'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-57929'
references:
  - url: 'https://git.kernel.org/stable/c/017c4470bff53585370028fec9341247bad358ff'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6002bec5354f86d1a2df21468f68e3ec03ede9da'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/738994872d77e189b2d13c501a1d145e95d98f46'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/9c7c03d0e926762adf3a3a0ba86156fb5e19538b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/e477021d252c007f0c6d45b5d13d341efed03979'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f2893c0804d86230ffb8f1c8703fdbb18648abc8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/fc1ef07c3522e257e32702954f265debbcb096a7'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-265688.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.00261
epssPercentile: 0.17717
ingestedAt: '2026-10-15T03:30:12.780Z'
---

## Overview

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>

## Affected

- `linux_kernel >= 4.9, < 5.4.290`
- `linux_kernel >= 5.5, < 5.10.234`
- `linux_kernel >= 5.11, < 5.15.177`
- `linux_kernel >= 5.16, < 6.1.125`
- `linux_kernel >= 6.2, < 6.6.72`
- `linux_kernel >= 6.7, < 6.12.10`
- `linux_kernel = 6.13`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.12.10`