Skip to content
Server Security Center
KEVhigh7.8

CVE-2019-13272: Linux Kernel Improper Privilege Management

Linux Kernel · listed in the CISA catalog of actively exploited vulnerabilities since 2021-12-10.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
52%
higher than 98.9% of all CVEs
Added to CISA KEV
2021-12-10
US federal due date 2022-06-10
Ubuntu priority
high

CVE-2019-13272 explained

CVE-2019-13272 is a flaw in the Linux kernel's ptrace_link function in kernel/ptrace.c, affecting kernels before 5.1.17. The kernel mishandles recording the credentials of a process that creates a ptrace relationship. A local user can use this to gain root access. The vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog.

Impact

A local user with low privileges can obtain root access without user interaction. This works in scenarios where a parent process drops privileges and calls execve. The description names Polkit's pkexec helper as one example path. Successful exploitation gives full control over confidentiality, integrity and availability of the system. An object lifetime issue in the same code can also cause a kernel panic.

Who is affected

The linux source package is affected on the listed Ubuntu releases. Ubuntu 16.04 LTS is fixed in 4.4.0-159.187; this release is end of life. Ubuntu 18.04 LTS is fixed in 4.15.0-58.64 in the standard archive; standard support for this release has ended and further fixes come only with Ubuntu Pro (ESM). Other Ubuntu kernel flavours are listed on the page.

Written with AI from the data on this page and checked against it automatically.

Official description

In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to create a ptrace relationship, which allows local users to obtain root access by leveraging certain scenarios with a parent-child process relationship, where a parent drops privileges and calls execve (potentially allowing control by an attacker). One contributing factor is an object lifetime issue (which can also cause a panic).

Another contributing factor is incorrect marking of a ptrace relationship as privileged, which is exploitable through (for example) Polkit's pkexec helper with PTRACE_TRACEME.

NOTE: SELinux deny_ptrace might be a usable workaround in some environments.

CISA required action: Apply updates per vendor instructions.

CISA notes

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

20 more Ubuntu kernel flavours (cloud, HWE, low-latency, real-time …) – 31 release entries
  • 24.04 linux-raspi-realtime: no fixed version published
  • 22.04 linux-intel-iot-realtime: no fixed version published
  • 22.04 linux-realtime: no fixed version published
  • 22.04 linux-riscv: no fixed version published
  • 20.04 linux-azure-fde: no fixed version published
  • 20.04 linux-gke: no fixed version published
  • 20.04 linux-riscv: no fixed version published
  • 18.04 linux-aws: 4.15.0-1047.49
  • 18.04 linux-azure: 5.0.0-1014.14~18.04.1
  • 18.04 linux-gcp: 4.15.0-1040.42
  • 18.04 linux-gke-4.15: 4.15.0-1040.42
  • 18.04 linux-hwe: 5.0.0-25.26~18.04.1
  • 18.04 linux-hwe-edge: no fixed version published
  • 18.04 linux-kvm: 4.15.0-1042.42
  • 18.04 linux-oem: 4.15.0-1050.57
  • 18.04 linux-oem-osp1: 5.0.0-1018.20
  • 18.04 linux-oracle: 4.15.0-1021.23
  • 18.04 linux-raspi2: 4.15.0-1043.46
  • 18.04 linux-snapdragon: 4.15.0-1060.66
  • 16.04 linux-aws: 4.4.0-1090.101
  • 16.04 linux-aws-hwe: 4.15.0-1047.49~16.04.1
  • 16.04 linux-azure: 4.15.0-1055.60
  • 16.04 linux-gcp: 4.15.0-1040.42~16.04.1
  • 16.04 linux-hwe: 4.15.0-58.64~16.04.1
  • 16.04 linux-kvm: 4.4.0-1054.61
  • 16.04 linux-oracle: 4.15.0-1021.23~16.04.1
  • 16.04 linux-raspi2: 4.4.0-1118.127
  • 16.04 linux-snapdragon: 4.4.0-1122.128
  • 14.04 linux-aws (Pro): 4.4.0-1054.58
  • 14.04 linux-azure (Pro): 4.15.0-1059.64~14.04.1
  • 14.04 linux-lts-xenial (Pro): 4.4.0-164.192~14.04.1

What to do

  1. Update the linux kernel packages to the fixed version for your release or later.
  2. Reboot each system so the updated kernel is actually running.
  3. Confirm after reboot that the running kernel matches the fixed version.
  4. Check the page for other kernel flavours you run and update those as well.
  5. Plan an upgrade from end-of-life Ubuntu 16.04 LTS to a supported release.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Kernel fixes arrive as a new kernel package (new ABI) through the metapackages, so upgrade the whole system and boot into the new kernel.

1. Show the running kernel and the version of its package

uname -r && dpkg-query -W -f='${Version}\n' "linux-image-$(uname -r)"

2. Compare with the fixed version for your release and kernel flavour from the table

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the new kernel, then reboot (or apply a livepatch)

sudo apt update && sudo apt full-upgrade && sudo reboot

On Debian, signed kernel images come from the linux-signed-* source packages; the version to compare is the same.

Rows marked “fix via Ubuntu Pro”: these fixes are only installable with an Ubuntu Pro subscription (ESM). Attach the machine first (sudo pro attach, then sudo pro enable esm-infra esm-apps), then run the commands above.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-269

Questions about CVE-2019-13272

Is this vulnerability exploited in practice?
Yes. CISA added CVE-2019-13272 to its Known Exploited Vulnerabilities catalog on 2021-12-10. The required action is to apply updates per vendor instructions.
Can it be exploited remotely?
No. The attack vector is local. An attacker needs a local account with low privileges, but no user interaction is required to gain root.
Is there a workaround if I cannot update right away?
The description notes that SELinux deny_ptrace might be a usable workaround in some environments. Updating the kernel and rebooting remains the fix.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.