<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 16:32:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-35801 — x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-35801</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD&lt;/p&gt;
&lt;p&gt;Commit 672365477ae8 (&amp;#34;x86/fpu: Update XFD state where required&amp;#34;) and
commit 8bf26758ca96 (&amp;#34;x86/fpu: Add XFD state to fpstate&amp;#34;) introduced a
per CPU variable xfd_state to keep the MSR_IA32_XFD value cached, in
order to avoid unnecessary writes to the MSR.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD&lt;/p&gt;
&lt;p&gt;Commit 672365477ae8 (&amp;#34;x86/fpu: Update XFD state where required&amp;#34;) and
commit 8bf26758ca96 (&amp;#34;x86/fpu: Add XFD state to fpstate&amp;#34;) introduced a
per CPU variable xfd_state to keep the MSR_IA32_XFD value cached, in
order to avoid unnecessary writes to the MSR.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-35801</guid>
    </item>
  </channel>
</rss>
