CVE-2026-53273

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
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.

In the Linux kernel, the following vulnerability has been resolved:

tee: optee: prevent use-after-free when the client exits before the supplicant

Commit 70b0d6b0a199 ("tee: optee: Fix supplicant wait loop") made the client wait as killable so it can be interrupted during shutdown or after a supplicant crash. This changes the original lifetime expectations: the client task can now terminate while the supplicant is still processing its request.

If the client exits first it removes the request from its queue and kfree()s it, while the request ID remains in supp->idr. A subsequent lookup on the supplicant path then dereferences freed memory, leading to a use-after-free.

Serialise access to the request with supp->mutex:

* Hold supp->mutex in optee_supp_recv() and optee_supp_send() while looking up and touching the request. * Let optee_supp_thrd_req() notice that the client has terminated and signal optee_supp_send() accordingly.

With these changes the request cannot be freed while the supplicant still has a reference, eliminating the race.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
2.6%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

tee: optee: prevent use-after-free when the client exits before the supplicant - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d5b57bb314d79e99bebb58a53588fa11dd4dbf69
generic

tee: optee: prevent use-after-free when the client exits before the supplicant - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d366a01475f927402c96a3fe78bfc06b924fc87d
generic

tee: optee: prevent use-after-free when the client exits before the supplicant - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ae847ab29ded2d7cece4d5970f0edefa4137bf2f
generic

tee: optee: prevent use-after-free when the client exits before the supplicant - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a0dc9279d0907b198f205a693aedf696b08145d
generic

tee: optee: prevent use-after-free when the client exits before the supplicant - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/724d0caffd4204b46f78efe22f18f8338031c6e1
generic

tee: optee: prevent use-after-free when the client exits before the supplicant - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/416259cb5bffecaaae5f76539deb535a8c1b2c34
generic

tee: optee: prevent use-after-free when the client exits before the supplicant - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/387a926ee166814611acecb960207fe2f3c4fd3e
generic

tee: optee: prevent use-after-free when the client exits before the supplicant - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/373152c94e57e9592b68c100e224fbd943cfd608

Vendor Advisories for CVE-2026-53273(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 34× in last 7d / 46× 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-07-07 01:45 UTCEG score recompute
  2. 2026-07-07 01:45 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 13:19 UTCEG score recompute
  6. 2026-07-06 13:18 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 00:38 UTCEG score recompute
  10. 2026-07-06 00:38 UTCGHSA enrichment
  11. 2026-07-05 12:12 UTCEG score recompute
  12. 2026-07-05 12:11 UTCGHSA enrichment
  13. 2026-07-04 23:45 UTCEG score recompute
  14. 2026-07-04 23:45 UTCGHSA enrichment
  15. 2026-07-04 11:18 UTCEG score recompute
  16. 2026-07-04 11:18 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 22:52 UTCEG score recompute
  20. 2026-07-03 22:52 UTCGHSA enrichment
  21. 2026-07-03 10:26 UTCEG score recompute
  22. 2026-07-03 10:26 UTCGHSA enrichment
  23. 2026-07-02 21:57 UTCEG score recompute
  24. 2026-07-02 21:57 UTCGHSA enrichment
  25. 2026-07-02 09:31 UTCEG score recompute
Show 21 more
  1. 2026-07-02 09:31 UTCGHSA enrichment
  2. 2026-07-01 21:05 UTCEG score recompute
  3. 2026-07-01 21:05 UTCGHSA enrichment
  4. 2026-07-01 15:07 UTCEPSS rescore
  5. 2026-07-01 08:39 UTCEG score recompute
  6. 2026-07-01 08:39 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 20:13 UTCEG score recompute 7.80
  9. 2026-06-30 20:13 UTCGHSA enrichment
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 03:08 UTCEG score recompute
  17. 2026-06-28 03:08 UTCGHSA enrichment
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 10:03 UTCEG score recompute
  21. 2026-06-25 10:03 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53273?
CVE-2026-53273 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: tee: optee: prevent use-after-free when the client exits before the supplicant Commit 70b0d6b0a199 ("tee: optee: Fix supplicant wait loop") made the client wait as killable so it can be interrupted during shutdown or after a…
When was CVE-2026-53273 disclosed?
CVE-2026-53273 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53273 actively exploited?
CVE-2026-53273 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53273?
CVE-2026-53273 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53273?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53273, 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-53273

Explore →

Is Your Infrastructure Affected by CVE-2026-53273?

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