https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:17:56 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-03584 bdu:2024-03584 https://cve.radiocsirt.org/vuln/bdu:2024-03584 https://cve.radiocsirt.org/vuln/certfr-2022-avi-974 certfr-2022-avi-974 https://cve.radiocsirt.org/vuln/certfr-2022-avi-974 https://cve.radiocsirt.org/vuln/euvd-2026-237702 EUVD-2026-237702 https://cve.radiocsirt.org/vuln/euvd-2026-237702 https://cve.radiocsirt.org/vuln/fkie_cve-2022-42316 <p>Xenstore: guests can let run xenstored out of memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Malicious guests can cause xenstored to allocate vast amounts of memory, eventually resulting in a Denial of Service (DoS) of xenstored. There are multiple ways how guests can cause large memory allocations in xenstored: - - by issuing new requests to xenstored without reading the responses, causing the responses to be buffered in memory - - by causing large number of watch events to be generated via setting up multiple xenstore watches and then e.g. deleting many xenstore nodes below the watched path - - by creating as many nodes as allowed with the maximum allowed size and path length in as many transactions as possible - - by accessing many nodes inside a transaction</p> <p>Xenstore: guests can let run xenstored out of memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Malicious guests can cause xenstored to allocate vast amounts of memory, eventually resulting in a Denial of Service (DoS) of xenstored. There are multiple ways how guests can cause large memory allocations in xenstored: - - by issuing new requests to xenstored without reading the responses, causing the responses to be buffered in memory - - by causing large number of watch events to be generated via setting up multiple xenstore watches and then e.g. deleting many xenstore nodes below the watched path - - by creating as many nodes as allowed with the maximum allowed size and path length in as many transactions as possible - - by accessing many nodes inside a transaction</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-42316 https://cve.radiocsirt.org/vuln/ghsa-xxpf-x8mq-p6v4 <p>Xenstore: guests can let run xenstored out of memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Malicious guests can cause xenstored to allocate vast amounts of memory, eventually resulting in a Denial of Service (DoS) of xenstored. There are multiple ways how guests can cause large memory allocations in xenstored: - - by issuing new requests to xenstored without reading the responses, causing the responses to be buffered in memory - - by causing large number of watch events to be generated via setting up multiple xenstore watches and then e.g. deleting many xenstore nodes below the watched path - - by creating as many nodes as allowed with the maximum allowed size and path length in as many transactions as possible - - by accessing many nodes inside a transaction</p> <p>Xenstore: guests can let run xenstored out of memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Malicious guests can cause xenstored to allocate vast amounts of memory, eventually resulting in a Denial of Service (DoS) of xenstored. There are multiple ways how guests can cause large memory allocations in xenstored: - - by issuing new requests to xenstored without reading the responses, causing the responses to be buffered in memory - - by causing large number of watch events to be generated via setting up multiple xenstore watches and then e.g. deleting many xenstore nodes below the watched path - - by creating as many nodes as allowed with the maximum allowed size and path length in as many transactions as possible - - by accessing many nodes inside a transaction</p> https://cve.radiocsirt.org/vuln/ghsa-xxpf-x8mq-p6v4 https://cve.radiocsirt.org/vuln/gsd-2022-42316 gsd-2022-42316 https://cve.radiocsirt.org/vuln/gsd-2022-42316 https://cve.radiocsirt.org/vuln/suse-su-2022:3925-1 <p>Security update for xen</p> <p>Security update for xen</p> https://cve.radiocsirt.org/vuln/suse-su-2022:3925-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-42316 <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.04:LTS: xen</p> <p>Xenstore: guests can let run xenstored out of memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Malicious guests can cause xenstored to allocate vast amounts of memory, eventually resulting in a Denial of Service (DoS) of xenstored. There are multiple ways how guests can cause large memory allocations in xenstored: - - by issuing new requests to xenstored without reading the responses, causing the responses to be buffered in memory - - by causing large number of watch events to be generated via setting up multiple xenstore watches and then e.g. deleting many xenstore nodes below the watched path - - by creating as many nodes as allowed with the maximum allowed size and path length in as many transactions as possible - - by accessing many nodes inside a transaction</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.04:LTS: xen</p> <p>Xenstore: guests can let run xenstored out of memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Malicious guests can cause xenstored to allocate vast amounts of memory, eventually resulting in a Denial of Service (DoS) of xenstored. There are multiple ways how guests can cause large memory allocations in xenstored: - - by issuing new requests to xenstored without reading the responses, causing the responses to be buffered in memory - - by causing large number of watch events to be generated via setting up multiple xenstore watches and then e.g. deleting many xenstore nodes below the watched path - - by creating as many nodes as allowed with the maximum allowed size and path length in as many transactions as possible - - by accessing many nodes inside a transaction</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-42316 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1939 <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Xen und Citrix Systems Hypervisor ausnutzen um einen Denial of Service zu verursachen, Informationen offenzulegen oder seine Rechte zu erweitern.</p> <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Xen und Citrix Systems Hypervisor ausnutzen um einen Denial of Service zu verursachen, Informationen offenzulegen oder seine Rechte zu erweitern.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1939