CVE-2021-47227

x86/fpu: Prevent state corruption in __fpu__restore_sig()

State
Published
Severity
Not scored
Published
May 21, 2024
Updated
May 11, 2026
Reserved
Apr 10, 2024

Read the record on cve.org

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 ]

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • b860eb8dce5906b14e3a7f3c771e0b3d6ef61b94 to before 076f732b16a5bf842686e1b43ab6021a2d98233eAffected
  • b860eb8dce5906b14e3a7f3c771e0b3d6ef61b94 to before ec25ea1f3f05d6f8ee51d1277efea986eafd4f2aAffected
  • b860eb8dce5906b14e3a7f3c771e0b3d6ef61b94 to before 484cea4f362e1eeb5c869abbfb5f90eae6421b38Affected
LinuxLinux
  • 5.8Affected
  • before 5.8Not affected
  • 5.10.46 through 5.10.*Not affected
  • 5.12.13 through 5.12.*Not affected
  • 5.13 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.