Qemu-kvm: stack buffer overflow in e1000 device via short frames in loopback mode
Noroxi assessment
Priority: Monitor (action score 24/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.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: gitlab.com/qemu-project/qemu qemu 10.1.3; azl3 qemu 8.2.0-23 on Azure Linux 3.0 8.2.0-25; azl3 qemu 8.2.0-25 on Azure Linux 3.0 8.2.0-25.
Low priority for now. Upgrade to gitlab.com/qemu-project/qemu qemu 10.1.3; azl3 qemu 8.2.0-23 on Azure Linux 3.0 8.2.0-25; azl3 qemu 8.2.0-25 on Azure Linux 3.0 8.2.0-25 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-based buffer overflow was found in the QEMU e1000 network device. The code for padding short frames was dropped from individual network devices and moved to the net core code. The issue stems from the device's receive code still being able to process a short frame in loopback mode. This could lead to a buffer overrun in the e1000_receive_iov() function via the loopback code path. A malicious guest user could use this vulnerability to crash the QEMU process on the host, resulting in a denial of service.
- Published
- Oct 31, 2025
- Updated
- Oct 18, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-121
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 6.2
- NVD has not scored this yet; the score shown is the CNA’s.
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.
—
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.
gitlab.com/qemu-project/qemu qemu
- 8.1.0 and later · before 10.1.3affected · semver
Red Hat Red Hat Enterprise Linux 10
- 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 9
- all versionsaffected
Red Hat Red Hat OpenShift Container Platform 4
- all versionsaffected
- all versionsaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | qemu | before 1:10.0.7+ds-0+deb13u1 | 1:10.0.7+ds-0+deb13u1 |
| Debian:14 | qemu | before 1:10.1.3+ds-1 | 1:10.1.3+ds-1 |
| openSUSE:Leap 15.6 | qemu | before 8.2.10-150600.3.43.1 | 8.2.10-150600.3.43.1 |
| openSUSE:Leap 15.6 | qemu-linux-user | before 8.2.10-150600.3.43.1 | 8.2.10-150600.3.43.1 |
| openSUSE:Leap 16.0 | qemu | before 10.0.7-160000.1.1 | 10.0.7-160000.1.1 |
| openSUSE:Leap 16.0 | qemu-linux-user | before 10.0.7-160000.1.1 | 10.0.7-160000.1.1 |
| openSUSE:Tumbleweed | qemu | before 10.1.3-1.1 | 10.1.3-1.1 |
| SUSE:Linux Enterprise Micro 5.3 | qemu | before 6.2.0-150400.37.46.1 | 6.2.0-150400.37.46.1 |
| SUSE:Linux Enterprise Micro 5.5 | qemu | before 7.1.0-150500.49.36.2 | 7.1.0-150500.49.36.2 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | qemu | before 9.2.4-150700.3.11.1 | 9.2.4-150700.3.11.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | qemu-linux-user | before 9.2.4-150700.3.11.1 | 9.2.4-150700.3.11.1 |
| SUSE:Linux Enterprise Server 15 SP6-LTSS | qemu | before 8.2.10-150600.3.43.1 | 8.2.10-150600.3.43.1 |
| SUSE:Linux Enterprise Server 16.0 | qemu-linux-user | before 10.0.7-160000.1.1 | 10.0.7-160000.1.1 |
| SUSE:Linux Micro 6.0 | qemu | before 8.2.10-1.1 | 8.2.10-1.1 |
| SUSE:Linux Micro 6.1 | qemu | before 8.2.10-slfo.1.1_3.1 | 8.2.10-slfo.1.1_3.1 |
| SUSE:Linux Micro 6.2 | qemu | before 10.0.7-160000.1.1 | 10.0.7-160000.1.1 |
Same product
red hat: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-10230Samba: command injection in wins server hook script52Plan
- CVE-2026-4631Cockpit: cockpit: unauthenticated remote code execution due to ssh command-line argument injection42Plan
- CVE-2026-76578Ipa: freeipa: freeipa: unauthenticated ldap client can obtain administrator credentials via the self-managed-token aci39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-11561Oct 9, 2025 · Sssd: sssd default kerberos configuration allows privilege escalation on ad-joined linux systems35Monitor
- ← EarlierCVE-2025-9640Oct 15, 2025 · Samba: vfs_streams_xattr uninitialized memory write possible17Monitor
- Later →CVE-2025-12748Nov 11, 2025 · Libvirt: denial of service in xml parsing22Monitor
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 |
|---|---|---|
| gitlab.com/qemu-project/qemu qemu | 10.1.3 | Vendor (CNA) |
| azl3 qemu 8.2.0-23 on Azure Linux 3.0 | 8.2.0-25 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 qemu 8.2.0-25 on Azure Linux 3.0 | 8.2.0-25 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:qemu | 1:10.0.7+ds-0+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:qemu | 8.2.10-150600.3.43.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:qemu-linux-user | 8.2.10-150600.3.43.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:qemu | 10.0.7-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:qemu | 8.2.10-150600.3.43.1 · SUSE:Linux Enterprise Server 15 SP6-LTSS | Package registry (OSV) |
| suse:qemu-linux-user | 10.0.7-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- CVE-2026-071969 days apartLibsoup: signed to unsigned conversion error leading to stack-based buffer overflow in libsoup ntlm authentication34Monitor
- CVE-2026-176194 days apartLibsoup: stack-based buffer overflow in libsoup multipart response parsingmultipart http response34Monitor
- CVE-2026-43958213 days apartRrdtool: rrdtool: stack buffer overflow allows local code execution or denial of service31Monitor
- CVE-2026-112257353 days apartGimp: gimp: heap out-of-bounds read/write in psd thumbnail loader (load_resource_1033)31Monitor
- CVE-2026-59692251 days apartGstreamer1-plugins-bad-free: gstreamer: dtls certificate subject dn stack buffer overflow in openssl_verify_callback30Monitor
- CVE-2026-16277262 days apartRpcbind: rpcbind: stack buffer overflow in rpcinfo rpcbaddrlist()26Monitor
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.
- No account or password is required.
- 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-121 · Stack-based Buffer OverflowCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
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.