https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 19 Oct 2026 10:44:47 +0000 https://cve.radiocsirt.org/vuln/certfr-2023-avi-0389 certfr-2023-avi-0389 https://cve.radiocsirt.org/vuln/certfr-2023-avi-0389 https://cve.radiocsirt.org/vuln/euvd-2026-211416 EUVD-2026-211416 https://cve.radiocsirt.org/vuln/euvd-2026-211416 https://cve.radiocsirt.org/vuln/fkie_cve-2022-42336 <p>Mishandling of guest SSBD selection on AMD hardware The current logic to set SSBD on AMD Family 17h and Hygon Family 18h processors requires that the setting of SSBD is coordinated at a core level, as the setting is shared between threads. Logic was introduced to keep track of how many threads require SSBD active in order to coordinate it, such logic relies on using a per-core counter of threads that have SSBD active. When running on the mentioned hardware, it&#39;s possible for a guest to under or overflow the thread counter, because each write to VIRT_SPEC_CTRL.SSBD by the guest gets propagated to the helper that does the per-core active accounting. Underflowing the counter causes the value to get saturated, and thus attempts for guests running on the same core to set SSBD won&#39;t have effect because the hypervisor assumes it&#39;s already active.</p> <p>Mishandling of guest SSBD selection on AMD hardware The current logic to set SSBD on AMD Family 17h and Hygon Family 18h processors requires that the setting of SSBD is coordinated at a core level, as the setting is shared between threads. Logic was introduced to keep track of how many threads require SSBD active in order to coordinate it, such logic relies on using a per-core counter of threads that have SSBD active. When running on the mentioned hardware, it&#39;s possible for a guest to under or overflow the thread counter, because each write to VIRT_SPEC_CTRL.SSBD by the guest gets propagated to the helper that does the per-core active accounting. Underflowing the counter causes the value to get saturated, and thus attempts for guests running on the same core to set SSBD won&#39;t have effect because the hypervisor assumes it&#39;s already active.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-42336 https://cve.radiocsirt.org/vuln/ghsa-79pv-m8fc-mhfj <p>Mishandling of guest SSBD selection on AMD hardware The current logic to set SSBD on AMD Family 17h and Hygon Family 18h processors requires that the setting of SSBD is coordinated at a core level, as the setting is shared between threads. Logic was introduced to keep track of how many threads require SSBD active in order to coordinate it, such logic relies on using a per-core counter of threads that have SSBD active. When running on the mentioned hardware, it&#39;s possible for a guest to under or overflow the thread counter, because each write to VIRT_SPEC_CTRL.SSBD by the guest gets propagated to the helper that does the per-core active accounting. Underflowing the counter causes the value to get saturated, and thus attempts for guests running on the same core to set SSBD won&#39;t have effect because the hypervisor assumes it&#39;s already active.</p> <p>Mishandling of guest SSBD selection on AMD hardware The current logic to set SSBD on AMD Family 17h and Hygon Family 18h processors requires that the setting of SSBD is coordinated at a core level, as the setting is shared between threads. Logic was introduced to keep track of how many threads require SSBD active in order to coordinate it, such logic relies on using a per-core counter of threads that have SSBD active. When running on the mentioned hardware, it&#39;s possible for a guest to under or overflow the thread counter, because each write to VIRT_SPEC_CTRL.SSBD by the guest gets propagated to the helper that does the per-core active accounting. Underflowing the counter causes the value to get saturated, and thus attempts for guests running on the same core to set SSBD won&#39;t have effect because the hypervisor assumes it&#39;s already active.</p> https://cve.radiocsirt.org/vuln/ghsa-79pv-m8fc-mhfj https://cve.radiocsirt.org/vuln/gsd-2022-42336 gsd-2022-42336 https://cve.radiocsirt.org/vuln/gsd-2022-42336 https://cve.radiocsirt.org/vuln/opensuse-su-2024:12959-1 <p>xen-4.17.1_04-1.1 on GA media</p> <p>xen-4.17.1_04-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:12959-1 https://cve.radiocsirt.org/vuln/suse-su-2023:2535-1 <p>Security update for xen</p> <p>Security update for xen</p> https://cve.radiocsirt.org/vuln/suse-su-2023:2535-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-42336 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen, Ubuntu:20.04:LTS: xen, Ubuntu:22.04:LTS: xen, Ubuntu:24.04:LTS: xen, Ubuntu:25.10: xen, Ubuntu:26.10: xen, Ubuntu:26.04:LTS: xen</p> <p>Mishandling of guest SSBD selection on AMD hardware The current logic to set SSBD on AMD Family 17h and Hygon Family 18h processors requires that the setting of SSBD is coordinated at a core level, as the setting is shared between threads. Logic was introduced to keep track of how many threads require SSBD active in order to coordinate it, such logic relies on using a per-core counter of threads that have SSBD active. When running on the mentioned hardware, it&#39;s possible for a guest to under or overflow the thread counter, because each write to VIRT_SPEC_CTRL.SSBD by the guest gets propagated to the helper that does the per-core active accounting. Underflowing the counter causes the value to get saturated, and thus attempts for guests running on the same core to set SSBD won&#39;t have effect because the hypervisor assumes it&#39;s already active.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen, Ubuntu:20.04:LTS: xen, Ubuntu:22.04:LTS: xen, Ubuntu:24.04:LTS: xen, Ubuntu:25.10: xen, Ubuntu:26.10: xen, Ubuntu:26.04:LTS: xen</p> <p>Mishandling of guest SSBD selection on AMD hardware The current logic to set SSBD on AMD Family 17h and Hygon Family 18h processors requires that the setting of SSBD is coordinated at a core level, as the setting is shared between threads. Logic was introduced to keep track of how many threads require SSBD active in order to coordinate it, such logic relies on using a per-core counter of threads that have SSBD active. When running on the mentioned hardware, it&#39;s possible for a guest to under or overflow the thread counter, because each write to VIRT_SPEC_CTRL.SSBD by the guest gets propagated to the helper that does the per-core active accounting. Underflowing the counter causes the value to get saturated, and thus attempts for guests running on the same core to set SSBD won&#39;t have effect because the hypervisor assumes it&#39;s already active.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-42336 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1234 <p>Ein lokaler Angreifer kann eine Schwachstelle in Xen ausnutzen, um falsche Informationen darzustellen.</p> <p>Ein lokaler Angreifer kann eine Schwachstelle in Xen ausnutzen, um falsche Informationen darzustellen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1234