Skip to content
Fencer Intel
high 7.8

CVE-2018-8822 json

Incorrect buffer length handling in the ncp_read_kernel function in fs/ncpfs/ncplib_kernel.c in the Linux kernel through 4.15.11, and in dr…

published 8y ago modified 4mo ago also EUVD-2018-20431

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

Incorrect buffer length handling in the ncp_read_kernel function in fs/ncpfs/ncplib_kernel.c in the Linux kernel through 4.15.11, and in drivers/staging/ncpfs/ncplib_kernel.c in the Linux kernel 4.16-rc through 4.16-rc6, could be exploited by malicious NCPFS servers to crash the kernel or execute code.

Patch / fix

  • linux linux_kernel 3.2.102, 3.16.57, 3.18.103, 4.1.52, 4.4.125, 4.9.91, 4.14.31, 4.15.14
  • linux Debian 14, Debian 13, Debian 12 4.15.17-1

debian advisories DEBIAN-CVE-2018-8822

  • linux Ubuntu 14.04 LTS 3.13.0-149.199
  • linux Ubuntu 16.04 LTS 4.4.0-127.153
  • linux-aws Ubuntu 14.04 LTS 4.4.0-1022.22
  • linux-aws Ubuntu 16.04 LTS 4.4.0-1060.69
  • linux-gcp Ubuntu 16.04 LTS 4.13.0-1017.21
  • linux-hwe Ubuntu 16.04 LTS 4.13.0-43.48~16.04.1
  • linux-kvm Ubuntu 16.04 LTS 4.4.0-1026.31
  • linux-oem Ubuntu 16.04 LTS 4.13.0-1028.31

ubuntu advisories UBUNTU-CVE-2018-8822

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-syms SLES 12 SP2-BCL, OpenStack Cloud 7, Enterprise Storage 4 +2 more 4.4.121-92.73.1
  • kernel-source SLES 12 SP2-BCL, OpenStack Cloud 7, Enterprise Storage 4 +2 more 4.4.121-92.73.1
  • kernel-default SLES 12 SP2-BCL, OpenStack Cloud 7, Enterprise Storage 4 +2 more 4.4.121-92.73.1
  • kgraft-patch-SLE12-SP2_Update_21 SLES 12 SP2-BCL, OpenStack Cloud 7, Enterprise Storage 4 +2 more 1-3.3.1
  • kernel-rt SLE Real Time 11 SP4 3.0.101.rt130-69.24.1
  • kernel-syms-rt SLE Real Time 11 SP4 3.0.101.rt130-69.24.1
  • kernel-rt_trace SLE Real Time 11 SP4 3.0.101.rt130-69.24.1
  • kernel-source-rt SLE Real Time 11 SP4 3.0.101.rt130-69.24.1

suse advisories SUSE-SU-2018:1173-2SUSE-SU-2018:1309-1SUSE-SU-2018:1220-1SUSE-SU-2018:1221-1SUSE-SU-2018:1217-1SUSE-SU-2018:1173-1

  • kernel-source openSUSE Tumbleweed 5.14.6-1.4
  • kernel-source openSUSE Tumbleweed 6.6.17-1.1

opensuse advisories openSUSE-SU-2024:10728-1openSUSE-SU-2024:13704-1

Is CVE-2018-8822 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-8822 updated cvss 6.4

kernel: Memory corruption in ncp_read_kernel function in fs/ncpfs/ncplib_kernel.c

  • Red Hat Enterprise Linux 5 kernel Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, kernel-alt, python-perf, +9 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-core, kernel-tools, python3-perf, +17 more Red Hat Enterprise MRG 2 kernel-rt, mrg-rt-release, kernel-rt-trace, kernel-rt-vanilla, kernel-rt-firmware
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.