# CVE-2010-0419: Privilege escalation in n/a

> Guest OS users can escalate privileges or crash the guest by exploiting a KVM x86 emulator flaw in SMP configurations.

- **Severity:** Medium 4.4 (`AV:L/AC:M/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:** 5 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7c97-97wj-vp33

## What is CVE-2010-0419?

CVE-2010-0419 is a medium-severity vulnerability in n/a, published on 5 Mar 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The x86 emulator in KVM 83, when a guest is configured for Symmetric Multiprocessing (SMP), does not properly restrict writing of segment selectors to segment registers, which might allow guest OS users to cause a denial of service (guest OS crash) or gain privileges on the guest OS by leveraging access to a (1) IO port or (2) MMIO region, and replacing an instruction in between emulator entry and instruction fetch.

Weakness: CWE-264

## Which versions are affected by CVE-2010-0419?

It affects 1 product.


Products: Kvm Qumranet Kvm.

## How do I fix CVE-2010-0419?

Apply the vendor's patch.

## Is CVE-2010-0419 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2382](https://insights.sbomify.com/CVE-2008-2382/): Denial of service in n/a (medium 5.0)
- [CVE-2010-0306](https://insights.sbomify.com/CVE-2010-0306/): Privilege escalation in n/a (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0419 and fix it if it is affected.

What it is: CVE-2010-0419 is a medium-severity vulnerability in n/a, published on 5 Mar 2010. 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-2010-0419 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-2010-0419/ (Markdown: https://insights.sbomify.com/CVE-2010-0419/index.md)
```

## Sources

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

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