CVE-2026-11985

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.

• CWE-200

• https://github.com/zephyrproject-rtos/zephyr/commit/3d405326a7653cba6860280e45c8734f8d3fc423
• https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-qxr9-wh3c-hvgv

Published

Aug 11, 2026

Last Modified

Oct 23, 2026

Status

Awaiting Analysis

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-119843A flaw was found in GStreamer's gst-plugins-good package. Th…6.5
• CVE-2026-119844Use after free in Windows Device Association Service allows …7
• CVE-2026-119846Out-of-bounds read in Windows Subsystem for Linux allows an …7.8
• CVE-2026-119847Heap-based buffer overflow in Windows Kerberos allows an aut…7.8
• CVE-2026-119848Improper input validation in Windows Message Queuing allows …5.3
• CVE-2026-119849Stack-based buffer overflow in Virtual Hard Disk (VHD) Minip…7
• CVE-2026-119851Time-of-check time-of-use (toctou) race condition in Windows…7
• CVE-2026-119852Missing authorization in Windows Installer allows an authori…6.7
• CVE-2026-119853Untrusted search path in Windows Remote Access API allows an…7.8
• CVE-2026-119855Buffer over-read in Windows COM+ Event System Service allows…5.5
• CVE-2026-119856Exposure of sensitive system information to an unauthorized …5.5
• CVE-2026-119857Buffer over-read in Windows Kernel allows an authorized atta…5.5