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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: Elevated riskExposed: 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)
EG Risk
51(Track*)
EG Risk 51/100SSVC: Track*

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
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

June 3, 2026

Last Modified

July 21, 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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
optee-os4.10.0-1 ... 4.9.0-1 (6 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
optee-os4.10.0-1, 4.5.0-2, 4.7.0-1, 4.8.0-1, 4.9.0-14.10.0-2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 139 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-15 03:11 UTCEPSS rescore
  3. 2026-09-14 05:30 UTCEG score recompute
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 09:37 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 03:36 UTCEG score recompute
  23. 2026-08-23 12:46 UTCEG score recompute
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 14:41 UTCEG score recompute
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-20 10:00 UTCEG score recompute
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 15:36 UTCEG score recompute
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 03:09 UTCEG score recompute
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 14:42 UTCEG score recompute
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-13 22:55 UTCEG score recompute
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 14:36 UTCEG score recompute
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-12 02:01 UTCEG score recompute
  18. 2026-08-11 13:43 UTCEPSS rescore
  19. 2026-08-11 01:06 UTCEG score recompute
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-10 00:13 UTCEG score recompute
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-08 23:16 UTCEG score recompute
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-07 22:20 UTCEG score recompute
  26. 2026-08-06 21:26 UTCEG score recompute
  27. 2026-08-06 13:46 UTCEPSS rescore
  28. 2026-08-05 20:32 UTCEG score recompute
  29. 2026-08-05 19:17 UTCEPSS rescore
  30. 2026-08-04 19:20 UTCEG score recompute
  31. 2026-08-04 15:10 UTCEPSS rescore
  32. 2026-08-04 10:38 UTCEPSS rescore
  33. 2026-08-03 15:42 UTCEG score recompute
  34. 2026-08-03 10:36 UTCEPSS rescore
  35. 2026-08-02 13:58 UTCEG score recompute
  36. 2026-08-02 02:27 UTCEPSS rescore
  37. 2026-08-01 13:04 UTCEG score recompute
  38. 2026-08-01 04:16 UTCEPSS rescore
  39. 2026-07-31 05:31 UTCEG score recompute
  40. 2026-07-30 16:28 UTCEPSS rescore
  41. 2026-07-30 01:30 UTCEPSS rescore
  42. 2026-07-29 10:19 UTCEG score recompute
  43. 2026-07-28 03:29 UTCEG score recompute
  44. 2026-07-27 14:13 UTCEPSS rescore
  45. 2026-07-26 22:31 UTCEG score recompute
  46. 2026-07-26 14:54 UTCEPSS rescore
  47. 2026-07-26 14:54 UTCEPSS rescore
  48. 2026-07-25 14:18 UTCEPSS rescore
  49. 2026-07-25 14:18 UTCEPSS rescore
  50. 2026-07-24 14:17 UTCEPSS rescore
  51. 2026-07-24 14:17 UTCEPSS rescore
  52. 2026-07-23 14:18 UTCEPSS rescore
  53. 2026-07-23 14:18 UTCEPSS rescore
  54. 2026-07-23 03:11 UTCEG score recompute
  55. 2026-07-22 14:08 UTCEPSS rescore
  56. 2026-07-21 15:24 UTCEPSS rescore
  57. 2026-07-20 17:08 UTCEPSS rescore
  58. 2026-07-19 14:31 UTCEPSS rescore
  59. 2026-07-19 02:29 UTCEPSS rescore
  60. 2026-07-18 10:04 UTCEPSS rescore
  61. 2026-07-16 17:03 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 16:57 UTCEPSS rescore
  64. 2026-07-15 02:00 UTCEPSS rescore
  65. 2026-07-13 22:30 UTCEPSS rescore
  66. 2026-07-13 06:13 UTCEPSS rescore
  67. 2026-07-13 06:13 UTCEPSS rescore
  68. 2026-07-12 05:46 UTCEPSS rescore
  69. 2026-07-11 08:27 UTCEPSS rescore
  70. 2026-07-09 19:10 UTCEPSS rescore
  71. 2026-07-08 15:15 UTCEPSS rescore
  72. 2026-07-07 13:46 UTCEPSS rescore
  73. 2026-07-06 16:27 UTCEPSS rescore
  74. 2026-07-06 16:27 UTCEPSS rescore
  75. 2026-07-06 02:23 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 July 21, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 91.5% of all scored CVEs.
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

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.

Start Free Scan →Browse All CVEs