Qemu-kvm: virtio-net: queue index out-of-bounds access in software rss
Noroxi assessment
Priority: Monitor (action score 27/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.65% (FIRST EPSS); higher than 50.7% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: gitlab.com/qemu-project/qemu qemu 9.1.0; azl3 qemu 8.2.0-14 on Azure Linux 3.0 8.2.0-14; azl3 qemu 8.2.0-16 on Azure Linux 3.0 8.2.0-14.
Low priority for now. Upgrade to gitlab.com/qemu-project/qemu qemu 9.1.0; azl3 qemu 8.2.0-14 on Azure Linux 3.0 8.2.0-14; azl3 qemu 8.2.0-16 on Azure Linux 3.0 8.2.0-14 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 flaw was found in the virtio-net device in QEMU. When enabling the RSS feature on the virtio-net network card, the indirections_table data within RSS becomes controllable. Setting excessively large values may cause an index out-of-bounds issue, potentially resulting in heap overflow access. This flaw allows a privileged user in the guest to crash the QEMU process on the host.
- Published
- Jul 5, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 50th percentile
- CWE
- CWE-125
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 6.8
- 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.
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 linux8.0
- 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.
gitlab.com/qemu-project/qemu qemu
- 5.1.0 and later · before 9.1.0affected · 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 versionsaffected
Red Hat Red Hat Enterprise Linux 8 Advanced Virtualization
- all versionsaffected
Red Hat Red Hat Enterprise Linux 9
- 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:12 | qemu | before 1:7.2+dfsg-7+deb12u8 | 1:7.2+dfsg-7+deb12u8 |
| Debian:13 | qemu | before 1:9.0.2+ds-3 | 1:9.0.2+ds-3 |
| SUSE:Linux Enterprise Micro 5.2 | qemu | before 5.2.0-150300.138.1 | 5.2.0-150300.138.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 |
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-2024-24474Feb 20, 2024 · QEMU before 8.2.0 has an integer underflow, and resultant buffer overflow, via a TI command when an expected non-DMA transfer length is less35Monitor
- ← EarlierCVE-2024-3567Apr 10, 2024 · Qemu-kvm: net: assertion failure in update_sctp_checksum()22Monitor
- Later →CVE-2024-8354Sep 19, 2024 · Qemu-kvm: usb: assertion failure in usb_ep_get()22Monitor
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 | 9.1.0 | Vendor (CNA) |
| azl3 qemu 8.2.0-14 on Azure Linux 3.0 | 8.2.0-14 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 qemu 8.2.0-16 on Azure Linux 3.0 | 8.2.0-14 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 qemu 6.2.0-24 on CBL Mariner 2.0 | 6.2.0-24 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 qemu 6.2.0-24 on CBL-Mariner 2.0 | 6.2.0-24 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:qemu | 1:7.2+dfsg-7+deb12u8 · Debian:12 | Package registry (OSV) |
| suse:qemu | 7.1.0-150500.49.36.2 · SUSE:Linux Enterprise Micro 5.5 | 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-2023-4135336 days apartOut-of-bounds read information disclosure vulnerability26Monitor
- CVE-2023-1544470 days apartQemu: pvrdma: out-of-bounds read in pvrdma_ring_next_elem_read()25Monitor
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
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are 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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
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.