dm-verity: disable recursive forward error correction
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a739ff3f543afbb4a041c16cd0182c8e8d366e70 · < d9f3e47d3fae0c101d9094bc956ed24e7a0ee801| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
Recursive forward error correction in the Linux kernel's dm-verity can cause excessive processing when it encounters an image that pushes recursion to its limit, leaving a udev-worker process stuck. Recursive correction can also overwrite shared buffer data and fail to work correctly. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Engineers running Linux systems that use dm-verity should check their kernel versions; affected versions are not specified.