Skip to content
Fencer Intel
medium 4.4

CVE-2019-19318 json

In the Linux kernel 5.3.11, mounting a crafted btrfs image twice can cause an rwsem_down_write_slowpath use-after-free because (in rwsem_ca…

published 6y ago modified 4mo ago also EUVD-2019-8941

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

Summary

In the Linux kernel 5.3.11, mounting a crafted btrfs image twice can cause an rwsem_down_write_slowpath use-after-free because (in rwsem_can_spin_on_owner in kernel/locking/rwsem.c) rwsem_owner_flags returns an already freed pointer,

Patch / fix

  • linux Debian 14, Debian 13, Debian 12 5.4.6-1

debian advisories DEBIAN-CVE-2019-19318

  • linux-hwe-edge Ubuntu 18.04 LTS 5.3.0-22.24~18.04.1

ubuntu advisories UBUNTU-CVE-2019-19318

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 for SAP 15, SLES 15-LTSS, SLE High Performance Computing 15-LTSS +1 more 4.12.14-150.52.1
  • kernel-source SLES for SAP 15, SLES 15-LTSS, SLE High Performance Computing 15-LTSS +1 more 4.12.14-150.52.1
  • kernel-default SLES for SAP 15, SLES 15-LTSS, SLE Live Patching 15 +3 more 4.12.14-150.52.1
  • kernel-vanilla SLES for SAP 15, SLES 15-LTSS, SLE High Performance Computing 15-LTSS +1 more 4.12.14-150.52.1
  • kernel-obs-build SLES for SAP 15, SLES 15-LTSS, SLE High Performance Computing 15-LTSS +1 more 4.12.14-150.52.1
  • 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

suse advisories SUSE-SU-2020:1663-1SUSE-SU-2020:0613-1SUSE-SU-2020:0605-1SUSE-SU-2020:0599-1SUSE-SU-2020:0584-1SUSE-SU-2020:0580-1

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

opensuse advisories openSUSE-SU-2020:0336-1

Is CVE-2019-19318 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-19318 updated cvss 4.4

kernel: use-after-free in rwsem_down_write_slowpath in kernel/locking/rwsem.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

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

Exploits and checks

  • github.com https://github.com/bobfuzzer/CVE/tree/master/CVE-2019-19318 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 2.1 AV:L/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.