https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 18:23:11 +0000 https://cve.radiocsirt.org/vuln/certfr-2020-avi-205 certfr-2020-avi-205 https://cve.radiocsirt.org/vuln/certfr-2020-avi-205 https://cve.radiocsirt.org/vuln/cnvd-2020-32853 cnvd-2020-32853 https://cve.radiocsirt.org/vuln/cnvd-2020-32853 https://cve.radiocsirt.org/vuln/euvd-2026-40789 EUVD-2026-40789 https://cve.radiocsirt.org/vuln/euvd-2026-40789 https://cve.radiocsirt.org/vuln/fkie_cve-2020-11741 <p>An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (with active profiling) to obtain sensitive information about other guests, cause a denial of service, or possibly gain privileges. For guests for which &#34;active&#34; profiling was enabled by the administrator, the xenoprof code uses the standard Xen shared ring structure. Unfortunately, this code did not treat the guest as a potential adversary: it trusts the guest not to modify buffer size information or modify head / tail pointers in unexpected ways. This can crash the host (DoS). Privilege escalation cannot be ruled out.</p> <p>An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (with active profiling) to obtain sensitive information about other guests, cause a denial of service, or possibly gain privileges. For guests for which &#34;active&#34; profiling was enabled by the administrator, the xenoprof code uses the standard Xen shared ring structure. Unfortunately, this code did not treat the guest as a potential adversary: it trusts the guest not to modify buffer size information or modify head / tail pointers in unexpected ways. This can crash the host (DoS). Privilege escalation cannot be ruled out.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-11741 https://cve.radiocsirt.org/vuln/ghsa-xqc2-qqq8-xfj5 <p>An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (with active profiling) to obtain sensitive information about other guests, cause a denial of service, or possibly gain privileges. For guests for which &#34;active&#34; profiling was enabled by the administrator, the xenoprof code uses the standard Xen shared ring structure. Unfortunately, this code did not treat the guest as a potential adversary: it trusts the guest not to modify buffer size information or modify head / tail pointers in unexpected ways. This can crash the host (DoS). Privilege escalation cannot be ruled out.</p> <p>An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (with active profiling) to obtain sensitive information about other guests, cause a denial of service, or possibly gain privileges. For guests for which &#34;active&#34; profiling was enabled by the administrator, the xenoprof code uses the standard Xen shared ring structure. Unfortunately, this code did not treat the guest as a potential adversary: it trusts the guest not to modify buffer size information or modify head / tail pointers in unexpected ways. This can crash the host (DoS). Privilege escalation cannot be ruled out.</p> https://cve.radiocsirt.org/vuln/ghsa-xqc2-qqq8-xfj5 https://cve.radiocsirt.org/vuln/gsd-2020-11741 gsd-2020-11741 https://cve.radiocsirt.org/vuln/gsd-2020-11741 https://cve.radiocsirt.org/vuln/opensuse-su-2020:0599-1 <p>Security update for xen</p> <p>Security update for xen</p> https://cve.radiocsirt.org/vuln/opensuse-su-2020:0599-1 https://cve.radiocsirt.org/vuln/suse-su-2020:1124-1 <p>Security update for xen</p> <p>Security update for xen</p> https://cve.radiocsirt.org/vuln/suse-su-2020:1124-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-11741 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen, Ubuntu:20.04:LTS: xen</p> <p>An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (with active profiling) to obtain sensitive information about other guests, cause a denial of service, or possibly gain privileges. For guests for which &#34;active&#34; profiling was enabled by the administrator, the xenoprof code uses the standard Xen shared ring structure. Unfortunately, this code did not treat the guest as a potential adversary: it trusts the guest not to modify buffer size information or modify head / tail pointers in unexpected ways. This can crash the host (DoS). Privilege escalation cannot be ruled out.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen, Ubuntu:20.04:LTS: xen</p> <p>An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (with active profiling) to obtain sensitive information about other guests, cause a denial of service, or possibly gain privileges. For guests for which &#34;active&#34; profiling was enabled by the administrator, the xenoprof code uses the standard Xen shared ring structure. Unfortunately, this code did not treat the guest as a potential adversary: it trusts the guest not to modify buffer size information or modify head / tail pointers in unexpected ways. This can crash the host (DoS). Privilege escalation cannot be ruled out.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-11741