cve.bz

CVE-2025-38169 linux linux kernel

5.5 mediumEPSS 0.2%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: Avoid clobbering kernel FPSIMD state with SMSTOP On system with SME, a thread's kernel FPSIMD state may be erroneously clobbered during a context switch immediately after that state is restored. Systems without SME are unaffected. If the CPU happens to be in streaming SVE mode before a context switch to a thread with kernel FPSIMD state, fpsimd_thread_switch() will restore the kernel FPSIMD state using fpsimd_load_kernel_state() while the CPU is still in streaming SVE mode. When fpsimd_thread_switch() subsequently calls fpsimd_flush_cpu_state(), this will execute an SMSTOP, causing an exit from streaming SVE mode. The exit from streaming SVE mode will cause the hardware to reset a number of FPSIMD/SVE/SME registers, clobbering the FPSIMD state. Fix this by calling fpsimd_flush_cpu_state() before restoring the kernel FPSIMD state.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-38169 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-38169?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-38169?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-38169 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 6.8.12 before 6.9
Linuxfrom 6.9.3 before 6.10
Linux6.10 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.34
Linux6.156.15.3
Linuxlater releases6.16

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13, 14linux6.12.35-1DEBIAN-CVE-2025-38169
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-38169
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-38169
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-38169
Ubuntu22.04:LTSlinux-aws-6.8, linux-nvidia-6.86.8.0-1046.49~22.04.1UBUNTU-CVE-2025-38169 USN-8028-5
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1051.57~22.04.1UBUNTU-CVE-2025-38169 USN-8126-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1046.53~22.04.1UBUNTU-CVE-2025-38169
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1047.50~22.04.2UBUNTU-CVE-2025-38169 USN-8031-1
Ubuntu22.04:LTSlinux-hwe-6.8, linux-riscv-6.86.8.0-100.100~22.04.1UBUNTU-CVE-2025-38169 USN-8028-6
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1044.44~22.04.1UBUNTU-CVE-2025-38169 USN-8028-8
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-100.100.1~22.04.1UBUNTU-CVE-2025-38169 USN-8028-6
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1043.44~22.04.1UBUNTU-CVE-2025-38169 USN-8028-5
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-38169
35 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.6.1SUSE-SU-2025:21179-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 5 more6.12.0-160000.6.1SUSE-SU-2025:21139-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.6.1.160000.2.4SUSE-SU-2025:21139-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.6.1.160000.2.4SUSE-SU-2025:21074-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.6.1SUSE-SU-2025:21074-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.6.1SUSE-SU-2026:20560-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.6.1.160000.2.4openSUSE-SU-2025:20081-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 8 more6.12.0-160000.6.1openSUSE-SU-2025:20081-1
Alpaquita25linux-lts6.12.41-r0BELL-CVE-2025-38169
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-38169

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate impact flaw was found in the Linux kernel arm64/fpsimd context-switch handling in Red Hat Enterprise Linux 9 and 10, and in Red Hat In-Vehicle OS. On arm64 systems with the Scalable Matrix Extension (SME), if the CPU is in streaming SVE mode when the scheduler switches to a thread with kernel FPSIMD state, fpsimd_thread_switch() restores that state via fpsimd_load_kernel_state() while the CPU is still in streaming SVE mode; the subsequent fpsimd_flush_cpu_state() executes an SMSTOP, and the resulting exit from streaming SVE mode causes the hardware to reset FPSIMD/SVE/SME registers, clobbering the kernel FPSIMD state that was just restored. This can result in data corruption and system instability, and can be triggered by a local user able to run code on the system. Red Hat rates this flaw Moderate severity (CVSS 5.5, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) because the demonstrated consequence is corruption of kernel FPSIMD state affecting availability, rather than the confidentiality and integrity impact reflected in the upstream CVEORG score of 7.8. Red Hat Enterprise Linux 6, 7, and 8 (kernel and kernel-rt) are not affected because the vulnerable code is not present in those releases, and systems without SME hardware are also unaffected. For the affected Red Hat Enterprise Linux 9 and 10 and Red Hat In-Vehicle OS kernel streams, the fix is currently deferred; the residual risk is that kernel FPSIMD state may be clobbered during context switches on SME-equipped systems, potentially causing data corruption or system instability.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-38169.

References

Check your stackJSON