Kernel panic via non-atomic stack switching
Published Aug 22, 2025 · Updated Aug 5, 2026
Race condition in ARM64 Linux and SIMATIC CN 4100 before V5.0 allows local users to trigger kernel panics during stack transitions. cpu_switch_to() and call_on_irq_stack() change the regular and shadow-call-stack pointers non-atomically without fully masking DAIF, so an intervening exception stores or uses a mismatched pointer. Local users need code execution on an affected ARM64 system; pseudo-NMIs increase exposure, while the resulting stack corruption interrupts the system through an unpredictable kernel panic.
Summary
What happened
Race condition in ARM64 Linux and SIMATIC CN 4100 before V5.0 allows local users to trigger kernel panics during stack transitions. cpu_switch_to() and call_on_irq_stack() change the regular and shadow-call-stack pointers non-atomically without fully masking DAIF, so an intervening exception stores or uses a mismatched pointer. Local users need code execution on an affected ARM64 system; pseudo-NMIs increase exposure, while the resulting stack corruption interrupts the system through an unpredictable kernel panic.
The record
- CVE
- CVE-2025-38670
- Published
- Aug 22, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-20, CWE-668, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 22, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=3f225f29c69c13ce1cbdb1d607a42efeef080056 <f7e0231eeaa33245c649fac0303cf97209605446
- Affected versionversion=402d2b1d54b7085d0c3bfd01fd50c2701dde64b3 <407047893a64399f2d2390ff35cc6061107d805d
- Affected versionversion=4403c7b7e5e1ad09a266b6e399fd7bf97931508e <a6b0cb523eaa01efe8a3f76ced493ba60674c6e6
- Affected versionversion=5.10.180 <5.10.210
- Affected versionversion=5.15.111 <5.15.190
- Affected versionversion=59b37fe52f49955791a460752c37145f1afdcad1 <0f67015d72627bad72da3c2084352e0aa134416b
- Affected versionversion=59b37fe52f49955791a460752c37145f1afdcad1 <708fd522b86d2a9544c34ec6a86fa3fc23336525
- Affected versionversion=59b37fe52f49955791a460752c37145f1afdcad1 <9433a5f437b0948d6a2d8a02ad7a42ab7ca27a61
- Affected versionversion=59b37fe52f49955791a460752c37145f1afdcad1 <d42e6c20de6192f8e4ab4cf10be8c694ef27e8cb
- Affected versionversion=6.1.28 <6.1.149
- Affected versionversion=6.2.15 <6.3
- Affected versionversion=6.3
- Affected versionversion=e47ce4f11e26fa3ea99b09521da8b3ac3a7b578d
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo