CVE-2026-90382

wifi: mt76: mt76x02: do not WARN on invalid rx descriptor length

N/A
Published: September 17, 2026 at 04:09 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt76x02: do not WARN on invalid rx descriptor length 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. Drop the WARN and discard the frame silently, matching what commit c2d4c8723dbf ("mt76x2: remove some harmless WARN_ONs in tx status and rx path") did for the neighboring rx and tx status paths. Observed immediately on rx with an MT7612U in fcsfail monitor mode on a busy channel.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.167bc04215a66b60e198aecaee8418f6d79fa19faa
Vendor states this is fixed in 17d6b89e09eac2d90272fceeba3644e92212e02f (fixed)
Vendor states this is fixed in 2d31e332c13b1db7745a7bd9cf74bc105524bcac (fixed)
Vendor states this is fixed in 61b1f6d92249bc34580ff19de7c69c805f82adca (fixed)
Vendor states this is fixed in 6def491fe9c4e83aa8cba62d74e9d4ab751ee967 (fixed)
Vendor states this is fixed in 81497634d9f872fd3e8b03aada55574afff6f174 (fixed)
Vendor states this is fixed in b6e7958602bd1acdb8ae92703b6689a28bcc9bc0 (fixed)
Vendor states this is fixed in c65bbfc730df9ebf0fea8e286b0ad2dfab03dbfe (fixed)
Vendor states this is fixed in d55e7aede542c4c76ead82d37d0c112f21eb2ac2 (fixed)
Vendor states this is fixed in 4.16 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card