<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T00:30:18.873871+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-46307</id>
    <title>CVE-2026-46307 — wifi: ath5k: do not access array OOB</title>
    <updated>2026-10-02T00:30:18.923785+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>wifi: ath5k: do not access array OOB</p>
<p>Vincent reports:
&gt; The ath5k driver seems to do an array-index-out-of-bounds access as
&gt; shown by the UBSAN kernel message:
&gt; UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath5k/base.c:1741:20
&gt; index 4 is out of range for type 'ieee80211_tx_rate [4]'
&gt; ...
&gt; Call Trace:
&gt;  &lt;TASK&gt;
&gt;  dump_stack_lvl+0x5d/0x80
&gt;  ubsan_epilogue+0x5/0x2b
&gt;  __ubsan_handle_out_of_bounds.cold+0x46/0x4b
&gt;  ath5k_tasklet_tx+0x4e0/0x560 [ath5k]
&gt;  tasklet_action_common+0xb5/0x1c0</p>
<p>It is real. 'ts-&gt;ts_final_idx' can be 3 on 5212, so:
   info-&gt;status.rates[ts-&gt;ts_final_idx + 1].idx = -1;
with the array defined as:
   struct ieee80211_tx_rate rates[IEEE80211_TX_MAX_RATES];
while the size is:
   #define IEEE80211_TX_MAX_RATES  4
is indeed bogus.</p>
<p>Set this 'idx = -1' sentinel only if the array index is less than the
array size. As mac80211 will not look at rates beyond the size
(IEEE80211_TX_MAX_RATES).</p>
<p>Note: The effect of the OOB write is negligible. It just overwrites the
next member of info-&gt;status, i.e. ack_signal.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-46307"/>
  </entry>
</feed>
