mm/page_owner: use memcg_data snapshot to avoid TOCTOU in print_page_owner_memcg()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mm/page_owner: use memcg_data snapshot to avoid TOCTOU in print_page_owner_memcg()
print_page_owner_memcg() reads page->memcg_data via READ_ONCE() at the start to guard against tail pages and NULL data. However, it later re-reads page->memcg_data locklessly in two places:
1: page_memcg_check(page)
2: PageMemcgKmem(page) (via folio_memcg_kmem(), which includes VM_BUG_ON assertions for tail pages and MEMCG_DATA_OBJEXTS)
If the page is concurrently freed and reallocated as a THP tail page or slab page between these calls, the VM_BUG_ON assertions can trigger on CONFIG_DEBUG_VM=y builds, crashing the kernel.
Fix both TOCTOU issues by using the memcg_data snapshot throughout.
From the CVE record · Linux
The Linux kernel's print_page_owner_memcg() can reread page metadata after it changes. If a page is concurrently freed and reallocated as a THP tail page or slab page, assertions on CONFIG_DEBUG_VM=y builds can crash the kernel. The input does not establish whether an attacker can trigger this remotely or locally, or whether authentication or user interaction is needed.
Engineers running Linux kernels with CONFIG_DEBUG_VM=y should check their builds; affected versions were not provided.