From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46307: wifi: ath5k: do not access array OOB
Date: Mon, 8 Jun 2026 17:46:14 +0200 [thread overview]
Message-ID: <2026060800-CVE-2026-46307-9ef9@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath5k: do not access array OOB
Vincent reports:
> The ath5k driver seems to do an array-index-out-of-bounds access as
> shown by the UBSAN kernel message:
> UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath5k/base.c:1741:20
> index 4 is out of range for type 'ieee80211_tx_rate [4]'
> ...
> Call Trace:
> <TASK>
> dump_stack_lvl+0x5d/0x80
> ubsan_epilogue+0x5/0x2b
> __ubsan_handle_out_of_bounds.cold+0x46/0x4b
> ath5k_tasklet_tx+0x4e0/0x560 [ath5k]
> tasklet_action_common+0xb5/0x1c0
It is real. 'ts->ts_final_idx' can be 3 on 5212, so:
info->status.rates[ts->ts_final_idx + 1].idx = -1;
with the array defined as:
struct ieee80211_tx_rate rates[IEEE80211_TX_MAX_RATES];
while the size is:
#define IEEE80211_TX_MAX_RATES 4
is indeed bogus.
Set this 'idx = -1' sentinel only if the array index is less than the
array size. As mac80211 will not look at rates beyond the size
(IEEE80211_TX_MAX_RATES).
Note: The effect of the OOB write is negligible. It just overwrites the
next member of info->status, i.e. ack_signal.
The Linux kernel CVE team has assigned CVE-2026-46307 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.0 with commit 6d7b97b23e114c8fbb825e6721164d228c1af3fc and fixed in 5.10.258 with commit ecb1c163166759dec004c1fdb9709b8a5992fc8e
Issue introduced in 3.0 with commit 6d7b97b23e114c8fbb825e6721164d228c1af3fc and fixed in 5.15.209 with commit 9dd6aae4bc7bfa11088d928670a3315eae542769
Issue introduced in 3.0 with commit 6d7b97b23e114c8fbb825e6721164d228c1af3fc and fixed in 6.1.175 with commit 744c19e266b0d2628c5951439195dcef27eadacf
Issue introduced in 3.0 with commit 6d7b97b23e114c8fbb825e6721164d228c1af3fc and fixed in 6.6.140 with commit 83226c71af53fb9b3cad40cb9a9a79f36d68c020
Issue introduced in 3.0 with commit 6d7b97b23e114c8fbb825e6721164d228c1af3fc and fixed in 6.12.88 with commit d6869537013b1f21b292342752d97868b79b5934
Issue introduced in 3.0 with commit 6d7b97b23e114c8fbb825e6721164d228c1af3fc and fixed in 6.18.30 with commit e9f1081bc775146156def0dbc821b92f35d56afb
Issue introduced in 3.0 with commit 6d7b97b23e114c8fbb825e6721164d228c1af3fc and fixed in 7.0.7 with commit 568173ad9bd0b46cc6cd937dea8791e9b5eefa57
Issue introduced in 3.0 with commit 6d7b97b23e114c8fbb825e6721164d228c1af3fc and fixed in 7.1-rc3 with commit d748603f12baff112caa3ab7d39f50100f010dbd
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-46307
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/ath5k/base.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/ecb1c163166759dec004c1fdb9709b8a5992fc8e
https://git.kernel.org/stable/c/9dd6aae4bc7bfa11088d928670a3315eae542769
https://git.kernel.org/stable/c/744c19e266b0d2628c5951439195dcef27eadacf
https://git.kernel.org/stable/c/83226c71af53fb9b3cad40cb9a9a79f36d68c020
https://git.kernel.org/stable/c/d6869537013b1f21b292342752d97868b79b5934
https://git.kernel.org/stable/c/e9f1081bc775146156def0dbc821b92f35d56afb
https://git.kernel.org/stable/c/568173ad9bd0b46cc6cd937dea8791e9b5eefa57
https://git.kernel.org/stable/c/d748603f12baff112caa3ab7d39f50100f010dbd
reply other threads:[~2026-06-08 15:47 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=2026060800-CVE-2026-46307-9ef9@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