<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 12:19:22 +0000</lastBuildDate>
    <item>
      <title>cnvd-2020-23021</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-23021</link>
      <description>cnvd-2020-23021</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-23021</guid>
    </item>
    <item>
      <title>EUVD-2026-67513</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-67513</link>
      <description>EUVD-2026-67513</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-67513</guid>
    </item>
    <item>
      <title>fkie_cve-2018-15470</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2018-15470</link>
      <description>&lt;p&gt;An issue was discovered in Xen through 4.11.x. The logic in oxenstored for handling writes depended on the order of evaluation of expressions making up a tuple. As indicated in section 7.7.3 &amp;#34;Operations on data structures&amp;#34; of the OCaml manual, the order of evaluation of subexpressions is not specified. In practice, different implementations behave differently. Thus, oxenstored may not enforce the configured quota-maxentity. This allows a malicious or buggy guest to write as many xenstore entries as it wishes, causing unbounded memory usage in oxenstored. This can lead to a system-wide DoS.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in Xen through 4.11.x. The logic in oxenstored for handling writes depended on the order of evaluation of expressions making up a tuple. As indicated in section 7.7.3 &amp;#34;Operations on data structures&amp;#34; of the OCaml manual, the order of evaluation of subexpressions is not specified. In practice, different implementations behave differently. Thus, oxenstored may not enforce the configured quota-maxentity. This allows a malicious or buggy guest to write as many xenstore entries as it wishes, causing unbounded memory usage in oxenstored. This can lead to a system-wide DoS.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2018-15470</guid>
    </item>
    <item>
      <title>GHSA-9xrv-h87m-r2vc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9xrv-h87m-r2vc</link>
      <description>&lt;p&gt;An issue was discovered in Xen through 4.11.x. The logic in oxenstored for handling writes depended on the order of evaluation of expressions making up a tuple. As indicated in section 7.7.3 &amp;#34;Operations on data structures&amp;#34; of the OCaml manual, the order of evaluation of subexpressions is not specified. In practice, different implementations behave differently. Thus, oxenstored may not enforce the configured quota-maxentity. This allows a malicious or buggy guest to write as many xenstore entries as it wishes, causing unbounded memory usage in oxenstored. This can lead to a system-wide DoS.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in Xen through 4.11.x. The logic in oxenstored for handling writes depended on the order of evaluation of expressions making up a tuple. As indicated in section 7.7.3 &amp;#34;Operations on data structures&amp;#34; of the OCaml manual, the order of evaluation of subexpressions is not specified. In practice, different implementations behave differently. Thus, oxenstored may not enforce the configured quota-maxentity. This allows a malicious or buggy guest to write as many xenstore entries as it wishes, causing unbounded memory usage in oxenstored. This can lead to a system-wide DoS.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9xrv-h87m-r2vc</guid>
    </item>
    <item>
      <title>gsd-2018-15470</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2018-15470</link>
      <description>gsd-2018-15470</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2018-15470</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:11520-1 — xen-4.15.1_01-1.2 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:11520-1</link>
      <description>&lt;p&gt;xen-4.15.1_01-1.2 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;xen-4.15.1_01-1.2 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:11520-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2018:3490-1 — Security update for xen</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2018:3490-1</link>
      <description>&lt;p&gt;Security update for xen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for xen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2018:3490-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2018-15470</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-15470</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen&lt;/p&gt;
&lt;p&gt;An issue was discovered in Xen through 4.11.x. The logic in oxenstored for handling writes depended on the order of evaluation of expressions making up a tuple. As indicated in section 7.7.3 &amp;#34;Operations on data structures&amp;#34; of the OCaml manual, the order of evaluation of subexpressions is not specified. In practice, different implementations behave differently. Thus, oxenstored may not enforce the configured quota-maxentity. This allows a malicious or buggy guest to write as many xenstore entries as it wishes, causing unbounded memory usage in oxenstored. This can lead to a system-wide DoS.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen&lt;/p&gt;
&lt;p&gt;An issue was discovered in Xen through 4.11.x. The logic in oxenstored for handling writes depended on the order of evaluation of expressions making up a tuple. As indicated in section 7.7.3 &amp;#34;Operations on data structures&amp;#34; of the OCaml manual, the order of evaluation of subexpressions is not specified. In practice, different implementations behave differently. Thus, oxenstored may not enforce the configured quota-maxentity. This allows a malicious or buggy guest to write as many xenstore entries as it wishes, causing unbounded memory usage in oxenstored. This can lead to a system-wide DoS.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-15470</guid>
    </item>
  </channel>
</rss>
