# CVE-2020-8832: Ubuntu 18.04 Linux kernel i915 incomplete fix for CVE-2019-14615

> An incomplete fix in the Linux kernel allows attackers to expose sensitive information via Intel graphics processors.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Apr 2020
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2020-8832, GHSA-xqc2-q3vp-2m56, UBUNTU-CVE-2020-8832

## What is CVE-2020-8832?

CVE-2020-8832 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 9 Apr 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The fix for the Linux kernel in Ubuntu 18.04 LTS for CVE-2019-14615 ("The Linux kernel did not properly clear data structures on context switches for certain Intel graphics processors.") was discovered to be incomplete, meaning that in versions of the kernel before 4.15.0-91.92, an attacker could use this vulnerability to expose sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 32 products.


Products: Canonical Ubuntu Linux, Netapp Aff 8300 Firmware, Netapp Aff 8700 Firmware, Netapp Aff A220 Firmware, Netapp Aff A320 Firmware, Netapp Aff A400 Firmware, Netapp Aff A700s Firmware, Netapp Aff C190 Firmware, Netapp Cloud Backup, Netapp Fas2720 Firmware, Netapp Fas2750 Firmware, Netapp Fas8300 Firmware, Netapp Fas8700 Firmware, Netapp Fas Baseboard Management Controller A220 Firmware, Netapp Fas Baseboard Management Controller A320 Firmware, Netapp Fas Baseboard Management Controller A400 Firmware, Netapp Fas Baseboard Management Controller A800 Firmware, Netapp Fas Baseboard Management Controller C190 Firmware, Netapp H300e Firmware, Netapp H300s Firmware and 12 more.

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

Apply the vendor's patch.

## Is CVE-2020-8832 being exploited?

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

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

What it is: CVE-2020-8832 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 9 Apr 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-8832 in the wild and no public exploit code.

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-2020-8832/ (Markdown: https://insights.sbomify.com/CVE-2020-8832/index.md)
```

## Sources

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

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