Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43303mm/page_alloc: clear page->private in free_pages_prepare()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43303, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 3b8000ae185cb068adbda5f966a3835053c85fd4 – < e7790ab165713b79b1617ce659742ceb3a859d05
    • affected 3b8000ae185cb068adbda5f966a3835053c85fd4 – < 3edb8ebbf79b9016040e8f3421d723ae3d542b32
    • affected 3b8000ae185cb068adbda5f966a3835053c85fd4 – < f9719e32a67b4b00b3c9b133e8b5ffa72a26b67b
    • affected 3b8000ae185cb068adbda5f966a3835053c85fd4 – < 23b82b7a26182ad840ae67d390d7ec9771e8c00f
    • affected 3b8000ae185cb068adbda5f966a3835053c85fd4 – < d757c793853ec5483eb41ec2942c300b8fa720fb
    • affected 3b8000ae185cb068adbda5f966a3835053c85fd4 – < ac1ea219590c09572ed5992dc233bbf7bb70fef9
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43303 badge
[![CVE-2026-43303](https://cveledger.app/badge/CVE-2026-43303.svg)](https://cveledger.app/cve/CVE-2026-43303)

Record last updated .