Security readout for executives and security teams
Plain-English summary
This is a Linux kernel reliability flaw in ARM IOMMU page-table unmapping. An error value is returned through an unsigned size field, becoming a very large number. The described impact is a kernel BUG condition, which can crash affected systems.
Executive priority
Handle through normal kernel patch governance, with higher priority for ARM infrastructure where unexpected host crashes would affect availability commitments.
Technical view
__arm_lpae_unmap() returned -ENOENT despite a size_t return type. The value becomes a huge unsigned number, propagates through arm_lpae_unmap_pages() and __iommu_unmap(), corrupts IOVA arithmetic, and can trigger BUG_ON in iommu_pgsize(). The fix returns 0 for unmapped PTEs.
Likely exposure
Exposure appears limited to Linux systems using the ARM LPAE IOMMU page-table path in affected kernel builds. The bundle does not identify specific distributions, devices, cloud images, or default configurations.
Exploitation context
The source bundle does not report active exploitation, public exploit code, KEV listing, privilege requirements, or remote reachability. Treat this as a kernel crash risk until vendor advisories clarify exploitability.
Researcher notes
The evidence supports a signedness-to-overflow bug leading to BUG_ON, not memory disclosure or code execution. Affected-version detail is incomplete in the bundle, so distribution mapping requires vendor confirmation.
Mitigation direction
- Identify Linux systems using affected kernel versions or referenced commit lineages.
- Apply vendor kernel updates containing the linked stable fixes.
- Prioritize ARM platforms using IOMMU-backed device mappings.
- Check distribution advisories before making unsupported kernel changes.
- Monitor kernel logs for related WARN_ON or BUG_ON events.
Validation and detection
- Inventory kernel versions across ARM Linux assets.
- Confirm whether affected hosts use the ARM LPAE IOMMU path.
- Verify installed kernels include one of the linked stable commits.
- Review crash logs for iommu_pgsize or __iommu_unmap BUG_ON traces.
- Track vendor CVE status for distribution-specific fixed builds.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2026-23067 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
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.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/41ec6988547819756fb65e94fc24f3e0dddf84acCVE reference, Linux
- https://git.kernel.org/stable/c/374e7af67d9d9d6103c2cfc8eb32abfecf3a2fd8CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.