CVE-2026-23345
Kernel Panic Vulnerability in Linux arm64 GCS with LPA2 Enabled
Publication date: 2026-03-25
Last updated on: 2026-04-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.13 |
| linux | linux_kernel | From 6.19 (inc) to 6.19.7 (exc) |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.13.1 (inc) to 6.18.17 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel on arm64 architectures when the FEAT_LPA2 feature is enabled. The issue arises because the kernel sets the PTE_SHARED bit on GCS (Generic Command Stream) memory mappings incorrectly. With FEAT_LPA2 enabled, bits 8-9 of the Page Table Entry (PTE) are repurposed, and setting PTE_SHARED causes a kernel panic due to a level 0 translation fault.
The panic manifests as an 'Unable to handle kernel paging request' error, leading to an internal kernel error and system crash. The fix involves changing how the kernel sets protection bits for GCS mappings by clearing the PTE_SHARED bit when LPA2 is enabled, preventing the panic.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to panic and crash on affected systems using arm64 architecture with FEAT_LPA2 enabled when GCS mappings are used. This results in system instability and potential downtime, which can disrupt services and applications running on the affected system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as a kernel panic related to the GCS mappings on arm64 systems with FEAT_LPA2 enabled. Detection involves monitoring for kernel panic messages similar to the following:
- Kernel panic logs containing messages like 'Unable to handle kernel paging request at virtual address ...' and 'Internal error: Oops: 0000000096000004' related to gcs_write_fault.
- Checking kernel logs (e.g., using 'dmesg' or examining /var/log/kern.log) for the specific error trace involving zap_huge_pmd and gcs_write_fault.
There are no specific commands provided in the context to detect this vulnerability directly.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is resolved by modifying the kernel code to avoid setting PTE_SHARED on GCS mappings when FEAT_LPA2 is enabled. Immediate mitigation steps include:
- Update the Linux kernel to a version that includes the fix which uses a gcs_page_prot variable to store protection bits and clears PTE_SHARED if LPA2 is enabled.
- Avoid enabling GCS on systems/models with LPA2 until the kernel is patched.
No other specific mitigation commands or workarounds are provided in the context.