CVE-2026-42546

LOWPre-NVD 3.83.8—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% 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
3.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.8Exploit: None knownExposed: 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.3.0 and prior to version 4.11.0, a resource leak exists in OP-TEE’s shared memory cleanup logic because the function cleanup_shm_refs() in core/tee/entry_std.c fails to apply a required bitmask (OPTEE_MSG_ATTR_TYPE_MASK) to parameter attributes. When processing non-contiguous memory parameters from a normal-world caller, the system fails to match the attribute type in its internal switch statement and skips the necessary mobj_put() call. This results in a persistent reference leak of mobj_reg_shm objects, which remain on internal lists with dangling refcounts. This affects non-FF-A configurations that support non-contiguous, non-secure shared memory. Over time, these accumulated leaks progressively consume the secure-world heap, degrading the system's ability to service trusted application operations and eventually requiring a reboot to recover. Version 4.11.0 contains a patch. No known workarounds are available.

CVSS v3
3.8
EG Score
3.8(medium)
EG Risk
17(Track)
EG Risk 17/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
Severity38% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

References (1)

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.9.0-1 (6 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× 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.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-42546?
CVE-2026-42546 is a low vulnerability published on July 6, 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.3.0 and prior to version 4.11.0, a resource leak exists in OP-TEE’s shared memory cleanup logic because the…
When was CVE-2026-42546 disclosed?
CVE-2026-42546 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42546 actively exploited?
CVE-2026-42546 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 95.4% of all scored CVEs.
What is the CVSS score of CVE-2026-42546?
CVE-2026-42546 has a CVSS v3 base score of 3.8 (NVD).
How do I remediate CVE-2026-42546?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42546, 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-42546

Explore →

Is Your Infrastructure Affected by CVE-2026-42546?

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

Start Free Scan →Browse All CVEs