CVERadar
HIGH · CVSS 3.0 7.8CISA KEV · added 2026-01-26Exploit-DBEPSS 14.69% (p97)Threat level 58

CVE-2018-14634: Linux Kernel Integer Overflow Vulnerability

Linux · Kernel · NVD published 2018-09-26 · posted 2026-01-26 · last modified 2026-06-17

What it is

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.

WeaknessCWE-190
CVSS vectorCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (source: [email protected])
CISA due date2026-02-16 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsExecution

Exploitation evidence

First exploit evidence seen: 2018-09-26 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2026-01-26. Source

Public exploit code

Exploit-DB

  • EDB-45516: Linux Kernel 2.6.x / 3.10.x / 4.14.x (RedHat / Debian / CentOS) (x64) - 'Mutagen Astronomy' Local Privilege Escalation (2018-09-26)

GitHub proof-of-concept repositories below quality bar

1 public repositories from 1 accounts, first seen 2018-10-08.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · Exploit-DB (OffSec) · nomi-sec/PoC-in-GitHub.

Defend the Chain

The attack chain for CVE-2018-14634 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 58/100
Defender level 1 · 0 XP
Chain links broken: 0/1

Reconnaissance

Resource Development

Initial Access

Execution

Persistence

Privilege Escalation

Stealth

Defense Impairment

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1203 Exploitation for Client Execution Inferred

Inferred from CWE CWE-190

How to fix it

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)

Fixed versions

  • paloaltonetworks pan-os: upgrade to 7.1.23 or later (affected from 7.1.0)
  • paloaltonetworks pan-os: upgrade to 8.0.16 or later (affected from 8.0.0)
  • paloaltonetworks pan-os: upgrade to 8.1.7 or later (affected from 8.1.0)
  • f5 big-ip access policy manager: upgrade to 11.6.4 or later (affected from 11.2.1)
  • f5 big-ip access policy manager: upgrade to 12.1.5 or later (affected from 12.1.0)
  • f5 big-ip access policy manager: upgrade to 13.1.1.5 or later (affected from 13.0.0)
  • f5 big-ip access policy manager: upgrade to 14.0.1.1 or later (affected from 14.0.0)
  • f5 big-ip access policy manager: upgrade to 14.1.0.6 or later (affected from 14.1.0)
  • f5 big-ip advanced firewall manager: upgrade to 11.6.4 or later (affected from 11.2.1)
  • f5 big-ip advanced firewall manager: upgrade to 12.1.5 or later (affected from 12.1.0)
  • f5 big-ip advanced firewall manager: upgrade to 13.1.1.5 or later (affected from 13.0.0)
  • f5 big-ip advanced firewall manager: upgrade to 14.0.1.1 or later (affected from 14.0.0)
  • f5 big-ip advanced firewall manager: upgrade to 14.1.0.6 or later (affected from 14.1.0)
  • f5 big-ip analytics: upgrade to 11.6.4 or later (affected from 11.2.1)
  • f5 big-ip analytics: upgrade to 12.1.5 or later (affected from 12.1.0)
  • f5 big-ip analytics: upgrade to 13.1.1.5 or later (affected from 13.0.0)
  • f5 big-ip analytics: upgrade to 14.0.1.1 or later (affected from 14.0.0)
  • f5 big-ip analytics: upgrade to 14.1.0.6 or later (affected from 14.1.0)
  • f5 big-ip application acceleration manager: upgrade to 11.6.4 or later (affected from 11.2.1)
  • f5 big-ip application acceleration manager: upgrade to 12.1.5 or later (affected from 12.1.0)
  • f5 big-ip application acceleration manager: upgrade to 13.1.1.5 or later (affected from 13.0.0)
  • f5 big-ip application acceleration manager: upgrade to 14.0.1.1 or later (affected from 14.0.0)
  • f5 big-ip application acceleration manager: upgrade to 14.1.0.6 or later (affected from 14.1.0)
  • f5 big-ip application security manager: upgrade to 11.6.4 or later (affected from 11.2.1)
  • f5 big-ip application security manager: upgrade to 12.1.5 or later (affected from 12.1.0)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

MITRE ATT&CK mitigations for this chain

  • M1050 Exploit Protection (for T1203) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
  • M1051 Update Software (for T1203) : Perform regular software updates to mitigate exploitation risk. Keeping software up-to-date with the latest security patches helps prevent adversaries from exploiting known vulnerabilities in client software, reducing the risk of successful attacks.
  • M1048 Application Isolation and Sandboxing (for T1203) : Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist. Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. Risks of additional exploits and weaknesses in those systems may still exist.

Detection Generic guidance

  • Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Sources