CVE-2021-20255: A stack overflow via an infinite recursion vulnerability was found in the eepro100 i8255x device emulator of QEMU.
Noroxi assessment
Priority: Monitor (action score 22/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.41% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: qemu (Alpine:v3.14) 6.0.0-r1; qemu (Debian:13) 1:8.1.0+ds-1; qemu (Debian:9) 1:2.8+dfsg-6+deb9u14.
Low priority for now. Upgrade to qemu (Alpine:v3.14) 6.0.0-r1; qemu (Debian:13) 1:8.1.0+ds-1; qemu (Debian:9) 1:2.8+dfsg-6+deb9u14 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
A stack overflow via an infinite recursion vulnerability was found in the eepro100 i8255x device emulator of QEMU. This issue occurs while processing controller commands due to a DMA reentry issue. This flaw allows a guest user or process to consume CPU cycles or crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
- BDU:2022-05644
- DLA-2623-1
- openSUSE-SU-2021:1202-1
- openSUSE-SU-2021:2789-1
- openSUSE-SU-2021:2858-1
- openSUSE-SU-2021:3614-1
- SUSE-SU-2021:14848-1
- SUSE-SU-2021:2789-1
- SUSE-SU-2021:2813-1
- SUSE-SU-2021:2858-1
- SUSE-SU-2021:2924-1
- SUSE-SU-2021:2955-1
- SUSE-SU-2021:2957-1
- SUSE-SU-2021:3322-1
- SUSE-SU-2021:3575-1
- SUSE-SU-2021:3613-1
- SUSE-SU-2021:3614-1
- SUSE-SU-2021:3635-1
- Published
- Mar 9, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-835
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
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.
- debian debian linux9.0
- qemu qemuall versions
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.
n/a QEMU
- all versionsaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.14 | qemu | before 6.0.0-r1 | 6.0.0-r1 |
| Debian:12 | qemu | from 0 | — |
| Debian:13 | qemu | before 1:8.1.0+ds-1 | 1:8.1.0+ds-1 |
| Debian:9 | qemu | before 1:2.8+dfsg-6+deb9u14 | 1:2.8+dfsg-6+deb9u14 |
| openSUSE:Leap 15.2 | qemu | before 4.2.1-lp152.9.20.1 | 4.2.1-lp152.9.20.1 |
| openSUSE:Leap 15.2 | qemu-linux-user | before 4.2.1-lp152.9.20.1 | 4.2.1-lp152.9.20.1 |
| openSUSE:Leap 15.2 | qemu-testsuite | before 4.2.1-lp152.9.20.1 | 4.2.1-lp152.9.20.1 |
| openSUSE:Leap 15.3 | qemu | before 3.1.1.1-80.40.1 | 3.1.1.1-80.40.1 |
| openSUSE:Leap 15.3 | qemu | before 4.2.1-11.28.1 | 4.2.1-11.28.1 |
| openSUSE:Leap 15.3 | qemu | before 5.2.0-103.2 | 5.2.0-103.2 |
| SUSE:HPE Helion OpenStack 8 | xen | before 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | qemu | before 3.1.1.1-80.40.1 | 3.1.1.1-80.40.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | qemu | before 2.11.2-70.59.1 | 2.11.2-70.59.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | qemu | before 4.2.1-11.28.1 | 4.2.1-11.28.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | qemu | before 5.2.0-103.2 | 5.2.0-103.2 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | xen | before 4.4.4_50-61.67.1 | 4.4.4_50-61.67.1 |
| SUSE:Linux Enterprise Server 12 SP2-BCL | qemu | before 2.6.2-41.73.1 | 2.6.2-41.73.1 |
| SUSE:Linux Enterprise Server 12 SP2-BCL | xen | before 4.7.6_16-43.79.5 | 4.7.6_16-43.79.5 |
| SUSE:Linux Enterprise Server 12 SP5 | qemu | before 3.1.1.1-57.2 | 3.1.1.1-57.2 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | xen | before 4.12.4_12-3.49.1 | 4.12.4_12-3.49.1 |
| SUSE:OpenStack Cloud 9 | qemu | before 2.11.2-5.40.2 | 2.11.2-5.40.2 |
| SUSE:OpenStack Cloud 9 | xen | before 4.11.4_20-2.60.1 | 4.11.4_20-2.60.1 |
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-2021-20203Feb 25, 2021 · An integer overflow issue was found in the vmxnet3 NIC emulator of the QEMU for versions up to v5.2.0.12Monitor
- ← EarlierCVE-2021-20263Mar 9, 2021 · A flaw was found in the virtio-fs shared file system daemon (virtiofsd) of QEMU.13Monitor
- Later →CVE-2021-3416Mar 18, 2021 · A potential stack overflow via infinite loop issue was found in various NIC emulators of QEMU in versions up to and including 5.2.0.24Monitor
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 |
|---|---|---|
| alpine:qemu | 6.0.0-r1 · Alpine:v3.14 | Package registry (OSV) |
| debian:qemu | 1:8.1.0+ds-1 · Debian:13 | Package registry (OSV) |
| opensuse:qemu | 4.2.1-lp152.9.20.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| opensuse:qemu-linux-user | 4.2.1-lp152.9.20.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| opensuse:qemu-testsuite | 4.2.1-lp152.9.20.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| suse:qemu | 4.2.1-11.28.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP2 | Package registry (OSV) |
| suse:xen | 4.4.4_50-61.67.1 · SUSE:Linux Enterprise Server 11 SP4-LTSS | 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.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.