From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74341: wifi: wcn36xx: fix heap overflow from oversized firmware HAL response
Date: Sat, 15 Aug 2026 15:11:08 +0900 [thread overview]
Message-ID: <2026081557-CVE-2026-74341-3d9e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: wcn36xx: fix heap overflow from oversized firmware HAL response
The firmware response dispatcher copies all synchronous HAL responses
into the 4096-byte hal_buf without validating the response length. A
response exceeding WCN36XX_HAL_BUF_SIZE causes a heap buffer overflow
with firmware-controlled content.
Add a bounds check on the response length.
The Linux kernel CVE team has assigned CVE-2026-74341 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.13 with commit 8e84c25821698bdef73c0329fb2022a4673b7adc and fixed in 6.1.178 with commit dae9cadf0925f1cbfb71306d60490890df3870a6
Issue introduced in 3.13 with commit 8e84c25821698bdef73c0329fb2022a4673b7adc and fixed in 6.6.145 with commit cfc67aee0c83e7f5d43a1dad3e25c789e9cc1d92
Issue introduced in 3.13 with commit 8e84c25821698bdef73c0329fb2022a4673b7adc and fixed in 6.12.97 with commit 15545ee71301e82d26d9a31b407ed0019eb62a60
Issue introduced in 3.13 with commit 8e84c25821698bdef73c0329fb2022a4673b7adc and fixed in 6.18.40 with commit 1b5d8a248c3afa640bcc99fa95abcd1e36f3ee18
Issue introduced in 3.13 with commit 8e84c25821698bdef73c0329fb2022a4673b7adc and fixed in 7.1.5 with commit 18813b90032bfaafb225906a4d2b51be4dfc02c3
Issue introduced in 3.13 with commit 8e84c25821698bdef73c0329fb2022a4673b7adc and fixed in 7.2-rc1 with commit 88a240d86d3d64521f9194abe185ac71cc74d0bd
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-74341
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/ath/wcn36xx/smd.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/dae9cadf0925f1cbfb71306d60490890df3870a6
https://git.kernel.org/stable/c/cfc67aee0c83e7f5d43a1dad3e25c789e9cc1d92
https://git.kernel.org/stable/c/15545ee71301e82d26d9a31b407ed0019eb62a60
https://git.kernel.org/stable/c/1b5d8a248c3afa640bcc99fa95abcd1e36f3ee18
https://git.kernel.org/stable/c/18813b90032bfaafb225906a4d2b51be4dfc02c3
https://git.kernel.org/stable/c/88a240d86d3d64521f9194abe185ac71cc74d0bd
reply other threads:[~2026-08-15 6:37 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=2026081557-CVE-2026-74341-3d9e@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.