CVE-2024-26603: Linux kernel · x86/fpu: Stop relying on userspace for info to fault in xsave buffer
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1063.69~20.04.1 : update Linux kernel when convenient.
Data as of 12 Nov 2026, 18:50 UTC
- Patch
- Available – fixed in 5.15.0-1063.69~20.04.1, 5.15.0-1065.74~20.04.1, 5.15.0-1062.70~20.04.1 +42
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6820-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6828-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6820-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6871-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6892-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6895-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6895-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6900-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu Pro Realtime 24.04 LTSlinux-raspi-realtimepkg:deb/ubuntu/linux-raspi-realtime?arch=source&distro=realtime/nobleOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=jammyOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinux-allwinner-5.19pkg:deb/ubuntu/linux-allwinner-5.19?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=jammyOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinux-aws-5.19pkg:deb/ubuntu/linux-aws-5.19?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlinux-aws-6.2pkg:deb/ubuntu/linux-aws-6.2?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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 ]
References
- ubuntu.com/security/CVE-2024-26603 (opens in a new tab)
- git.kernel.org/linus/d877550eaf2dc9090d782864c96939397a3c6835 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-26603 (opens in a new tab)
- ubuntu.com/security/notices/USN-6820-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6828-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6820-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6871-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6892-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6895-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6895-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6900-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6895-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6919-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6895-4 (opens in a new tab)