CVE-2019-19241

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 1.1%, top 38% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
7.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), public exploit)
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: Exploit-DB (verified) · public exploitExposed: 0

A fix is available — apply it.

In the Linux kernel before 5.4.2, the io_uring feature leads to requests that inadvertently have UID 0 and full capabilities, aka CID-181e448d8709. This is related to fs/io-wq.c, fs/io_uring.c, and net/socket.c. For example, an attacker can bypass intended restrictions on adding an IPv4 address to the loopback interface. This occurs because IORING_OP_SENDMSG operations, although requested in the context of an unprivileged user, are sometimes performed by a kernel worker thread without considering that context.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
66(Track)
EG Risk 66/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
Severity78% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
63%
KEV
Not listed

Published

December 17, 2019

Last Modified

November 21, 2024

References (12)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-virtual (5.3.0.40.34) @ eoan2026-05-27ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux—5.3.15-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—5.3.15-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—5.3.15-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—5.3.15-1—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 27× 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 122 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-47779✓ verified
    First seen Dec 16, 2019

    Linux 5.3 - Privilege Escalation via io_uring Offload of sendmsg() onto Kernel Thread with Kernel Creds

    Open source ↗

Frequently asked(5)

What is CVE-2019-19241?
CVE-2019-19241 is a high vulnerability published on December 17, 2019. In the Linux kernel before 5.4.2, the iouring feature leads to requests that inadvertently have UID 0 and full capabilities, aka CID-181e448d8709. This is related to fs/io-wq.c, fs/iouring.c, and net/socket.c. For example, an attacker can bypass intended restrictions on adding an IPv4 address to…
When was CVE-2019-19241 disclosed?
CVE-2019-19241 was first published in the National Vulnerability Database on December 17, 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-19241 actively exploited?
CVE-2019-19241 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 37.3% of all scored CVEs.
What is the CVSS score of CVE-2019-19241?
CVE-2019-19241 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2019-19241?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-19241, 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-19241

Explore →

Is Your Infrastructure Affected by CVE-2019-19241?

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

Start Free Scan →Browse All CVEs