<?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:34:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39750 — wifi: ath12k: Correct tid cleanup when tid setup fails</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-39750</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;wifi: ath12k: Correct tid cleanup when tid setup fails&lt;/p&gt;
&lt;p&gt;Currently, if any error occurs during ath12k_dp_rx_peer_tid_setup(),
the tid value is already incremented, even though the corresponding
TID is not actually allocated. Proceed to
ath12k_dp_rx_peer_tid_delete() starting from unallocated tid,
which might leads to freeing unallocated TID and cause potential
crash or out-of-bounds access.&lt;/p&gt;
&lt;p&gt;Hence, fix by correctly decrementing tid before cleanup to match only
the successfully allocated TIDs.&lt;/p&gt;
&lt;p&gt;Also, remove tid-- from failure case of ath12k_dp_rx_peer_frag_setup(),
as decrementing the tid before cleanup in loop will take care of this.&lt;/p&gt;
&lt;p&gt;Compile tested only.&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;wifi: ath12k: Correct tid cleanup when tid setup fails&lt;/p&gt;
&lt;p&gt;Currently, if any error occurs during ath12k_dp_rx_peer_tid_setup(),
the tid value is already incremented, even though the corresponding
TID is not actually allocated. Proceed to
ath12k_dp_rx_peer_tid_delete() starting from unallocated tid,
which might leads to freeing unallocated TID and cause potential
crash or out-of-bounds access.&lt;/p&gt;
&lt;p&gt;Hence, fix by correctly decrementing tid before cleanup to match only
the successfully allocated TIDs.&lt;/p&gt;
&lt;p&gt;Also, remove tid-- from failure case of ath12k_dp_rx_peer_frag_setup(),
as decrementing the tid before cleanup in loop will take care of this.&lt;/p&gt;
&lt;p&gt;Compile tested only.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-39750</guid>
    </item>
  </channel>
</rss>
