CVE-2025-68171
Last modified
CVE-2025-68171 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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 ]. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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 ]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 672365477ae8afca5a1cca98c1deb733235e4525, < eefbfb722042fc9210d2e0ac2b063fd1abf51895; >= 672365477ae8afca5a1cca98c1deb733235e4525, < 1811c610653c0cd21cc9add14595b7cffaeca511; >= 672365477ae8afca5a1cca98c1deb733235e4525, < 5b2619b488f1d08b960c43c6468dd0759e8b3035; >= 672365477ae8afca5a1cca98c1deb733235e4525, < 3f735419c4b43cde42e6d408db39137b82474e31; >= 672365477ae8afca5a1cca98c1deb733235e4525, < 388eff894d6bc5f921e9bfff0e4b0ab2684a96e9 |
| Linux | Linux | 5.16 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-68171?
How severe is CVE-2025-68171?
How do I fix CVE-2025-68171?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-68166In JetBrains TeamCity before 2025.11 a DOM-based XSS was pos…6.1
- CVE-2025-68167In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68168In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68169In the Linux kernel, the following vulnerability has been re…
- CVE-2025-6817A vulnerability, which was classified as problematic, has be…3.3
- CVE-2025-68170In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68172In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68173In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68174In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68175In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68176In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68177In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2025-68171?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
