<?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://db.gcve.eu</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>Tue, 29 Sep 2026 06:34:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49416 — wifi: mac80211: fix use-after-free in chanctx code</title>
      <link>https://db.gcve.eu/vuln/cve-2022-49416</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: mac80211: fix use-after-free in chanctx code&lt;/p&gt;
&lt;p&gt;In ieee80211_vif_use_reserved_context(), when we have an
old context and the new context&amp;#39;s replace_state is set to
IEEE80211_CHANCTX_REPLACE_NONE, we free the old context
in ieee80211_vif_use_reserved_reassign(). Therefore, we
cannot check the old_ctx anymore, so we should set it to
NULL after this point.&lt;/p&gt;
&lt;p&gt;However, since the new_ctx replace state is clearly not
IEEE80211_CHANCTX_REPLACES_OTHER, we&amp;#39;re not going to do
anything else in this function and can just return to
avoid accessing the freed old_ctx.&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: mac80211: fix use-after-free in chanctx code&lt;/p&gt;
&lt;p&gt;In ieee80211_vif_use_reserved_context(), when we have an
old context and the new context&amp;#39;s replace_state is set to
IEEE80211_CHANCTX_REPLACE_NONE, we free the old context
in ieee80211_vif_use_reserved_reassign(). Therefore, we
cannot check the old_ctx anymore, so we should set it to
NULL after this point.&lt;/p&gt;
&lt;p&gt;However, since the new_ctx replace state is clearly not
IEEE80211_CHANCTX_REPLACES_OTHER, we&amp;#39;re not going to do
anything else in this function and can just return to
avoid accessing the freed old_ctx.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2022-49416</guid>
    </item>
  </channel>
</rss>
