# CVE-2024-6505: Qemu-kvm: virtio-net: queue index out-of-bounds access in software rss

> A privileged guest user can crash the host QEMU process via an out-of-bounds access in virtio-net RSS, requiring the RSS feature to be enabled.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jul 2024
- **Updated:** 8 Nov 2025
- **Also known as:** AZL-60070, AZL-60925, DEBIAN-CVE-2024-6505, GHSA-3qx7-ff8p-6j2r, OESA-2024-2199, OESA-2024-2200, OESA-2024-2201, OESA-2024-2240, UBUNTU-CVE-2024-6505

## What is CVE-2024-6505?

CVE-2024-6505 is a medium-severity memory corruption vulnerability in Qemu Qemu, published on 5 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-6505?

It affects 2 products.


Products: Qemu Qemu, Redhat Enterprise Linux.

## How do I fix CVE-2024-6505?

Apply the vendor's patch.

## Is CVE-2024-6505 being exploited?

There is no known exploitation of CVE-2024-6505 in the wild and no public exploit code.

## Other vulnerabilities in Qemu Qemu

- [CVE-2022-36648](https://insights.sbomify.com/CVE-2022-36648/): Null dereference in n/a (critical 10.0)
- [CVE-2015-8556](https://insights.sbomify.com/CVE-2015-8556/): Race condition in n/a (critical 10.0)
- [CVE-2009-3616](https://insights.sbomify.com/CVE-2009-3616/): Use after free in n/a (critical 9.9)
- [CVE-2019-12928](https://insights.sbomify.com/CVE-2019-12928/): Command injection in n/a (critical 9.8)
- [CVE-2019-12929](https://insights.sbomify.com/CVE-2019-12929/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6505 and fix it if it is affected.

What it is: CVE-2024-6505 is a medium-severity memory corruption vulnerability in Qemu Qemu, published on 5 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6505 in the wild and no public exploit code.

Affected product: Qemu Qemu. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6505/ (Markdown: https://insights.sbomify.com/CVE-2024-6505/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6505
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6505
- OSV: https://osv.dev/vulnerability/CVE-2024-6505

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6505/
Summaries are generated and may contain mistakes; the official description above is the record.