<?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 17:52:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90382 — wifi: mt76: mt76x02: do not WARN on invalid rx descriptor length</title>
      <link>https://db.gcve.eu/vuln/cve-2026-90382</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: mt76x02: do not WARN on invalid rx descriptor length&lt;/p&gt;
&lt;p&gt;The MPDU length in the rx descriptor comes from the hardware. In
monitor mode with the fcsfail filter enabled, the hardware passes up
corrupted frames, and a corrupted frame can report a length larger
than the received buffer. The bounds check correctly discards such
frames, but its WARN_ON_ONCE wrapper means any over-the-air garbage
frame taints the kernel, and panics it on the first such frame when
panic_on_warn is set.&lt;/p&gt;
&lt;p&gt;Drop the WARN and discard the frame silently, matching what
commit c2d4c8723dbf (&amp;#34;mt76x2: remove some harmless WARN_ONs in tx
status and rx path&amp;#34;) did for the neighboring rx and tx status paths.&lt;/p&gt;
&lt;p&gt;Observed immediately on rx with an MT7612U in fcsfail monitor mode
on a busy channel.&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: mt76x02: do not WARN on invalid rx descriptor length&lt;/p&gt;
&lt;p&gt;The MPDU length in the rx descriptor comes from the hardware. In
monitor mode with the fcsfail filter enabled, the hardware passes up
corrupted frames, and a corrupted frame can report a length larger
than the received buffer. The bounds check correctly discards such
frames, but its WARN_ON_ONCE wrapper means any over-the-air garbage
frame taints the kernel, and panics it on the first such frame when
panic_on_warn is set.&lt;/p&gt;
&lt;p&gt;Drop the WARN and discard the frame silently, matching what
commit c2d4c8723dbf (&amp;#34;mt76x2: remove some harmless WARN_ONs in tx
status and rx path&amp;#34;) did for the neighboring rx and tx status paths.&lt;/p&gt;
&lt;p&gt;Observed immediately on rx with an MT7612U in fcsfail monitor mode
on a busy channel.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-90382</guid>
    </item>
  </channel>
</rss>
