CVE-2026-11985
Received Received - Intake

Hardware FPU Context Switch Information Disclosure in Zephyr RTOS

Vulnerability report for CVE-2026-11985, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-11

Last updated on: 2026-08-11

Assigner: Zephyr Project

Description

On the Zephyr ARM port, enabling the hardware FPU (CONFIG_FPU) forces the "Floating point ABI" choice, which defaults to CONFIG_FP_HARDABI. Both FP_HARDABI and FP_SOFTABI permit the compiler to emit hardware FP instructions in any function, even code that never uses floating-point types. However, the callee-saved FP registers (s16-s31 / d8-d15) are only saved and restored across a context switch when CONFIG_FPU_SHARING is enabled (arch/arm/core/cortex_m/swap_helper.S and arch/arm/core/cortex_a_r/swap_helper.S), and prior to this fix selecting an ABI did not enable FPU register sharing, which defaults off. In a build that enables the FPU with the default ABI but leaves CONFIG_FPU_SHARING disabled, the kernel preserves no callee-saved FP register state across thread switches. The documented precondition for this "unshared" mode β€” that only a single thread ever executes FP instructions β€” is silently violated because the compiler may generate FP instructions in every thread. Under CONFIG_USERSPACE, where threads are mutually isolated, this becomes an information-disclosure boundary crossing: a victim thread can leave secret-derived values in s16-s31, and a co-resident unprivileged thread can read those registers directly (FP register access is not privilege-gated), recovering data left behind by another thread. Without userspace the same defect causes cross-thread FP state corruption (a correctness fault). The leak is bounded to the 16 callee-saved single-precision registers and is opportunistic, so impact is low. The fix makes FP_HARDABI and FP_SOFTABI select CONFIG_FPU_SHARING and tags every thread with K_FP_REGS at creation, so callee-saved FP state is always preserved across context switches whenever the compiler may emit FP instructions.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-11
Last Modified
2026-08-11
Generated
2026-08-11
AI Q&A
2026-08-11
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
zephyrproject zephyr From 1.13.0 (inc) to 4.4.1 (inc)
zephyrproject zephyr 4.5.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the Zephyr RTOS ARM port when the hardware FPU is enabled. The default floating-point ABI allows compilers to generate FP instructions even in non-FP code. However, callee-saved FP registers are only preserved during context switches if CONFIG_FPU_SHARING is enabled. Without this, FP state leaks or corrupts across threads, enabling information disclosure under CONFIG_USERSPACE or correctness faults otherwise.

Detection Guidance

To detect this vulnerability, check if CONFIG_FPU is enabled in your Zephyr RTOS build configuration while CONFIG_FPU_SHARING is disabled. Verify if FP_HARDABI or FP_SOFTABI is selected without forced FPU register sharing. Inspect thread initialization for missing K_FP_REGS tags.

Impact Analysis

Under CONFIG_USERSPACE, an unprivileged thread could read FP registers left by another thread, potentially exposing sensitive data. Without userspace, it causes FP state corruption across threads, leading to incorrect program behavior. The impact is limited to the 16 callee-saved FP registers and requires local access.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by enabling information disclosure through floating-point register leaks. Under CONFIG_USERSPACE, an unprivileged thread could read FP registers left by a victim thread, recovering sensitive data. This violates data confidentiality requirements in GDPR (Article 5) and HIPAA (Safeguards Rule).

Mitigation Strategies

Immediately upgrade Zephyr RTOS to version 4.5.0 or later. Ensure CONFIG_FPU_SHARING is enabled when CONFIG_FPU is active. Verify all threads are tagged with K_FP_REGS during creation to preserve FP register state across context switches.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-11985. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart