Skip to content
Fencer Vulns
high 7.5

CVE-2019-19049 json

A memory leak in the unittest_data_add() function in drivers/of/unittest.c in the Linux kernel before 5.3.10 allows attackers to cause a de…

published 2019-11-18 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-8688

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

Summary

A memory leak in the unittest_data_add() function in drivers/of/unittest.c in the Linux kernel before 5.3.10 allows attackers to cause a denial of service (memory consumption) by triggering of_fdt_unflatten_tree() failures, aka CID-e13de8fe0d6a. NOTE: third parties dispute the relevance of this because unittest.c can only be reached during boot

Patch / fix

  • linux linux_kernel 4.4.200, 4.9.200, 4.14.153, 4.19.83, 5.3.10
  • linux Debian 14, Debian 13, Debian 12 5.3.15-1

debian advisories DEBIAN-CVE-2019-19049

  • linux-aws Ubuntu Pro 14.04 LTS 4.4.0-1059.63
  • linux-fips Ubuntu Pro FIPS-updates 16.04 LTS 4.4.0-1026.31
  • linux-azure Ubuntu Pro 14.04 LTS 4.15.0-1066.71~14.04.1
  • linux-aws-fips Ubuntu Pro FIPS-updates 18.04 LTS 4.15.0-2018.18
  • linux-azure-fips Ubuntu Pro FIPS-updates 18.04 LTS 4.15.0-2006.7
  • linux-lts-xenial Ubuntu Pro 14.04 LTS 4.4.0-170.199~14.04.1

ubuntu advisories UBUNTU-CVE-2019-19049

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

suse advisories SUSE-SU-2020:0613-1SUSE-SU-2020:0599-1SUSE-SU-2020:0093-1SUSE-SU-2019:3381-1SUSE-SU-2019:3372-1SUSE-SU-2019:3371-1

  • kernel-syms openSUSE Leap 15.1 4.12.14-lp151.28.36.1
  • kernel-obs-qa openSUSE Leap 15.1 4.12.14-lp151.28.36.1
  • kernel-source openSUSE Leap 15.1 4.12.14-lp151.28.36.1
  • kernel-default openSUSE Leap 15.1 4.12.14-lp151.28.36.1
  • kernel-vanilla openSUSE Leap 15.1 4.12.14-lp151.28.36.1
  • kernel-kvmsmall openSUSE Leap 15.1 4.12.14-lp151.28.36.1
  • kernel-obs-build openSUSE Leap 15.1 4.12.14-lp151.28.36.1

opensuse advisories openSUSE-SU-2019:2675-1

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-19049 updated cvss 6.2

kernel: dos in unittest_data_add() function in drivers/of/unittest.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
    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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

3.60% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime
Technology feeds

References

Sources

Fencer Vulns 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.