From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68355: wifi: ath11k: fix potential buffer underflow in ath11k_hal_rx_msdu_list_get()
Date: Mon, 10 Aug 2026 14:01:12 +0200 [thread overview]
Message-ID: <2026081040-CVE-2026-68355-e340@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath11k: fix potential buffer underflow in ath11k_hal_rx_msdu_list_get()
When the first entry in msdu_details has a zero buffer address,
the code accesses msdu_details[i - 1] with i == 0, causing a
buffer underflow.
Fix similarly to ath12k_wifi7_hal_rx_msdu_list_get() by adding
a separate check for i == 0 before the main condition to prevent
the out-of-bounds access.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
The Linux kernel CVE team has assigned CVE-2026-68355 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 6.6.148 with commit 69a6a4f60b2da92c0bdfd9264b8ffe053f51f52a
Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 6.12.101 with commit 904367381a922aa2dc3e8bd2488e6c9180516c7a
Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 6.18.42 with commit a154ca3c441a67d36b3a9ea63a4f11b06abe6223
Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 7.1.6 with commit 725c1c3a8c5d920a7d3f5887412f2ad8e95a74f5
Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 7.2-rc5 with commit 7f11e70629650ff6ea140984e5ce188b775b2683
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-68355
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/ath11k/dp_rx.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/69a6a4f60b2da92c0bdfd9264b8ffe053f51f52a
https://git.kernel.org/stable/c/904367381a922aa2dc3e8bd2488e6c9180516c7a
https://git.kernel.org/stable/c/a154ca3c441a67d36b3a9ea63a4f11b06abe6223
https://git.kernel.org/stable/c/725c1c3a8c5d920a7d3f5887412f2ad8e95a74f5
https://git.kernel.org/stable/c/7f11e70629650ff6ea140984e5ce188b775b2683
reply other threads:[~2026-08-10 12:12 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=2026081040-CVE-2026-68355-e340@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