CVE-2024-26603

x86/fpu: Stop relying on userspace for info to fault in xsave buffer

State
Published
Severity
Not scored
Published
Feb 24, 2024
Updated
May 11, 2026
Reserved
Feb 19, 2024

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

x86/fpu: Stop relying on userspace for info to fault in xsave buffer

Before this change, the expected size of the user space buffer was taken from fx_sw->xstate_size. fx_sw->xstate_size can be changed from user-space, so it is possible construct a sigreturn frame where:

* fx_sw->xstate_size is smaller than the size required by valid bits in fx_sw->xfeatures. * user-space unmaps parts of the sigrame fpu buffer so that not all of the buffer required by xrstor is accessible.

In this case, xrstor tries to restore and accesses the unmapped area which results in a fault. But fault_in_readable succeeds because buf + fx_sw->xstate_size is within the still mapped area, so it goes back and tries xrstor again. It will spin in this loop forever.

Instead, fault in the maximum size which can be touched by XRSTOR (taken from fpstate->user_size).

[ dhansen: tweak subject / changelog ]

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • fcb3635f5018e53024c6be3c3213737f469f74ff to before 8bd3eee7720c14b59a206bd05b98d7586bccf99aAffected
  • fcb3635f5018e53024c6be3c3213737f469f74ff to before 627339cccdc9166792ecf96bc3c9f711a60ce996Affected
  • fcb3635f5018e53024c6be3c3213737f469f74ff to before b2479ab426cef7ab79a13005650eff956223ced2Affected
  • fcb3635f5018e53024c6be3c3213737f469f74ff to before 627e28cbb65564e55008315d9e02fbb90478bedaAffected
  • fcb3635f5018e53024c6be3c3213737f469f74ff to before d877550eaf2dc9090d782864c96939397a3c6835Affected
LinuxLinux
  • 5.14Affected
  • before 5.14Not affected
  • 5.15.150 through 5.15.*Not affected
  • 6.1.79 through 6.1.*Not affected
  • 6.6.18 through 6.6.*Not affected
  • 6.7.6 through 6.7.*Not affected
  • 6.8 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.