Kernel privilege escalation via mutable syscall return frame
Published Nov 11, 2025 · Updated Nov 12, 2025
Privilege context switching error in Zephyr RTOS 4.2 and earlier allows local users to gain kernel privileges on Cortex-M systems. The syscall entry path clears nPRIV before returning through an exception frame on an attacker-writable thread stack, letting a racing thread replace the saved PC. Exploitation requires Zephyr userspace, repeated low-priority syscalls, and higher-priority preemption before the privileged-stack switch.
Summary
What happened
Privilege context switching error in Zephyr RTOS 4.2 and earlier allows local users to gain kernel privileges on Cortex-M systems. The syscall entry path clears nPRIV before returning through an exception frame on an attacker-writable thread stack, letting a racing thread replace the saved PC. Exploitation requires Zephyr userspace, repeated low-priority syscalls, and higher-priority preemption before the privileged-stack switch.
The record
- CVE
- CVE-2025-9408
- Published
- Nov 11, 2025
- Updated
- Nov 12, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-270, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 11, 2025CVE publishedPublication date reported by the CVE source.
- Nov 12, 2025Record 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=* <=4.2
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