CVE-2025-38670 Details
Description
In the Linux kernel, the following vulnerability has been resolved: arm64/entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack() `cpu_switch_to()` and `call_on_irq_stack()` manipulate SP to change to different stacks along with the Shadow Call Stack if it is enabled. Those two stack changes cannot be done atomically and both functions can be interrupted by SErrors or Debug Exceptions which, though unlikely, is very much broken : if interrupted, we can end up with mismatched stacks and Shadow Call Stack leading to clobbered stacks. In `cpu_switch_to()`, it can happen when SP_EL0 points to the new task, but x18 stills points to the old task's SCS. When the interrupt handler tries to save the task's SCS pointer, it will save the old task SCS pointer (x18) into the new task struct (pointed to by SP_EL0), clobbering it. In `call_on_irq_stack()`, it can happen when switching from the task stack to the IRQ stack and when switching back. In both cases, we can be interrupted when the SCS pointer points to the IRQ SCS, but SP points to the task stack. The nested interrupt handler pushes its return addresses on the IRQ SCS. It then detects that SP points to the task stack, calls `call_on_irq_stack()` and clobbers the task SCS pointer with the IRQ SCS pointer, which it will also use ! This leads to tasks returning to addresses on the wrong SCS, or even on the IRQ SCS, triggering kernel panics via CONFIG_VMAP_STACK or FPAC if enabled. This is possible on a default config, but unlikely. However, when enabling CONFIG_ARM64_PSEUDO_NMI, DAIF is unmasked and instead the GIC is responsible for filtering what interrupts the CPU should receive based on priority. Given the goal of emulating NMIs, pseudo-NMIs can be received by the CPU even in `cpu_switch_to()` and `call_on_irq_stack()`, possibly *very* frequently depending on the system configuration and workload, leading to unpredictable kernel panics. Completely mask DAIF in `cpu_switch_to()` and restore it when returning. Do the same in `call_on_irq_stack()`, but restore and mask around the branch. Mask DAIF even if CONFIG_SHADOW_CALL_STACK is not enabled for consistency of behaviour between all configurations. Introduce and use an assembly macro for saving and masking DAIF, as the existing one saves but only masks IF.
A vulnerability has been identified in the Linux kernel's handling of stack switches in ARM64 architecture, specifically within the 'cpu_switch_to()' and 'call_on_irq_stack()' functions. These functions manage transitions between different stacks and the Shadow Call Stack (SCS) when enabled. However, the stack changes cannot be performed atomically and can be disrupted by SErrors or Debug Exceptions. Such interruptions may cause a mismatch in the stacks and SCS, leading to corrupted stack states. This issue is particularly problematic when 'CONFIG_ARM64_PSEUDO_NMI' is enabled, as it allows the CPU to receive pseudo-NMI interrupts during critical stack switching processes, potentially causing unpredictable kernel panics.
The vulnerability has been addressed by modifying the 'cpu_switch_to()' and 'call_on_irq_stack()' functions to properly mask and restore the DAIF register, ensuring consistent behavior across different configurations. Users should upgrade to the latest version of the Linux kernel where this vulnerability has been patched.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://cert-portal.siemens.com/productcert/html/ssa-032379.html | siemens-SADP | |
| https://git.kernel.org/stable/c/0f67015d72627bad72da3c2084352e0aa134416b | kernel.org | Patch |
| https://git.kernel.org/stable/c/407047893a64399f2d2390ff35cc6061107d805d | kernel.org | Patch |
| https://git.kernel.org/stable/c/708fd522b86d2a9544c34ec6a86fa3fc23336525 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9433a5f437b0948d6a2d8a02ad7a42ab7ca27a61 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a6b0cb523eaa01efe8a3f76ced493ba60674c6e6 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d42e6c20de6192f8e4ab4cf10be8c694ef27e8cb | kernel.org | Patch |
| https://git.kernel.org/stable/c/f7e0231eeaa33245c649fac0303cf97209605446 | kernel.org | Patch |
| https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html | CVE | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-668 | Exposure of Resource to Wrong Sphere | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.10.180, < 5.10.210 >= 5.15.111, < 5.15.190 >= 6.1.28, < 6.1.149 >= 6.2.15, < 6.6.101 >= 6.7, < 6.12.41 >= 6.13, < 6.15.9 6.16 rc1 6.16 rc2 6.16 rc3 6.16 rc4 6.16 rc5 6.16 rc6 6.16 rc7 |
CPE
Remediation
| |
| debian debian linux | 11.0 |
CPE
Remediation
| |
Change History
9 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | siemens-SADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 12, 2026 | CVE Modified | siemens-SADP |
| Jan 22, 2026 | Initial Analysis | [email protected] |
| Dec 23, 2025 | CVE Modified | kernel.org |
| Nov 3, 2025 | CVE Modified | CVE |
| Aug 28, 2025 | CVE Modified | kernel.org |
| Aug 22, 2025 | New CVE Received | kernel.org |