Description
In the Linux kernel, the following vulnerability has been resolved:
x86/fpu: Prevent state corruption in __fpu__restore_sig()
The non-compacted slowpath uses __copy_from_user() and copies the entire
user buffer into the kernel buffer, verbatim. This means that the kernel
buffer may now contain entirely invalid state on which XRSTOR will #GP.
validate_user_xstate_header() can detect some of that corruption, but that
leaves the onus on callers to clear the buffer.
Prior to XSAVES support, it was possible just to reinitialize the buffer,
completely, but with supervisor states that is not longer possible as the
buffer clearing code split got it backwards. Fixing that is possible but
not corrupting the state in the first place is more robust.
Avoid corruption of the kernel XSAVE buffer by using copy_user_to_xstate()
which validates the XSAVE header contents before copying the actual states
to the kernel. copy_user_to_xstate() was previously only called for
compacted-format kernel buffers, but it works for both compacted and
non-compacted forms.
Using it for the non-compacted form is slower because of multiple
__copy_from_user() operations, but that cost is less important than robust
code in an already slow path.
[ Changelog polished by Dave Hansen ]
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Linux | Linux | 5.8 | 5.10.46 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | linux | 5.10.46-1 | — |
| Debian 13 | linux | 5.10.46-1 | — |
| Debian 12 | linux | 5.10.46-1 | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 22.04 LTS | linux-riscv +20 | No fix yet | — |
| Ubuntu 20.04 LTS | linux-gke +26 | No fix yet | — |
| Ubuntu 18.04 LTS | linux-gcp +14 | No fix yet | — |
| Ubuntu 16.04 LTS | linux-hwe-edge | No fix yet | — |
SUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES 15 SP3 | kernel-64kb +7 | 5.3.18-150300.59.164.1 | SUSE-SU-2024:2185-1 |
| SLES 15 SP3 | kernel-default-base | 5.3.18-150300.59.164.1.150300.18.96.1 | SUSE-SU-2024:2185-1 |
Show 6 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES for SAP 15 SP3 | kernel-default-base | 5.3.18-150300.59.164.1.150300.18.96.1 | SUSE-SU-2024:2185-1 |
| SLES for SAP 15 SP3 | kernel-docs +5 | 5.3.18-150300.59.164.1 | SUSE-SU-2024:2185-1 |
| SLE Micro 5.2 | kernel-default | 5.3.18-150300.59.164.1 | SUSE-SU-2024:2185-1 |
| SLE Micro 5.2 | kernel-default-base | 5.3.18-150300.59.164.1.150300.18.96.1 | SUSE-SU-2024:2185-1 |
| SLE Micro 5.2 | kernel-rt +1 | 5.3.18-150300.172.1 | SUSE-SU-2024:2010-1 |
| SLE Micro 5.1 | kernel-default | 5.3.18-150300.59.164.1 | SUSE-SU-2024:2185-1 |
| SLE Micro 5.1 | kernel-default-base | 5.3.18-150300.59.164.1.150300.18.96.1 | SUSE-SU-2024:2185-1 |
| SLE Micro 5.1 | kernel-rt +1 | 5.3.18-150300.172.1 | SUSE-SU-2024:2010-1 |
| SLE Live Patching 15 SP3 | kernel-default | 5.3.18-150300.59.164.1 | SUSE-SU-2024:2185-1 |
| SLE Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_45 | 1-150300.7.3.1 | SUSE-SU-2024:2185-1 |
| SLE HPC 15 SP3 | kernel-64kb +6 | 5.3.18-150300.59.164.1 | SUSE-SU-2024:2185-1 |
| SLE HPC 15 SP3 | kernel-default-base | 5.3.18-150300.59.164.1.150300.18.96.1 | SUSE-SU-2024:2185-1 |
| SUSE Enterprise Storage 7.1 | kernel-64kb +6 | 5.3.18-150300.59.164.1 | SUSE-SU-2024:2185-1 |
| SUSE Enterprise Storage 7.1 | kernel-default-base | 5.3.18-150300.59.164.1.150300.18.96.1 | SUSE-SU-2024:2185-1 |
Advisories 2
- SUSE-SU-2024:2010-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Feb 4, 2026
- SUSE-SU-2024:2185-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · May 2, 2025