# CVE-2020-36516: Other in n/a

> An off-path attacker can inject data into or terminate a victim's TCP session due to flawed IPID assignment in the Linux kernel.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-36516, GHSA-w52c-ppqw-2gxp, SUSE-SU-2022:3064-1, UBUNTU-CVE-2020-36516

## What is CVE-2020-36516?

CVE-2020-36516 is a medium-severity vulnerability in Linux kernel, published on 26 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in the Linux kernel through 5.16.11. The mixed IPID assignment method with the hash-based IPID assignment policy allows an off-path attacker to inject data into a victim's TCP session or terminate that session.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2020-36516?

It affects 17 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kgraft-patch-SLE12-SP5_Update_34` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 2-2.2 |
| `kernel-livepatch-SLE15_Update_32` | SUSE:Linux Enterprise Live Patching 15 | All versions | 2-150000.2.1 |
| `kernel-livepatch-SLE15-SP1_Update_33` | SUSE:Linux Enterprise Live Patching 15 SP1 | All versions | 2-150100.2.1 |

Products: Linux kernel, Netapp Bootstrap Os, Netapp Cloud Volumes Ontap Mediator, Netapp E-Series Santricity Os Controller, Netapp H300e Firmware, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500e Firmware, Netapp H500s Firmware, Netapp H610c Firmware, Netapp H610s Firmware, Netapp H615c Firmware, Netapp H700e Firmware, Netapp H700s Firmware, Netapp Solidfire\, Enterprise Sds \& Hci Storage Node, Netapp Solidfire \& Hci Management Node.

## How do I fix CVE-2020-36516?

Apply the vendor's patch.

## Is CVE-2020-36516 being exploited?

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

What it is: CVE-2020-36516 is a medium-severity vulnerability in Linux kernel, published on 26 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36516 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-2020-36516/ (Markdown: https://insights.sbomify.com/CVE-2020-36516/index.md)
```

## Sources

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

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