# CVE-2013-1773: Memory corruption in n/a

> Local attackers can exploit a buffer overflow in the Linux kernel VFAT filesystem to gain privileges or crash the system when the utf8 mount option is enabled.

- **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:** 28 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-1773, GHSA-wrp6-2w63-vpc4

## What is CVE-2013-1773?

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

### Official description

Buffer overflow in the VFAT filesystem implementation in the Linux kernel before 3.3 allows local users to gain privileges or cause a denial of service (system crash) via a VFAT write operation on a filesystem with the utf8 mount option, which is not properly handled during UTF-8 to UTF-16 conversion.

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

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

It affects 3 products.


Products: Linux kernel, Redhat Enterprise Linux, Redhat Enterprise Mrg.

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

Upgrade to a fixed version.

## Is CVE-2013-1773 being exploited?

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

Public exploit code:

- Google Android Kernel 2.6 - Local Denial of Service Crash (PoC) (exploitdb)

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

What it is: CVE-2013-1773 is a medium-severity memory corruption vulnerability in Linux kernel, published on 28 Feb 2013. 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-2013-1773 exists.

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

## Sources

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

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