cve.bz

CVE-2025-71078 linux linux kernel: Race Condition

7.8 highEPSS 0.1%Fix available

High (7.8) in linux linux kernel. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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---

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-71078 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-71078?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-71078?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-71078 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-71078

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-71078](https://cve.bz/cve/badge/CVE-2025-71078.svg)](https://cve.bz/cve/CVE-2025-71078)

HTML:

<a href="https://cve.bz/cve/CVE-2025-71078"><img src="https://cve.bz/cve/badge/CVE-2025-71078.svg" alt="CVE-2025-71078"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux4.20 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.248
Linux5.155.15.198
Linux6.16.1.160
Linux6.66.6.120
Linux6.126.12.64
Linux6.186.18.4
Linuxlater releases6.19

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11linux-6.16.1.162-1~deb11u1DLA-4476-1
Debian12linux6.1.162-1DEBIAN-CVE-2025-71078 DSA-6127-1
Debian13linux6.12.69-1DEBIAN-CVE-2025-71078 DSA-6126-1
Debian14linux6.18.5-1DEBIAN-CVE-2025-71078
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-71078
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-71078
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-71078
Ubuntu22.04:LTSlinux, linux-lowlatency5.15.0-173.183UBUNTU-CVE-2025-71078 USN-8096-1
Ubuntu22.04:LTSlinux-aws5.15.0-1103.110UBUNTU-CVE-2025-71078 USN-8096-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-71078 USN-8179-1
Ubuntu22.04:LTSlinux-azure5.15.0-1109.118UBUNTU-CVE-2025-71078 USN-8163-2
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1059.65~22.04.1UBUNTU-CVE-2025-71078 USN-8440-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1109.118.1UBUNTU-CVE-2025-71078
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-71078
Ubuntu22.04:LTSlinux-gcp5.15.0-1103.112UBUNTU-CVE-2025-71078 USN-8096-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1054.57~22.04.1UBUNTU-CVE-2025-71078 USN-8179-4
76 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6kernel-default6.4.0-150600.23.87.1SUSE-SU-2026:0471-1
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.31.1SUSE-SU-2026:0447-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.26.1SUSE-SU-2026:20615-1
SUSELinux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_201-150600.13.3.1SUSE-SU-2026:0471-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_91-150700.1.3.2SUSE-SU-2026:0587-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_91-150700.15.3.1SUSE-SU-2026:0447-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.31.1SUSE-SU-2026:0447-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.31.1.150700.17.21.1SUSE-SU-2026:0447-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.31.1SUSE-SU-2026:0447-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure, kernel-syms-azure, kernel-source-azure6.4.0-150700.20.27.1SUSE-SU-2026:0472-1
SUSELinux Enterprise Server 15 SP6-LTSSkernel-64kb, kernel-docs, kernel-syms and 4 more6.4.0-150600.23.87.1SUSE-SU-2026:0471-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6kernel-default-base6.4.0-150600.23.87.1.150600.12.40.1SUSE-SU-2026:0471-1
14 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 15.6dtb-aarch64, kernel-64kb, kernel-docs and 8 more6.4.0-150600.23.87.1SUSE-SU-2026:0471-1
openSUSELeap 15.6kernel-default-base6.4.0-150600.23.87.1.150600.12.40.1SUSE-SU-2026:0471-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.26.1.160000.2.7openSUSE-SU-2026:20287-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.26.1openSUSE-SU-2026:20287-1
Azure Linux3kernel6.6.121.1-1AZL-74309
Alpaquita23linux-lts6.1.161-r0BELL-CVE-2025-71078
Alpaquita25linux-lts6.12.65-r0BELL-CVE-2025-71078
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-71078

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This vulnerability affects PowerPC 64-bit systems using the hash MMU (not radix). The race requires specific process migration patterns across CPUs during context switches. When triggered, the SLB multi-hit error causes a machine check exception that typically results in system crash. The issue is specific to PowerPC server hardware.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-71078.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON