CVE-2026-46163
wifi: b43legacy: enforce bounds check on firmware key index in RX path
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: b43legacy: enforce bounds check on firmware key index in RX path Same fix as b43: the firmware-controlled key index in b43legacy_rx() can exceed dev->max_nr_keys. The existing B43legacy_WARN_ON is non-enforcing in production builds, allowing an out-of-bounds read of dev->key[]. Make the check enforcing by dropping the frame for invalid indices.
INFO
Published Date :
May 28, 2026, 10:16 a.m.
Last Modified :
June 10, 2026, 9:13 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Update the Linux kernel to include the fix.
- Drop frames with invalid key indices.
- Ensure RX path bounds checks are enforced.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-46163.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-46163 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-46163
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-46163 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-46163 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jun. 10, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Added CWE CWE-129 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.30 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.175 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.209 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.7 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.88 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.140 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 2.6.24 up to (excluding) 5.10.258 Added Reference Type kernel.org: https://git.kernel.org/stable/c/1baaeb6adecb9691748c0253dab6ddd19a2b4e9e Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/4242db36de99de734cc1f60e5edd86cda7e598c6 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/6ee946077607d7783ae6709a899213fc4fe08f35 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/9d1bc155802943e92c57a5fb923d23edfbf0b525 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/a035766f970bde2d4298346a31a80685be5c0205 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/a92bd0503df2488f2cc040f329ebccff1c1934cb Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/df805c1d085b7a96077f0964185764c87060950d Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/fdd4e51979f42ca8b1ab7e6176b607e1caabf2a5 Types: Patch -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 01, 2026
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/4242db36de99de734cc1f60e5edd86cda7e598c6 Added Reference https://git.kernel.org/stable/c/a92bd0503df2488f2cc040f329ebccff1c1934cb Added Reference https://git.kernel.org/stable/c/df805c1d085b7a96077f0964185764c87060950d -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 28, 2026
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: wifi: b43legacy: enforce bounds check on firmware key index in RX path Same fix as b43: the firmware-controlled key index in b43legacy_rx() can exceed dev->max_nr_keys. The existing B43legacy_WARN_ON is non-enforcing in production builds, allowing an out-of-bounds read of dev->key[]. Make the check enforcing by dropping the frame for invalid indices. Added Reference https://git.kernel.org/stable/c/1baaeb6adecb9691748c0253dab6ddd19a2b4e9e Added Reference https://git.kernel.org/stable/c/6ee946077607d7783ae6709a899213fc4fe08f35 Added Reference https://git.kernel.org/stable/c/9d1bc155802943e92c57a5fb923d23edfbf0b525 Added Reference https://git.kernel.org/stable/c/a035766f970bde2d4298346a31a80685be5c0205 Added Reference https://git.kernel.org/stable/c/fdd4e51979f42ca8b1ab7e6176b607e1caabf2a5