From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9D8153BB12E for ; Mon, 8 Jun 2026 15:47:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780933654; cv=none; b=GONF1ZF/jnF4Frt8u6T+BCVlxWKHsSldsU7oqHh0IPCGSZVuGwzIjJh6YiZqlpEM++VqYLpp0T5bTWaR9deeczr+L4xBOGBhteo3Bw/LUSBCmp5LPjEJV+4ZSxnz8psy2QBHUN3ccaXKoRoVMo5l+2wVYFnKiKxkOvqNlSacigo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780933654; c=relaxed/simple; bh=5xhHXM7DcK08s/ruPU93peNJq8lIJmoSKVvUavUAZVY=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=MkHRrHNIYTqOPgvepNPBxY3nH6IGDgJ+jbswgEAvl3SeEgGO/lYgAQIUu2LUDR0cAWRf6JyYJA13mLW3CTJyTrpJ1B3jLhJbxGUe2sYB6L+u5q0ZDIK9OBvd5OPqK/8+vY2r/HFHVP8EFNRgGQXuf5WPfR9OlTQ4bFct9Yb33uI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=roRHbIGv; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="roRHbIGv" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D8D401F00893; Mon, 8 Jun 2026 15:47:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1780933653; bh=+VRX2j9IsH6E3GshAsnnAh09y5kQlvt1XhRtbc4y99o=; h=From:To:Cc:Subject:Date:Reply-To; b=roRHbIGvUt/W7d9tjltogL6tWZIp/Irp+2uGX4JstyuR6fPGqARLN+eNY1lm2uMTQ Z0cJPSsRJjlSC8oDAswCIENvrKGAZeExO91Ys5alFlEeBRgAYOWjTkDzs5MHtw0S+I hZvpi0173nU9vQ721nnYJMYs6z/QdXevd3YmparY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-46307: wifi: ath5k: do not access array OOB Date: Mon, 8 Jun 2026 17:46:14 +0200 Message-ID: <2026060800-CVE-2026-46307-9ef9@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4174; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=QSHlfmnaiGM4RiL/T5e+F8+GspHY5Id+vVCTK2ldNjU=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlqj3cumZmsxDDrerTs502TNL0/5H1Z7nHsYfHOXE7pg nOBKn0zOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAi+l4M89PSbvad4/ph+9X1 3EGNuvWaHuVZSxjmcHbMif1jYLH+QGb/ys/pFp7XlQ13AQA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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: > > 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