{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-74674","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-08-15T05:44:03.925Z","datePublished":"2026-08-22T15:32:43.670Z","dateUpdated":"2026-08-25T05:41:26.569Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-25T05:41:26.569Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm: fix incorrect flush address in direct page table reclaim\n\nWhen zap_pte_range reclaims a page table, it does:\n\n    pte_free_tlb(tlb, pmd_pgtable(pmdval), addr);\n\nand this is unconditionally wrong: if this code executes, addr *always*\npoints one past the end of the range covered by the table.  The addr\nparameter is used to flush the TLB (really the paging-structure-cache)\nto drop references to the to-be-freed table, and any architecture that\ncares about the parameter will flush the wrong address.  (But they'll\nstill free the correct page).\n\nI think it's worth contemplating why the kernel works at all.\n\nIf we hit the offending line of code, we will first clear the PMD entry\n(line 1954, zap_empty_pte_table), then we will issue pending flushes if\nforce_flush is set (tlb_flush_mmu_tlbonly(tlb)), then we will skip the\nretry on line 1979 (phew!), and then we will do the offending\npte_free_tlb call.  *Or* we will clear the PMD entry immediately before\npte_free_tlb (line 1983, zap_pte_table_if_empty).\n\nIf we have any pending flushes (i.e. we actually zapped any last-level\nentries) at the time we clear the PMD entry, then the flush really ought\nto flush all references to the table (Linus certainly seems to think it\nwill on all architectures [0]).\n\nThe condition under which we have no accumulated flushes at the time of\nthe clear is very complex (the whole zap_pte_range function has absurdly\ncomplex control flow).  If we do hit the bad case, then we will end up\nclearing the PMD entry after the last time the range is flushed, and any\nCPU is free to cache a reference to the (empty) page table.  If this\nhappens due to an ordinary read or write, it would segfault, so it would\nbe rare.  But the cache could be speculatively filled as well.  Then\nwe'll flush the wrong address and then free and possibly reuse the\ntable.\n\nOn x86, even flushing the wrong address works on non-KPTI Intel systems\nbecause INVLPG flushes *all* paging-structure-caches, not just the ones\nfor the target address.  But INVPCID does not, and flush_tlb_one_user\nwill use INVPCID if it's available.  And then we're toast.  AMD systems\nare more susceptible: we set the EFER.TCE bit, which makes even INVLPG\nonly flush the target address.\n\nI think this might fix an issue in ripgrep reported here:\nhttps://github.com/BurntSushi/ripgrep/issues/3494\n\n[0] https://lore.kernel.org/all/CA+55aFzBggoXtNXQeng5d_mRoDnaMBE5Y+URs+PHR67nUpMtaw@mail.gmail.com/T/#u"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The bug is only reachable via local memory-management syscalls—primarily madvise(MADV_DONTNEED) on anonymous mappings—that drive zap_pte_range() page-table reclaim; there is no network, adjacent-radio, or physical-device path to this code.\nAC:L - An unprivileged attacker can repeatedly mmap and madvise(DONTNEED) 2MB+ anonymous regions and run concurrent memory pressure (as in the ripgrep repro) to hit the faulty pte_free_tlb() flush; attacker-controlled syscalls and threading make triggering the bad case feasible rather than dependent on uncontrollable system state.\nPR:L - Exploitation requires only a local unprivileged user manipulating their own address space through standard madvise/mmap syscalls; no root, capabilities beyond normal UID, or authentication is needed, and this works within user namespaces on the caller's mm.\nUI:N - No victim interaction is required; the attacker directly issues the syscalls and memory-access patterns that cause incorrect paging-structure-cache flushes during PTE page reclaim.\nS:U - Impact is stale paging-structure-cache entries and corrupted virtual-to-physical translations within the attacker's process and kernel MM subsystem—standard local memory corruption, not a VM escape, IOMMU bypass, or cross-authority sandbox breakout.\nC:H - Flushing the wrong address leaves CPUs with cached references to freed PTE pages; once reused, stale translations can map unrelated physical pages into the attacker's address space, giving arbitrary read primitives and information disclosure consistent with use-after-free severity.\nI:H - Freed page-table pages can be reallocated while stale paging-structure caches still reference them, enabling wrong virtual-to-physical mappings and demonstrated user-space memory corruption (ripgrep/musl heap corruption), exploitable for arbitrary writes and control-flow hijacking.\nA:H - Stale TLB/paging-structure-cache entries after incorrect flushes cause user-space SIGSEGV (demonstrated in ripgrep on Linux 7.0) and can destabilize or crash affected workloads; memory-corruption class bugs in the MM path carry high availability impact even when not fully weaponized."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["mm/memory.c"],"versions":[{"version":"4c640eb4181cf8de74c8b9e7c9cf16bf8d26b73e","lessThan":"0b8ff21cbda8808c86b18f1b0ca2d0025af9a80a","status":"affected","versionType":"git"},{"version":"4c640eb4181cf8de74c8b9e7c9cf16bf8d26b73e","lessThan":"478a1c3abebfc717db0d1281a9cdd7befafee542","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["mm/memory.c"],"versions":[{"version":"7.0","status":"affected"},{"version":"0","lessThan":"7.0","status":"unaffected","versionType":"semver"},{"version":"7.1.9","lessThanOrEqual":"7.1.*","status":"unaffected","versionType":"semver"},{"version":"7.2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"7.0","versionEndExcluding":"7.1.9"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"7.0","versionEndExcluding":"7.2"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/0b8ff21cbda8808c86b18f1b0ca2d0025af9a80a"},{"url":"https://git.kernel.org/stable/c/478a1c3abebfc717db0d1281a9cdd7befafee542"}],"title":"mm: fix incorrect flush address in direct page table reclaim","x_generator":{"engine":"bippy-1.2.0"}}}}