CVE-2023-41325

MEDIUMNVD 6.76.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.7 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
6.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.7Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

OP-TEE is a Trusted Execution Environment (TEE) designed as companion to a non-secure Linux kernel running on Arm; Cortex-A cores using the TrustZone technology. Starting in version 3.20 and prior to version 3.22, shdr_verify_signature can make a double free. shdr_verify_signature used to verify a TA binary before it is loaded. To verify a signature of it, allocate a memory for RSA key. RSA key allocate function (sw_crypto_acipher_alloc_rsa_public_key) will try to allocate a memory (which is optee’s heap memory). RSA key is consist of exponent and modulus (represent as variable e, n) and it allocation is not atomic way, so it may succeed in e but fail in n. In this case sw_crypto_acipher_alloc_rsa_public_key will free on e and return as it is failed but variable ‘e’ is remained as already freed memory address . shdr_verify_signature will free again that memory (which is e`) even it is freed when it failed allocate RSA key. A patch is available in version 3.22. No known workarounds are available.

CVSS v3
6.7
EG Score
6.7MEDIUMmedium confidence
EG Risk
46
EG Risk 46/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)
Severity67% × 45%
Impact severity (EG Severity): CVSS 6.7 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
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 (6.7): severity, escalated by confirmed exploitation. This CVE's 6.7 is its impact severity (EG Severity), not escalated.

EG Severity
6.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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.

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 15, 2023

Last Modified

June 17, 2026

References (2)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 34× 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 85 of 198 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. 15 repeat rows among the latest 100 are merged into the row they repeat. The 113 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-41325?
CVE-2023-41325 is a medium-severity vulnerability; its CVE record was published on September 15, 2023. OP-TEE is a Trusted Execution Environment (TEE) designed as companion to a non-secure Linux kernel running on Arm; Cortex-A cores using the TrustZone technology. Starting in version 3.20 and prior to version 3.22, shdrverifysignature can make a double free. shdrverifysignature used to verify a TA…
When was the CVE record for CVE-2023-41325 published?
The CVE record for CVE-2023-41325 was published on September 15, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2023-41325 actively exploited?
CVE-2023-41325 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-41325?
CVE-2023-41325 has a CVSS v3 base score of 6.7 (NVD).
How do I remediate CVE-2023-41325?
The CVE record for CVE-2023-41325 names the fix: "A patch is available in version 3.22."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-41325

Explore →

Is Your Infrastructure Affected by CVE-2023-41325?

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

Book a Demo →Browse All CVEs