From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98159: wifi: mt76: mt7921: validate CLC firmware records
Date: Fri, 25 Sep 2026 12:40:06 +0200 [thread overview]
Message-ID: <2026092520-CVE-2026-98159-0eb3@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7921: validate CLC firmware records
The CLC region is supplied by firmware, but the loader trusts the
region count and each record length. A malformed image can make the
region table pointer precede the firmware buffer, make the record loop
fail to advance, or index phy->clc past its end. Validate the table and
record bounds before dereferencing or copying.
The Linux kernel CVE team has assigned CVE-2026-98159 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1 with commit 23bdc5d8cadfc941e7782d0cb8afb2d9ae73b125 and fixed in 6.12.111 with commit 602a950134ee2940136f60797e4457c3983b06ce
Issue introduced in 6.1 with commit 23bdc5d8cadfc941e7782d0cb8afb2d9ae73b125 and fixed in 6.18.53 with commit 3896be051e928c891922d91de94c99519d215dff
Issue introduced in 6.1 with commit 23bdc5d8cadfc941e7782d0cb8afb2d9ae73b125 and fixed in 7.2.7 with commit 3c505e2af16a9320f4355218394a955fbbc65322
Issue introduced in 6.1 with commit 23bdc5d8cadfc941e7782d0cb8afb2d9ae73b125 and fixed in 7.3-rc1 with commit 9417c5818a0146980c2608fda94c908e604eb033
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-98159
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/mt7921/mcu.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/602a950134ee2940136f60797e4457c3983b06ce
https://git.kernel.org/stable/c/3896be051e928c891922d91de94c99519d215dff
https://git.kernel.org/stable/c/3c505e2af16a9320f4355218394a955fbbc65322
https://git.kernel.org/stable/c/9417c5818a0146980c2608fda94c908e604eb033
reply other threads:[~2026-09-25 10:42 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=2026092520-CVE-2026-98159-0eb3@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.