CVE-2026-53273

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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: None knownExposed: 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(medium)
EG Risk
40(Track)
EG Risk 40/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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 60× 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 199 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:36 UTCEG score recompute
  11. 2026-08-30 19:36 UTCGHSA enrichment
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 23:56 UTCEG score recompute
  16. 2026-08-27 23:56 UTCGHSA enrichment
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 01:37 UTCEG score recompute
  20. 2026-08-25 01:37 UTCGHSA enrichment
  21. 2026-08-24 13:11 UTCEG score recompute
  22. 2026-08-24 13:11 UTCGHSA enrichment
  23. 2026-08-23 23:57 UTCGHSA enrichment
  24. 2026-08-23 11:31 UTCEG score recompute
  25. 2026-08-23 11:31 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-22 23:05 UTCGHSA enrichment
  3. 2026-08-22 10:39 UTCGHSA enrichment
  4. 2026-08-21 20:24 UTCGHSA enrichment
  5. 2026-08-21 07:58 UTCEG score recompute
  6. 2026-08-21 07:58 UTCGHSA enrichment
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 19:31 UTCGHSA enrichment
  9. 2026-08-20 07:05 UTCEG score recompute
  10. 2026-08-20 07:05 UTCGHSA enrichment
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-19 14:14 UTCGHSA enrichment
  13. 2026-08-19 01:30 UTCEG score recompute
  14. 2026-08-19 01:30 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 12:40 UTCGHSA enrichment
  18. 2026-08-17 00:13 UTCEG score recompute
  19. 2026-08-17 00:13 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 11:46 UTCEG score recompute
  22. 2026-08-16 11:46 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 23:20 UTCGHSA enrichment
  25. 2026-08-15 10:52 UTCEG score recompute
  26. 2026-08-15 10:52 UTCGHSA enrichment
  27. 2026-08-15 01:30 UTCEPSS rescore
  28. 2026-08-14 22:25 UTCGHSA enrichment
  29. 2026-08-14 09:59 UTCEG score recompute
  30. 2026-08-14 09:59 UTCGHSA enrichment
  31. 2026-08-13 22:00 UTCEPSS rescore
  32. 2026-08-13 21:33 UTCGHSA enrichment
  33. 2026-08-13 08:44 UTCGHSA enrichment
  34. 2026-08-12 20:17 UTCEG score recompute
  35. 2026-08-12 20:17 UTCGHSA enrichment
  36. 2026-08-12 13:51 UTCEPSS rescore
  37. 2026-08-12 07:51 UTCGHSA enrichment
  38. 2026-08-11 19:25 UTCEG score recompute
  39. 2026-08-11 19:25 UTCGHSA enrichment
  40. 2026-08-11 06:59 UTCEG score recompute
  41. 2026-08-11 06:59 UTCGHSA enrichment
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-10 18:33 UTCGHSA enrichment
  44. 2026-08-10 05:35 UTCGHSA enrichment
  45. 2026-08-09 17:09 UTCGHSA enrichment
  46. 2026-08-09 04:43 UTCEG score recompute
  47. 2026-08-09 04:43 UTCGHSA enrichment
  48. 2026-08-08 16:37 UTCEPSS rescore
  49. 2026-08-08 16:17 UTCGHSA enrichment
  50. 2026-08-08 03:50 UTCEG score recompute
  51. 2026-08-08 03:50 UTCGHSA enrichment
  52. 2026-08-07 15:24 UTCGHSA enrichment
  53. 2026-08-07 02:58 UTCGHSA enrichment
  54. 2026-08-06 14:25 UTCEG score recompute
  55. 2026-08-06 14:25 UTCGHSA enrichment
  56. 2026-08-06 13:47 UTCEPSS rescore
  57. 2026-08-06 01:58 UTCEG score recompute
  58. 2026-08-06 01:58 UTCGHSA enrichment
  59. 2026-08-05 19:17 UTCEPSS rescore
  60. 2026-08-05 13:33 UTCEG score recompute
  61. 2026-08-05 13:33 UTCGHSA enrichment
  62. 2026-08-04 22:15 UTCEG score recompute
  63. 2026-08-04 22:15 UTCGHSA enrichment
  64. 2026-08-04 15:10 UTCEPSS rescore
  65. 2026-08-04 10:39 UTCEPSS rescore
  66. 2026-08-04 08:58 UTCGHSA enrichment
  67. 2026-08-03 20:18 UTCEG score recompute
  68. 2026-08-03 20:18 UTCGHSA enrichment
  69. 2026-08-03 10:36 UTCEPSS rescore
  70. 2026-08-03 07:52 UTCGHSA enrichment
  71. 2026-08-02 17:52 UTCGHSA enrichment
  72. 2026-08-02 05:26 UTCEG score recompute
  73. 2026-08-02 05:26 UTCGHSA enrichment
  74. 2026-08-02 02:27 UTCEPSS rescore
  75. 2026-08-01 16:59 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 August 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-53273 actively exploited?
CVE-2026-53273 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 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53273?
CVE-2026-53273 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.