Answer in brief
CVE-2026-43303 records a High severity (CVSS 7.8) vulnerability in mm/page_alloc: clear page->private in free_pages_prepare(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-43303 records a High severity (CVSS 7.8) vulnerability in mm/page_alloc: clear page->private in free_pages_prepare(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3b8000ae185cb068adbda5f966a3835053c85fd4 <e7790ab165713b79b1617ce659742ceb3a859d05 || >=3b8000ae185cb068adbda5f966a3835053c85fd4 <3edb8ebbf79b9016040e8f3421d723ae3d542b32 || >=3b8000ae185cb068adbda5f966a3835053c85fd4 <f9719e32a67b4b00b3c9b133e8b5ffa72a26b67b || >=3b8000ae185cb068adbda5f966a3835053c85fd4 <23b82b7a26182ad840ae67d390d7ec9771e8c00f || >=3b8000ae185cb068adbda5f966a3835053c85fd4 <d757c793853ec5483eb41ec2942c300b8fa720fb || >=3b8000ae185cb068adbda5f966a3835053c85fd4 <ac1ea219590c09572ed5992dc233bbf7bb70fef9 | e7790ab165713b79b1617ce659742ceb3a859d05, 3edb8ebbf79b9016040e8f3421d723ae3d542b32, f9719e32a67b4b00b3c9b133e8b5ffa72a26b67b, 23b82b7a26182ad840ae67d390d7ec9771e8c00f, d757c793853ec5483eb41ec2942c300b8fa720fb, ac1ea219590c09572ed5992dc233bbf7bb70fef9 |
| Linux/Linuxgeneric | 5.18 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3b8000ae185cb068adbda5f966a3835053c85fd4 <e7790ab165713b79b1617ce659742ceb3a859d05 || >=3b8000ae185cb068adbda5f966a3835053c85fd4 <3edb8ebbf79b9016040e8f3421d723ae3d542b32 || >=3b8000ae185cb068adbda5f966a3835053c85fd4 <f9719e32a67b4b00b3c9b133e8b5ffa72a26b67b || >=3b8000ae185cb068adbda5f966a3835053c85fd4 <23b82b7a26182ad840ae67d390d7ec9771e8c00f || >=3b8000ae185cb068adbda5f966a3835053c85fd4 <d757c793853ec5483eb41ec2942c300b8fa720fb || >=3b8000ae185cb068adbda5f966a3835053c85fd4 <ac1ea219590c09572ed5992dc233bbf7bb70fef9 | e7790ab165713b79b1617ce659742ceb3a859d05, 3edb8ebbf79b9016040e8f3421d723ae3d542b32, f9719e32a67b4b00b3c9b133e8b5ffa72a26b67b, 23b82b7a26182ad840ae67d390d7ec9771e8c00f, d757c793853ec5483eb41ec2942c300b8fa720fb, ac1ea219590c09572ed5992dc233bbf7bb70fef9 |
| Linux/Linuxgeneric | 5.18 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.