CVE-2022-20409

MEDIUMNVD 6.76.7—
EchelonGraph scoreMEDIUM confidence

Score 6.7 from GitHub Security Advisory published 2022-10-12. NVD baseline CVSS 6.7; sources differ by 0.0.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In io_identity_cow of io_uring.c, there is a possible way to corrupt memory due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-238177383References: Upstream kernel

CVSS v3
6.7
EG Score
6.7(medium)
EPSS
42.9%
KEV
Not listed

Published

October 11, 2022

Last Modified

November 21, 2024

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 48× 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.

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

Publicly available exploits

(1 reference)

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

  • GitHub PoCMarkakd/bad_io_uring
    First seen Nov 21, 2022

    Android kernel exploitation for CVE-2022-20409

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-20409?
CVE-2022-20409 is a medium vulnerability published on October 11, 2022. In ioidentitycow of io_uring.c, there is a possible way to corrupt memory due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:…
When was CVE-2022-20409 disclosed?
CVE-2022-20409 was first published in the National Vulnerability Database on October 11, 2022, 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-2022-20409 actively exploited?
CVE-2022-20409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-20409?
CVE-2022-20409 has a CVSS v3 base score of 6.7 (NVD).
How do I remediate CVE-2022-20409?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-20409, 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

Explore the affected products and dependency analysis for CVE-2022-20409

Explore →

Is Your Infrastructure Affected by CVE-2022-20409?

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

Start Free Scan →Browse All CVEs