https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T07:54:34.167070+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2020-02415 bdu:2020-02415 2026-10-04T07:54:34.328009+00:00 bdu:2020-02415 https://cve.radiocsirt.org/vuln/certfr-2020-avi-191 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… 2026-10-04T07:54:34.328064+00:00 certfr-2020-avi-191 https://cve.radiocsirt.org/vuln/cnvd-2020-28054 cnvd-2020-28054 2026-10-04T07:54:34.328084+00:00 cnvd-2020-28054 https://cve.radiocsirt.org/vuln/euvd-2026-173465 EUVD-2026-173465 2026-10-04T07:54:34.328097+00:00 EUVD-2026-173465 https://cve.radiocsirt.org/vuln/fkie_cve-2020-8834 fkie_cve-2020-8834 2026-10-04T07:54:34.328108+00:00

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 ("KVM: PPC: Book3S HV: Pull out TM state save/restore into separate procedures") 87a11bb6a7f7 ("KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode") 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's believed the first is the only strictly necessary commit: 6f597c6b63b6 ("KVM: PPC: Book3S PR: Add guest MSR parameter for kvmppc_save_tm()/kvmppc_restore_tm()") 7b0e827c6970 ("KVM: PPC: Book3S HV: Factor fake-suspend handling out of kvmppc_save/restore_tm") 009c872a8bc4 ("KVM: PPC: Book3S PR: Move kvmppc_save_tm/kvmppc_restore_tm to separate file")

 https://cve.radiocsirt.org/vuln/ghsa-7fx7-755p-qmjj GHSA-7fx7-755p-qmjj 2026-10-04T07:54:34.328145+00:00

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 ("KVM: PPC: Book3S HV: Pull out TM state save/restore into separate procedures") 87a11bb6a7f7 ("KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode") 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's believed the first is the only strictly necessary commit: 6f597c6b63b6 ("KVM: PPC: Book3S PR: Add guest MSR parameter for kvmppc_save_tm()/kvmppc_restore_tm()") 7b0e827c6970 ("KVM: PPC: Book3S HV: Factor fake-suspend handling out of kvmppc_save/restore_tm") 009c872a8bc4 ("KVM: PPC: Book3S PR: Move kvmppc_save_tm/kvmppc_restore_tm to separate file")

 https://cve.radiocsirt.org/vuln/gsd-2020-8834 gsd-2020-8834 2026-10-04T07:54:34.328168+00:00 gsd-2020-8834 https://cve.radiocsirt.org/vuln/opensuse-su-2020:0543-1 openSUSE-SU-2020:0543-1 — Security update for the Linux Kernel 2026-10-04T07:54:34.328180+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/rhsa-2020:2854 RHSA-2020:2854 — Red Hat Security Advisory: kernel-alt security and bug fix update 2026-10-04T07:54:34.328202+00:00

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

 https://cve.radiocsirt.org/vuln/suse-su-2020:1084-1 SUSE-SU-2020:1084-1 — Security update for the Linux Kernel 2026-10-04T07:54:34.328239+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-8834 UBUNTU-CVE-2020-8834 2026-10-04T07:54:34.328259+00:00

Affected: 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

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 ("KVM: PPC: Book3S HV: Pull out TM state save/restore into separate procedures") 87a11bb6a7f7 ("KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode") 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's believed the first is the only strictly necessary commit: 6f597c6b63b6 ("KVM: PPC: Book3S PR: Add guest MSR parameter for kvmppc_save_tm()/kvmppc_restore_tm()") 7b0e827c6970 ("KVM: PPC: Book3S HV: Factor fake-suspend handling out of kvmppc_save/restore_tm") 009c872a8bc4 ("KVM: PPC: Book3S PR: Move kvmppc_save_tm/kvmppc_restore_tm to separate file")