CVE-2026-46163

NVD 0.07.8▲
EchelonGraph scoreLOW confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-28.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
Trending — 4 sources updated this week
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
—
EG Score
7.8(low)
EPSS
2.9%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 14, 2026

Advisory Details (8)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

wifi: b43legacy: enforce bounds check on firmware key index in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fdd4e51979f42ca8b1ab7e6176b607e1caabf2a5
generic

wifi: b43legacy: enforce bounds check on firmware key index in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/df805c1d085b7a96077f0964185764c87060950d
generic

wifi: b43legacy: enforce bounds check on firmware key index in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a92bd0503df2488f2cc040f329ebccff1c1934cb
generic

wifi: b43legacy: enforce bounds check on firmware key index in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a035766f970bde2d4298346a31a80685be5c0205
generic

wifi: b43legacy: enforce bounds check on firmware key index in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d1bc155802943e92c57a5fb923d23edfbf0b525
generic

wifi: b43legacy: enforce bounds check on firmware key index in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ee946077607d7783ae6709a899213fc4fe08f35
generic

wifi: b43legacy: enforce bounds check on firmware key index in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4242db36de99de734cc1f60e5edd86cda7e598c6
generic

wifi: b43legacy: enforce bounds check on firmware key index in RX path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1baaeb6adecb9691748c0253dab6ddd19a2b4e9e

Vendor Advisories for CVE-2026-46163(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 90× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 149 total refreshes for this CVE.

  1. 2026-07-16 10:23 UTCEG score recompute
  2. 2026-07-16 10:23 UTCVendor advisory
  3. 2026-07-16 10:23 UTCGHSA enrichment
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-13 22:30 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 21:16 UTCEG score recompute
  10. 2026-07-11 21:16 UTCVendor advisory
  11. 2026-07-11 21:16 UTCGHSA enrichment
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 18:28 UTCEG score recompute
  15. 2026-07-08 18:28 UTCVendor advisory
  16. 2026-07-08 18:28 UTCGHSA enrichment
  17. 2026-07-08 15:16 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-02 14:14 UTCEG score recompute
  24. 2026-07-02 14:14 UTCVendor advisory
  25. 2026-07-02 14:14 UTCGHSA enrichment
Show 75 more
  1. 2026-07-01 14:59 UTCEG score recompute
  2. 2026-07-01 14:59 UTCVendor advisory
  3. 2026-07-01 14:58 UTCGHSA enrichment
  4. 2026-07-01 03:09 UTCEG score recompute
  5. 2026-07-01 03:09 UTCVendor advisory
  6. 2026-07-01 03:09 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 02:01 UTCEG score recompute
  9. 2026-06-30 02:01 UTCVendor advisory
  10. 2026-06-30 02:01 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 13:45 UTCEG score recompute
  14. 2026-06-29 13:45 UTCVendor advisory
  15. 2026-06-29 13:45 UTCGHSA enrichment
  16. 2026-06-28 18:37 UTCEG score recompute
  17. 2026-06-28 18:37 UTCVendor advisory
  18. 2026-06-28 18:37 UTCGHSA enrichment
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 06:38 UTCEG score recompute
  21. 2026-06-28 06:38 UTCVendor advisory
  22. 2026-06-28 06:38 UTCGHSA enrichment
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 18:17 UTCEG score recompute
  26. 2026-06-27 18:17 UTCVendor advisory
  27. 2026-06-27 18:17 UTCGHSA enrichment
  28. 2026-06-27 05:28 UTCEG score recompute
  29. 2026-06-27 05:28 UTCVendor advisory
  30. 2026-06-27 05:28 UTCGHSA enrichment
  31. 2026-06-27 03:08 UTCEPSS rescore
  32. 2026-06-26 16:52 UTCEG score recompute
  33. 2026-06-26 16:52 UTCVendor advisory
  34. 2026-06-26 16:51 UTCGHSA enrichment
  35. 2026-06-25 22:52 UTCEG score recompute
  36. 2026-06-25 22:52 UTCVendor advisory
  37. 2026-06-25 22:52 UTCGHSA enrichment
  38. 2026-06-25 13:49 UTCEPSS rescore
  39. 2026-06-25 11:02 UTCEG score recompute
  40. 2026-06-25 11:02 UTCVendor advisory
  41. 2026-06-25 11:02 UTCGHSA enrichment
  42. 2026-06-24 22:46 UTCEG score recompute
  43. 2026-06-24 22:46 UTCVendor advisory
  44. 2026-06-24 22:46 UTCGHSA enrichment
  45. 2026-06-24 14:05 UTCEPSS rescore
  46. 2026-06-23 21:33 UTCEPSS rescore
  47. 2026-06-23 21:33 UTCEPSS rescore
  48. 2026-06-22 14:25 UTCEPSS rescore
  49. 2026-06-22 14:25 UTCEPSS rescore
  50. 2026-06-21 14:56 UTCEPSS rescore
  51. 2026-06-21 14:56 UTCEPSS rescore
  52. 2026-06-21 01:59 UTCEPSS rescore
  53. 2026-06-21 01:59 UTCEPSS rescore
  54. 2026-06-19 19:26 UTCEPSS rescore
  55. 2026-06-19 19:26 UTCEPSS rescore
  56. 2026-06-18 17:52 UTCEPSS rescore
  57. 2026-06-18 17:52 UTCEPSS rescore
  58. 2026-06-18 03:38 UTCEG score recompute
  59. 2026-06-18 03:38 UTCGHSA enrichment
  60. 2026-06-17 17:53 UTCEPSS rescore
  61. 2026-06-17 15:22 UTCEG score recompute
  62. 2026-06-17 15:22 UTCGHSA enrichment
  63. 2026-06-17 03:31 UTCEG score recompute
  64. 2026-06-17 03:31 UTCGHSA enrichment
  65. 2026-06-16 17:52 UTCEPSS rescore
  66. 2026-06-16 15:43 UTCEG score recompute
  67. 2026-06-16 15:43 UTCVendor advisory
  68. 2026-06-16 15:43 UTCGHSA enrichment
  69. 2026-06-16 00:52 UTCEG score recompute
  70. 2026-06-16 00:52 UTCVendor advisory
  71. 2026-06-16 00:52 UTCGHSA enrichment
  72. 2026-06-15 17:49 UTCEPSS rescore
  73. 2026-06-15 13:02 UTCEG score recompute
  74. 2026-06-15 13:02 UTCVendor advisory
  75. 2026-06-15 13:02 UTCGHSA enrichment

Frequently asked(4)

What is CVE-2026-46163?
CVE-2026-46163 is a publicly disclosed vulnerability published on May 28, 2026. 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->maxnrkeys. The existing B43legacyWARNON is non-enforcing in production…
When was CVE-2026-46163 disclosed?
CVE-2026-46163 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46163 actively exploited?
CVE-2026-46163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-46163?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46163, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46163

Explore →

Is Your Infrastructure Affected by CVE-2026-46163?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs