<?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://cve.radiocsirt.org</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 01:30:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-8834 — Linux kernel KVM Power8 conflicting use of  HSTATE_HOST_R1</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-8834</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux kernel&lt;/p&gt;
&lt;p&gt;KVM in the Linux kernel on Power8 processors has a conflicting use of HSTATE_HOST_R1 to store r1 state in kvmppc_hv_entry plus in kvmppc_{save,restore}_tm, leading to a stack corruption. Because of this, an attacker with the ability run code in kernel space of a guest VM can cause the host kernel to panic. There were two commits that, according to the reporter, introduced the vulnerability: f024ee098476 (&amp;#34;KVM: PPC: Book3S HV: Pull out TM state save/restore into separate procedures&amp;#34;) 87a11bb6a7f7 (&amp;#34;KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode&amp;#34;) The former landed in 4.8, the latter in 4.17. This was fixed without realizing the impact in 4.18 with the following three commits, though it&amp;#39;s believed the first is the only strictly necessary commit: 6f597c6b63b6 (&amp;#34;KVM: PPC: Book3S PR: Add guest MSR parameter for kvmppc_save_tm()/kvmppc_restore_tm()&amp;#34;) 7b0e827c6970 (&amp;#34;KVM: PPC: Book3S HV: Factor fake-suspend handling out of kvmppc_save/restore_tm&amp;#34;) 009c872a8bc4 (&amp;#34;KVM: PPC: Book3S PR: Move kvmppc_save_tm/kvmppc_restore_tm to separate file&amp;#34;)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux kernel&lt;/p&gt;
&lt;p&gt;KVM in the Linux kernel on Power8 processors has a conflicting use of HSTATE_HOST_R1 to store r1 state in kvmppc_hv_entry plus in kvmppc_{save,restore}_tm, leading to a stack corruption. Because of this, an attacker with the ability run code in kernel space of a guest VM can cause the host kernel to panic. There were two commits that, according to the reporter, introduced the vulnerability: f024ee098476 (&amp;#34;KVM: PPC: Book3S HV: Pull out TM state save/restore into separate procedures&amp;#34;) 87a11bb6a7f7 (&amp;#34;KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode&amp;#34;) The former landed in 4.8, the latter in 4.17. This was fixed without realizing the impact in 4.18 with the following three commits, though it&amp;#39;s believed the first is the only strictly necessary commit: 6f597c6b63b6 (&amp;#34;KVM: PPC: Book3S PR: Add guest MSR parameter for kvmppc_save_tm()/kvmppc_restore_tm()&amp;#34;) 7b0e827c6970 (&amp;#34;KVM: PPC: Book3S HV: Factor fake-suspend handling out of kvmppc_save/restore_tm&amp;#34;) 009c872a8bc4 (&amp;#34;KVM: PPC: Book3S PR: Move kvmppc_save_tm/kvmppc_restore_tm to separate file&amp;#34;)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-8834</guid>
    </item>
  </channel>
</rss>
