mm/page_alloc: clear page->private in free_pages_prepare()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3b8000ae185cb068adbda5f966a3835053c85fd4 · < ac1ea219590c09572ed5992dc233bbf7bb70fef9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mm/page_alloc: clear page->private in free_pages_prepare()
Several subsystems (slub, shmem, ttm, etc.) use page->private but don't clear it before freeing pages. When these pages are later allocated as high-order pages and split via split_page(), tail pages retain stale page->private values.
This causes a use-after-free in the swap subsystem. The swap code uses page->private to track swap count continuations, assuming freshly allocated pages have page->private == 0. When stale values are present, swap_count_continued() incorrectly assumes the continuation list is valid and iterates over uninitialized page->lru containing LIST_POISON values, causing a crash:
KASAN: maybe wild-memory-access in range [0xdead000000000100-0xdead000000000107] RIP: 0010:__do_sys_swapoff+0x1151/0x1860
Fix this by clearing page->private in free_pages_prepare(), ensuring all freed pages have clean state regardless of previous use.
From the CVE record · Linux
The Linux kernel can leave stale page->private values on freed pages. If those pages are reused and split, the swap subsystem can encounter a use-after-free and crash during swapoff. The input does not establish how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running Linux kernels should check whether their kernel includes the page allocator fix; affected versions are not specified.