Vulnerability · Published Jan 14, 2026 · Assigned by Linux
CVE-2025-71135md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() The variable mddev->private is first assigned to conf and then checked: conf = mddev->private; if (!conf) ... If conf is NULL, then mddev->private is also NULL. In this case, null-pointer dereferences can occur when calling raid5_quiesce(): raid5_quiesce(mddev, true); raid5_quiesce(mddev, false); since mddev->private is assigned to conf again in raid5_quiesce(), and conf is dereferenced in several places, for example: conf->quiesce = 0; wake_up(&conf->wait_for_quiescent); To fix this issue, the function should unlock mddev and return before invoking raid5_quiesce() when conf is NULL, following the existing pattern in raid5_change_consistency_policy().
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:13 | linux | 6.12.69-1 | DEBIAN-CVE-2025-71135 |
| Debian:14 | linux | 6.18.5-1 | DEBIAN-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux | 6.8.0-110.110 | UBUNTU-CVE-2025-71135 |
| Ubuntu:25.10 | linux | 6.17.0-22.22 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1052.55 | UBUNTU-CVE-2025-71135 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1012.12 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1012.12~24.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1052.55~22.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1054.60 | UBUNTU-CVE-2025-71135 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1013.13 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1013.13~24.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1059.65~22.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1058.65 | UBUNTU-CVE-2025-71135 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1058.65~22.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1054.57 | UBUNTU-CVE-2025-71135 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1012.12 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1012.12~24.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1054.57~22.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1050.56 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1037.40 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-22.22~24.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-110.110~22.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1051.51 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1051.51~22.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-110.110.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-110.110.1~22.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1051.54 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1018.18 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1051.54~22.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1051.54.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1022.22 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1020.20 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1049.50 | UBUNTU-CVE-2025-71135 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1011.11 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1011.11~24.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1049.50~22.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1052.56 | UBUNTU-CVE-2025-71135 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1013.13 | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1010.11 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:25.10 | linux-riscv | 6.17.0-22.22.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | 6.17.0-22.22.1~24.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-110.110~22.04.1 | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-71135 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1028.29 | UBUNTU-CVE-2025-71135 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | be19e6e4339d1579d5f2fae8ce4facf9521dbbfc – before 20597b7229aea8b5bc45cd92097640257c7fc33bfa1944bbe6220eb929e2c02e5e8706b908565711 – before e5abb6af905de6b2fead8a0b3f32ab0b81468a01fa1944bbe6220eb929e2c02e5e8706b908565711 – before 7ad6ef91d8745d04aff9cce7bdbc6320d8e05fe96.12.4 – before 6.12.64 |
| Linux | Linux | 6.13 |