Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 23b82b7a26182ad840ae67d390d7ec9771e8c00f, 3edb8ebbf79b9016040e8f3421d723ae3d542b32, ac1ea219590c09572ed5992dc233bbf7bb70fef9.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 23b82b7a26182ad840ae67d390d7ec9771e8c00f, 3edb8ebbf79b9016040e8f3421d723ae3d542b32, ac1ea219590c09572ed5992dc233bbf7bb70fef9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
May 8, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43303

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.18affected
    • 3b8000ae185cb068adbda5f966a3835053c85fd4 and later · before e7790ab165713b79b1617ce659742ceb3a859d05affected · git
    • 3b8000ae185cb068adbda5f966a3835053c85fd4 and later · before 3edb8ebbf79b9016040e8f3421d723ae3d542b32affected · git
    • 3b8000ae185cb068adbda5f966a3835053c85fd4 and later · before f9719e32a67b4b00b3c9b133e8b5ffa72a26b67baffected · git
    • 3b8000ae185cb068adbda5f966a3835053c85fd4 and later · before 23b82b7a26182ad840ae67d390d7ec9771e8c00faffected · git
    • 3b8000ae185cb068adbda5f966a3835053c85fd4 and later · before d757c793853ec5483eb41ec2942c300b8fa720fbaffected · git
    • 3b8000ae185cb068adbda5f966a3835053c85fd4 and later · before ac1ea219590c09572ed5992dc233bbf7bb70fef9affected · git
    • before 5.18not affected · semver
    • 6.1.176 and later · up to and including 6.1.*not affected · semver
    • 6.6.143 and later · up to and including 6.6.*not affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.18.1 and later · before 6.18.16
  • linux linux kernel6.19 and later · before 6.19.6
  • linux linux kernel5.18

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43301May 8, 2026 · media: chips-media: wave5: Fix PM runtime usage count underflow
    22Monitor
  • ← EarlierCVE-2026-43302May 8, 2026 · drm/v3d: Set DMA segment size to avoid debug warnings
    22Monitor
  • Later →CVE-2026-43304May 8, 2026 · libceph: define and enforce CEPH_MAX_KEY_LEN
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux23b82b7a26182ad840ae67d390d7ec9771e8c00fVendor (CNA)
Linux Linux3edb8ebbf79b9016040e8f3421d723ae3d542b32Vendor (CNA)
Linux Linuxac1ea219590c09572ed5992dc233bbf7bb70fef9Vendor (CNA)
Linux Linuxd757c793853ec5483eb41ec2942c300b8fa720fbVendor (CNA)
Linux Linuxe7790ab165713b79b1617ce659742ceb3a859d05Vendor (CNA)
Linux Linuxf9719e32a67b4b00b3c9b133e8b5ffa72a26b67bVendor (CNA)
almalinux:kernel5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+2

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records