https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T03:29:16.544326+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2020-01431 bdu:2020-01431 2026-10-03T03:29:16.758862+00:00 bdu:2020-01431 https://cve.radiocsirt.org/vuln/certfr-2019-avi-628 certfr-2019-avi-628 — De multiples vulnérabilités ont été découvertes dans Xen. Elles permettent à un attaquant de provoquer un déni de servi… 2026-10-03T03:29:16.758904+00:00 certfr-2019-avi-628 https://cve.radiocsirt.org/vuln/cnvd-2020-07293 cnvd-2020-07293 2026-10-03T03:29:16.758924+00:00 cnvd-2020-07293 https://cve.radiocsirt.org/vuln/euvd-2026-59374 EUVD-2026-59374 2026-10-03T03:29:16.758937+00:00 EUVD-2026-59374 https://cve.radiocsirt.org/vuln/fkie_cve-2019-19583 fkie_cve-2019-19583 2026-10-03T03:29:16.758948+00:00

An issue was discovered in Xen through 4.12.x allowing x86 HVM/PVH guest OS users to cause a denial of service (guest OS crash) because VMX VMEntry checks mishandle a certain case. Please see XSA-260 for background on the MovSS shadow. Please see XSA-156 for background on the need for #DB interception. The VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Stepping is active, and blocked by STI/MovSS is active, despite this being a legitimate state to be in. The resulting VMEntry failure is fatal to the guest. HVM/PVH guest userspace code may be able to crash the guest, resulting in a guest Denial of Service. All versions of Xen are affected. Only systems supporting VMX hardware virtual extensions (Intel, Cyrix, or Zhaoxin CPUs) are affected. Arm and AMD systems are unaffected. Only HVM/PVH guests are affected. PV guests cannot leverage the vulnerability.

 https://cve.radiocsirt.org/vuln/ghsa-5g75-j346-c9xj GHSA-5g75-j346-c9xj 2026-10-03T03:29:16.758979+00:00

An issue was discovered in Xen through 4.12.x allowing x86 HVM/PVH guest OS users to cause a denial of service (guest OS crash) because VMX VMEntry checks mishandle a certain case. Please see XSA-260 for background on the MovSS shadow. Please see XSA-156 for background on the need for #DB interception. The VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Stepping is active, and blocked by STI/MovSS is active, despite this being a legitimate state to be in. The resulting VMEntry failure is fatal to the guest. HVM/PVH guest userspace code may be able to crash the guest, resulting in a guest Denial of Service. All versions of Xen are affected. Only systems supporting VMX hardware virtual extensions (Intel, Cyrix, or Zhaoxin CPUs) are affected. Arm and AMD systems are unaffected. Only HVM/PVH guests are affected. PV guests cannot leverage the vulnerability.

 https://cve.radiocsirt.org/vuln/gsd-2019-19583 gsd-2019-19583 2026-10-03T03:29:16.758999+00:00 gsd-2019-19583 https://cve.radiocsirt.org/vuln/opensuse-su-2020:0011-1 openSUSE-SU-2020:0011-1 — Security update for xen 2026-10-03T03:29:16.759010+00:00

Security update for xen

 https://cve.radiocsirt.org/vuln/suse-su-2019:3296-1 SUSE-SU-2019:3296-1 — Security update for xen 2026-10-03T03:29:16.759031+00:00

Security update for xen

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-19583 UBUNTU-CVE-2019-19583 2026-10-03T03:29:16.759048+00:00

Affected: Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen

An issue was discovered in Xen through 4.12.x allowing x86 HVM/PVH guest OS users to cause a denial of service (guest OS crash) because VMX VMEntry checks mishandle a certain case. Please see XSA-260 for background on the MovSS shadow. Please see XSA-156 for background on the need for #DB interception. The VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Stepping is active, and blocked by STI/MovSS is active, despite this being a legitimate state to be in. The resulting VMEntry failure is fatal to the guest. HVM/PVH guest userspace code may be able to crash the guest, resulting in a guest Denial of Service. All versions of Xen are affected. Only systems supporting VMX hardware virtual extensions (Intel, Cyrix, or Zhaoxin CPUs) are affected. Arm and AMD systems are unaffected. Only HVM/PVH guests are affected. PV guests cannot leverage the vulnerability.