<?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>Sat, 03 Oct 2026 05:21:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50179 — ath9k: fix use-after-free in ath9k_hif_usb_rx_cb</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-50179</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;ath9k: fix use-after-free in ath9k_hif_usb_rx_cb&lt;/p&gt;
&lt;p&gt;Syzbot reported use-after-free Read in ath9k_hif_usb_rx_cb() [0]. The
problem was in incorrect htc_handle-&amp;gt;drv_priv initialization.&lt;/p&gt;
&lt;p&gt;Probable call trace which can trigger use-after-free:&lt;/p&gt;
&lt;p&gt;ath9k_htc_probe_device()
  /* htc_handle-&amp;gt;drv_priv = priv; */
  ath9k_htc_wait_for_target()      &amp;lt;--- Failed
  ieee80211_free_hw()		   &amp;lt;--- priv pointer is freed&lt;/p&gt;
&lt;p&gt;&amp;lt;IRQ&amp;gt;
...
ath9k_hif_usb_rx_cb()
  ath9k_hif_usb_rx_stream()
   RX_STAT_INC()		&amp;lt;--- htc_handle-&amp;gt;drv_priv access&lt;/p&gt;
&lt;p&gt;In order to not add fancy protection for drv_priv we can move
htc_handle-&amp;gt;drv_priv initialization at the end of the
ath9k_htc_probe_device() and add helper macro to make
all *_STAT_* macros NULL safe, since syzbot has reported related NULL
deref in that macros [1]&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;ath9k: fix use-after-free in ath9k_hif_usb_rx_cb&lt;/p&gt;
&lt;p&gt;Syzbot reported use-after-free Read in ath9k_hif_usb_rx_cb() [0]. The
problem was in incorrect htc_handle-&amp;gt;drv_priv initialization.&lt;/p&gt;
&lt;p&gt;Probable call trace which can trigger use-after-free:&lt;/p&gt;
&lt;p&gt;ath9k_htc_probe_device()
  /* htc_handle-&amp;gt;drv_priv = priv; */
  ath9k_htc_wait_for_target()      &amp;lt;--- Failed
  ieee80211_free_hw()		   &amp;lt;--- priv pointer is freed&lt;/p&gt;
&lt;p&gt;&amp;lt;IRQ&amp;gt;
...
ath9k_hif_usb_rx_cb()
  ath9k_hif_usb_rx_stream()
   RX_STAT_INC()		&amp;lt;--- htc_handle-&amp;gt;drv_priv access&lt;/p&gt;
&lt;p&gt;In order to not add fancy protection for drv_priv we can move
htc_handle-&amp;gt;drv_priv initialization at the end of the
ath9k_htc_probe_device() and add helper macro to make
all *_STAT_* macros NULL safe, since syzbot has reported related NULL
deref in that macros [1]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-50179</guid>
    </item>
  </channel>
</rss>
