CVE-2025-71078powerpc/64s/slb: Fix SLB multihit issue during SLB preload
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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---
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 5434ae74629af58ad0fc27143a9ea435f7734410 builds before 01324c0328181b94cf390bda22ff91c75126ea57; 5434ae74629af58ad0fc27143a9ea435f7734410 builds before 2e9a95d60f1df7b57618fd5ef057aef331575bd2; from 5434ae74629af58ad0fc27143a9ea435f7734410 before c9f865022a1823d814032a09906e91e4701a35fc; from 5434ae74629af58ad0fc27143a9ea435f7734410 before b13a3dbfa196af68eae2031f209743735ad416bf; from 5434ae74629af58ad0fc27143a9ea435f7734410 before 895123c309a34d2cfccf7812b41e17261a3a6f37; 5434ae74629af58ad0fc27143a9ea435f7734410 builds before 4ae1e46d8a290319f33f71a2710a1382ba5431e8; from 5434ae74629af58ad0fc27143a9ea435f7734410 before 00312419f0863964625d6dcda8183f96849412c6 | CNA record |
linux linux_kernel linux:linux_kernel | from 4.20.1 before 5.10.248; from 5.11 before 5.15.198; from 5.16 before 6.1.160; from 6.2 before 6.6.120; from 6.7 before 6.12.64; from 6.13 before 6.18.4; 4.20; 6.19; and 7 more ranges | NVD |
References
- https://git.kernel.org/stable/c/01324c0328181b94cf390bda22ff91c75126ea57patch
- https://git.kernel.org/stable/c/2e9a95d60f1df7b57618fd5ef057aef331575bd2patch
- https://git.kernel.org/stable/c/c9f865022a1823d814032a09906e91e4701a35fcpatch
- https://git.kernel.org/stable/c/b13a3dbfa196af68eae2031f209743735ad416bfpatch
- https://git.kernel.org/stable/c/895123c309a34d2cfccf7812b41e17261a3a6f37patch
- https://git.kernel.org/stable/c/4ae1e46d8a290319f33f71a2710a1382ba5431e8patch
- https://git.kernel.org/stable/c/00312419f0863964625d6dcda8183f96849412c6patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.