Skip to content
Fencer Intel
high 7.5

CVE-2019-12818 json

An issue was discovered in the Linux kernel before 4.20.15.

published 7y ago modified 4mo ago also EUVD-2019-4399

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.0%
EPSS 6.0% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

An issue was discovered in the Linux kernel before 4.20.15. The nfc_llcp_build_tlv function in net/nfc/llcp_commands.c may return NULL. If the caller does not check for this, it will trigger a NULL pointer dereference. This will cause denial of service. This affects nfc_llcp_build_gb in net/nfc/llcp_core.c.

Patch / fix

  • linux linux_kernel 4.20.15
  • linux Debian 14, Debian 13, Debian 12 4.19.28-1

debian advisories DEBIAN-CVE-2019-12818

  • linux Ubuntu 16.04 LTS 4.4.0-148.174
  • linux Ubuntu 18.04 LTS 4.15.0-58.64
  • linux-aws Ubuntu 14.04 LTS 4.4.0-1044.47
  • linux-aws Ubuntu 16.04 LTS 4.4.0-1083.93
  • linux-aws Ubuntu 18.04 LTS 4.15.0-1047.49
  • linux-gcp Ubuntu 16.04 LTS 4.15.0-1040.42~16.04.1
  • linux-gcp Ubuntu 18.04 LTS 4.15.0-1040.42
  • linux-hwe Ubuntu 16.04 LTS 4.15.0-58.64~16.04.1

ubuntu advisories UBUNTU-CVE-2019-12818

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-rt SLE Real Time 12 SP4 4.12.14-8.3.1
  • kernel-syms-rt SLE Real Time 12 SP4 4.12.14-8.3.1
  • kernel-rt_debug SLE Real Time 12 SP4 4.12.14-8.3.1
  • kernel-source-rt SLE Real Time 12 SP4 4.12.14-8.3.1
  • kernel-source-rt Real Time Module 15 SP1 4.12.14-14.8.1
  • kernel-rt Real Time Module 15 SP1 4.12.14-14.8.1
  • kernel-syms-rt Real Time Module 15 SP1 4.12.14-14.8.1
  • kernel-rt_debug Real Time Module 15 SP1 4.12.14-14.8.1

suse advisories SUSE-SU-2019:2450-1SUSE-SU-2019:2430-1SUSE-SU-2019:2069-1SUSE-SU-2019:1870-1SUSE-SU-2019:1855-1SUSE-SU-2019:1852-1

  • kernel-syms openSUSE Leap 15.0 4.12.14-lp150.12.64.1
  • kernel-obs-qa openSUSE Leap 15.0 4.12.14-lp150.12.64.1
  • kernel-source openSUSE Leap 15.0 4.12.14-lp150.12.64.1
  • kernel-default openSUSE Leap 15.0 4.12.14-lp150.12.64.1
  • kernel-vanilla openSUSE Leap 15.0 4.12.14-lp150.12.64.1
  • kernel-kvmsmall openSUSE Leap 15.0 4.12.14-lp150.12.64.1
  • kernel-obs-build openSUSE Leap 15.0 4.12.14-lp150.12.64.1
  • kernel-syms openSUSE Leap 15.1 4.12.14-lp151.28.7.1

opensuse advisories openSUSE-SU-2019:1579-1openSUSE-SU-2019:1571-1

Is CVE-2019-12818 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-2019-12818 updated cvss 6.2

kernel: null-pointer dereference in function nfc_llcp_build_tlv in net/nfc/llcp_commands.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-rt, kernel-core, kernel-tools, +29 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

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

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
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.