<?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://cve.radiocsirt.org</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, 08 Oct 2026 14:25:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49539 — rtw89: ser: fix CAM leaks occurring in L2 reset</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49539</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;rtw89: ser: fix CAM leaks occurring in L2 reset&lt;/p&gt;
&lt;p&gt;The CAM, meaning address CAM and bssid CAM here, will get leaks during
SER (system error recover) L2 reset process and ieee80211_restart_hw()
which is called by L2 reset process eventually.&lt;/p&gt;
&lt;p&gt;The normal flow would be like
-&amp;gt; add interface (acquire 1)
-&amp;gt; enter ips (release 1)
-&amp;gt; leave ips (acquire 1)
-&amp;gt; connection (occupy 1) &amp;lt;(A) 1 leak after L2 reset if non-sec connection&amp;gt;&lt;/p&gt;
&lt;p&gt;The ieee80211_restart_hw() flow (under connection)
-&amp;gt; ieee80211 reconfig
-&amp;gt; add interface (acquire 1)
-&amp;gt; leave ips (acquire 1)
-&amp;gt; connection (occupy (A) + 2) &amp;lt;(B) 1 more leak&amp;gt;&lt;/p&gt;
&lt;p&gt;Originally, CAM is released before HW restart only if connection is under
security. Now, release CAM whatever connection it is to fix leak in (A).
OTOH, check if CAM is already valid to avoid acquiring multiple times to
fix (B).&lt;/p&gt;
&lt;p&gt;Besides, if AP mode, release address CAM of all stations before HW restart.&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;rtw89: ser: fix CAM leaks occurring in L2 reset&lt;/p&gt;
&lt;p&gt;The CAM, meaning address CAM and bssid CAM here, will get leaks during
SER (system error recover) L2 reset process and ieee80211_restart_hw()
which is called by L2 reset process eventually.&lt;/p&gt;
&lt;p&gt;The normal flow would be like
-&amp;gt; add interface (acquire 1)
-&amp;gt; enter ips (release 1)
-&amp;gt; leave ips (acquire 1)
-&amp;gt; connection (occupy 1) &amp;lt;(A) 1 leak after L2 reset if non-sec connection&amp;gt;&lt;/p&gt;
&lt;p&gt;The ieee80211_restart_hw() flow (under connection)
-&amp;gt; ieee80211 reconfig
-&amp;gt; add interface (acquire 1)
-&amp;gt; leave ips (acquire 1)
-&amp;gt; connection (occupy (A) + 2) &amp;lt;(B) 1 more leak&amp;gt;&lt;/p&gt;
&lt;p&gt;Originally, CAM is released before HW restart only if connection is under
security. Now, release CAM whatever connection it is to fix leak in (A).
OTOH, check if CAM is already valid to avoid acquiring multiple times to
fix (B).&lt;/p&gt;
&lt;p&gt;Besides, if AP mode, release address CAM of all stations before HW restart.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49539</guid>
    </item>
  </channel>
</rss>
