CVE-2024-26603: x86/fpu: Stop relying on userspace for info to fault in xsave buffer
First published: Sat Feb 24 2024(Updated: )
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 ]
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Linux kernel | >=5.14.0<5.15.150 | |
| Linux Linux kernel | >=5.16.0<6.1.79 | |
| Linux Linux kernel | >=6.2.0<6.6.18 | |
| Linux Linux kernel | >=6.7.0<6.7.6 | |
| redhat/kernel | <6.1.79 | 6.1.79 |
| redhat/kernel | <6.6.18 | 6.6.18 |
| redhat/kernel | <6.7.6 | 6.7.6 |
| redhat/kernel | <6.8 | 6.8 |
| debian/linux | 5.10.223-1 5.10.226-1 6.1.115-1 6.1.119-1 6.12.5-1 6.12.6-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/627339cccdc9166792ecf96bc3c9f711a60ce996
- https://git.kernel.org/stable/c/627e28cbb65564e55008315d9e02fbb90478beda
- https://git.kernel.org/stable/c/8bd3eee7720c14b59a206bd05b98d7586bccf99a
- https://git.kernel.org/stable/c/b2479ab426cef7ab79a13005650eff956223ced2
- https://git.kernel.org/stable/c/d877550eaf2dc9090d782864c96939397a3c6835
- https://launchpad.net/bugs/cve/CVE-2024-26603
- https://access.redhat.com/security/cve/CVE-2024-26603
- https://lore.kernel.org/linux-cve-announce/2024022415-CVE-2024-26603-42c2@gregkh/T/#u
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2265834
- https://access.redhat.com/errata/RHSA-2024:3618
- https://access.redhat.com/errata/RHSA-2024:3627
- https://access.redhat.com/errata/RHSA-2024:9315
- https://bugzilla.redhat.com/show_bug.cgi?id=2265833
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26603
- https://nvd.nist.gov/vuln/detail/CVE-2024-26603
- https://security-tracker.debian.org/tracker/CVE-2024-26603
- https://ubuntu.com/security/CVE-2024-26603
- https://git.kernel.org/linus/d877550eaf2dc9090d782864c96939397a3c6835
- agent/title
- agent/type
- agent/first-publish-date
- collector/epss-latest
- source/FIRST
- agent/epss
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/weakness
- agent/severity
- agent/remedy
- collector/launchpad-cve
- source/Launchpad
- agent/author
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-26603
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- collector/security-tracker-debian
- source/Debian
- collector/mitre-cve
- source/MITRE
- agent/event
- agent/description
- agent/softwarecombine
- agent/tags
- agent/last-modified-date
- agent/references
- agent/trending
- vendor/linux
- canonical/linux linux kernel
- version/linux linux kernel/5.14.0
- version/linux linux kernel/5.16.0
- version/linux linux kernel/6.2.0
- version/linux linux kernel/6.7.0
- package-manager/redhat
- package-manager/debian