# CVE-2010-3699: Denial of service in n/a

> Guest OS users can cause a denial of service in Xen by leaking kernel threads, preventing proper shutdown or command execution.

- **Severity:** Low 2.7 (`AV:A/AC:L/Au:S/C:N/I:N/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:** 8 Dec 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-897j-59mc-qfvp

## What is CVE-2010-3699?

CVE-2010-3699 is a low-severity denial of service vulnerability in n/a, published on 8 Dec 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The backend driver in Xen 3.x allows guest OS users to cause a denial of service via a kernel thread leak, which prevents the device and guest OS from being shut down or create a zombie domain, causes a hang in zenwatch, or prevents unspecified xm commands from working properly, related to (1) netback, (2) blkback, or (3) blktap.

Weakness: CWE-399

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

It affects 1 product.


Products: Citrix Xen.

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

Apply the vendor's patch.

## Is CVE-2010-3699 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-1898](https://insights.sbomify.com/CVE-2011-1898/): Privilege escalation in n/a (high 7.4)
- [CVE-2008-5716](https://insights.sbomify.com/CVE-2008-5716/): Missing authorization in n/a (high 7.2)
- [CVE-2008-4405](https://insights.sbomify.com/CVE-2008-4405/): Missing authorization in n/a (high 7.2)
- [CVE-2011-1583](https://insights.sbomify.com/CVE-2011-1583/): Integer overflow in n/a (medium 6.9)
- [CVE-2010-4255](https://insights.sbomify.com/CVE-2010-4255/): Denial of service in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-3699 is a low-severity denial of service vulnerability in n/a, published on 8 Dec 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-3699 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-3699/ (Markdown: https://insights.sbomify.com/CVE-2010-3699/index.md)
```

## Sources

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

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