# CVE-2017-16995: Memory corruption in n/a

> Local attackers can exploit incorrect sign extension in the BPF verifier to cause memory corruption, leading to denial of service or potential code execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 22 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-16995, GHSA-45mv-5p9c-6w7c, UBUNTU-CVE-2017-16995, USN-3633-1

## What is CVE-2017-16995?

CVE-2017-16995 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 22 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.

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

## Which versions are affected by CVE-2017-16995?

It affects 3 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Linux kernel.

## How do I fix CVE-2017-16995?

Apply the vendor's patch.

## Is CVE-2017-16995 being exploited?

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

Public exploit code:

- CVE-2017-16995（Ubuntu本地提权漏洞） (github_poc): https://github.com/Al1ex/CVE-2017-16995
- 👻CVE-2017-16995 (github_poc): https://github.com/ph4ntonn/CVE-2017-16995
- Exploit adapted for a specific PoC on Ubuntu 16.04.01 (github_poc): https://github.com/gugronnier/CVE-2017-16995
- Writeup for CVE-2017-16995 Linux BPF Local Privilege Escalation (github_poc): https://github.com/senyuuri/cve-2017-16995
- CVE-2017-16995 eBPF PoC for Ubuntu 16.04 (github_poc): https://github.com/vnik5287/CVE-2017-16995
- CVE-2017-16995 ubuntun本地提权 POC (github_poc): https://github.com/littlebin404/CVE-2017-16995

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

What it is: CVE-2017-16995 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 22 Dec 2017. 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-2017-16995 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-2017-16995/ (Markdown: https://insights.sbomify.com/CVE-2017-16995/index.md)
```

## Sources

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

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