CVE-2026-43303
Essential information
- Published
- 08/05/2026 14:16
- Modified
- 08/05/2026 14:16
- Author
- —
- Creator
- —
- CVSS
- 7.8 HIGH (v3.1)
- CISA KEV
- No
- CWE
- CWE-416
- CVSS vector
-
—
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H—
CVSS metrics
- Access vector
- —
- Access complexity
- —
- Authentication
- —
- Confidentiality impact
- —
- Integrity impact
- —
- Availability impact
- —
- Exploitability
- —
- Remediation level
- —
- Report confidence
- —
- Temporal score
- —
- Attack vector
- LOCAL
- Attack complexity
- LOW
- Privileges required
- LOW
- User interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality impact
- HIGH
- Integrity impact
- HIGH
- Availability impact
- HIGH
- Exploit code maturity
- —
- Remediation level
- —
- Report confidence
- —
- Temporal score
- —
- Attack vector
- —
- Attack complexity
- —
- Attack requirements
- —
- Privileges required
- —
- User interaction
- —
- Confidentiality (V)
- —
- Confidentiality (S)
- —
- Integrity (V)
- —
- Integrity (S)
- —
- Availability (V)
- —
- Availability (S)
- —
- Exploit maturity
- —
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.
NVD status
- Status
- Modified — CVE has been recently published to the CVE List and has been received by the NVD.
- Source
- nist-nvd-api
- NVD
- View on NVD
Affected products (CPE)
| Product | CPE |
|---|---|
| linux / linux kernel | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux / linux kernel | cpe:2.3:o:linux:linux_kernel:5.18:-:*:*:*:*:*:* |
| linux / linux kernel | cpe:2.3:o:linux:linux_kernel:5.18:rc4:*:*:*:*:*:* |
| linux / linux kernel | cpe:2.3:o:linux:linux_kernel:5.18:rc5:*:*:*:*:*:* |
| linux / linux kernel | cpe:2.3:o:linux:linux_kernel:5.18:rc6:*:*:*:*:*:* |
| linux / linux kernel | cpe:2.3:o:linux:linux_kernel:5.18:rc7:*:*:*:*:*:* |
| linux / linux kernel | cpe:2.3:o:linux:linux_kernel:5.18:rc9:*:*:*:*:*:* |