CVE-2025-37964x86/mm: Eliminate window where TLB flushes may be inadvertently skipped
- 7.8HighCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 34 days later
· 34 days later
Published
- 18 months later
· 18 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 848b5815177582de0e1d0118725378e0fbadca20 – < 12f703811af043d32b1c8a30001b2fa04d5cd0ac
- affected b47002ed65ade940839b7f439ff4a194e7d5ec28 – < 02ad4ce144bd27f71f583f667fdf3b3ba0753477
- affected a04fe3bfc71e28009e20357b79df1e8ef7c9d600 – < d41072906abec8bb8e01ed16afefbaa558908c89
- affected 3dbe889a1b829b4c07e0836ff853fe649e51ce4f – < d87392094f96e162fa5fa5a8640d70cc0952806f
- affected 6db2526c1d694c91c6e05e2f186c085e9460f202 – < 399ec9ca8fc4999e676ff89a90184ec40031cf59
- affected 6db2526c1d694c91c6e05e2f186c085e9460f202 – < fea4e317f9e7e1f449ce90dedc27a2d2a95bee5a
- affected d1347977661342cb09a304a17701eb2d4aa21dec
- affected 5.15.179 – < 5.15.183
- affected 6.1.129 – < 6.1.139
- affected 6.6.79 – < 6.6.91
- affected 6.12.16 – < 6.12.29
- affected 6.13.4 – < 6.14
- affected 6.14
- unaffected < 6.14
- unaffected 5.15.183 – ≤ 5.15.*
- unaffected 6.1.139 – ≤ 6.1.*
- unaffected 6.6.91 – ≤ 6.6.*
- unaffected 6.12.29 – ≤ 6.12.*
- unaffected 6.14.7 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References9
- https://git.kernel.org/stable/c/12f703811af043d32b1c8a30001b2fa04d5cd0ac (opens in a new tab)
- https://git.kernel.org/stable/c/02ad4ce144bd27f71f583f667fdf3b3ba0753477 (opens in a new tab)
- https://git.kernel.org/stable/c/d41072906abec8bb8e01ed16afefbaa558908c89 (opens in a new tab)
- https://git.kernel.org/stable/c/d87392094f96e162fa5fa5a8640d70cc0952806f (opens in a new tab)
- https://git.kernel.org/stable/c/399ec9ca8fc4999e676ff89a90184ec40031cf59 (opens in a new tab)
- https://git.kernel.org/stable/c/fea4e317f9e7e1f449ce90dedc27a2d2a95bee5a (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-15884 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-37964)Record last updated .