<?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://db.gcve.eu</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>Wed, 30 Sep 2026 13:24:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90375 — wifi: mt76: fix non-AQL packet accounting for MLO stations</title>
      <link>https://db.gcve.eu/vuln/cve-2026-90375</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: mt76: fix non-AQL packet accounting for MLO stations&lt;/p&gt;
&lt;p&gt;__mt76_tx_queue_skb() overrides the wcid passed by the driver with
sta-&amp;gt;drv_priv, so the wcid might incorrectly be changed after TX,
causing wcid-&amp;gt;non_aql_packets to be counted on the wrong wcid. For
example, on the AP side, if a station&amp;#39;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.&lt;/p&gt;
&lt;p&gt;Drop the reassignment and account on the wcid used for transmission.
This also records the actual wcid in the queue entry.&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: mt76: fix non-AQL packet accounting for MLO stations&lt;/p&gt;
&lt;p&gt;__mt76_tx_queue_skb() overrides the wcid passed by the driver with
sta-&amp;gt;drv_priv, so the wcid might incorrectly be changed after TX,
causing wcid-&amp;gt;non_aql_packets to be counted on the wrong wcid. For
example, on the AP side, if a station&amp;#39;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.&lt;/p&gt;
&lt;p&gt;Drop the reassignment and account on the wcid used for transmission.
This also records the actual wcid in the queue entry.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-90375</guid>
    </item>
  </channel>
</rss>
