<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T22:36:02.135105+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2025-11234</id>
    <title>CVE-2025-11234 — Qemu-kvm: vnc websocket handshake use-after-free</title>
    <updated>2026-11-21T22:36:02.138207+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> qemu, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On, Red Hat Enterprise Linux 8.8 Telecommunications Update Service, Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions, Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions and 7 more</p>
<p>A flaw was found in QEMU. If the QIOChannelWebsock object is freed while it is waiting to complete a handshake, a GSource is leaked. This can lead to the callback firing later on and triggering a use-after-free in the use of the channel. This can be abused by a malicious client with network access to the VNC WebSocket port to cause a denial of service during the WebSocket handshake prior to the VNC client authentication.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2025-11234"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-8073-1</id>
    <title>USN-8073-1 — qemu vulnerabilities</title>
    <updated>2026-11-21T22:36:02.138301+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: qemu, Ubuntu:24.04:LTS: qemu, Ubuntu:25.10: qemu</p>
<p>It was discovered that the UHCI controller implementation of QEMU could be
brought into an invalid state. An attacker inside the guest could possibly
use this issue to cause QEMU to crash, resulting in a denial of service.
(CVE-2024-8354)</p>
<p>It was discovered that QEMU incorrectly handled memory during certain VNC
operations. An remote attacker could possibly use this issue to cause QEMU
to crash, resulting in a denial of service, or possibly execute arbitrary
code. (CVE-2025-11234)</p>
<p>It was discovered that the e1000 network device implementation of QEMU
could be made to write out of bounds. An attacker inside the guest could
possibly use this issue to cause QEMU to crash, resulting in a denial of
service, or possibly execute arbitrary code. This issue only affected
Ubuntu 24.04 LTS and Ubuntu 25.10. (CVE-2025-12464)</p>
<p>It was discovered that the virtio-crypto device implementation of QEMU did
not limit the length of a certain path input. An attacker inside the guest
could possibly use this issue to cause QEMU to consume large amount of
memory, resulting in a denial of service. This issue only affected Ubuntu
24.04 LTS and Ubuntu 25.10. (CVE-2025-14876)</p>
<p>It was discovered that the KVM Xen guest support of QEMU could be made to
read out of bounds. An attacker inside the guest could possibly use this
issue to cause QEMU to crash, resulting in a denial of service. This issue
only affected Ubuntu 24.04 LTS and Ubuntu 25.10. (CVE-2026-0665)</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-8073-1"/>
  </entry>
</feed>
