All reports
Low

kernel: dm-verity: disable recursive forward error correction

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2025-71161

Probability of exploitation in the next 30 days: 0.47%

FIRST EPSS · 2026-11-18

Description

In the Linux kernel, the following vulnerability has been resolved: dm-verity: disable recursive forward error correction There are two problems with the recursive correction:

  1. It may cause denial-of-service. In fec_read_bufs, there is a loop that has 253 iterations. For each iteration, we may call verity_hash_for_block recursively. There is a limit of 4 nested recursions - that means that there may be at most 253^4 (4 billion) iterations. Red Hat QE team actually created an image that pushes dm-verity to this limit - and this image just makes the udev-worker process get stuck in the 'D' state.

  2. It doesn't work. In fec_read_bufs we store data into the variable "fio->bufs", but fio bufs is shared between recursive invocations, if "verity_hash_for_block" invoked correction recursively, it would overwrite partially filled fio->bufs.

A denial-of-service vulnerability was found in the Linux kernel's dm-verity device mapper target. The recursive forward error correction (FEC) implementation allows up to 253^4 (approximately 4 billion) iterations due to nested recursion in fec_read_bufs() and verity_hash_for_block(). A specially crafted dm-verity image can trigger this worst-case behavior, causing the udev-worker process to become stuck in uninterruptible sleep state.