<?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>Mon, 28 Sep 2026 09:32:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46760 — wifi: rtw88: usb: schedule rx work after everything is set up</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46760</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: rtw88: usb: schedule rx work after everything is set up&lt;/p&gt;
&lt;p&gt;Right now it&amp;#39;s possible to hit NULL pointer dereference in
rtw_rx_fill_rx_status on hw object and/or its fields because
initialization routine can start getting USB replies before
rtw_dev is fully setup.&lt;/p&gt;
&lt;p&gt;The stack trace looks like this:&lt;/p&gt;
&lt;p&gt;rtw_rx_fill_rx_status
rtw8821c_query_rx_desc
rtw_usb_rx_handler
...
queue_work
rtw_usb_read_port_complete
...
usb_submit_urb
rtw_usb_rx_resubmit
rtw_usb_init_rx
rtw_usb_probe&lt;/p&gt;
&lt;p&gt;So while we do the async stuff rtw_usb_probe continues and calls
rtw_register_hw, which does all kinds of initialization (e.g.
via ieee80211_register_hw) that rtw_rx_fill_rx_status relies on.&lt;/p&gt;
&lt;p&gt;Fix this by moving the first usb_submit_urb after everything
is set up.&lt;/p&gt;
&lt;p&gt;For me, this bug manifested as:
[    8.893177] rtw_8821cu 1-1:1.2: band wrong, packet dropped
[    8.910904] rtw_8821cu 1-1:1.2: hw-&amp;gt;conf.chandef.chan NULL in rtw_rx_fill_rx_status
because I&amp;#39;m using Larry&amp;#39;s backport of rtw88 driver with the NULL
checks in rtw_rx_fill_rx_status.&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: rtw88: usb: schedule rx work after everything is set up&lt;/p&gt;
&lt;p&gt;Right now it&amp;#39;s possible to hit NULL pointer dereference in
rtw_rx_fill_rx_status on hw object and/or its fields because
initialization routine can start getting USB replies before
rtw_dev is fully setup.&lt;/p&gt;
&lt;p&gt;The stack trace looks like this:&lt;/p&gt;
&lt;p&gt;rtw_rx_fill_rx_status
rtw8821c_query_rx_desc
rtw_usb_rx_handler
...
queue_work
rtw_usb_read_port_complete
...
usb_submit_urb
rtw_usb_rx_resubmit
rtw_usb_init_rx
rtw_usb_probe&lt;/p&gt;
&lt;p&gt;So while we do the async stuff rtw_usb_probe continues and calls
rtw_register_hw, which does all kinds of initialization (e.g.
via ieee80211_register_hw) that rtw_rx_fill_rx_status relies on.&lt;/p&gt;
&lt;p&gt;Fix this by moving the first usb_submit_urb after everything
is set up.&lt;/p&gt;
&lt;p&gt;For me, this bug manifested as:
[    8.893177] rtw_8821cu 1-1:1.2: band wrong, packet dropped
[    8.910904] rtw_8821cu 1-1:1.2: hw-&amp;gt;conf.chandef.chan NULL in rtw_rx_fill_rx_status
because I&amp;#39;m using Larry&amp;#39;s backport of rtw88 driver with the NULL
checks in rtw_rx_fill_rx_status.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46760</guid>
    </item>
  </channel>
</rss>
