p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in qemu · Seite 4

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für qemu: 7. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 79

  1. CVE-2026-2243

    Mittel · CVSS 5.1EPSS 0,13%Keine Korrektur veröffentlicht

    Qemu-kvm: heap buffer out-of-bounds read in vmdk compressed grain parsing

    A flaw was found in QEMU. A specially crafted VMDK image could trigger an out-of-bounds read vulnerability, potentially leading to a 12-byte leak of sensitive information or a denial of service condition (DoS).

    Veröffentlicht Aktualisiert
  2. CVE-2024-8612

    Niedrig · CVSS 3.8EPSS 0,2%Keine Korrektur veröffentlicht

    Qemu-kvm: information leak in virtio devices

    A flaw was found in QEMU, in the virtio-scsi, virtio-blk, and virtio-crypto devices. The size for virtqueue_push as set in virtio_scsi_complete_req / virtio_blk_req_complete / virito_crypto_req_complete could be larger than the true size of the data which has been sent to guest. Once virtqueue_push() finally calls dma_memory_unmap to ummap the in_iov, it may call the address_space_write function to write back the data. Some uninitialized data may exist in the bounce.buffer, leading to an information leak.

    Veröffentlicht Aktualisiert
  3. CVE-2023-1386

    Niedrig · CVSS 3.3EPSS 0,24%Keine Korrektur veröffentlicht

    Qemu: 9pfs: suid/sgid bits not dropped on file write

    A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. When a local user in the guest writes an executable file with SUID or SGID, none of these privileged bits are correctly dropped. As a result, in rare circumstances, this flaw could be used by malicious users in the guest to elevate their privileges within the guest and help a host local user to elevate privileges on the host.

    Veröffentlicht Aktualisiert
  4. CVE-2022-3872

    Hoch · CVSS 8.6EPSS 0,91%Keine Korrektur veröffentlicht

    CVE-2022-3872

    An off-by-one read/write issue was found in the SDHCI device of QEMU. It occurs when reading/writing the Buffer Data Port Register in sdhci_read_dataport and sdhci_write_dataport, respectively, if data_count == block_size. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.

    Veröffentlicht Aktualisiert
  5. CVE-2021-3735

    Mittel · CVSS 4.4EPSS 0,21%Keine Korrektur veröffentlicht

    CVE-2021-3735

    A deadlock issue was found in the AHCI controller device of QEMU. It occurs on a software reset (ahci_reset_port) while handling a host-to-device Register FIS (Frame Information Structure) packet from the guest. A privileged user inside the guest could use this flaw to hang the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability.

    Veröffentlicht Aktualisiert
  6. CVE-2020-35503

    Mittel · CVSS 6EPSS 0,27%Keine Korrektur veröffentlicht

    CVE-2020-35503

    A NULL pointer dereference flaw was found in the megasas-gen2 SCSI host bus adapter emulation of QEMU in versions before and including 6.0. This issue occurs in the megasas_command_cancelled() callback function while dropping a SCSI request. This flaw allows a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.

    Veröffentlicht Aktualisiert
  7. CVE-2021-20255

    Mittel · CVSS 5.5EPSS 0,41%Keine Korrektur veröffentlicht

    CVE-2021-20255

    A stack overflow via an infinite recursion vulnerability was found in the eepro100 i8255x device emulator of QEMU. This issue occurs while processing controller commands due to a DMA reentry issue. This flaw allows a guest user or process to consume CPU cycles or crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →