Vulnerability · Published Jan 13, 2026 · Assigned by Linux
CVE-2025-71078powerpc/64s/slb: Fix SLB multihit issue during SLB preload
High 7.8
In plain English
A high-severity race condition 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.1% (higher than 1% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: powerpc/64s/slb: Fix SLB multihit issue during SLB preload On systems using the hash MMU, there is a software SLB preload cache that mirrors the entries loaded into the hardware SLB buffer. This preload cache is subject to periodic eviction — typically after every 256 context switches — to remove old entry. To optimize performance, the kernel skips switch_mmu_context() in switch_mm_irqs_off() when the prev and next mm_struct are the same. However, on hash MMU systems, this can lead to inconsistencies between the hardware SLB and the software preload cache. If an SLB entry for a process is evicted from the software cache on one CPU, and the same process later runs on another CPU without executing switch_mmu_context(), the hardware SLB may retain stale entries. If the kernel then attempts to reload that entry, it can trigger an SLB multi-hit error. The following timeline shows how stale SLB entries are created and can cause a multi-hit error when a process moves between CPUs without a MMU context switch. CPU 0 CPU 1 ----- ----- Process P exec swapper/1 load_elf_binary begin_new_exc activate_mm switch_mm_irqs_off switch_mmu_context switch_slb /* * This invalidates all * the entries in the HW * and setup the new HW * SLB entries as per the * preload cache. */ context_switch sched_migrate_task migrates process P to cpu-1 Process swapper/0 context switch (to process P) (uses mm_struct of Process P) switch_mm_irqs_off() switch_slb load_slb++ /* * load_slb becomes 0 here * and we evict an entry from * the preload cache with * preload_age(). We still * keep HW SLB and preload * cache in sync, that is * because all HW SLB entries * anyways gets evicted in * switch_slb during SLBIA. * We then only add those * entries back in HW SLB, * which are currently * present in preload_cache * (after eviction). */ load_elf_binary continues... setup_new_exec() slb_setup_new_exec() sched_switch event sched_migrate_task migrates process P to cpu-0 context_switch from swapper/0 to Process P switch_mm_irqs_off() /* * Since both prev and next mm struct are same we don't call * switch_mmu_context(). This will cause the HW SLB and SW preload * cache to go out of sync in preload_new_slb_context. Because there * was an SLB entry which was evicted from both HW and preload cache * on cpu-1. Now later in preload_new_slb_context(), when we will try * to add the same preload entry again, we will add this to the SW * preload cache and then will add it to the HW SLB. Since on cpu-0 * this entry was never invalidated, hence adding this entry to the HW * SLB will cause a SLB multi-hit error. */ load_elf_binary cont ---truncated---
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.162-1 | DEBIAN-CVE-2025-71078 |
| Debian:13 | linux | 6.12.69-1 | DEBIAN-CVE-2025-71078 |
| Debian:14 | linux | 6.18.5-1 | DEBIAN-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux | 5.15.0-173.183 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux | 6.8.0-110.110 | UBUNTU-CVE-2025-71078 |
| Ubuntu:25.10 | linux | 6.17.0-22.22 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1103.110 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1052.55 | UBUNTU-CVE-2025-71078 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1012.12 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1012.12~24.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1052.55~22.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1109.118 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1054.60 | UBUNTU-CVE-2025-71078 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1013.13 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1013.13~24.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1059.65~22.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1109.118.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1058.65 | UBUNTU-CVE-2025-71078 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1058.65~22.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1103.112 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1054.57 | UBUNTU-CVE-2025-71078 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1012.12 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1012.12~24.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1054.57~22.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1099.105 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1050.56 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1086.94 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1037.40 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-22.22~24.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-110.110~22.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1097.100 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1051.51 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1051.51~22.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1098.104 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1095.100 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-173.183 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-110.110.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-110.110.1~22.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1098.99 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1051.54 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1018.18 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1051.54~22.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1051.54.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1055.55 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1022.22 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1044.44 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1020.20 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1100.106 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1049.50 | UBUNTU-CVE-2025-71078 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1011.11 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1011.11~24.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1049.50~22.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1097.100 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1052.56 | UBUNTU-CVE-2025-71078 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1013.13 | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1010.11 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:25.10 | linux-riscv | 6.17.0-22.22.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | 6.17.0-22.22.1~24.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-110.110~22.04.1 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-71078 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1028.29 | UBUNTU-CVE-2025-71078 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1067.71 | UBUNTU-CVE-2025-71078 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 5434ae74629af58ad0fc27143a9ea435f7734410 – before 01324c0328181b94cf390bda22ff91c75126ea575434ae74629af58ad0fc27143a9ea435f7734410 – before 2e9a95d60f1df7b57618fd5ef057aef331575bd25434ae74629af58ad0fc27143a9ea435f7734410 – before c9f865022a1823d814032a09906e91e4701a35fc5434ae74629af58ad0fc27143a9ea435f7734410 – before b13a3dbfa196af68eae2031f209743735ad416bf5434ae74629af58ad0fc27143a9ea435f7734410 – before 895123c309a34d2cfccf7812b41e17261a3a6f375434ae74629af58ad0fc27143a9ea435f7734410 – before 4ae1e46d8a290319f33f71a2710a1382ba5431e85434ae74629af58ad0fc27143a9ea435f7734410 – before 00312419f0863964625d6dcda8183f96849412c6 |
| Linux | Linux | 4.20 |
Weakness: CWE-362 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
References
- https://git.kernel.org/stable/c/01324c0328181b94cf390bda22ff91c75126ea57
- https://git.kernel.org/stable/c/2e9a95d60f1df7b57618fd5ef057aef331575bd2
- https://git.kernel.org/stable/c/c9f865022a1823d814032a09906e91e4701a35fc
- https://git.kernel.org/stable/c/b13a3dbfa196af68eae2031f209743735ad416bf
- https://git.kernel.org/stable/c/895123c309a34d2cfccf7812b41e17261a3a6f37
- https://git.kernel.org/stable/c/4ae1e46d8a290319f33f71a2710a1382ba5431e8
- https://git.kernel.org/stable/c/00312419f0863964625d6dcda8183f96849412c6