<?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>Sun, 04 Oct 2026 09:03:24 +0000</lastBuildDate>
    <item>
      <title>bdu:2020-02415</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2020-02415</link>
      <description>bdu:2020-02415</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2020-02415</guid>
    </item>
    <item>
      <title>certfr-2020-avi-191 — De multiples vulnérabilités ont été découvertes dans le noyau Linux
d'Ubuntu. Elles permettent à un attaquant de provoq…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2020-avi-191</link>
      <description>certfr-2020-avi-191</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2020-avi-191</guid>
    </item>
    <item>
      <title>cnvd-2020-28054</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-28054</link>
      <description>cnvd-2020-28054</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-28054</guid>
    </item>
    <item>
      <title>EUVD-2026-173465</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-173465</link>
      <description>EUVD-2026-173465</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-173465</guid>
    </item>
    <item>
      <title>fkie_cve-2020-8834</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-8834</link>
      <description>&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;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/fkie_cve-2020-8834</guid>
    </item>
    <item>
      <title>GHSA-7fx7-755p-qmjj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7fx7-755p-qmjj</link>
      <description>&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;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/ghsa-7fx7-755p-qmjj</guid>
    </item>
    <item>
      <title>gsd-2020-8834</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-8834</link>
      <description>gsd-2020-8834</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-8834</guid>
    </item>
    <item>
      <title>openSUSE-SU-2020:0543-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2020:0543-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2020:0543-1</guid>
    </item>
    <item>
      <title>RHSA-2020:2854 — Red Hat Security Advisory: kernel-alt security and bug fix update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2020:2854</link>
      <description>&lt;p&gt;kernel: nfs: use-after-free in svc_process_common() kernel: use after free due to race condition in the video driver leads to local privilege escalation kernel: use-after-free in drivers/char/ipmi/ipmi_si_intf.c, ipmi_si_mem_io.c, ipmi_si_port_io.c kernel: use-after-free in drivers/bluetooth/hci_ldisc.c kernel: memory leak in ccp_run_sha_cmd() function in drivers/crypto/ccp/ccp-ops.c kernel: memory leak in the crypto_report() function in crypto/crypto_user_base.c allows for DoS kernel: use-after-free in __ext4_expand_extra_isize and ext4_xattr_set_entry related to fs/ext4/inode.c and fs/ext4/super.c kernel: out-of-bounds write via crafted keycode table Kernel: ppc: kvm: conflicting use of HSTATE_HOST_R1 to store r1 state leads to host stack corruption kernel: use-after-free read in napi_gro_frags() in the Linux kernel kernel: out-of-bounds write in mpol_parse_str function in mm/mempolicy.c Kernel: vfio: access to disabled MMIO space of some devices may lead to DoS scenario&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: nfs: use-after-free in svc_process_common() kernel: use after free due to race condition in the video driver leads to local privilege escalation kernel: use-after-free in drivers/char/ipmi/ipmi_si_intf.c, ipmi_si_mem_io.c, ipmi_si_port_io.c kernel: use-after-free in drivers/bluetooth/hci_ldisc.c kernel: memory leak in ccp_run_sha_cmd() function in drivers/crypto/ccp/ccp-ops.c kernel: memory leak in the crypto_report() function in crypto/crypto_user_base.c allows for DoS kernel: use-after-free in __ext4_expand_extra_isize and ext4_xattr_set_entry related to fs/ext4/inode.c and fs/ext4/super.c kernel: out-of-bounds write via crafted keycode table Kernel: ppc: kvm: conflicting use of HSTATE_HOST_R1 to store r1 state leads to host stack corruption kernel: use-after-free read in napi_gro_frags() in the Linux kernel kernel: out-of-bounds write in mpol_parse_str function in mm/mempolicy.c Kernel: vfio: access to disabled MMIO space of some devices may lead to DoS scenario&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2020:2854</guid>
    </item>
    <item>
      <title>SUSE-SU-2020:1084-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2020:1084-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2020:1084-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2020-8834</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-8834</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:FIPS:16.04:LTS: linux-fips, Ubuntu:18.04:LTS: linux, Ubuntu:Pro:FIPS-updates:18.04:LTS: linux-aws-fips, Ubuntu:Pro:FIPS-updates:18.04:LTS: linux-azure-fips, Ubuntu:Pro:FIPS-updates:18.04:LTS: linux-fips, Ubuntu:Pro:FIPS:18.04:LTS: linux-aws-fips, Ubuntu:Pro:FIPS:18.04:LTS: linux-azure-fips, Ubuntu:Pro:FIPS:18.04:LTS: linux-gcp-fips and 7 more&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; Ubuntu:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:FIPS:16.04:LTS: linux-fips, Ubuntu:18.04:LTS: linux, Ubuntu:Pro:FIPS-updates:18.04:LTS: linux-aws-fips, Ubuntu:Pro:FIPS-updates:18.04:LTS: linux-azure-fips, Ubuntu:Pro:FIPS-updates:18.04:LTS: linux-fips, Ubuntu:Pro:FIPS:18.04:LTS: linux-aws-fips, Ubuntu:Pro:FIPS:18.04:LTS: linux-azure-fips, Ubuntu:Pro:FIPS:18.04:LTS: linux-gcp-fips and 7 more&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/ubuntu-cve-2020-8834</guid>
    </item>
  </channel>
</rss>
