Menu

Star on GitHub · 3.2k

CVE-2025-38670

7.8 · HIGH

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 cha…

Published Aug 22, 2025CWE-668EPSS 0.16%

Overview

CVE-2025-38670 is a high-severity vulnerability. It was published on August 22, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-38670?

CVE-2025-38670 is a high-severity vulnerability. It was published on August 22, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-38670?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-38670?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-38670?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-38670 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all