cve.bz

CVE-2025-37964

5.5 mediumEPSS 0.2%Fix available

Medium (5.5). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Eliminate window where TLB flushes may be inadvertently skipped tl;dr: There is a window in the mm switching code where the new CR3 is set and the CPU should be getting TLB flushes for the new mm. But should_flush_tlb() has a bug and suppresses the flush. Fix it by widening the window where should_flush_tlb() sends an IPI. Long Version: === History === There were a few things leading up to this. First, updating mm_cpumask() was observed to be too expensive, so it was made lazier. But being lazy caused too many unnecessary IPIs to CPUs due to the now-lazy mm_cpumask(). So code was added to cull mm_cpumask() periodically[2]. But that culling was a bit too aggressive and skipped sending TLB flushes to CPUs that need them. So here we are again. === Problem === The too-aggressive code in should_flush_tlb() strikes in this window: // Turn on IPIs for this CPU/mm combination, but only // if should_flush_tlb() agrees: cpumask_set_cpu(cpu, mm_cpumask(next)); next_tlb_gen = atomic64_read(&next->context.tlb_gen); choose_new_asid(next, next_tlb_gen, &new_asid, &need_flush); load_new_mm_cr3(need_flush); // ^ After 'need_flush' is set to false, IPIs *MUST* // be sent to this CPU and not be ignored. this_cpu_write(cpu_tlbstate.loaded_mm, next); // ^ Not until this point does should_flush_tlb() // become true! should_flush_tlb() will suppress TLB flushes between load_new_mm_cr3() and writing to 'loaded_mm', which is a window where they should not be suppressed. Whoops. === Solution === Thankfully, the fuzzy "just about to write CR3" window is already marked with loaded_mm==LOADED_MM_SWITCHING. Simply checking for that state in should_flush_tlb() is sufficient to ensure that the CPU is targeted with an IPI. This will cause more TLB flush IPIs. But the window is relatively small and I do not expect this to cause any kind of measurable performance impact. Update the comment where LOADED_MM_SWITCHING is written since it grew yet another user. Peter Z also raised a concern that should_flush_tlb() might not observe 'loaded_mm' and 'is_lazy' in the same order that switch_mm_irqs_off() writes them. Add a barrier to ensure that they are observed in the order they are written.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
Assigned by
Linux (CNA)
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-37964 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-37964?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-37964?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-37964 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 5.15.179 before 5.15.183
Linuxfrom 6.1.129 before 6.1.139
Linuxfrom 6.6.79 before 6.6.91
Linuxfrom 6.12.16 before 6.12.29
Linuxfrom 6.13.4 before 6.14
Linux6.14 and later

Fixed in

ProductRelease lineFixed in
Linux5.155.15.183
Linux6.16.1.139
Linux6.66.6.91
Linux6.126.12.29
Linux6.146.14.7
Linuxlater releases6.15

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11linux-6.16.1.140-1~deb11u1DLA-4271-1
Debian12linux6.1.140-1DEBIAN-CVE-2025-37964 DSA-5925-1
Debian13, 14linux6.12.29-1DEBIAN-CVE-2025-37964
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-37964
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-37964
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-37964
Ubuntu22.04:LTSlinux, linux-lowlatency5.15.0-144.157UBUNTU-CVE-2025-37964 USN-7654-1
Ubuntu22.04:LTSlinux-aws5.15.0-1088.95UBUNTU-CVE-2025-37964 USN-7654-1
Ubuntu22.04:LTSlinux-azure5.15.0-1094.103UBUNTU-CVE-2025-37964 USN-7711-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1094.103.1UBUNTU-CVE-2025-37964
Ubuntu22.04:LTSlinux-gcp5.15.0-1087.96UBUNTU-CVE-2025-37964 USN-7654-1
Ubuntu22.04:LTSlinux-gke, linux-oracle5.15.0-1085.91UBUNTU-CVE-2025-37964 USN-7654-1
Ubuntu22.04:LTSlinux-gkeop5.15.0-1070.78UBUNTU-CVE-2025-37964 USN-7654-1
Ubuntu22.04:LTSlinux-ibm5.15.0-1080.83UBUNTU-CVE-2025-37964 USN-7654-1
Ubuntu22.04:LTSlinux-intel-iotg5.15.0-1083.89UBUNTU-CVE-2025-37964 USN-7654-1
32 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquita23linux-lts6.1.140-r0BELL-CVE-2025-37964
Alpaquita25linux-lts6.12.41-r0BELL-CVE-2025-37964
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-37964

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

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because exploitation requires local access and precise race-condition timing during process context switching, primarily resulting in system instability or a denial of service. The issue is confined to x86 multi-processor architectures where inter-processor interrupts for memory translation invalidations could be briefly suppressed. The strict timing window and prerequisite local execution conditions significantly restrict practical exploitability on enterprise systems.

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

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

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-295-11Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP2026-10-13Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and FacilitiesSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.7, SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.7, SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.7 and 2 morenone listed
ICSA-26-209-04Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP2026-07-14Critical ManufacturingSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6, SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6, SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6 and 2 morenone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

References

Check your stackJSON