From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98830: wifi: wfx: validate MIB read length before copying to caller
Date: Sun, 18 Oct 2026 17:46:45 +0200 [thread overview]
Message-ID: <2026101830-CVE-2026-98830-2b3f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: wfx: validate MIB read length before copying to caller
wfx_hif_read_mib() copies reply->length bytes from the firmware
response into the caller-provided buffer without checking that
reply->length does not exceed val_len. A firmware response with
a length field larger than expected overruns the caller buffer and
reads past the end of the reply allocation.
Replace the dead -ENOMEM check with an active validation that
reply->length fits within val_len before the memcpy.
The Linux kernel CVE team has assigned CVE-2026-98830 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.5 with commit f95a29d40782f4f0052a692a822de3ba044b19ff and fixed in 6.12.113 with commit 02886c18a340da59df57365f29009e1258bfe333
Issue introduced in 5.5 with commit f95a29d40782f4f0052a692a822de3ba044b19ff and fixed in 6.18.56 with commit 71d140099165de03128c00dd129f1eab21c6a3c4
Issue introduced in 5.5 with commit f95a29d40782f4f0052a692a822de3ba044b19ff and fixed in 7.2.10 with commit 7acb36fd60a3e7b858f12e69a919c3609b281408
Issue introduced in 5.5 with commit f95a29d40782f4f0052a692a822de3ba044b19ff and fixed in 7.3-rc6 with commit ce67ebe9d8629776ce38e6995ae72fb903c828db
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-98830
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/silabs/wfx/hif_tx.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/02886c18a340da59df57365f29009e1258bfe333
https://git.kernel.org/stable/c/71d140099165de03128c00dd129f1eab21c6a3c4
https://git.kernel.org/stable/c/7acb36fd60a3e7b858f12e69a919c3609b281408
https://git.kernel.org/stable/c/ce67ebe9d8629776ce38e6995ae72fb903c828db
reply other threads:[~2026-10-18 16:21 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=2026101830-CVE-2026-98830-2b3f@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.