CVE-2019-3901

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2022-05-24. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

A fix is available — apply it.

A race condition in perf_event_open() allows local attackers to leak sensitive data from setuid programs. As no relevant locks (in particular the cred_guard_mutex) are held during the ptrace_may_access() call, it is possible for the specified target task to perform an execve() syscall with setuid execution before perf_event_alloc() actually attaches to it, allowing an attacker to bypass the ptrace_may_access() check and the perf_event_exit_task(current) call that is performed in install_exec_creds() during privileged execve() calls. This issue affects kernel versions before 4.8.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
26(Track)
EG Risk 26/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

April 22, 2019

Last Modified

November 21, 2024

References (10)

Vendor Advisories for CVE-2019-3901(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:3.10.0-957.56.1.el72020-07-07redhat
redhatkernel-0:3.10.0-1062.26.1.el72020-06-11redhat
redhatkernel-rt-0:3.10.0-1127.rt56.1093.el72020-03-31redhat
redhatkernel-0:3.10.0-1127.el72020-03-31redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux—4.6.1-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—4.6.1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—4.6.1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—4.6.1-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
linux3.16.36-1 ... 3.16.7-ckt9-3~deb8u1~bpo70+1 (63 versions)3.16.68-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 147 total refreshes for this CVE.

  1. 2026-09-18 19:23 UTCEPSS rescore
  2. 2026-09-17 19:22 UTCEPSS rescore
  3. 2026-09-16 14:04 UTCEPSS rescore
  4. 2026-09-15 03:06 UTCEPSS rescore
  5. 2026-09-13 16:42 UTCEPSS rescore
  6. 2026-09-12 14:56 UTCEPSS rescore
  7. 2026-09-11 14:48 UTCEPSS rescore
  8. 2026-09-11 09:32 UTCEPSS rescore
  9. 2026-09-08 21:55 UTCEPSS rescore
  10. 2026-09-08 13:04 UTCOSV refresh
  11. 2026-09-06 13:44 UTCEPSS rescore
  12. 2026-09-05 15:24 UTCEPSS rescore
  13. 2026-09-04 13:56 UTCEPSS rescore
  14. 2026-09-02 14:08 UTCEPSS rescore
  15. 2026-09-01 03:32 UTCEPSS rescore
  16. 2026-08-30 01:18 UTCEPSS rescore
  17. 2026-08-27 14:21 UTCEPSS rescore
  18. 2026-08-26 14:42 UTCEPSS rescore
  19. 2026-08-25 13:45 UTCEPSS rescore
  20. 2026-08-21 23:41 UTCOSV refresh
  21. 2026-08-19 17:00 UTCEPSS rescore
  22. 2026-08-18 13:44 UTCEPSS rescore
  23. 2026-08-17 13:43 UTCEPSS rescore
  24. 2026-08-15 01:26 UTCEPSS rescore
  25. 2026-08-13 21:57 UTCEPSS rescore
Show 75 more
  1. 2026-08-12 13:47 UTCEPSS rescore
  2. 2026-08-09 13:43 UTCEPSS rescore
  3. 2026-08-08 16:33 UTCEPSS rescore
  4. 2026-08-07 16:23 UTCEPSS rescore
  5. 2026-08-06 05:21 UTCOSV refresh
  6. 2026-08-05 19:13 UTCEPSS rescore
  7. 2026-08-04 15:05 UTCEPSS rescore
  8. 2026-08-04 10:34 UTCEPSS rescore
  9. 2026-08-03 10:32 UTCEPSS rescore
  10. 2026-08-02 02:23 UTCEPSS rescore
  11. 2026-08-01 04:12 UTCEPSS rescore
  12. 2026-07-30 16:24 UTCEPSS rescore
  13. 2026-07-30 01:27 UTCEPSS rescore
  14. 2026-07-28 15:32 UTCEPSS rescore
  15. 2026-07-26 14:51 UTCEPSS rescore
  16. 2026-07-25 14:14 UTCEPSS rescore
  17. 2026-07-24 14:14 UTCEPSS rescore
  18. 2026-07-23 14:15 UTCEPSS rescore
  19. 2026-07-23 01:45 UTCEG score recompute
  20. 2026-07-22 22:26 UTCEG score recompute
  21. 2026-07-22 14:05 UTCEPSS rescore
  22. 2026-07-21 15:22 UTCEPSS rescore
  23. 2026-07-21 15:22 UTCEPSS rescore
  24. 2026-07-20 18:02 UTCOSV refresh
  25. 2026-07-20 17:04 UTCEPSS rescore
  26. 2026-07-19 14:28 UTCEPSS rescore
  27. 2026-07-19 14:28 UTCEPSS rescore
  28. 2026-07-19 02:26 UTCEPSS rescore
  29. 2026-07-19 02:26 UTCEPSS rescore
  30. 2026-07-18 10:02 UTCEPSS rescore
  31. 2026-07-16 16:59 UTCEPSS rescore
  32. 2026-07-16 16:59 UTCEPSS rescore
  33. 2026-07-15 16:55 UTCEPSS rescore
  34. 2026-07-15 01:57 UTCEPSS rescore
  35. 2026-07-13 22:27 UTCEPSS rescore
  36. 2026-07-13 22:27 UTCEPSS rescore
  37. 2026-07-13 06:10 UTCEPSS rescore
  38. 2026-07-13 06:10 UTCEPSS rescore
  39. 2026-07-12 05:44 UTCEPSS rescore
  40. 2026-07-12 05:43 UTCEPSS rescore
  41. 2026-07-11 08:24 UTCEPSS rescore
  42. 2026-07-11 08:24 UTCEPSS rescore
  43. 2026-07-09 19:06 UTCEPSS rescore
  44. 2026-07-08 15:11 UTCEPSS rescore
  45. 2026-07-07 13:43 UTCEPSS rescore
  46. 2026-07-06 16:25 UTCEPSS rescore
  47. 2026-07-06 16:25 UTCEPSS rescore
  48. 2026-07-06 02:20 UTCEPSS rescore
  49. 2026-07-06 02:20 UTCEPSS rescore
  50. 2026-07-05 02:27 UTCEPSS rescore
  51. 2026-07-04 06:28 UTCEPSS rescore
  52. 2026-07-03 13:26 UTCOSV refresh
  53. 2026-07-01 15:03 UTCEPSS rescore
  54. 2026-07-01 15:03 UTCEPSS rescore
  55. 2026-06-30 23:20 UTCEPSS rescore
  56. 2026-06-29 14:03 UTCEPSS rescore
  57. 2026-06-28 14:04 UTCEPSS rescore
  58. 2026-06-28 04:54 UTCEPSS rescore
  59. 2026-06-28 04:54 UTCEPSS rescore
  60. 2026-06-27 03:06 UTCEPSS rescore
  61. 2026-06-25 13:47 UTCEPSS rescore
  62. 2026-06-25 13:47 UTCEPSS rescore
  63. 2026-06-24 14:03 UTCEPSS rescore
  64. 2026-06-24 14:03 UTCEPSS rescore
  65. 2026-06-23 21:31 UTCEPSS rescore
  66. 2026-06-23 21:31 UTCEPSS rescore
  67. 2026-06-22 14:23 UTCEPSS rescore
  68. 2026-06-22 14:23 UTCEPSS rescore
  69. 2026-06-21 14:54 UTCEPSS rescore
  70. 2026-06-21 14:54 UTCEPSS rescore
  71. 2026-06-21 01:57 UTCEPSS rescore
  72. 2026-06-21 01:57 UTCEPSS rescore
  73. 2026-06-19 19:23 UTCEPSS rescore
  74. 2026-06-19 19:23 UTCEPSS rescore
  75. 2026-06-18 17:50 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-3901?
CVE-2019-3901 is a medium vulnerability published on April 22, 2019. A race condition in perfeventopen() allows local attackers to leak sensitive data from setuid programs. As no relevant locks (in particular the credguardmutex) are held during the ptracemayaccess() call, it is possible for the specified target task to perform an execve() syscall with setuid…
When was CVE-2019-3901 disclosed?
CVE-2019-3901 was first published in the National Vulnerability Database on April 22, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-3901 actively exploited?
CVE-2019-3901 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.6% of all scored CVEs.
What is the CVSS score of CVE-2019-3901?
CVE-2019-3901 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2019-3901?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-3901, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-3901

Explore →

Is Your Infrastructure Affected by CVE-2019-3901?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs