# CVE-2016-5870: Null dereference in n/a

> Attackers can cause a denial of service via NULL pointer dereference in the Linux kernel's MSM IPC router by triggering an accept system call failure.

- **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:** No
- **Published:** 4 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rv4x-88cg-xjcp

## What is CVE-2016-5870?

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

### Official description

The msm_ipc_router_close function in net/ipc_router/ipc_router_socket.c in the ipc_router component for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allow attackers to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact by triggering failure of an accept system call for an AF_MSM_IPC socket.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Linux kernel.

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

No fix has been published for CVE-2016-5870 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-5870 being exploited?

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

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

## Sources

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

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