# CVE-2014-0069: Memory corruption in n/a

> Local attackers can exploit a CIFS write vulnerability to read kernel memory, crash the system, or escalate privileges via crafted writev calls.

- **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:** 28 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** AZL-34154, AZL-34848, DEBIAN-CVE-2014-0069, GHSA-mg5h-jxw2-63w8

## What is CVE-2014-0069?

CVE-2014-0069 is a high-severity memory corruption vulnerability in Linux kernel, published on 28 Feb 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The cifs_iovec_write function in fs/cifs/file.c in the Linux kernel through 3.13.5 does not properly handle uncached write operations that copy fewer than the requested number of bytes, which allows local users to obtain sensitive information from kernel memory, cause a denial of service (memory corruption and system crash), or possibly gain privileges via a writev system call with a crafted pointer.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2014-0069?

It affects 9 products.


Products: Linux kernel, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Suse Linux Enterprise Desktop, Suse Linux Enterprise Server.

## How do I fix CVE-2014-0069?

Apply the vendor's patch.

## Is CVE-2014-0069 being exploited?

There is no known exploitation of CVE-2014-0069 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-2014-0069 and fix it if it is affected.

What it is: CVE-2014-0069 is a high-severity memory corruption vulnerability in Linux kernel, published on 28 Feb 2014. 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-2014-0069 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-2014-0069/ (Markdown: https://insights.sbomify.com/CVE-2014-0069/index.md)
```

## Sources

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

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