CVE-2026-43303

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

Published

May 8, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated May 11, 2026
Patch available.
generic

mm/page_alloc: clear page->private in free_pages_prepare() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d757c793853ec5483eb41ec2942c300b8fa720fb
generic

mm/page_alloc: clear page->private in free_pages_prepare() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ac1ea219590c09572ed5992dc233bbf7bb70fef9
generic

mm/page_alloc: clear page->private in free_pages_prepare() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23b82b7a26182ad840ae67d390d7ec9771e8c00f

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:6.12.0-55.84.1.el10_02026-06-29redhat
redhatkernel-0:5.14.0-427.132.1.el9_42026-06-22redhat
redhatkernel-0:5.14.0-570.123.1.el9_62026-06-22redhat
redhatkernel-0:5.14.0-284.176.1.el9_22026-06-17redhat
redhatkernel-rt-0:5.14.0-284.176.1.rt14.461.el9_22026-06-17redhat
redhatkernel-0:5.14.0-687.12.1.el9_82026-05-28redhat
redhatkernel-0:6.12.0-211.18.1.el10_22026-05-28redhat
linuxKernel @ 6.1.176 (fixes >=5.18.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (117 versions)
  • every version up to 6.19.6-1: fixed in 6.19.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 265 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-01 19:50 UTCEPSS rescore
  4. 2026-09-30 15:03 UTCEPSS rescore
  5. 2026-09-28 02:02 UTCOSV refresh
  6. 2026-09-27 13:48 UTCEPSS rescore
  7. 2026-09-26 15:58 UTCEPSS rescore
  8. 2026-09-23 17:53 UTCEPSS rescore
  9. 2026-09-20 20:15 UTCEPSS rescore
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-17 19:31 UTCEPSS rescore
  12. 2026-09-16 14:08 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-13 16:47 UTCEPSS rescore
  15. 2026-09-12 15:01 UTCEPSS rescore
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-11 09:37 UTCEPSS rescore
  18. 2026-09-10 09:34 UTCEPSS rescore
  19. 2026-09-08 22:00 UTCEPSS rescore
  20. 2026-09-08 09:46 UTCEG score recompute
  21. 2026-09-08 09:46 UTCVendor advisory
  22. 2026-09-08 09:45 UTCGHSA enrichment
  23. 2026-09-08 09:02 UTCEG score recompute
  24. 2026-09-08 09:02 UTCVendor advisory
  25. 2026-09-08 09:01 UTCGHSA enrichment
Show 75 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-23 19:18 UTCEG score recompute
  13. 2026-08-23 19:18 UTCVendor advisory
  14. 2026-08-23 19:18 UTCGHSA enrichment
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 11:57 UTCEG score recompute
  22. 2026-08-17 11:57 UTCVendor advisory
  23. 2026-08-17 11:56 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 04:38 UTCEG score recompute
  26. 2026-08-16 04:38 UTCVendor advisory
  27. 2026-08-16 04:38 UTCGHSA enrichment
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 15:31 UTCVendor advisory
  31. 2026-08-14 15:31 UTCGHSA enrichment
  32. 2026-08-14 03:13 UTCEG score recompute
  33. 2026-08-14 03:13 UTCVendor advisory
  34. 2026-08-14 03:13 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 06:00 UTCVendor advisory
  37. 2026-08-13 06:00 UTCGHSA enrichment
  38. 2026-08-12 16:49 UTCEG score recompute
  39. 2026-08-12 16:49 UTCVendor advisory
  40. 2026-08-12 16:49 UTCGHSA enrichment
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-11 15:53 UTCEG score recompute
  43. 2026-08-11 15:53 UTCVendor advisory
  44. 2026-08-11 15:53 UTCGHSA enrichment
  45. 2026-08-11 13:43 UTCEPSS rescore
  46. 2026-08-11 01:20 UTCEG score recompute
  47. 2026-08-11 01:20 UTCVendor advisory
  48. 2026-08-11 01:19 UTCGHSA enrichment
  49. 2026-08-11 00:00 UTCEPSS rescore
  50. 2026-08-10 02:59 UTCVendor advisory
  51. 2026-08-10 02:59 UTCGHSA enrichment
  52. 2026-08-09 14:43 UTCEG score recompute
  53. 2026-08-09 14:43 UTCVendor advisory
  54. 2026-08-09 14:43 UTCGHSA enrichment
  55. 2026-08-09 13:46 UTCEPSS rescore
  56. 2026-08-09 02:26 UTCEG score recompute
  57. 2026-08-09 02:26 UTCVendor advisory
  58. 2026-08-09 02:26 UTCGHSA enrichment
  59. 2026-08-08 16:37 UTCEPSS rescore
  60. 2026-08-08 09:23 UTCVendor advisory
  61. 2026-08-08 09:23 UTCGHSA enrichment
  62. 2026-08-07 21:06 UTCEG score recompute
  63. 2026-08-07 21:06 UTCVendor advisory
  64. 2026-08-07 21:06 UTCGHSA enrichment
  65. 2026-08-07 08:49 UTCVendor advisory
  66. 2026-08-07 08:49 UTCGHSA enrichment
  67. 2026-08-06 16:52 UTCEG score recompute
  68. 2026-08-06 16:52 UTCVendor advisory
  69. 2026-08-06 16:52 UTCGHSA enrichment
  70. 2026-08-06 13:46 UTCEPSS rescore
  71. 2026-08-06 02:07 UTCEG score recompute
  72. 2026-08-06 02:07 UTCVendor advisory
  73. 2026-08-06 02:07 UTCGHSA enrichment
  74. 2026-08-05 19:17 UTCEPSS rescore
  75. 2026-08-05 13:50 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-43303?
CVE-2026-43303 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/pagealloc: clear page->private in freepages_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…
When was CVE-2026-43303 disclosed?
CVE-2026-43303 was first published on May 8, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43303 actively exploited?
CVE-2026-43303 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43303?
CVE-2026-43303 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-43303?
A fix for CVE-2026-43303 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43303 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43303

Explore →

Is Your Infrastructure Affected by CVE-2026-43303?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.