CVE-2023-2680: Dma reentrancy issue (incomplete fix for cve-2021-3750)
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: qemu-guest-agent (AlmaLinux:9) 17:8.0.0-16.el9_3.alma.1; qemu-img (AlmaLinux:9) 17:8.0.0-16.el9_3.alma.1; qemu-kvm (AlmaLinux:9) 17:8.0.0-16.el9_3.alma.1.
Low priority for now. Upgrade to qemu-guest-agent (AlmaLinux:9) 17:8.0.0-16.el9_3.alma.1; qemu-img (AlmaLinux:9) 17:8.0.0-16.el9_3.alma.1; qemu-kvm (AlmaLinux:9) 17:8.0.0-16.el9_3.alma.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
This CVE exists because of an incomplete fix for CVE-2021-3750. More specifically, the qemu-kvm package as released for Red Hat Enterprise Linux 9.1 via RHSA-2022:7967 included a version of qemu-kvm that was actually missing the fix for CVE-2021-3750.
- Published
- Sep 13, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-416
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 8.2
- CNA · redhat
- 7.5
- 0.7 point gap
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qemu qemuall versions
- redhat enterprise linux9.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Fedora Extra Packages for Enterprise Linux
- all versionsunknown
Fedora Fedora
- all versionsunknown
n/a qemu
- all versionsaffected
Red Hat Red Hat Enterprise Linux 6
- all versionsunknown
Red Hat Red Hat Enterprise Linux 7
- all versionsunknown
- all versionsunknown
Red Hat Red Hat Enterprise Linux 8
- all versionsunknown
Red Hat Red Hat Enterprise Linux 8 Advanced Virtualization
- all versionsunknown
Red Hat Red Hat Enterprise Linux 9
- all versionsaffected
Red Hat Red Hat OpenStack Platform 13 (Queens)
- all versionsunknown
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | qemu-guest-agent | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-img | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-audio-pa | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-block-blkio | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-block-curl | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-block-rbd | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-common | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-core | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-device-display-virtio-gpu | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-device-display-virtio-gpu-ccw | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-device-display-virtio-gpu-pci | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-device-display-virtio-vga | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-device-usb-host | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-device-usb-redirect | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-docs | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-tools | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-ui-egl-headless | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-kvm-ui-opengl | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| AlmaLinux:9 | qemu-pr-helper | before 17:8.0.0-16.el9_3.alma.1 | 17:8.0.0-16.el9_3.alma.1 |
| Red Hat:enterprise_linux:9::appstream | qemu-guest-agent | before 17:8.0.0-16.el9_3 | 17:8.0.0-16.el9_3 |
| Red Hat:enterprise_linux:9::appstream | qemu-guest-agent-debuginfo | before 17:8.0.0-16.el9_3 | 17:8.0.0-16.el9_3 |
| Red Hat:enterprise_linux:9::appstream | qemu-img | before 17:8.0.0-16.el9_3 | 17:8.0.0-16.el9_3 |
| Red Hat:enterprise_linux:9::appstream | qemu-img-debuginfo | before 17:8.0.0-16.el9_3 | 17:8.0.0-16.el9_3 |
+39
Same product
qemu: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-12928The QMP migrate command in QEMU version 4.0.0 and earlier is vulnerable to OS command injection, which allows the remote attacker to achieve60This week
- CVE-2015-8556Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.44Plan
- CVE-2017-15118A stack-based buffer overflow vulnerability was found in NBD server implementation in qemu before 2.11 allowing a client to request an expor43Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-24165Aug 28, 2023 · An issue was discovered in TCG Accelerator in QEMU 4.2.0, allows local attackers to execute arbitrary code, escalate privileges, and cause a35Monitor
- ← EarlierCVE-2023-42467Sep 11, 2023 · 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 not22Monitor
- Later →CVE-2023-3255Sep 13, 2023 · Qemu: vnc: infinite loop in inflate_buffer() leads to denial of service27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:qemu-guest-agent | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-img | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-kvm | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-kvm-audio-pa | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-kvm-block-blkio | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-kvm-block-curl | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-kvm-block-rbd | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-kvm-common | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-kvm-core | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-kvm-device-display-virtio-gpu | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-kvm-device-display-virtio-gpu-ccw | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:qemu-kvm-device-display-virtio-gpu-pci | 17:8.0.0-16.el9_3.alma.1 · AlmaLinux:9 | Package registry (OSV) |
| red hat:qemu-guest-agent | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-guest-agent-debuginfo | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-img | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-img-debuginfo | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-kvm | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-kvm-audio-dbus-debuginfo | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-kvm-audio-pa | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-kvm-audio-pa-debuginfo | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-kvm-block-blkio | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-kvm-block-blkio-debuginfo | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-kvm-block-curl | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:qemu-kvm-block-curl-debuginfo | 17:8.0.0-16.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.