CVE-2026-53273 — tee: optee: prevent use-after-free when the client exits before the supplicant
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 21234efe2a8474a6d2d01ea9573319de7858ce44≥ 0180cf0373f84fff61b16f8c062553a13dd7cfca and < 416259cb5bffecaaae5f76539deb535a8c1b2c34≥ c0a9a948159153be145f9471435695373904ee6d and < 724d0caffd4204b46f78efe22f18f8338031c6e1≥ ec18520f5edc20a00c34a8c9fdd6507c355e880f and < ae847ab29ded2d7cece4d5970f0edefa4137bf2f≥ d61cc1a435e6894bfb0dd3370c6f765d2d12825d and < 9a0dc9279d0907b198f205a693aedf696b08145d≥ fd9d2d6124c293e40797a080adf8a9c237efd8b8 and < d366a01475f927402c96a3fe78bfc06b924fc87d≥ 70b0d6b0a199c5a3ee6c72f5e61681ed6f759612 and < d5b57bb314d79e99bebb58a53588fa11dd4dbf69≥ 70b0d6b0a199c5a3ee6c72f5e61681ed6f759612 and < 373152c94e57e9592b68c100e224fbd943cfd608 and 10 more≥ 70b0d6b0a199c5a3ee6c72f5e61681ed6f759612 and < 387a926ee166814611acecb960207fe2f3c4fd3eversion 3eb4911364c764572e9db4ab900a57689a54e8ce≥ 5.10.235 and < 5.10.259≥ 5.15.179 and < 5.15.210≥ 6.1.130 and < 6.1.176≥ 6.6.80 and < 6.6.143≥ 6.12.17 and < 6.12.94≥ 5.4.291 and < 5.5≥ 6.13.5 and < 6.14version 6.14 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 7.1-rc6version 6.14-rc4≥ 5.10.235 and < 5.10.259≥ 5.15.179 and < 5.15.210≥ 6.1.130 and < 6.1.176≥ 6.6.80 and < 6.6.143≥ 6.12.17 and < 6.12.94≥ 6.13.5 and < 6.14 and 12 more≥ 6.14.1 and < 6.18.36≥ 6.19 and < 7.0.13version 6.14≥ 5.4.291 and < 5.5version 6.14-rc5version 6.14-rc6version 6.14-rc7version 7.1-rc1version 7.1-rc2version 7.1-rc3version 7.1-rc4version 7.1-rc5 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.12%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 7.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/416259cb5bffecaaae5f76539deb535a8c1b2c34
- git.kernel.org/stable/c/d366a01475f927402c96a3fe78bfc06b924fc87d
- git.kernel.org/stable/c/724d0caffd4204b46f78efe22f18f8338031c6e1
- git.kernel.org/stable/c/373152c94e57e9592b68c100e224fbd943cfd608
- git.kernel.org/stable/c/ae847ab29ded2d7cece4d5970f0edefa4137bf2f
- git.kernel.org/stable/c/d5b57bb314d79e99bebb58a53588fa11dd4dbf69
- git.kernel.org/stable/c/387a926ee166814611acecb960207fe2f3c4fd3e
- git.kernel.org/stable/c/9a0dc9279d0907b198f205a693aedf696b08145d
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 2d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 2d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 2d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-53273 is "tee: optee: prevent use-after-free when the client exits before the supplicant", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.12% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.