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

> Local attackers can trigger out-of-bounds writes in the Linux kernel DRM subsystem via crafted ioctl arguments, causing system crashes or potential code execution.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 9 May 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xcm2-p2fv-cfg9

## What is CVE-2011-1013?

CVE-2011-1013 is a high-severity vulnerability in Linux kernel, published on 9 May 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer signedness error in the drm_modeset_ctl function in (1) drivers/gpu/drm/drm_irq.c in the Direct Rendering Manager (DRM) subsystem in the Linux kernel before 2.6.38 and (2) sys/dev/pci/drm/drm_irq.c in the kernel in OpenBSD before 4.9 allows local users to trigger out-of-bounds write operations, and consequently cause a denial of service (system crash) or possibly have unspecified other impact, via a crafted num_crtcs (aka vb_num) structure member in an ioctl argument.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


Products: Linux kernel, Openbsd Openbsd.

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

Apply the vendor's patch.

## Is CVE-2011-1013 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1013 is a high-severity vulnerability in Linux kernel, published on 9 May 2011. 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-1013 in the wild and no public exploit code.

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

## Sources

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

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