CVE-2026-40290

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

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.8(medium)
EPSS
8.5%
KEV
Not listed

Published

June 3, 2026

Last Modified

June 5, 2026

Advisory Details (1)

Auto-updated Jun 4, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 66× 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 107 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-40290?
CVE-2026-40290 is a high vulnerability 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 CVE-2026-40290 disclosed?
CVE-2026-40290 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on June 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40290 actively exploited?
CVE-2026-40290 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40290?
CVE-2026-40290 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-40290?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40290, 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-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.