# CVE-2026-74674: linux: In the Linux kernel, the following vulnerability has been resolved:  mm: fix incorrect flush address in direct page t...

CVE-2026-74674 is fixed in linux on 1 platform by DEBIAN-CVE-2026-74674 (version 7.1.9-1), released September 4, 2026. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2026-74674
- Priority: High
- CVSS: 7.8 (high)
- EPSS: 0.0012
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Aug 22, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  mm: fix incorrect flush address in direct page table reclaim  When zap_pte_range reclaims a page table, it does:      pte_free_tlb(tlb, pmd_pgtable(pmdval), addr);  and this is unconditionally wrong: if this code executes, addr *always* points one past the end of the range covered by the table.  The addr parameter is used to flush the TLB (really the paging-structure-cache) to drop references to the to-be-freed table, and any architecture that cares about the parameter will flush the wrong address.  (But they'll still free the correct page).  I think it's worth contemplating why the kernel works at all.  If we hit the offending line of code, we will first clear the PMD entry (line 1954, zap_empty_pte_table), then we will issue pending flushes if force_flush is set (tlb_flush_mmu_tlbonly(tlb)), then we will skip the retry on line 1979 (phew!), and then we will do the offending pte_free_tlb call.  *Or* we will clear the PMD entry immediately before pte_free_tlb (line 1983, zap_pte_table_if_empty).  If we have any pending flushes (i.e. we actually zapped any last-level entries) at the time we clear the PMD entry, then the flush really ought to flush all references to the table (Linus certainly seems to think it will on all architectures [0]).  The condition under which we have no accumulated flushes at the time of the clear is very complex (the whole zap_pte_range function has absurdly complex control flow).  If we do hit the bad case, then we will end up clearing the PMD entry after the last time the range is flushed, and any CPU is free to cache a reference to the (empty) page table.  If this happens due to an ordinary read or write, it would segfault, so it would be rare.  But the cache could be speculatively filled as well.  Then we'll flush the wrong address and then free and possibly reuse the table.  On x86, even flushing the wrong address works on non-KPTI Intel systems because INVLPG flushes *all* paging-structure-caches, not just the ones for the target address.  But INVPCID does not, and flush_tlb_one_user will use INVPCID if it's available.  And then we're toast.  AMD systems are more susceptible: we set the EFER.TCE bit, which makes even INVLPG only flush the target address.  I think this might fix an issue in ripgrep reported here: https://github.com/BurntSushi/ripgrep/issues/3494  [0] https://lore.kernel.org/all/CA+55aFzBggoXtNXQeng5d_mRoDnaMBE5Y+URs+PHR67nUpMtaw@mail.gmail.com/T/#u

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 14 | 7.1.9-1 | [DEBIAN-CVE-2026-74674](https://patchblox.com/security/data/fix/linux/debian-cve-2026-74674.md) | Sep 4, 2026 |

---

Data as of 2026-11-08T19:12:23Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.