CVE-2023-33107

CRITICALNVD 8.49.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-12-05), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.4 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 1%CVSS: 8.4Exploit: cisa kev · ssvc active · public exploitExposed: 0

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

Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.

CVSS v3
8.4
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

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
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
56%
KEV
⚠ Exploited

Published

December 5, 2023

Last Modified

October 28, 2025

Advisory Details (2)

Auto-updated Jun 2, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-33107

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 48× in last 7d / 240× 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 491 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

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

  • GitHub PoC264312431/picohaxx
    First seen Jul 18, 2026

    A kernel exploit for Pico 4 devices based on cve-2023-33107

    Open source ↗
  • GitHub PoCketo0422/CVE-2023-33107
    First seen Feb 5, 2026

    full exploit code

    Open source ↗

Frequently asked(6)

What is CVE-2023-33107?
CVE-2023-33107 is a critical vulnerability published on December 5, 2023. Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.
When was CVE-2023-33107 disclosed?
CVE-2023-33107 was first published in the National Vulnerability Database on December 5, 2023, with the most recent update on October 28, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-33107 actively exploited?
Yes. CISA added CVE-2023-33107 to the Known Exploited Vulnerabilities catalog on December 5, 2023, affecting Qualcomm Multiple Chipsets. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2023-33107?
CVE-2023-33107 has a CVSS v3 base score of 8.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2023-33107?
CVE-2023-33107 affects Qualcomm Multiple Chipsets. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2023-33107?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-33107, 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-2023-33107

Explore →

Is Your Infrastructure Affected by CVE-2023-33107?

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