🛡️ CVE-2021-3608 on Debian — qemu
Description
A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device in versions prior to 6.1.0. The issue occurs while handling a "PVRDMA_REG_DSRHIGH" write from the guest and may result in a crash of QEMU or cause undefined behavior due to the access of an uninitialized pointer. The highest threat from this vulnerability is to system availability.
Distribution advisory
This page covers CVE-2021-3608 as tracked by Debian, for the package qemu. The fix is available in version 1:5.2+dfsg-11; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs administrative privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality none, integrity none, availability high.
Affected software
DEBIAN-CVE-2021-3608 is recorded against 1 package.
- qemu (fixed in 1:5.2+dfsg-11)
Timeline and source
Published on 24 February 2022 and last revised on 4 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
CVE-2021-3608 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| qemu | — | 1:5.2+dfsg-11 |
References
Similar Threats
Free Vulnerability Check
Is your site affected by DEBIAN-CVE-2021-3608?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against DEBIAN-CVE-2021-3608 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.