Answer in brief
CVE-2023-52503 records a High severity (CVSS 7.8) vulnerability in tee: amdtee: fix use-after-free vulnerability in amdtee_close_session. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.6 | Not reported |
| Linux/Linuxgeneric | >=757cc3e9ff1d72d014096399d6e2bf03974d9da1 <da7ce52a2f6c468946195b116615297d3d113a27 || >=757cc3e9ff1d72d014096399d6e2bf03974d9da1 <1680c82929bc14d706065f123dab77f2f1293116 || >=757cc3e9ff1d72d014096399d6e2bf03974d9da1 <60c3e7a00db954947c265b55099c21b216f2a05c || >=757cc3e9ff1d72d014096399d6e2bf03974d9da1 <1c95574350cd63bc3c5c2fa06658010768f2a0ce || >=757cc3e9ff1d72d014096399d6e2bf03974d9da1 <f4384b3e54ea813868bb81a861bf5b2406e15d8f | da7ce52a2f6c468946195b116615297d3d113a27, 1680c82929bc14d706065f123dab77f2f1293116, 60c3e7a00db954947c265b55099c21b216f2a05c, 1c95574350cd63bc3c5c2fa06658010768f2a0ce, f4384b3e54ea813868bb81a861bf5b2406e15d8f |
Published upstream
Mar 2, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: tee: amdtee: fix use-after-free vulnerability in amdtee_close_session There is a potential race condition in amdtee_close_session that may cause use-after-free in amdtee_open_session. For instance, if a session has refcount == 1, and one thread tries to free this session via: kref_put(&sess->refcount, destroy_session); the reference count will get decremented, and the next step would be to call destroy_session(). However, if in another thread, amdtee_open_session() is called before destroy_session() has completed execution, alloc_session() may return 'sess' that will be freed up later in destroy_session() leading to use-after-free in amdtee_open_session. To fix this issue, treat decrement of sess->refcount and removal of 'sess' from session list in destroy_session() as a critical section, so that it is executed atomically.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-52503 records a High severity (CVSS 7.8) vulnerability in tee: amdtee: fix use-after-free vulnerability in amdtee_close_session. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.6 | Not reported |
| Linux/Linuxgeneric | >=757cc3e9ff1d72d014096399d6e2bf03974d9da1 <da7ce52a2f6c468946195b116615297d3d113a27 || >=757cc3e9ff1d72d014096399d6e2bf03974d9da1 <1680c82929bc14d706065f123dab77f2f1293116 || >=757cc3e9ff1d72d014096399d6e2bf03974d9da1 <60c3e7a00db954947c265b55099c21b216f2a05c || >=757cc3e9ff1d72d014096399d6e2bf03974d9da1 <1c95574350cd63bc3c5c2fa06658010768f2a0ce || >=757cc3e9ff1d72d014096399d6e2bf03974d9da1 <f4384b3e54ea813868bb81a861bf5b2406e15d8f | da7ce52a2f6c468946195b116615297d3d113a27, 1680c82929bc14d706065f123dab77f2f1293116, 60c3e7a00db954947c265b55099c21b216f2a05c, 1c95574350cd63bc3c5c2fa06658010768f2a0ce, f4384b3e54ea813868bb81a861bf5b2406e15d8f |
Published upstream
Mar 2, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: tee: amdtee: fix use-after-free vulnerability in amdtee_close_session There is a potential race condition in amdtee_close_session that may cause use-after-free in amdtee_open_session. For instance, if a session has refcount == 1, and one thread tries to free this session via: kref_put(&sess->refcount, destroy_session); the reference count will get decremented, and the next step would be to call destroy_session(). However, if in another thread, amdtee_open_session() is called before destroy_session() has completed execution, alloc_session() may return 'sess' that will be freed up later in destroy_session() leading to use-after-free in amdtee_open_session. To fix this issue, treat decrement of sess->refcount and removal of 'sess' from session list in destroy_session() as a critical section, so that it is executed atomically.
Quoted source text, attributed separately from HOL analysis.