# CVE-2019-20636: Memory corruption in n/a

> Out-of-bounds write in the Linux kernel input subsystem allows attackers to execute arbitrary code or escalate privileges via a crafted keycode table.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** A-153715664, ASB-A-153715664, DEBIAN-CVE-2019-20636, GHSA-rmm3-6hwr-c8q9, UBUNTU-CVE-2019-20636

## What is CVE-2019-20636?

CVE-2019-20636 is a medium-severity memory corruption vulnerability in Linux kernel, published on 8 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel before 5.4.12, drivers/input/input.c has out-of-bounds writes via a crafted keycode table, as demonstrated by input_set_keycode, aka CID-cb222aed03d7.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-20636?

It affects 18 products.


Products: Linux kernel, Netapp Cloud Backup, Netapp Fas 8300, Netapp Fas 8700, Netapp Fas A400, Netapp Fas Baseboard Management Controller A220, Netapp Fas Baseboard Management Controller A320, Netapp Fas Baseboard Management Controller A800, Netapp Fas Baseboard Management Controller C190, Netapp H300s, Netapp H410s, Netapp H500s, Netapp H610c, Netapp H610s, Netapp H615c, Netapp H700s, Netapp Solidfire, Netapp Steelstore Cloud Integrated Storage.

## How do I fix CVE-2019-20636?

Apply the vendor's patch.

## Is CVE-2019-20636 being exploited?

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

What it is: CVE-2019-20636 is a medium-severity memory corruption vulnerability in Linux kernel, published on 8 Apr 2020. 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-2019-20636 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-2019-20636/ (Markdown: https://insights.sbomify.com/CVE-2019-20636/index.md)
```

## Sources

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

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