<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 20:16:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52503 — tee: amdtee: fix use-after-free vulnerability in amdtee_close_session</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-52503</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tee: amdtee: fix use-after-free vulnerability in amdtee_close_session&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;kref_put(&amp;amp;sess-&amp;gt;refcount, destroy_session);&lt;/p&gt;
&lt;p&gt;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 &amp;#39;sess&amp;#39; that will be freed up
later in destroy_session() leading to use-after-free in
amdtee_open_session.&lt;/p&gt;
&lt;p&gt;To fix this issue, treat decrement of sess-&amp;gt;refcount and removal of
&amp;#39;sess&amp;#39; from session list in destroy_session() as a critical section, so
that it is executed atomically.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tee: amdtee: fix use-after-free vulnerability in amdtee_close_session&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;kref_put(&amp;amp;sess-&amp;gt;refcount, destroy_session);&lt;/p&gt;
&lt;p&gt;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 &amp;#39;sess&amp;#39; that will be freed up
later in destroy_session() leading to use-after-free in
amdtee_open_session.&lt;/p&gt;
&lt;p&gt;To fix this issue, treat decrement of sess-&amp;gt;refcount and removal of
&amp;#39;sess&amp;#39; from session list in destroy_session() as a critical section, so
that it is executed atomically.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-52503</guid>
    </item>
  </channel>
</rss>
