CVE-2023-52503
Last modified
CVE-2023-52503 is a high-severity vulnerability rated 7/10 on the CVSS scale. 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(). EPSS estimates a 0.26% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.6, < 5.10.199 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.136 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.59 | — |
| Linux | Linux Kernel | >= 6.2, < 6.5.8 | — |
| Linux | Linux Kernel | 6.6 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-52503?
How severe is CVE-2023-52503?
How do I fix CVE-2023-52503?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-52498In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52499In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5250The Grid Plus plugin for WordPress is vulnerable to Local Fi…8.8
- CVE-2023-52500In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52501In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-52502In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2023-52504In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-52505In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2023-52506In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52507In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-52508In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52509In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2023-52503?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
