# CVE-2016-8636: Integer overflow in n/a

> Local attackers can trigger an integer overflow in the Linux kernel's Soft RoCE driver to cause memory corruption, denial of service, or information disclosure.

- **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 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-8636, GHSA-vv9c-r5jj-58f9, UBUNTU-CVE-2016-8636

## What is CVE-2016-8636?

CVE-2016-8636 is a high-severity vulnerability in Linux kernel, published on 22 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer overflow in the mem_check_range function in drivers/infiniband/sw/rxe/rxe_mr.c in the Linux kernel before 4.9.10 allows local users to cause a denial of service (memory corruption), obtain sensitive information from kernel memory, or possibly have unspecified other impact via a write or read request involving the "RDMA protocol over infiniband" (aka Soft RoCE) technology.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2016-8636?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2016-8636?

Apply the vendor's patch.

## Is CVE-2016-8636 being exploited?

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

Public exploit code:

- Integer Overflow (CyberSecurity | UMCP 2018) . This involves exploiting integer overflow vulnerability present in mem_check function of infiniband Soft RoCE implemetation (Ref: CVE-2016-8636). It also exploring Pwnie Adventure island (Reference: LiveOverflow) (github_poc): https://github.com/jigerjain/Integer-Overflow-test

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

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

## Sources

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

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