# CVE-2010-2963: Memory corruption in n/a

> Local attackers can exploit a memory copy validation flaw in the Linux kernel's V4L implementation to write to arbitrary kernel memory and gain privileges.

- **Severity:** Medium 6.2 (`AV:L/AC:H/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:** 26 Nov 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7276-wmh7-g227

## What is CVE-2010-2963?

CVE-2010-2963 is a medium-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 26 Nov 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

drivers/media/video/v4l2-compat-ioctl32.c in the Video4Linux (V4L) implementation in the Linux kernel before 2.6.36 on 64-bit platforms does not validate the destination of a memory copy operation, which allows local users to write to arbitrary kernel memory locations, and consequently gain privileges, via a VIDIOCSTUNER ioctl call on a /dev/video device, followed by a VIDIOCSMICROCODE ioctl call on this device.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 7 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Linux kernel, Opensuse Opensuse, Suse Linux Enterprise Desktop, Suse Linux Enterprise Server.

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

Upgrade to a fixed version.

## Is CVE-2010-2963 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-2963 exists.

Public exploit code:

- Linux Kernel 2.6.36 - VIDIOCSMICROCODE IOCTL Local Memory Overwrite (exploitdb)

## 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-2010-2963 and fix it if it is affected.

What it is: CVE-2010-2963 is a medium-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 26 Nov 2010. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-2963 exists.

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-2010-2963/ (Markdown: https://insights.sbomify.com/CVE-2010-2963/index.md)
```

## Sources

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

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