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-68171x86/fpu: Ensure XFD state on signal delivery

Description

In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Ensure XFD state on signal delivery Sean reported [1] the following splat when running KVM tests: WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70 Call Trace: <TASK> fpu__clear_user_states+0x9c/0x100 arch_do_signal_or_restart+0x142/0x210 exit_to_user_mode_loop+0x55/0x100 do_syscall_64+0x205/0x2c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 Chao further identified [2] a reproducible scenario involving signal delivery: a non-AMX task is preempted by an AMX-enabled task which modifies the XFD MSR. When the non-AMX task resumes and reloads XSTATE with init values, a warning is triggered due to a mismatch between fpstate::xfd and the CPU's current XFD state. fpu__clear_user_states() does not currently re-synchronize the XFD state after such preemption. Invoke xfd_update_state() which detects and corrects the mismatch if there is a dynamic feature. This also benefits the sigreturn path, as fpu__restore_sig() may call fpu__clear_user_states() when the sigframe is inaccessible. [ dhansen: minor changelog munging ]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 10 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-68171, 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 · Deferred3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (16 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 672365477ae8afca5a1cca98c1deb733235e4525 – < eefbfb722042fc9210d2e0ac2b063fd1abf51895
    • affected 672365477ae8afca5a1cca98c1deb733235e4525 – < 1811c610653c0cd21cc9add14595b7cffaeca511
    • affected 672365477ae8afca5a1cca98c1deb733235e4525 – < 5b2619b488f1d08b960c43c6468dd0759e8b3035
    • affected 672365477ae8afca5a1cca98c1deb733235e4525 – < 3f735419c4b43cde42e6d408db39137b82474e31
    • affected 672365477ae8afca5a1cca98c1deb733235e4525 – < 388eff894d6bc5f921e9bfff0e4b0ab2684a96e9
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.117 – ≤ 6.6.*
    • unaffected 6.12.58 – ≤ 6.12.*
    • unaffected 6.17.8 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .