CVE-2026-40290

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-34139 (ENISA EUVD)Source: ENISA EUVD

7.8EG
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.2%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — 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.16.0 and prior to 4.11.0, a user-after-free (UAF) race condition exists in the shared memory teardown logic of FF-A within OP-TEE SPMC/SP flows. This only applies when OP-TEE is configured as an SPMC for S-EL0 SPs, that is, with CFG_SECURE_PARTITION=y. The function sp_mem_remove(), responsible for freeing entries in smem->receivers and smem->regions, fails to acquire the global sp_mem_lock before performing the free() operations. Concurrently, other code paths, such as sp_mem_get_receiver(), iterate over these same lists without holding a lock, or, like sp_mem_is_shared(), iterate while holding the lock but are not serialized against the unprotected free() in sp_mem_remove(). This creates a cross-thread race where a thread iterating the list can acquire a pointer to an entry (e.g., struct sp_mem_map_region or struct sp_mem_receiver), and then another thread calls sp_mem_remove(), freeing the object. When the first thread resumes and dereferences the pointer, it results in a Use-After-Free vulnerability. Version 4.11.0 fixes the issue.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
51
EG 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, 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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
8th
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. 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.

A fix is available. 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

June 3, 2026

Last Modified

July 21, 2026

Advisory Details (1)

Auto-updated Jun 4, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Use-After-Free race in FF-A shared-memory teardown · Advisory · OP-TEE/optee_os · GitHub

https://github.com/OP-TEE/optee_os/security/advisories/GHSA-332c-xr93-849m

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
optee-os4.10.0-1 ... 4.9.0-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
optee-os4.10.0-1, 4.5.0-2, 4.7.0-1, 4.8.0-1, 4.9.0-1
  • every version up to 4.10.0-2: fixed in 4.10.0-2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 35× 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 99 of 182 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-40290?
CVE-2026-40290 is a high-severity vulnerability; its CVE record was published on June 3, 2026. 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.16.0 and prior to 4.11.0, a user-after-free (UAF) race condition exists in the shared memory teardown logic of FF-A…
When was the CVE record for CVE-2026-40290 published?
The CVE record for CVE-2026-40290 was published on June 3, 2026. 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 July 21, 2026; the record at its source may have been updated since.
Is CVE-2026-40290 actively exploited?
CVE-2026-40290 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40290?
CVE-2026-40290 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-40290?
A fix for CVE-2026-40290 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40290

Explore →

Is Your Infrastructure Affected by CVE-2026-40290?

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

Book a Demo →Browse All CVEs