Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26603x86/fpu: Stop relying on userspace for info to fault in xsave buffer

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 ]

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26603, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected fcb3635f5018e53024c6be3c3213737f469f74ff – < 8bd3eee7720c14b59a206bd05b98d7586bccf99a
    • affected fcb3635f5018e53024c6be3c3213737f469f74ff – < 627339cccdc9166792ecf96bc3c9f711a60ce996
    • affected fcb3635f5018e53024c6be3c3213737f469f74ff – < b2479ab426cef7ab79a13005650eff956223ced2
    • affected fcb3635f5018e53024c6be3c3213737f469f74ff – < 627e28cbb65564e55008315d9e02fbb90478beda
    • affected fcb3635f5018e53024c6be3c3213737f469f74ff – < d877550eaf2dc9090d782864c96939397a3c6835
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.150 – ≤ 5.15.*
    • unaffected 6.1.79 – ≤ 6.1.*
    • unaffected 6.6.18 – ≤ 6.6.*
    • unaffected 6.7.6 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26603 badge
[![CVE-2024-26603](https://cveledger.app/badge/CVE-2024-26603.svg)](https://cveledger.app/cve/CVE-2024-26603)

Record last updated .