LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13272: In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentia...

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.

HighCVSS 7.8Known exploitedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2019-13272 is a Linux kernel local privilege escalation flaw. An attacker who already has local code execution or a low-privileged account may be able to gain root. Business urgency is high for multi-user Linux systems, shared hosting, developer workstations, and servers where untrusted code can run.

Executive priority

Treat as urgent patching for Linux fleets because KEV status indicates real-world exploitation and successful abuse can give root access. Prioritize externally reachable systems with any local execution path, shared-user infrastructure, and business-critical Linux hosts.

Technical view

The flaw is in Linux kernel ptrace_link before 5.1.17. It mishandles credential recording for ptrace relationships, including privileged relationship marking and object lifetime handling. The CVE notes exploitation through parent-child process scenarios and Polkit pkexec with PTRACE_TRACEME; object lifetime issues may also cause kernel panic.

Likely exposure

Exposure is most relevant on Linux systems running vulnerable kernel builds before the fixed upstream kernel or missing vendor backports. Local access is required, so internet-facing exposure depends on whether attackers can first obtain shell access, run workloads, or abuse shared-user environments.

Exploitation context

The provided bundle marks this CVE as KEV, so active exploitation should be assumed for prioritization. Public references include detailed vulnerability research and exploit-oriented writeups. The issue is local, low-complexity, and can produce full confidentiality, integrity, and availability impact.

Researcher notes

Evidence identifies the vulnerable area as kernel/ptrace.c ptrace_link and the fix in upstream commit 6994eefb. The bundle does not provide a complete affected-distribution matrix, so validation should rely on each vendor advisory and installed package backport metadata.

Mitigation direction

  • Apply kernel updates from the relevant Linux distribution vendor advisory.
  • Confirm the running kernel includes the upstream fix or vendor backport.
  • Consider SELinux deny_ptrace where compatible with operational requirements.
  • Prioritize shared systems and hosts running untrusted code.
  • Reboot systems after kernel update where required.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, and images.
  • Map each kernel package to vendor advisories or backport status.
  • Check whether affected systems use Polkit pkexec and allow local users.
  • Verify SELinux ptrace restrictions if using them as interim mitigation.
  • Confirm patched kernels are active after reboot.
Prepared
Confidence
high
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-13272 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
25Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2019-13272Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.