From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80933: wifi: mt76: mt7996: validate default EEPROM firmware size
Date: Fri, 11 Sep 2026 21:40:39 +0200 [thread overview]
Message-ID: <2026091135-CVE-2026-80933-b526@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7996: validate default EEPROM firmware size
The default EEPROM firmware is parsed and copied as a full EEPROM
without checking its length. A truncated file can make the driver
read beyond the firmware buffer during variant validation or the
fallback copy.
Reject files shorter than MT7996_EEPROM_SIZE before parsing or
copying the firmware.
The Linux kernel CVE team has assigned CVE-2026-80933 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.2 with commit 98686cd21624c75a043e96812beadddf4f6f48e5 and fixed in 6.18.50 with commit 03b81f015dbb29807ce1ec6d45537d658abdac69
Issue introduced in 6.2 with commit 98686cd21624c75a043e96812beadddf4f6f48e5 and fixed in 7.2.4 with commit 7074ec3769820302f1ccf8794a40a6582153b820
Issue introduced in 6.2 with commit 98686cd21624c75a043e96812beadddf4f6f48e5 and fixed in 7.3-rc1 with commit 653c6e289b13cc6942f3e8f8e3c568e70fa42d1f
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-80933
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/eeprom.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/03b81f015dbb29807ce1ec6d45537d658abdac69
https://git.kernel.org/stable/c/7074ec3769820302f1ccf8794a40a6582153b820
https://git.kernel.org/stable/c/653c6e289b13cc6942f3e8f8e3c568e70fa42d1f
reply other threads:[~2026-09-11 19:46 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=2026091135-CVE-2026-80933-b526@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.