Answer in brief
CVE-2025-38169 records a Unknown severity vulnerability in arm64/fpsimd: Avoid clobbering kernel FPSIMD state with SMSTOP. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e92bee9f861b466c676f0200be3e46af7bc4ac6b <55d52af498daea75aa03ba9b7e444c8ae495ac20 || >=e92bee9f861b466c676f0200be3e46af7bc4ac6b <a305821f597ec943849d3e53924adb88c61ed682 || >=e92bee9f861b466c676f0200be3e46af7bc4ac6b <01098d893fa8a6edb2b56e178b798e3e6b674f02 || e003c485ac82a9f8de4204912ed059ac6dd4257c || 25b90cd122d546823da90b916f7c3289dfe83a99 || >=6.8.12 <6.9 || >=6.9.3 <6.10 | 55d52af498daea75aa03ba9b7e444c8ae495ac20, a305821f597ec943849d3e53924adb88c61ed682, 01098d893fa8a6edb2b56e178b798e3e6b674f02, 6.9, 6.10 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Jul 3, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38169 records a Unknown severity vulnerability in arm64/fpsimd: Avoid clobbering kernel FPSIMD state with SMSTOP. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e92bee9f861b466c676f0200be3e46af7bc4ac6b <55d52af498daea75aa03ba9b7e444c8ae495ac20 || >=e92bee9f861b466c676f0200be3e46af7bc4ac6b <a305821f597ec943849d3e53924adb88c61ed682 || >=e92bee9f861b466c676f0200be3e46af7bc4ac6b <01098d893fa8a6edb2b56e178b798e3e6b674f02 || e003c485ac82a9f8de4204912ed059ac6dd4257c || 25b90cd122d546823da90b916f7c3289dfe83a99 || >=6.8.12 <6.9 || >=6.9.3 <6.10 | 55d52af498daea75aa03ba9b7e444c8ae495ac20, a305821f597ec943849d3e53924adb88c61ed682, 01098d893fa8a6edb2b56e178b798e3e6b674f02, 6.9, 6.10 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Jul 3, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.