LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71078: powerpc/64s/slb: Fix SLB multihit issue during SLB preload

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---

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel flaw can leave stale memory-translation entries on 64-bit PowerPC systems using the hash MMU. Under specific process migration and context-switch conditions, reloading an entry may cause an SLB multi-hit error. The supplied CVSS score is 7.8, indicating potentially serious confidentiality, integrity, and availability impact from a local, low-privileged context.

Executive priority

Prioritize verification and patching for affected PowerPC hash-MMU systems, especially those running untrusted local workloads. Broad emergency action across non-PowerPC fleets is unsupported. Because no active exploitation is documented, use accelerated risk-based remediation rather than treating this as a confirmed active incident.

Technical view

The hardware Segment Lookaside Buffer and software SLB preload cache can become inconsistent when a process migrates between CPUs and switch_mmu_context() is skipped because adjacent tasks share an mm_struct. A later preload may duplicate a stale hardware entry and trigger an SLB multi-hit. The cited Linux stable commits correct this behavior.

Likely exposure

Exposure is limited to Linux on 64-bit PowerPC systems using the hash MMU. Other architectures and PowerPC systems not using this MMU mode are not identified as affected. The supplied version data is ambiguous, so exact exposure requires matching deployed kernels against vendor advisories and the cited stable fixes.

Exploitation context

The CVSS vector describes local access, low privileges, low complexity, and no user interaction. The bundle does not provide evidence of public exploitation, a proof of concept, or inclusion in CISA KEV; KEV is explicitly false. Treat exploitability beyond the described race-like scheduling conditions as unconfirmed.

Researcher notes

The affected-version list appears insufficient for reliable range interpretation and includes repeated commit-like values. The description establishes the faulty state transition and cited stable fixes, but supplies no CWE, exploit demonstration, or observed attack evidence. Researchers should verify branch-specific fix inclusion without assuming every listed numeric version has identical status.

Mitigation direction

  • Identify 64-bit PowerPC Linux systems configured to use the hash MMU.
  • Apply a vendor-supported kernel containing the applicable cited Linux stable fix.
  • Prioritize multi-user or otherwise untrusted-workload systems where local users can execute processes.
  • If patching is delayed, check Linux or distribution guidance for supported temporary mitigations.

Validation and detection

  • Record kernel versions, architecture, MMU mode, and distribution package revisions.
  • Compare kernel sources or vendor package changelogs with the cited stable commits.
  • Confirm updated systems boot the intended patched kernel after maintenance.
  • Monitor kernel logs for SLB multi-hit errors before and after remediation.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71078 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
8Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-71078Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5434ae74629af58ad0fc27143a9ea435f7734410, 5434ae74629af58ad0fc27143a9ea435f7734410, 5434ae74629af58ad0fc27143a9ea435f7734410, 5434ae74629af58ad0fc27143a9ea435f7734410, 5434ae74629af58ad0fc27143a9ea435f7734410, 5434ae74629af58ad0fc27143a9ea435f7734410, 5434ae74629af58ad0fc27143a9ea435f7734410unaffected
LinuxLinux4.20, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.