# CVE-2018-1120: Denial of service in kernel

> An attacker can cause system utilities to block indefinitely by mapping a FUSE-backed file onto process memory, leading to denial of service.

- **Severity:** Low 2.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-1120, GHSA-gq4w-28gq-c8cj, RHSA-2020:3804, RHSA-2020:3810, UBUNTU-CVE-2018-1120

## What is CVE-2018-1120?

CVE-2018-1120 is a low-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 20 Jun 2018. 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

A flaw was found affecting the Linux kernel before version 4.17. By mmap()ing a FUSE-backed file onto a process's memory containing command line arguments (or environment strings), an attacker can cause utilities from psutils or procps (such as ps, w) or any other program which makes a read() call to the /proc/<pid>/cmdline (or /proc/<pid>/environ) files to block indefinitely (denial of service) or for some controlled time (as a synchronization primitive for other attacks).

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2018-1120?

It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-rt` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-debug` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-debug-debuginfo` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-debug-devel` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-debuginfo` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-debuginfo-common-x86_64` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-devel` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-doc` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-firmware` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-trace` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-trace-debuginfo` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-trace-devel` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-vanilla` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-vanilla-debuginfo` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel-rt-vanilla-devel` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.76.1.rt56.676.el6rt |
| `kernel` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-abi-whitelists` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-debug` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-debug-debuginfo` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-debug-devel` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-debuginfo` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-debuginfo-common-x86_64` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-devel` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-doc` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-tools` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-tools-debuginfo` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-tools-libs` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-tools-libs-devel` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `perf` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `perf-debuginfo` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `python-perf` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `python-perf-debuginfo` | Red Hat:rhel_aus:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel` | Red Hat:rhel_e4s:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-abi-whitelists` | Red Hat:rhel_e4s:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-bootwrapper` | Red Hat:rhel_e4s:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-debug` | Red Hat:rhel_e4s:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-debug-debuginfo` | Red Hat:rhel_e4s:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-debug-devel` | Red Hat:rhel_e4s:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-debuginfo` | Red Hat:rhel_e4s:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |
| `kernel-debuginfo-common-ppc64le` | Red Hat:rhel_e4s:7.4::server | All versions | 0:3.10.0-693.76.1.el7 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Linux kernel, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation, Redhat Virtualization Host.

## How do I fix CVE-2018-1120?

Apply the vendor's patch.

## Is CVE-2018-1120 being exploited?

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

Public exploit code:

- Procps-ng - Multiple Vulnerabilities (exploitdb)
- Procps-ng - Multiple Vulnerabilities (exploitdb)

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

What it is: CVE-2018-1120 is a low-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 20 Jun 2018. 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-2018-1120 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-2018-1120/ (Markdown: https://insights.sbomify.com/CVE-2018-1120/index.md)
```

## Sources

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

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