CVE-2025-71078: powerpc/64s/slb: Fix SLB multihit issue during SLB preload
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 00312419f0863964625d6dcda8183f96849412c6, 01324c0328181b94cf390bda22ff91c75126ea57, 2e9a95d60f1df7b57618fd5ef057aef331575bd2; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.
Low priority for now. Upgrade to Linux Linux 00312419f0863964625d6dcda8183f96849412c6, 01324c0328181b94cf390bda22ff91c75126ea57, 2e9a95d60f1df7b57618fd5ef057aef331575bd2; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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---
- Published
- Jan 13, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-362
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.20affected
- 5434ae74629af58ad0fc27143a9ea435f7734410 and later · before 01324c0328181b94cf390bda22ff91c75126ea57affected · git
- 5434ae74629af58ad0fc27143a9ea435f7734410 and later · before 2e9a95d60f1df7b57618fd5ef057aef331575bd2affected · git
- 5434ae74629af58ad0fc27143a9ea435f7734410 and later · before c9f865022a1823d814032a09906e91e4701a35fcaffected · git
- 5434ae74629af58ad0fc27143a9ea435f7734410 and later · before b13a3dbfa196af68eae2031f209743735ad416bfaffected · git
- 5434ae74629af58ad0fc27143a9ea435f7734410 and later · before 895123c309a34d2cfccf7812b41e17261a3a6f37affected · git
- 5434ae74629af58ad0fc27143a9ea435f7734410 and later · before 4ae1e46d8a290319f33f71a2710a1382ba5431e8affected · git
- 5434ae74629af58ad0fc27143a9ea435f7734410 and later · before 00312419f0863964625d6dcda8183f96849412c6affected · git
- before 4.20not affected · semver
- 5.10.248 and later · up to and including 5.10.*not affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.20.1 and later · before 5.10.248
- linux linux kernel5.11 and later · before 5.15.198
- linux linux kernel5.16 and later · before 6.1.160
- linux linux kernel6.2 and later · before 6.6.120
- linux linux kernel6.7 and later · before 6.12.64
- linux linux kernel6.13 and later · before 6.18.4
- linux linux kernel4.20
- linux linux kernel6.19
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.5-1 | 6.18.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-71076Jan 13, 2026 · drm/xe/oa: Limit num_syncs to prevent oversized allocations22Monitor
- ← EarlierCVE-2025-71077Jan 13, 2026 · tpm: Cap the number of PCR banks22Monitor
- Later →CVE-2025-71079Jan 13, 2026 · net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 00312419f0863964625d6dcda8183f96849412c6 | Vendor (CNA) |
| Linux Linux | 01324c0328181b94cf390bda22ff91c75126ea57 | Vendor (CNA) |
| Linux Linux | 2e9a95d60f1df7b57618fd5ef057aef331575bd2 | Vendor (CNA) |
| Linux Linux | 4ae1e46d8a290319f33f71a2710a1382ba5431e8 | Vendor (CNA) |
| Linux Linux | 895123c309a34d2cfccf7812b41e17261a3a6f37 | Vendor (CNA) |
| Linux Linux | b13a3dbfa196af68eae2031f209743735ad416bf | Vendor (CNA) |
| Linux Linux | c9f865022a1823d814032a09906e91e4701a35fc | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/01324c0328181b94cf390bda22ff91c75126ea57
- git.kernel.org/stable/c/2e9a95d60f1df7b57618fd5ef057aef331575bd2
- git.kernel.org/stable/c/4ae1e46d8a290319f33f71a2710a1382ba5431e8
- git.kernel.org/stable/c/895123c309a34d2cfccf7812b41e17261a3a6f37
- git.kernel.org/stable/c/b13a3dbfa196af68eae2031f209743735ad416bf
- git.kernel.org/stable/c/c9f865022a1823d814032a09906e91e4701a35fc
Vendor advisories and official records. Exploit/PoC links are deliberately left out.