CVE-2019-13272
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
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…
rank 76 = 40 + 20 + 0 + 10 + 6
rank@v1 · act now
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.52199 · CISA KEV listed · without this subject the record ranks 36
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 7.8, from NVD · without this subject the record ranks 56
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
no persisting rise in 365 days · without this subject the record ranks 76
How much of the world it touches
NVD CPE configurations
20 products in the CPE ranges · without this subject the record ranks 66
Someone else already set the date
CISA KEV remediation due date
CISA remediation date held · without this subject the record ranks 70
$2.60M = $4.99M incident cost x 1 exposure x 0.52199 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
Hindsight · the state
Foresight · where to check next
No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.
Check a version against this record
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Set up a watchlist (needs a Practitioner account)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
AcceptDeferPatch by…Not affectedMitigatedChoose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Exploited in the wild · CISA KEV listed, 2021-12-10.
Affected & Fixed Versions as published
Show all 20 published ranges
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
What it is stated by the CNA
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. receipt
Read the rest of the CNA's description
NOTE: SELinux deny_ptrace might be a usable workaround in some environments.
NVD's analysis a second authority
- severity
- 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- affected versions
- linux kernel >= 3.16.52 < 3.16.71; linux kernel >= 4.1.39 < 4.2; linux kernel >= 4.4.40 < 4.4.185; and 17 more, listed in full below
- also scored by
- 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
check it yourself packetstormsecurity.com bugs.chromium.org cdn.kernel.org github.com git.kernel.org bugzilla.suse.com +14 morereceipt
Dated events
Movement the material steps
This score more than doubled inside 72 hours. Both observations are in the full history below.
Show all 53 observations
53 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The full biography
Listed by CISA 877 days after it published, exploit probability more than doubled between 2021-09-14 and 2021-09-16 (0.1282 → 0.52074) and the record had been public for 7 years, 1 month when this index was last written.
No material movement in 81 days as of the last ingest this index recorded.
Siblings and hubs
Records related to this one
None. No alias set, and nothing in the corpus cites this identifier or shares its product family within 60 days.
Browse the index from here
These are index-wide views, not findings about CVE-2019-13272.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.