CVE-2026-43303

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
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%CVSS: 7.8Exploit: None knownExposed: 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)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 8, 2026

Last Modified

August 5, 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(8)

Vendor / EcosystemFixed in / 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—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 rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 87× 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 224 total refreshes for this CVE.

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

Related CVEs(same product + 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 August 5, 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% probability of exploitation in the next 30 days, which ranks it in the top 93.8% of all scored CVEs.
What is the CVSS score of CVE-2026-43303?
CVE-2026-43303 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

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.

Start Free Scan →Browse All CVEs