Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash affected ARM64 systems when Guarded Control Stack mappings are used with LPA2 enabled. The reported failure is a kernel panic during GCS cleanup. The sources do not provide CVSS, broad impact details, or evidence of active exploitation.
Executive priority
Treat as targeted infrastructure hygiene unless your environment runs ARM64 systems with LPA2 and GCS. Prioritize patch validation for those platforms, but do not escalate as internet-wide emergency based on the provided evidence.
Technical view
On arm64, FEAT_LPA2 repurposes PTE bits 8-9 as output address bits. GCS page protection macros included PTE_SHARED in those bits, producing invalid mappings and a translation fault. The fix stores GCS protections separately and clears PTE_SHARED when LPA2 is enabled.
Likely exposure
Exposure appears limited to Linux arm64 systems using kernels in the affected ranges with FEAT_LPA2 and GCS enabled. The provided version data is not fully explained, so teams should verify against their exact vendor kernel build and stable patch status.
Exploitation context
The bundle marks CISA KEV as false and provides no cited evidence of active exploitation. The described observable impact is kernel panic or oops under a specific ARM64 feature combination, not a documented remote exploitation path.
Researcher notes
The affected-version metadata is sparse and potentially ambiguous. Analysis should center on the PTE bit collision under LPA2, GCS mapping paths, and whether downstream vendor kernels include the stable commits referenced by the CVE record.
Mitigation direction
Check vendor kernel advisories for CVE-2026-23345 coverage.
Update to a kernel build carrying the referenced stable fixes.
Prioritize ARM64 platforms where LPA2 and GCS are enabled.
If patch status is unclear, request confirmation from the kernel or platform vendor.
Validation and detection
Inventory ARM64 hosts and kernel versions.
Confirm whether FEAT_LPA2 and GCS are present or enabled.
Compare kernel package changelogs against the referenced stable commits.
Review crash logs for GCS-related translation faults or kernel oops traces.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23345 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 25, 2026, 10:27 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.