<?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>Tue, 29 Sep 2026 04:55:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23073 — wifi: rsi: Fix memory corruption due to not set vif driver data size</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23073</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: rsi: Fix memory corruption due to not set vif driver data size&lt;/p&gt;
&lt;p&gt;The struct ieee80211_vif contains trailing space for vif driver data,
when struct ieee80211_vif is allocated, the total memory size that is
allocated is sizeof(struct ieee80211_vif) + size of vif driver data.
The size of vif driver data is set by each WiFi driver as needed.&lt;/p&gt;
&lt;p&gt;The RSI911x driver does not set vif driver data size, no trailing space
for vif driver data is therefore allocated past struct ieee80211_vif .
The RSI911x driver does however use the vif driver data to store its
vif driver data structure &amp;#34;struct vif_priv&amp;#34;. An access to vif-&amp;gt;drv_priv
leads to access out of struct ieee80211_vif bounds and corruption of
some memory.&lt;/p&gt;
&lt;p&gt;In case of the failure observed locally, rsi_mac80211_add_interface()
would write struct vif_priv *vif_info = (struct vif_priv *)vif-&amp;gt;drv_priv;
vif_info-&amp;gt;vap_id = vap_idx. This write corrupts struct fq_tin member
struct list_head new_flows . The flow = list_first_entry(head, struct
fq_flow, flowchain); in fq_tin_reset() then reports non-NULL bogus
address, which when accessed causes a crash.&lt;/p&gt;
&lt;p&gt;The trigger is very simple, boot the machine with init=/bin/sh , mount
devtmpfs, sysfs, procfs, and then do &amp;#34;ip link set wlan0 up&amp;#34;, &amp;#34;sleep 1&amp;#34;,
&amp;#34;ip link set wlan0 down&amp;#34; and the crash occurs.&lt;/p&gt;
&lt;p&gt;Fix this by setting the correct size of vif driver data, which is the
size of &amp;#34;struct vif_priv&amp;#34;, so that memory is allocated and t…&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: rsi: Fix memory corruption due to not set vif driver data size&lt;/p&gt;
&lt;p&gt;The struct ieee80211_vif contains trailing space for vif driver data,
when struct ieee80211_vif is allocated, the total memory size that is
allocated is sizeof(struct ieee80211_vif) + size of vif driver data.
The size of vif driver data is set by each WiFi driver as needed.&lt;/p&gt;
&lt;p&gt;The RSI911x driver does not set vif driver data size, no trailing space
for vif driver data is therefore allocated past struct ieee80211_vif .
The RSI911x driver does however use the vif driver data to store its
vif driver data structure &amp;#34;struct vif_priv&amp;#34;. An access to vif-&amp;gt;drv_priv
leads to access out of struct ieee80211_vif bounds and corruption of
some memory.&lt;/p&gt;
&lt;p&gt;In case of the failure observed locally, rsi_mac80211_add_interface()
would write struct vif_priv *vif_info = (struct vif_priv *)vif-&amp;gt;drv_priv;
vif_info-&amp;gt;vap_id = vap_idx. This write corrupts struct fq_tin member
struct list_head new_flows . The flow = list_first_entry(head, struct
fq_flow, flowchain); in fq_tin_reset() then reports non-NULL bogus
address, which when accessed causes a crash.&lt;/p&gt;
&lt;p&gt;The trigger is very simple, boot the machine with init=/bin/sh , mount
devtmpfs, sysfs, procfs, and then do &amp;#34;ip link set wlan0 up&amp;#34;, &amp;#34;sleep 1&amp;#34;,
&amp;#34;ip link set wlan0 down&amp;#34; and the crash occurs.&lt;/p&gt;
&lt;p&gt;Fix this by setting the correct size of vif driver data, which is the
size of &amp;#34;struct vif_priv&amp;#34;, so that memory is allocated and t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23073</guid>
    </item>
  </channel>
</rss>
