<?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-09-30T20:48:51.700941+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-90375</id>
    <title>CVE-2026-90375 — wifi: mt76: fix non-AQL packet accounting for MLO stations</title>
    <updated>2026-09-30T20:48:51.703197+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: mt76: fix non-AQL packet accounting for MLO stations</p>
<p>__mt76_tx_queue_skb() overrides the wcid passed by the driver with
sta-&gt;drv_priv, so the wcid might incorrectly be changed after TX,
causing wcid-&gt;non_aql_packets to be counted on the wrong wcid. For
example, on the AP side, if a station's setup link is the 5G link and
the station uses 2G to transmit a frame, the value of non_aql_packets
is increased on the 5G wcid but decreased on the 2G wcid. Once the
inflated counter exceeds MT_MAX_NON_AQL_PKT, the TX scheduler
permanently refuses to service the station.</p>
<p>Drop the reassignment and account on the wcid used for transmission.
This also records the actual wcid in the queue entry.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-90375"/>
  </entry>
</feed>
