CVE-2026-23114

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

arm64/fpsimd: ptrace: Fix SVE writes on !SME systems

When SVE is supported but SME is not supported, a ptrace write to the

NT_ARM_SVE regset can place the tracee into an invalid state where

(non-streaming) SVE register data is stored in FP_STATE_SVE format but

TIF_SVE is clear. This can result in a later warning from

fpsimd_restore_current_state(), e.g.

WARNING: CPU: 0 PID: 7214 at arch/arm64/kernel/fpsimd.c:383 fpsimd_restore_current_state+0x50c/0x748

When this happens, fpsimd_restore_current_state() will set TIF_SVE,

placing the task into the correct state. This occurs before any other

check of TIF_SVE can possibly occur, as other checks of TIF_SVE only

happen while the FPSIMD/SVE/SME state is live. Thus, aside from the

warning, there is no functional issue.

This bug was introduced during rework to error handling in commit:

9f8bf718f2923 ("arm64/fpsimd: ptrace: Gracefully handle errors")

... where the sett

/// 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.

/// References