Kernel crash via lockless page-table teardown race
Published Sep 24, 2026 · Updated Sep 24, 2026
Race condition in arm64 Linux allows local users to crash the kernel during a concurrent task page-table teardown. The show_pte() fault-reporting path walks page tables without locks while interrupts remain enabled, so teardown can free a table page or clear a parent entry before the next-level pointer is derived. Triggering requires an arm64 task to fault while another thread removes its mappings; dereferencing released memory can cause a nested kernel fault or corrupt diagnostic output.
Summary
What happened
Race condition in arm64 Linux allows local users to crash the kernel during a concurrent task page-table teardown. The show_pte() fault-reporting path walks page tables without locks while interrupts remain enabled, so teardown can free a table page or clear a parent entry before the next-level pointer is derived. Triggering requires an arm64 task to fault while another thread removes its mappings; dereferencing released memory can cause a nested kernel fault or corrupt diagnostic output.
The record
- CVE
- CVE-2026-93239
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1d18c47c735e8adfe531fc41fae31e98f86b68fe <08d931a0a850ad16a64f2cd23a19f40795cdbdf7
- Affected versionversion=1d18c47c735e8adfe531fc41fae31e98f86b68fe <0f05d95b99164a9ccc4cf4a4920e0ff0228138ad
- Affected versionversion=1d18c47c735e8adfe531fc41fae31e98f86b68fe <68cbd70795dd8c06e7ccdc4eb0b74c5b180076c3
- Affected versionversion=1d18c47c735e8adfe531fc41fae31e98f86b68fe <a77644d009dece1104b6fcc6e322b0e4503db0d6
- Affected versionversion=1d18c47c735e8adfe531fc41fae31e98f86b68fe <b28fe65a36b8209b6adcf2722c7ce974cf9ac8d1
- Affected versionversion=3.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started