Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38169arm64/fpsimd: Avoid clobbering kernel FPSIMD state with SMSTOP

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 16 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38169, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected e92bee9f861b466c676f0200be3e46af7bc4ac6b – < 55d52af498daea75aa03ba9b7e444c8ae495ac20
    • affected e92bee9f861b466c676f0200be3e46af7bc4ac6b – < a305821f597ec943849d3e53924adb88c61ed682
    • affected e92bee9f861b466c676f0200be3e46af7bc4ac6b – < 01098d893fa8a6edb2b56e178b798e3e6b674f02
    • affected e003c485ac82a9f8de4204912ed059ac6dd4257c
    • affected 25b90cd122d546823da90b916f7c3289dfe83a99
    • affected 6.8.12 – < 6.9
    • affected 6.9.3 – < 6.10
  • Linux · Linux

    • affected 6.10
    • unaffected < 6.10
    • unaffected 6.12.34 – ≤ 6.12.*
    • unaffected 6.15.3 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38169 badge
[![CVE-2025-38169](https://cveledger.app/badge/CVE-2025-38169.svg)](https://cveledger.app/cve/CVE-2025-38169)

Record last updated .