CVE-2023-42467

Exp

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.

Published: 2023-09-11 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-42467 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.05%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2023-42467

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2023-42467

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-03-30 0.07% 0.05% -0.02%
2 2025-03-29 0.04% 0.07% +0.02%
3 2023-09-11 — 0.04% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-42467

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2023-42467

OS Trackers for CVE-2023-42467

vendor priority summary link
alpine medium CVE-2023-42467: 1 source package rows (qemu); 49 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 49. https://security.alpinelinux.org/vuln/CVE-2023-42467
debian unimportant CVE-2023-42467 unimportant priority: Debian including 1 source packages (qemu), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-42467
redhat low — https://access.redhat.com/security/cve/CVE-2023-42467
suse medium CVE-2023-42467 severity moderate: SUSE including 522 source package names (2.0.4-3.5.275:qemu-guest-agent-7.1.0-150500.49.30.1, amazon/suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, …), 1183 product×package rows across 50 product lines (Container suse/sle-micro/kvm-5.5, SUSE CaaS Platform 4.0, … (50 product lines)): Known Not Affected 703, Fixed 249, Known Affected 231. https://www.suse.com/security/cve/CVE-2023-42467/
ubuntu low CVE-2023-42467 low priority: Ubuntu including 1 source packages (qemu), 10 status rows across 10 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, trusty, upstream, xenial): not-affected 5, released 4, needs-triage 1. https://ubuntu.com/security/CVE-2023-42467

Affected software / configurations for CVE-2023-42467

Vendor Product Version Raw CPE
qemu qemu <= 8.0.0 cpe:2.3:a:qemu:qemu:*:*:*:*:*:*:*:*

References for CVE-2023-42467

cvelogic Threat Intelligence