CVE-2025-38670: arm64/entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack()
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0f67015d72627bad72da3c2084352e0aa134416b, 407047893a64399f2d2390ff35cc6061107d805d, 5.10.210; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.
Low priority for now. Upgrade to Linux Linux 0f67015d72627bad72da3c2084352e0aa134416b, 407047893a64399f2d2390ff35cc6061107d805d, 5.10.210; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 22, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-668
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 7.1
- CNA · Linux
- 7.8
- 0.7 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.15.111 and later · before 5.15.190
- linux linux kernel6.1.28 and later · before 6.1.149
- linux linux kernel6.2.15 and later · before 6.6.101
- linux linux kernel5.10.180 and later · before 5.10.210
- linux linux kernel6.13 and later · before 6.15.9
- linux linux kernel6.7 and later · before 6.12.41
- linux linux kernel6.16
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- e47ce4f11e26fa3ea99b09521da8b3ac3a7b578d, 6.3affected
- 3f225f29c69c13ce1cbdb1d607a42efeef080056 and later · before f7e0231eeaa33245c649fac0303cf97209605446affected · git
- 402d2b1d54b7085d0c3bfd01fd50c2701dde64b3 and later · before 407047893a64399f2d2390ff35cc6061107d805daffected · git
- 4403c7b7e5e1ad09a266b6e399fd7bf97931508e and later · before a6b0cb523eaa01efe8a3f76ced493ba60674c6e6affected · git
- 59b37fe52f49955791a460752c37145f1afdcad1 and later · before 9433a5f437b0948d6a2d8a02ad7a42ab7ca27a61affected · git
- 59b37fe52f49955791a460752c37145f1afdcad1 and later · before 708fd522b86d2a9544c34ec6a86fa3fc23336525affected · git
- 59b37fe52f49955791a460752c37145f1afdcad1 and later · before 0f67015d72627bad72da3c2084352e0aa134416baffected · git
- 59b37fe52f49955791a460752c37145f1afdcad1 and later · before d42e6c20de6192f8e4ab4cf10be8c694ef27e8cbaffected · git
- 5.10.180 and later · before 5.10.210affected · semver
- 5.15.111 and later · before 5.15.190affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.153-1 | 6.1.153-1 |
| Debian:13 | linux | before 6.12.41-1 | 6.12.41-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38666Aug 22, 2025 · net: appletalk: Fix use-after-free in AARP proxy probe31Monitor
- ← EarlierCVE-2025-38667Aug 22, 2025 · iio: fix potential out-of-bound write31Monitor
- Later →CVE-2025-38672Aug 22, 2025 · Revert "drm/gem-dma: Use dma_buf from GEM object instance"22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0f67015d72627bad72da3c2084352e0aa134416b | Vendor (CNA) |
| Linux Linux | 407047893a64399f2d2390ff35cc6061107d805d | Vendor (CNA) |
| Linux Linux | 5.10.210 | Vendor (CNA) |
| Linux Linux | 5.15.190 | Vendor (CNA) |
| Linux Linux | 6.1.149 | Vendor (CNA) |
| Linux Linux | 6.3 | Vendor (CNA) |
| Linux Linux | 708fd522b86d2a9544c34ec6a86fa3fc23336525 | Vendor (CNA) |
| Linux Linux | 9433a5f437b0948d6a2d8a02ad7a42ab7ca27a61 | Vendor (CNA) |
| Linux Linux | a6b0cb523eaa01efe8a3f76ced493ba60674c6e6 | Vendor (CNA) |
| Linux Linux | d42e6c20de6192f8e4ab4cf10be8c694ef27e8cb | Vendor (CNA) |
| Linux Linux | f7e0231eeaa33245c649fac0303cf97209605446 | Vendor (CNA) |
| azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 | 6.6.104.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.153-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-22069128 days apartriscv: fgraph: Fix stack layout to match __arch_ftrace_regs argument of ftrace_return_to_handler31Monitor
- CVE-2026-63914331 days apartxfrm: route MIGRATE notifications to caller's netns29Monitor
- CVE-2025-385216 days apartdrm/imagination: Fix kernel crash when hard resetting the GPU28Monitor
- CVE-2022-49509177 days apartmedia: i2c: max9286: fix kernel oops when removing module28Monitor
- CVE-2024-57838223 days aparts390/entry: Mark IRQ entries to fix stack depot warnings28Monitor
- CVE-2024-43881367 days apartwifi: ath12k: change DMA direction while mapping reinjected packets28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-668 · Exposure of Resource to Wrong SphereCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/407047893a64399f2d2390ff35cc6061107d805d
- git.kernel.org/stable/c/708fd522b86d2a9544c34ec6a86fa3fc23336525
- git.kernel.org/stable/c/9433a5f437b0948d6a2d8a02ad7a42ab7ca27a61
- git.kernel.org/stable/c/a6b0cb523eaa01efe8a3f76ced493ba60674c6e6
- git.kernel.org/stable/c/d42e6c20de6192f8e4ab4cf10be8c694ef27e8cb
- git.kernel.org/stable/c/f7e0231eeaa33245c649fac0303cf97209605446
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- cert-portal.siemens.com/productcert/html/ssa-032379.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.