CVE-2026-43303 Details
Description
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.
A vulnerability in the Linux kernel's memory management can lead to a use-after-free condition in the swap subsystem. This issue arises because several subsystems, including slub, shmem, and ttm, use the page->private field but fail to clear it before freeing pages. When these pages are later allocated as high-order pages and split, the tail pages can retain stale private values. The swap subsystem relies on page->private to track swap count continuations, expecting freshly allocated pages to have a private value of zero. The presence of stale values can cause the swap_count_continued() function to incorrectly validate continuation lists, leading to iterations over uninitialized page lists containing invalid data, which can cause a system crash.
The vulnerability has been addressed by modifying the free_pages_prepare() function to clear the page->private field before pages are freed. This change ensures that all freed pages have a clean state, regardless of how they were previously used. Users should upgrade to the latest version of the Linux kernel where this fix has been applied.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Oct 16, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
| CWE-457 | Use of Uninitialized Variable | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.18.1, < 6.18.16 >= 6.19, < 6.19.6 5.18 - 5.18 rc4 5.18 rc5 5.18 rc6 5.18 rc7 5.18 rc9 |
CPE
Remediation
| |
Change History
13 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 11, 2026 | CVE Translated | [email protected] |
| Nov 10, 2026 | CVE Modified | siemens-SADP |
| Oct 19, 2026 | CVE Modified | CISA-ADP |
| Oct 16, 2026 | CVE Modified | CISA-ADP |
| Oct 15, 2026 | CVE Modified | siemens-SADP |
| Sep 8, 2026 | CVE Modified | kernel.org |
| Sep 8, 2026 | CVE Modified | siemens-SADP |
| Jun 19, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 9, 2026 | CVE Modified | kernel.org |
| May 15, 2026 | Initial Analysis | [email protected] |
| May 11, 2026 | CVE Modified | kernel.org |
| May 8, 2026 | New CVE Received | kernel.org |