CVE-2025-71161
published 2026-01-23CVE-2025-71161: In the Linux kernel, the following vulnerability has been resolved: dm-verity: disable recursive forward error correction There are two problems with the…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.17%
6.1th percentile
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.
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.18.8-1 (forky) | linux 6.18.8-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= a739ff3f543afbb4a041c16cd0182c8e8d366e70 < 8b821ca892cfeeaf0bedc9fc72717294f67144d5 | 8b821ca892cfeeaf0bedc9fc72717294f67144d5 |
| linux | linux | >= a739ff3f543afbb4a041c16cd0182c8e8d366e70 < e227d2b229c7529bd98d348efc55262ccf24ab35 | e227d2b229c7529bd98d348efc55262ccf24ab35 |
| linux | linux | >= a739ff3f543afbb4a041c16cd0182c8e8d366e70 < 897d9006e75f46f8bd7df78faa424327ae6a4bcf | 897d9006e75f46f8bd7df78faa424327ae6a4bcf |
| linux | linux | >= a739ff3f543afbb4a041c16cd0182c8e8d366e70 < 4220cb37406915c926c0e4a3dbab77cd9cceeb1e | 4220cb37406915c926c0e4a3dbab77cd9cceeb1e |
| linux | linux | >= a739ff3f543afbb4a041c16cd0182c8e8d366e70 < 232948cf600fba69aff36b25d85ef91a73a35756 | 232948cf600fba69aff36b25d85ef91a73a35756 |
| linux | linux | >= a739ff3f543afbb4a041c16cd0182c8e8d366e70 < d9f3e47d3fae0c101d9094bc956ed24e7a0ee801 | d9f3e47d3fae0c101d9094bc956ed24e7a0ee801 |
| linux | linux_kernel | >= 0 < 6.18.8-1 | 6.18.8-1 |
| linux | linux_kernel | >= 4.5 < 6.18.6 | 6.18.6 |
| ubuntu | linux | — | — |
| ubuntu | linux-gcp | — | — |
| ubuntu | linux-gcp-6.17 | — | — |
| ubuntu | linux-gcp-6.8 | — | — |
| ubuntu | linux-gke | — | — |
| ubuntu | linux-gkeop | — | — |
| ubuntu | linux-realtime | — | — |
| ubuntu | linux-realtime-6.17 | — | — |
| ubuntu | linux-realtime-6.8 | — | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
vendor_ubuntu2.0LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
Linux kernel vulnerabilities
vendor_ubuntu·2026-07-20·CVSS 2.0
CVE-2026-46073 [LOW] Linux kernel vulnerabilities
Title: Linux kernel vulnerabilities
Summary: Several security issues were fixed in the Linux kernel.
It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)
It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)
It was discovered that some AMD Zen 5 processors supporting RDSEED
instruction did not properly handle entropy, potentially resulting in the
consumption of insufficiently random values. A local attacke
Ubuntu
Linux kernel vulnerabilities
vendor_ubuntu·2026-07-20
CVE-2025-71190 Linux kernel vulnerabilities
Title: Linux kernel vulnerabilities
Summary: Several security issues were fixed in the Linux kernel.
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- Foo-over-UDP (FOU);
- ARM64 architecture;
- x86 architecture;
- Block layer subsystem;
- Drivers core;
- Null block device driver;
- Bluetooth drivers;
- Counter interface drivers;
- DMA engine subsystem;
- DPLL subsystem;
- GPIO subsystem;
- GPU drivers;
- I2C subsystem;
- IIO ADC drivers;
- IIO subsystem;
- On-Chip Interconnect management framework;
- IOMMU subsystem;
- IRQ chip drivers;
- Modular ISDN driver;
- LED subsystem;
- Multiple devices driver;
- UACCE accelerator framework;
- MMC subsystem;
- Ether
Red Hat
kernel: dm-verity: disable recursive forward error correction
vendor_redhat·2026-01-23·CVSS 5.5
CVE-2025-71161 [MEDIUM] CWE-835 kernel: dm-verity: disable recursive forward error correction
kernel: dm-verity: disable recursive forward error correction
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 invocation
Debian
CVE-2025-71161: linux - In the Linux kernel, the following vulnerability has been resolved: dm-verity: ...
vendor_debian·2025·CVSS 5.5
CVE-2025-71161 [MEDIUM] CVE-2025-71161: linux - In the Linux kernel, the following vulnerability has been resolved: dm-verity: ...
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, i
GHSA
GHSA-m3cp-9jq6-3gg3: In the Linux kernel, the following vulnerability has been resolved:
dm-verity: disable recursive forward error correction
There are two problems wit
ghsa_unreviewed·2026-01-23
CVE-2025-71161 [MEDIUM] CWE-193 GHSA-m3cp-9jq6-3gg3: In the Linux kernel, the following vulnerability has been resolved:
dm-verity: disable recursive forward error correction
There are two problems wit
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 recursivel
OSV
CVE-2025-71161: In the Linux kernel, the following vulnerability has been resolved: dm-verity: disable recursive forward error correction There are two problems with
osv·2026-01-23·CVSS 5.5
CVE-2025-71161 [MEDIUM] CVE-2025-71161: In the Linux kernel, the following vulnerability has been resolved: dm-verity: disable recursive forward error correction There are two problems with
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, i
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/232948cf600fba69aff36b25d85ef91a73a35756https://git.kernel.org/stable/c/4220cb37406915c926c0e4a3dbab77cd9cceeb1ehttps://git.kernel.org/stable/c/897d9006e75f46f8bd7df78faa424327ae6a4bcfhttps://git.kernel.org/stable/c/8b821ca892cfeeaf0bedc9fc72717294f67144d5https://git.kernel.org/stable/c/d9f3e47d3fae0c101d9094bc956ed24e7a0ee801https://git.kernel.org/stable/c/e227d2b229c7529bd98d348efc55262ccf24ab35https://cert-portal.siemens.com/productcert/html/ssa-019113.htmlhttps://cert-portal.siemens.com/productcert/html/ssa-082556.html
2026-01-23
Published