Exploited Known exploited (KEV) CVE-2018-14634

No single party to fix it: an integer overflow in the Linux kernel

Linux Kernel ・Added to KEV Jan 26, 2026 ・Federal remediation due 2026-02-16

A privilege escalation flaw added to the catalog on 26 January 2026. Its note says the flaw sits in a common component and that patching status must be checked with each vendor.

Key facts

  • CVE IDCVE-2018-14634
  • Affected (vendor / product)Linux Kernel
  • CWECWE-190
  • ExploitationListed in CISA KEV (exploitation confirmed)
  • Remediation due2026-02-16 (U.S. federal civilian agencies, BOD 22-01)
  • Required action (CISA)Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Key points

  • An integer overflow in the Linux kernel function create_elf_tables() enabling privilege escalation by an unprivileged user.
  • Added 26 January 2026 with a 16 February deadline, a twenty-one-day window.
  • The note directs readers to check patching status with each vendor, and references point at the kernel repository.
  • The kernel appears 28 times in the catalog, with ransomware use confirmed on two entries.

1Privilege escalation through an integer overflow in the Linux kernel

CVE-2018-14634 is a vulnerability arising from an integer overflow in the Linux kernel function create_elf_tables(). The record states that an unprivileged local user with access to a SUID or otherwise privileged binary could escalate privileges. It was added to the catalog on 26 January 2026 with a remediation date of 16 February, a twenty-one-day window.

Because the kernel underpins many products, the note asks readers to check patching status with each vendor, product by product.

2The record does not say who fixes it

Elsewhere in the catalog, the Flash Player record has nothing left to fix. Here a fix exists, but there is no single party who applies it.

Times the Linux kernel appears28fifth most of any product
Window on this record21 daysadded 26 January 2026, due 16 February
Ransomware use confirmed among the 282of 28 entries

The note states that the flaw affects a component used across many products and directs readers to check patching status with each vendor. The references point at the kernel's own repository rather than any product's update notice.

3The path a fix travels

  1. 1Fixed upstreamThe correction lands in the kernel source
  2. 2Distributions pick it upEach distribution carries it into its own release
  3. 3Product vendors pick it upDevices and software built on that distribution ship an update
  4. 4It reaches the userThe update is applied to the machine in front of you

From where a user stands, it is entirely normal for upstream to be fixed while nothing has yet arrived locally. The catalog window is twenty-one days; how long this path takes depends on each stage.

4Where privilege escalation sits

This is the type in which an unprivileged user climbs by way of a privileged binary. It is not a way in from outside but a way to widen damage once inside. The kernel's 28 entries scatter across weakness types — out-of-bounds write (CWE-787) four, use after free (CWE-416) three — with identifier years from 2010 to 2026.

The next article takes up a record with a window of only three days.

Why it matters

Shared-component flaws cannot be followed by product name. Knowing what your products are built on, and confirming that upstream fixes have arrived, requires a separate process.

FAQ

Why must each vendor be checked separately?
The kernel underpins many products, and when an upstream fix reaches each of them differs product by product.
How does an integer overflow lead to privilege escalation?
A calculation wraps past its intended range, corrupting decisions such as how much memory to allocate. Here the record describes escalation by way of a privileged binary.
Is an upstream fix enough?
No. The issue closes only when the update reaches your environment. Verify that separately from the upstream state.

Sources (primary)

This article is an independent organization based on the U.S. official data below. Always verify the exact, latest details and applicability with the official and vendor sources.

#KEV#Known exploited#Linux kernel#Privilege escalation#Supply chain
Disclaimer: This site independently summarizes and classifies information based on official data sources. Always verify the latest and accurate information with the official sources. Content on finance, health, legal, and security is information, not advice. This site is not an official website of the U.S. government.