CVE-2026-53288

Medium

In the Linux kernel, the following vulnerability has been resolved: arm64: Reserve an extra page for early kernel mapping The final part of [data, end) segment may overflow into the next page of init_pg_end[1] which is the gap page before early_init_stack[2]: [1] crash_arm64_v9.0.1> vtop ffffffed00601000 VIRTUAL PHYSICAL ffffffed00601000 83401000 PAGE DIRECTORY: ffffffecffd62000 PGD: ffffffecffd62da0 => 10000000833fb003 PMD: ffffff80033fb018 => 10000000833fe003 PTE: ffffff80033fe008 => 68000083401f03 PAGE: 83401000 PTE PHYSICAL FLAGS 68000083401f03 83401000 (VALID|SHARED|AF|NG|PXN|UXN) PAGE PHYSICAL MAPPING INDEX CNT FLAGS fffffffec00d0040 83401000 0 0 1 4000 reserved [2] ffffffed002c8000 (r) __pi__data ffffffed0054e000 (d) __pi___bss_start ffffffed005f5000 (b) __pi_init_pg_dir ffffffed005fe000 (b) __pi_init_pg_end ffffffed005ff000 (B) early_init_stack ffffffed00608000 (b) __pi__end For 4K pages, the early kernel mapping may use 2MB block entries but the kernel segments are only 64KB aligned. Segment boundaries that fall within a 2MB block therefore require a PTE table so that different attributes can be applied on either side of the boundary. KERNEL_SEGMENT_COUNT still correctly counts the five permanent kernel VMAs registered by declare_kernel_vmas(). However, since commit 5973a62efa34 ("arm64: map [_text, _stext) virtual address range non-executable+read-only"), the early mapper also maps [_text, _stext) separately from [_stext, _etext). This adds one more early-only split and can require one more page-table page than the existing EARLY_SEGMENT_EXTRA_PAGES allowance reserves. Increase the 4K-page early mapping allowance by one page to cover that additional split. [[email protected]: rewrote part of the commit log] [[email protected]: expanded the code comment]

Package Linux Kernel
Published 2026-06-26
Last modified 2026-07-08
CVSS version 3.1
Patch available
Yes

CVSS 3.1 score

5.5

out of 10
Medium
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-674

CVE-2026-53288 is a Uncontrolled Recursion vulnerability

What is Uncontrolled Recursion?

The product does not properly control the amount of recursion which triggers resource consumption. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.12.54, 6.17.4, 6.18 and later are affected. Fixed in 6.12.91, 6.18.33, 7.0.10, 7.1 and their respective stable series.

Affected from
≥ 6.12.54 ≥ 6.17.4 ≥ 6.18
Fixed in
✓ 6.12.91 6.12.x ✓ 6.18.33 6.18.x ✓ 7.0.10 7.0.x ✓ 7.1

Frequently asked questions

  • What is CVE-2026-53288?

    CVE-2026-53288 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Uncontrolled Recursion flaw (CWE-674) . It affects Linux kernel versions from 6.12.54 onward and has been patched in 6.12.91, 6.18.33, 7.0.10 and others. CVE-2026-53288 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • What is the CVSS score for CVE-2026-53288?

    CVE-2026-53288 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H .

  • Is there a patch available for CVE-2026-53288?

    Yes. CVE-2026-53288 has been patched. Fixed versions include 6.12.91, 6.18.33, 7.0.10 and others. If you are running Linux kernel 6.12.54 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-53288 actively exploited?

    No. CVE-2026-53288 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.