From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-90374: wifi: mt76: mt7996: validate RX band_idx before dereferencing phys[]
Date: Thu, 17 Sep 2026 17:13:24 +0100 [thread overview]
Message-ID: <2026091709-CVE-2026-90374-ea5b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7996: validate RX band_idx before dereferencing phys[]
band_idx comes from a 2-bit descriptor field (0-3) and was used directly
to index dev->mt76.phys[] (size __MT_MAX_BAND == 3) and dereference the
result. A corrupt or reserved descriptor value could index out of bounds
or hit a NULL phy on parts with fewer bands. Reject invalid band indices,
mirroring mt7996_rx_get_wcid().
The Linux kernel CVE team has assigned CVE-2026-90374 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.2 with commit 98686cd21624c75a043e96812beadddf4f6f48e5 and fixed in 6.12.110 with commit 535091c587268cc783608642838a655d828eefdd
Issue introduced in 6.2 with commit 98686cd21624c75a043e96812beadddf4f6f48e5 and fixed in 6.18.52 with commit 0f53ece876e1f3bbb3e18f48afc4af1ee967b16c
Issue introduced in 6.2 with commit 98686cd21624c75a043e96812beadddf4f6f48e5 and fixed in 7.2.6 with commit b1c5cf8903bec5476a2233b4e45287b9a2213e02
Issue introduced in 6.2 with commit 98686cd21624c75a043e96812beadddf4f6f48e5 and fixed in 7.3-rc1 with commit 2243778a5fae8329ab5f18e7adcd7e03b911a1b7
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-90374
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/net/wireless/mediatek/mt76/mt7996/mac.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/535091c587268cc783608642838a655d828eefdd
https://git.kernel.org/stable/c/0f53ece876e1f3bbb3e18f48afc4af1ee967b16c
https://git.kernel.org/stable/c/b1c5cf8903bec5476a2233b4e45287b9a2213e02
https://git.kernel.org/stable/c/2243778a5fae8329ab5f18e7adcd7e03b911a1b7
reply other threads:[~2026-09-17 16:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091709-CVE-2026-90374-ea5b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.