# CVE-2018-14634: Linux Kernel Integer Overflow

> An integer overflow in the Linux kernel allows local users to escalate privileges via SUID binaries.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 26 Jan 2026 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2018
- **Updated:** 27 Jan 2026
- **Also known as:** CVE-2019-9457, DEBIAN-CVE-2018-14634, GHSA-4994-8w6g-9jvw, RHSA-2018:2748, RHSA-2018:2763, RHSA-2018:3643, UBUNTU-CVE-2018-14634

## What is CVE-2018-14634?

CVE-2018-14634 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 25 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An integer overflow flaw was found in the Linux kernel's create_elf_tables() function. An unprivileged local user with access to SUID (or otherwise privileged) binary could use this flaw to escalate their privileges on the system. Kernel versions 2.6.x, 3.10.x and 4.14.x are believed to be vulnerable.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 28 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-abi-whitelists` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debug` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debug-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debug-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-doc` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-headers` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-tools` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-tools-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-tools-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-tools-libs-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `perf` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `perf-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `python-perf` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `python-perf-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-abi-whitelists` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debug` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debug-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debug-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-doc` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-headers` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-tools` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-tools-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-tools-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-tools-libs-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `perf` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `perf-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `python-perf` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `python-perf-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel` | Red Hat:enterprise_linux:7::server | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-abi-whitelists` | Red Hat:enterprise_linux:7::server | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-bootwrapper` | Red Hat:enterprise_linux:7::server | All versions | 0:3.10.0-862.14.4.el7 |
| `kernel-debug` | Red Hat:enterprise_linux:7::server | All versions | 0:3.10.0-862.14.4.el7 |

Products: Canonical Ubuntu Linux, F5 Big-Ip Access Policy Manager, F5 Big-Ip Advanced Firewall Manager, F5 Big-Ip Analytics, F5 Big-Ip Application Acceleration Manager, F5 Big-Ip Application Security Manager, F5 Big-Ip Domain Name System, F5 Big-Ip Edge Gateway, F5 Big-Ip Fraud Protection Service, F5 Big-Ip Global Traffic Manager, F5 Big-Ip Link Controller, F5 Big-Ip Local Traffic Manager, F5 Big-Ip Policy Enforcement Manager, F5 Big-Ip Webaccelerator, F5 Big-Iq Centralized Management, F5 Big-Iq Cloud and Orchestration, F5 Enterprise Manager, F5 Iworkflow, F5 Traffix Signaling Delivery Controller, Linux kernel and 8 more.

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

Apply the vendor's patch. US federal agencies must fix it by 16 Feb 2026.

## Is CVE-2018-14634 being exploited?

Yes. Attackers have exploited CVE-2018-14634 in the wild since at least 26 Jan 2026.

Public exploit code:

- proof-of-concept (PoC) for linux dists based on Debian, CentOS and RedHat - exploit 1 (github_poc): https://github.com/luan0ap/cve-2018-14634
- Linux Kernel 2.6.x / 3.10.x / 4.14.x (RedHat / Debian / CentOS) (x64) - 'Mutagen Astronomy' Local Privilege Escalation (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-14634 and fix it if it is affected.

What it is: CVE-2018-14634 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 25 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-14634 in the wild since at least 26 Jan 2026.

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

## Sources

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

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