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.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.1%top 98.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.162-1DEBIAN-CVE-2025-71078
Debian:13linux6.12.69-1DEBIAN-CVE-2025-71078
Debian:14linux6.18.5-1DEBIAN-CVE-2025-71078
Ubuntu:22.04:LTSlinux5.15.0-173.183UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux6.8.0-110.110UBUNTU-CVE-2025-71078
Ubuntu:25.10linux6.17.0-22.22UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-aws5.15.0-1103.110UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-aws6.8.0-1052.55UBUNTU-CVE-2025-71078
Ubuntu:25.10linux-aws6.17.0-1012.12UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1012.12~24.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-azure5.15.0-1109.118UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-azure6.8.0-1054.60UBUNTU-CVE-2025-71078
Ubuntu:25.10linux-azure6.17.0-1013.13UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1013.13~24.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1059.65~22.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1109.118.1UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1058.65UBUNTU-CVE-2025-71078
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-gcp5.15.0-1103.112UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-gcp6.8.0-1054.57UBUNTU-CVE-2025-71078
Ubuntu:25.10linux-gcp6.17.0-1012.12UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1012.12~24.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1054.57~22.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-gke5.15.0-1099.105UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-gke6.8.0-1050.56UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1086.94UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1037.40UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-22.22~24.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-ibm5.15.0-1097.100UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-ibm6.8.0-1051.51UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1051.51~22.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1098.104UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-kvm5.15.0-1095.100UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-173.183UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-110.110.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-110.110.1~22.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1098.99UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1051.54UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1018.18UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1051.54~22.04.1UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1051.54.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1055.55UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1022.22UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1044.44UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1020.20UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-oracle5.15.0-1100.106UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-oracle6.8.0-1049.50UBUNTU-CVE-2025-71078
Ubuntu:25.10linux-oracle6.17.0-1011.11UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1011.11~24.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1049.50~22.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-raspi5.15.0-1097.100UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-raspi6.8.0-1052.56UBUNTU-CVE-2025-71078
Ubuntu:25.10linux-raspi6.17.0-1013.13UBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-71078
Ubuntu:25.10linux-realtime6.17.0-1010.11UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-71078
Ubuntu:25.10linux-riscv6.17.0-22.22.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-riscv-6.176.17.0-22.22.1~24.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-71078
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1028.29UBUNTU-CVE-2025-71078
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1067.71UBUNTU-CVE-2025-71078

Affected products (as reported)

VendorProductVersions
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