<?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>Thu, 08 Oct 2026 01:44:44 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07318</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07318</link>
      <description>bdu:2024-07318</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07318</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2022-2962 — CVE-2022-2962 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2022-2962</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2022-2962</guid>
    </item>
    <item>
      <title>certfr-2023-avi-0318 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;VMware&lt;/span&gt;. Elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2023-avi-0318</link>
      <description>certfr-2023-avi-0318</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2023-avi-0318</guid>
    </item>
    <item>
      <title>EUVD-2026-233718</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233718</link>
      <description>EUVD-2026-233718</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233718</guid>
    </item>
    <item>
      <title>fkie_cve-2022-2962</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-2962</link>
      <description>&lt;p&gt;A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn&amp;#39;t check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly leading to a stack or heap overflow. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn&amp;#39;t check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly leading to a stack or heap overflow. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-2962</guid>
    </item>
    <item>
      <title>GHSA-wmwv-5vwp-c54w</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wmwv-5vwp-c54w</link>
      <description>&lt;p&gt;A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn&amp;#39;t check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly leading to a stack or heap overflow. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn&amp;#39;t check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly leading to a stack or heap overflow. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wmwv-5vwp-c54w</guid>
    </item>
    <item>
      <title>gsd-2022-2962</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-2962</link>
      <description>gsd-2022-2962</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-2962</guid>
    </item>
    <item>
      <title>msrc_CVE-2022-2962 — A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descrip…</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2022-2962</link>
      <description>msrc_CVE-2022-2962</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2022-2962</guid>
    </item>
    <item>
      <title>OESA-2022-1997 — qemu security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2022-1997</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS: qemu&lt;/p&gt;
&lt;p&gt;QEMU is a FAST! processor emulator using dynamic translation to achieve good emulation speed.&lt;/p&gt;
&lt;p&gt;QEMU has two operating modes:&lt;/p&gt;
&lt;p&gt;Full system emulation. In this mode, QEMU emulates a full system (for example a PC),
		including one or several processors and various peripherals. It can be used to launch
		different Operating Systems without rebooting the PC or to debug system code.&lt;/p&gt;
&lt;p&gt;User mode emulation. In this mode, QEMU can launch processes compiled for one CPU on another CPU.
		It can be used to launch the Wine Windows API emulator (https://www.winehq.org) or to ease
		cross-compilation and cross-debugging.
		You can refer to https://www.qemu.org for more infortmation.&#13;
&#13;
Security Fix(es):&#13;
&#13;
An out-of-bounds memory access flaw was found in the ATI VGA device emulation of QEMU. This flaw occurs in the ati_2d_blt() routine while handling MMIO write operations when the guest provides invalid values for the destination display parameters. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service.(CVE-2021-3638)&#13;
&#13;
A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn&amp;amp;apos;t check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly leading to a stack or heap overflow. A malicious guest could use this flaw to crash the QEMU process on the host…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS: qemu&lt;/p&gt;
&lt;p&gt;QEMU is a FAST! processor emulator using dynamic translation to achieve good emulation speed.&lt;/p&gt;
&lt;p&gt;QEMU has two operating modes:&lt;/p&gt;
&lt;p&gt;Full system emulation. In this mode, QEMU emulates a full system (for example a PC),
		including one or several processors and various peripherals. It can be used to launch
		different Operating Systems without rebooting the PC or to debug system code.&lt;/p&gt;
&lt;p&gt;User mode emulation. In this mode, QEMU can launch processes compiled for one CPU on another CPU.
		It can be used to launch the Wine Windows API emulator (https://www.winehq.org) or to ease
		cross-compilation and cross-debugging.
		You can refer to https://www.qemu.org for more infortmation.&#13;
&#13;
Security Fix(es):&#13;
&#13;
An out-of-bounds memory access flaw was found in the ATI VGA device emulation of QEMU. This flaw occurs in the ati_2d_blt() routine while handling MMIO write operations when the guest provides invalid values for the destination display parameters. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service.(CVE-2021-3638)&#13;
&#13;
A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn&amp;amp;apos;t check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly leading to a stack or heap overflow. A malicious guest could use this flaw to crash the QEMU process on the host…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2022-1997</guid>
    </item>
    <item>
      <title>WID-SEC-W-2022-1158 — QEMU: Schwachstelle ermöglicht Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1158</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in QEMU ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in QEMU ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1158</guid>
    </item>
  </channel>
</rss>
