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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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.8(medium)
EPSS
3.0%
KEV
Not listed

Published

May 8, 2026

Last Modified

June 19, 2026

Advisory Details (3)

Auto-updated May 11, 2026
No patch confirmed yet.
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

Vendor Advisories for CVE-2026-43303(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
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:6.12.0-211.18.1.el10_22026-05-28redhat
redhatkernel-0:5.14.0-687.12.1.el9_82026-05-28redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 89× 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 153 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 in the National Vulnerability Database on May 8, 2026, with the most recent update on June 19, 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 3.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43303?
CVE-2026-43303 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43303?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43303, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs