# CVE-2013-0241: Denial of service in n/a

> Local attackers can cause a guest system crash or hang via a SPICE connection that blocks the qemu_mutex in the QXL display driver.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-0241, GHSA-6x5v-pqrf-rh9v, RHSA-2013:0218

## What is CVE-2013-0241?

CVE-2013-0241 is a low-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 13 Feb 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The QXL display driver in QXL Virtual GPU 0.1.0 allows local users to cause a denial of service (guest crash or hang) via a SPICE connection that prevents other threads from obtaining the qemu_mutex mutex.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-399

## Which versions are affected by CVE-2013-0241?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xorg-x11-drv-qxl` | Red Hat:enterprise_linux:6::client | All versions | 0:0.0.14-14.el6_3 |
| `xorg-x11-drv-qxl-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:0.0.14-14.el6_3 |
| `xorg-x11-drv-qxl` | Red Hat:enterprise_linux:6::server | All versions | 0:0.0.14-14.el6_3 |
| `xorg-x11-drv-qxl-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:0.0.14-14.el6_3 |
| `xorg-x11-drv-qxl` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.0.14-14.el6_3 |
| `xorg-x11-drv-qxl-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.0.14-14.el6_3 |

Products: Canonical Ubuntu Linux, Qxl Graphics Driver Project Xf86-Video-Qxl, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2013-0241?

Apply the vendor's patch.

## Is CVE-2013-0241 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0241 and fix it if it is affected.

What it is: CVE-2013-0241 is a low-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 13 Feb 2013. 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-2013-0241 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2013-0241/ (Markdown: https://insights.sbomify.com/CVE-2013-0241/index.md)
```

## Sources

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

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