# CVE-2014-3180: Information disclosure in kernel

> An out-of-bounds read in the Linux kernel's restart_syscall could allow local attackers to read uninitialized memory, though the code path is disputed as unreachable.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3180, GHSA-97v5-ggfx-g9wc, UBUNTU-CVE-2014-3180

## What is CVE-2014-3180?

CVE-2014-3180 is a critical vulnerability in Google Chrome Os, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In kernel/compat.c in the Linux kernel before 3.17, as used in Google Chrome OS and other products, there is a possible out-of-bounds read. restart_syscall uses uninitialized data when restarting compat_sys_nanosleep. NOTE: this is disputed because the code path is unreachable

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 2 products.


Products: Google Chrome Os, Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2014-3180 being exploited?

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

## Other vulnerabilities in Google Chrome Os

- [CVE-2014-1708](https://insights.sbomify.com/CVE-2014-1708/): Code injection in n/a (critical 10.0)
- [CVE-2013-2833](https://insights.sbomify.com/CVE-2013-2833/): Use after free in n/a (critical 10.0)
- [CVE-2013-0915](https://insights.sbomify.com/CVE-2013-0915/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2864](https://insights.sbomify.com/CVE-2012-2864/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-4050](https://insights.sbomify.com/CVE-2012-4050/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3180 and fix it if it is affected.

What it is: CVE-2014-3180 is a critical vulnerability in Google Chrome Os, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3180 in the wild and no public exploit code.

Affected product: Google Chrome Os. 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-3180/ (Markdown: https://insights.sbomify.com/CVE-2014-3180/index.md)
```

## Sources

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

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