<?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>Sun, 04 Oct 2026 05:59:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47110 — x86/kvm: Disable kvmclock on all CPUs on shutdown</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2021-47110</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/kvm: Disable kvmclock on all CPUs on shutdown&lt;/p&gt;
&lt;p&gt;Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.&lt;/p&gt;
&lt;p&gt;Note, writing &amp;#39;0&amp;#39; to kvmclock MSR doesn&amp;#39;t clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don&amp;#39;t need to switch to some other clocksource.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/kvm: Disable kvmclock on all CPUs on shutdown&lt;/p&gt;
&lt;p&gt;Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.&lt;/p&gt;
&lt;p&gt;Note, writing &amp;#39;0&amp;#39; to kvmclock MSR doesn&amp;#39;t clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don&amp;#39;t need to switch to some other clocksource.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2021-47110</guid>
    </item>
  </channel>
</rss>
