Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2024-35801

5.5 · MEDIUM

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 8…

Published May 17, 2024CWE-416EPSS 0.24%

Overview

CVE-2024-35801 is a medium-severity vulnerability. It was published on May 17, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/10e4b5166df9ff7a2d5316138ca668b42d004422Refgit.kernel.org/stable/c/1acbca933313aa866e39996904c9aca4d435c4cdRefgit.kernel.org/stable/c/21c7c00dae55cb0e3810d5f9506b58f68475d41dRefgit.kernel.org/stable/c/92b0f04e937665bde5768f3fcc622dcce44413d8Refgit.kernel.org/stable/c/b61e3b7055ac6edee4be071c52f48c26472d2624Refgit.kernel.org/stable/c/10e4b5166df9ff7a2d5316138ca668b42d004422Refgit.kernel.org/stable/c/1acbca933313aa866e39996904c9aca4d435c4cdRefgit.kernel.org/stable/c/21c7c00dae55cb0e3810d5f9506b58f68475d41dRefgit.kernel.org/stable/c/92b0f04e937665bde5768f3fcc622dcce44413d8Refgit.kernel.org/stable/c/b61e3b7055ac6edee4be071c52f48c26472d2624

How CyberStrike helps

Frequently asked questions

What is CVE-2024-35801?

CVE-2024-35801 is a medium-severity vulnerability. It was published on May 17, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2024-35801?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2024-35801?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2024-35801?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-35801 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2024

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999