# CVE-2011-2512: Integer overflow in n/a

> Guest users can trigger a crash or execute arbitrary code on the host by sending a negative virtqueue number, bypassing validation checks.

- **Severity:** Medium 5.8 (`AV:A/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-2270-1, GHSA-g293-9rv5-w2qx

## What is CVE-2011-2512?

CVE-2011-2512 is a medium-severity vulnerability in n/a, published on 21 Jun 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The virtio_queue_notify in qemu-kvm 0.14.0 and earlier does not properly validate the virtqueue number, which allows guest users to cause a denial of service (guest crash) and possibly execute arbitrary code via a negative number in the Queue Notify field of the Virtio Header, which bypasses a signed comparison.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-2512?

It affects 1 product.


Products: Kvm Group Qemu-Kvm.

## How do I fix CVE-2011-2512?

Apply the vendor's patch.

## Is CVE-2011-2512 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0029](https://insights.sbomify.com/CVE-2012-0029/): Memory corruption in n/a (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2512 and fix it if it is affected.

What it is: CVE-2011-2512 is a medium-severity vulnerability in n/a, published on 21 Jun 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2512 in the wild and no public exploit code.

Affected product: n/a. 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-2011-2512/ (Markdown: https://insights.sbomify.com/CVE-2011-2512/index.md)
```

## Sources

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

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