Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-35801: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 10e4b5166df9ff7a2d5316138ca668b42d004422, 1acbca933313aa866e39996904c9aca4d435c4cd, 21c7c00dae55cb0e3810d5f9506b58f68475d41d; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1.

Low priority for now. Upgrade to Linux Linux 10e4b5166df9ff7a2d5316138ca668b42d004422, 1acbca933313aa866e39996904c9aca4d435c4cd, 21c7c00dae55cb0e3810d5f9506b58f68475d41d; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD Commit 672365477ae8 ("x86/fpu: Update XFD state where required") and commit 8bf26758ca96 ("x86/fpu: Add XFD state to fpstate") introduced a per CPU variable xfd_state to keep the MSR_IA32_XFD value cached, in order to avoid unnecessary writes to the MSR. On CPU hotplug MSR_IA32_XFD is reset to the init_fpstate.xfd, which wipes out any stale state. But the per CPU cached xfd value is not reset, which brings them out of sync. As a consequence a subsequent xfd_update_state() might fail to update the MSR which in turn can result in XRSTOR raising a #NM in kernel space, which crashes the kernel. To fix this, introduce xfd_set_state() to write xfd_state together with MSR_IA32_XFD, and use it in all places that set MSR_IA32_XFD.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 17, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-35801

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.16 and later · before 6.1.84
  • linux linux kernel6.2 and later · before 6.6.24
  • linux linux kernel6.7 and later · before 6.7.12
  • linux linux kernel6.8 and later · before 6.8.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.16affected
    • 672365477ae8afca5a1cca98c1deb733235e4525 and later · before 21c7c00dae55cb0e3810d5f9506b58f68475d41daffected · git
    • 672365477ae8afca5a1cca98c1deb733235e4525 and later · before 1acbca933313aa866e39996904c9aca4d435c4cdaffected · git
    • 672365477ae8afca5a1cca98c1deb733235e4525 and later · before 92b0f04e937665bde5768f3fcc622dcce44413d8affected · git
    • 672365477ae8afca5a1cca98c1deb733235e4525 and later · before b61e3b7055ac6edee4be071c52f48c26472d2624affected · git
    • 672365477ae8afca5a1cca98c1deb733235e4525 and later · before 10e4b5166df9ff7a2d5316138ca668b42d004422affected · git
    • before 5.16not affected · semver
    • 6.1.84 and later · up to and including 6.1.*not affected · semver
    • 6.6.24 and later · up to and including 6.6.*not affected · semver
    • 6.7.12 and later · up to and including 6.7.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.85-16.1.85-1
Debian:13linuxbefore 6.7.12-16.7.12-1
Red Hat:rhel_eus:9.4::appstreambpftool-debuginfobefore 0:7.3.0-427.59.1.el9_40:7.3.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-develbefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-develbefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfobefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-develbefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-devel-matchedbefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-docbefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debuginfobefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-tools-debuginfobefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-427.59.1.el9_40:5.14.0-427.59.1.el9_4

+56

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35799May 17, 2024 · drm/amd/display: Prevent crash when disable stream
    22Monitor
  • ← EarlierCVE-2024-35800May 17, 2024 · efi: fix panic in kdump kernel
    22Monitor
  • Later →CVE-2024-35803May 17, 2024 · x86/efistub: Call mixed mode boot services on the firmware's stack
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux10e4b5166df9ff7a2d5316138ca668b42d004422Vendor (CNA)
Linux Linux1acbca933313aa866e39996904c9aca4d435c4cdVendor (CNA)
Linux Linux21c7c00dae55cb0e3810d5f9506b58f68475d41dVendor (CNA)
Linux Linux92b0f04e937665bde5768f3fcc622dcce44413d8Vendor (CNA)
Linux Linuxb61e3b7055ac6edee4be071c52f48c26472d2624Vendor (CNA)
azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.06.6.35.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.06.6.35.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.59.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records