From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46271: wifi: ath12k: do WoW offloads only on primary link
Date: Wed, 3 Jun 2026 17:50:00 +0200 [thread overview]
Message-ID: <2026060339-CVE-2026-46271-3f1c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath12k: do WoW offloads only on primary link
In case of multi-link connection, WCN7850 firmware crashes due to WoW
offloads enabled on both primary and secondary links.
Change to do it only on primary link to fix it.
Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00284-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1
The Linux kernel CVE team has assigned CVE-2026-46271 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit 32f7b19668bd2894f1a236580c2132fc4b9f4449 and fixed in 6.18.14 with commit 7379837c3f9efa576dc2d716ebfaa3a113b3112f
Issue introduced in 6.16 with commit 32f7b19668bd2894f1a236580c2132fc4b9f4449 and fixed in 6.19.4 with commit e042da1085d9f1686c58a4378d5840f52a36598e
Issue introduced in 6.16 with commit 32f7b19668bd2894f1a236580c2132fc4b9f4449 and fixed in 7.0 with commit e62102ac9b773bdb08475aa9ca24dea61ae98708
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-46271
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/ath12k/wow.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/7379837c3f9efa576dc2d716ebfaa3a113b3112f
https://git.kernel.org/stable/c/e042da1085d9f1686c58a4378d5840f52a36598e
https://git.kernel.org/stable/c/e62102ac9b773bdb08475aa9ca24dea61ae98708
reply other threads:[~2026-06-03 15:51 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=2026060339-CVE-2026-46271-3f1c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox