In BootRom, there is a possible unchecked write address. This could lead to local escalation of privilege with no additional execution privileges needed.
CVE-2022-38694
“—” beside the score: it is equal to NVD's CVSS score.
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-02. NVD baseline CVSS 7.8; sources differ by 0.0.
Also known asEUVD-2022-41263 (ENISA EUVD) · GHSA-9x9c-rv2f-m4v9 (GitHub Security Advisories)Source: ENISA EUVD
- Public exploit or proof-of-concept code is available
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHmedium confidence
- EG Risk
- 51EG Risk 51/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule. - EPSS PROB
- 0.6%
- EPSS %ILE
- 48th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 1, 2025
Last Modified
April 15, 2026
Advisory Details (1)
Auto-updated Oct 8, 2026Unisoc ROM Vulnerabilities in SoCs | NCC Group
https://www.nccgroup.com/research-blog/there-s-another-hole-in-your-soc-unisoc-rom-vulnerabilities/Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 39× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 96 of 241 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 145 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:38 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-30 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-29 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-28 16:25 UTCGHSA enrichmentGHSA-9x9c-rv2f-m4v9 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-27 21:33 UTCEG score recompute
- 2026-10-27 21:33 UTCGHSA enrichmentGHSA-9x9c-rv2f-m4v9 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-25 18:02 UTCEG score recompute
- 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-21 06:26 UTCEG score recompute
- 2026-10-21 06:26 UTCGHSA enrichmentGHSA-9x9c-rv2f-m4v9 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-18 08:29 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
Show 71 moreShow fewer
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-12 18:49 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-11 23:13 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-01 19:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-30 16:02 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-22 14:45 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-17 19:24 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-10 14:08 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
- 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
- 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
- 2026-07-28 15:33 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
Publicly available exploits
(10 references)Public exploit code is referenced for this CVE (9 GitHub PoCs), as is 1 GitHub checker repository. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.
- GitHub PoCxun404/spd_dump-macosPublished Aug 18, 2026
UNISOC BootROM/FDL flasher for macOS: patched spd_dump with CVE-2022-38694 exec_addr2, protocol reference, partition rules, backup verification (UMS9621)
Open source ↗ - GitHub PoCmutur4/UnisocBootROMsPublished Jun 22, 2026
This is a collection of Unisoc BootROMs dumped from various Unisoc chipsets via CVE-2022-38694
Open source ↗ - GitHub PoCJoshAtticus/ztewastePublished May 31, 2026
Extract a concerning amount of user information from Unisoc ZTE devices using CVE-2022-38694.
Open source ↗ - GitHub PoCGopartner/realme-c53-unlock-rootPublished May 16, 2026
Bootloader unlock (CVE-2022-38694) & root guide for Realme C53 / RMX3760 (Unisoc T612)
Open source ↗ - GitHub PoCPhlegmelm/CRACK12Published May 14, 2026
rooting an ATOZEE P12 on Android 14 using CVE-2022-38694 — because fastboot oem unlock said no, so we found another way.
Open source ↗ - GitHub PoCAureliusIvan/ubl-itel-s23Published Mar 4, 2026
Unlock Bootloader for Itel S23 (S665L) / Unisoc T606 using CVE-2022-38694
Open source ↗ - GitHub PoCLeoChen-CoreMind/spd_flasherPublished Feb 20, 2026
CVE-2022-38694 Hardened Exploit - RP2350 USB Host Auto Flasher for Unisoc devices
Open source ↗ - GitHub PoCSeriousattempts/Bootloader_Unlock_Retroid_Pocket_3PlusPublished Feb 21, 2025
Bootloader unlock using CVE-2022-38694 for Retroid Pocket 3+
Open source ↗ - GitHub PoCTheGammaSqueeze/Bootloader_Unlock_Anbernic_T820Published Jun 27, 2024
Bootloader unlock using CVE-2022-38694 for Anbernic Unisoc T820 devices
Open source ↗ - GitHub checkerTomKing062/CVE-2022-38694_unlock_bootloaderPublished Jun 10, 2023
This is a one-time signature verification bypass. For persistent signature verification bypass, check https://github.com/TomKing062/CVE-2022-38691_38692
Open source ↗
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2022-38694?
When was the CVE record for CVE-2022-38694 published?
Is CVE-2022-38694 actively exploited?
What is the CVSS score of CVE-2022-38694?
How do I remediate CVE-2022-38694?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2022-38694
Is Your Infrastructure Affected by CVE-2022-38694?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.