| Name | CVE-2021-3409 |
| Description | The patch for CVE-2020-17380/CVE-2020-25085 was found to be ineffective, thus making QEMU vulnerable to the out-of-bounds read/write access issues previously found in the SDHCI controller emulation code. This flaw allows a malicious privileged guest to crash the QEMU process on the host, resulting in a denial of service or potential code execution. QEMU up to (including) 5.2.0 is affected by this. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| References | DLA-2623-1, DLA-3362-1 |
| Debian Bugs | 986795 |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| qemu (PTS) | bullseye | 1:5.2+dfsg-11+deb11u3 | fixed |
| bullseye (security) | 1:5.2+dfsg-11+deb11u2 | fixed | |
| bookworm | 1:7.2+dfsg-7+deb12u7 | fixed | |
| trixie | 1:9.2.0+ds-2 | fixed | |
| sid | 1:9.2.0+ds-3 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| qemu | source | stretch | 1:2.8+dfsg-6+deb9u14 | DLA-2623-1 | ||
| qemu | source | buster | 1:3.1+dfsg-8+deb10u10 | DLA-3362-1 | ||
| qemu | source | (unstable) | 1:5.2+dfsg-10 | 986795 |
https://bugzilla.redhat.com/show_bug.cgi?id=1928146
https://www.openwall.com/lists/oss-security/2021/03/09/1
New patch series: https://lists.nongnu.org/archive/html/qemu-devel/2021-03/msg00949.html
https://git.qemu.org/?p=qemu.git;a=commit;h=b263d8f928001b5cfa2a993ea43b7a5b3a1811e8
https://git.qemu.org/?p=qemu.git;a=commit;h=8be45cc947832b3c02144c9d52921f499f2d77fe
https://git.qemu.org/?p=qemu.git;a=commit;h=bc6f28995ff88f5d82c38afcfd65406f0ae375aa
https://git.qemu.org/?p=qemu.git;a=commit;h=5cd7aa3451b76bb19c0f6adc2b931f091e5d7fcd
https://git.qemu.org/?p=qemu.git;a=commit;h=cffb446e8fd19a14e1634c7a3a8b07be3f01d5c9
This is a re-submission of CVE-2020-17380 following its confusion with CVE-2020-25085 at a point, see RH bug