Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38670arm64/entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 12 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38670, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 3f225f29c69c13ce1cbdb1d607a42efeef080056 – < f7e0231eeaa33245c649fac0303cf97209605446
    • affected 402d2b1d54b7085d0c3bfd01fd50c2701dde64b3 – < 407047893a64399f2d2390ff35cc6061107d805d
    • affected 4403c7b7e5e1ad09a266b6e399fd7bf97931508e – < a6b0cb523eaa01efe8a3f76ced493ba60674c6e6
    • affected 59b37fe52f49955791a460752c37145f1afdcad1 – < 9433a5f437b0948d6a2d8a02ad7a42ab7ca27a61
    • affected 59b37fe52f49955791a460752c37145f1afdcad1 – < 708fd522b86d2a9544c34ec6a86fa3fc23336525
    • affected 59b37fe52f49955791a460752c37145f1afdcad1 – < 0f67015d72627bad72da3c2084352e0aa134416b
    • affected 59b37fe52f49955791a460752c37145f1afdcad1 – < d42e6c20de6192f8e4ab4cf10be8c694ef27e8cb
    • affected e47ce4f11e26fa3ea99b09521da8b3ac3a7b578d
    • affected 5.10.180 – < 5.10.210
    • affected 5.15.111 – < 5.15.190
    • affected 6.1.28 – < 6.1.149
    • affected 6.2.15 – < 6.3
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 5.10.210 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.101 – ≤ 6.6.*
    • unaffected 6.12.41 – ≤ 6.12.*
    • unaffected 6.15.9 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38670 badge
[![CVE-2025-38670](https://cveledger.app/badge/CVE-2025-38670.svg)](https://cveledger.app/cve/CVE-2025-38670)

Record last updated .