Skip to content
Fencer Vulns
medium 5.5

CVE-2023-42467 json

QEMU through 8.0.0 could trigger a division by zero in scsi_disk_reset in hw/scsi/scsi-disk.c because scsi_disk_emulate_mode_select does no…

published 2023-09-11 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-46907

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

QEMU through 8.0.0 could trigger a division by zero in scsi_disk_reset in hw/scsi/scsi-disk.c because scsi_disk_emulate_mode_select does not prevent s->qdev.blocksize from being 256. This stops QEMU and the guest immediately.

Patch / fix

  • qemu Debian 12 1:7.2+dfsg-7+deb12u3
  • qemu Debian 14, Debian 13 1:8.1.1+ds-1

debian advisories DEBIAN-CVE-2023-42467

  • qemu-kvm RHEL 9 17:8.2.0-11.el9_4
  • qemu-img RHEL 9 17:8.2.0-11.el9_4
  • qemu-kvm-core RHEL 9 17:8.2.0-11.el9_4
  • qemu-kvm-tools RHEL 9 17:8.2.0-11.el9_4
  • qemu-pr-helper RHEL 9 17:8.2.0-11.el9_4
  • qemu-kvm-common RHEL 9 17:8.2.0-11.el9_4
  • qemu-guest-agent RHEL 9 17:8.2.0-11.el9_4
  • qemu-kvm-audio-pa RHEL 9 17:8.2.0-11.el9_4

red hat advisories RHSA-2024:2135

  • qemu SLE Micro 5.5 7.1.0-150500.49.30.1

suse advisories SUSE-SU-2025:0516-1

  • qemu openSUSE Tumbleweed 8.1.2-1.1

opensuse advisories openSUSE-SU-2024:13364-1

  • qemu-kvm AlmaLinux 9 17:8.2.0-11.el9_4
  • qemu-img AlmaLinux 9 17:8.2.0-11.el9_4
  • qemu-kvm-core AlmaLinux 9 17:8.2.0-11.el9_4
  • qemu-kvm-tools AlmaLinux 9 17:8.2.0-11.el9_4
  • qemu-pr-helper AlmaLinux 9 17:8.2.0-11.el9_4
  • qemu-kvm-common AlmaLinux 9 17:8.2.0-11.el9_4
  • qemu-guest-agent AlmaLinux 9 17:8.2.0-11.el9_4
  • qemu-kvm-audio-pa AlmaLinux 9 17:8.2.0-11.el9_4

almalinux advisories ALSA-2024:2135

  • qemu-kvm Rocky Linux 9 7:8.2.0-11.el9_4

rocky linux advisories RLSA-2024:2135

  • qemu Azure Linux 3.0 8.2.0-1

azure linux advisories AZL-35172

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-42467 updated cvss 2.3

QEMU: am53c974: denial of service due to division by zero

  • Red Hat Enterprise Linux 8 Advanced Virtualization qemu-img, qemu-kvm, qemu-kiwi, qemu-kvm-core, qemu-kvm-tests, qemu-kvm-common, +9 more
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux AppStream (v. 9) qemu-img 8.2.0-11.el9_4, qemu-kvm 8.2.0-11.el9_4, qemu-kvm-core 8.2.0-11.el9_4, qemu-kvm-tools 8.2.0-11.el9_4, qemu-pr-helper 8.2.0-11.el9_4, qemu-kvm-common 8.2.0-11.el9_4, +13 more
    fixed: vendor fix RHSA-2024:2135
  • Red Hat Enterprise Linux 6 qemu-img, qemu-kvm, qemu-kvm-tools, qemu-guest-agent, qemu-guest-agent-win32 Red Hat Enterprise Linux 7 qemu-img, qemu-kvm, libcacard, qemu-img-ma, qemu-kvm-ma, qemu-kvm-tools, +5 more Red Hat Enterprise Linux 8 qemu-img, qemu-kvm, qemu-kvm-core, qemu-kvm-tests, qemu-kvm-common, qemu-guest-agent, +8 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • gitlab.com https://gitlab.com/qemu-project/qemu/-/issues/1813 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.