CVE-2026-46307

HIGHPre-NVD 8.38.3—
EchelonGraph scoreHIGH confidence

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-08. the CNA's CVSS baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.3Exploit: 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: 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.

CVSS v3
8.3
EG Score
8.3(high)
EPSS
12.5%
KEV
Not listed

Published

June 8, 2026

Last Modified

June 14, 2026

Advisory Details (8)

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

wifi: ath5k: do not access array OOB - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: ath5k: do not access array OOB - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: ath5k: do not access array OOB - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: ath5k: do not access array OOB - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: ath5k: do not access array OOB - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: ath5k: do not access array OOB - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83226c71af53fb9b3cad40cb9a9a79f36d68c020
generic

wifi: ath5k: do not access array OOB - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/744c19e266b0d2628c5951439195dcef27eadacf
generic

wifi: ath5k: do not access array OOB - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/568173ad9bd0b46cc6cd937dea8791e9b5eefa57

Vendor Advisories for CVE-2026-46307(2)

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

Data Freshness Timeline

(refreshed 36× in last 7d / 138× 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 138 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46307?
CVE-2026-46307 is a high vulnerability published on June 8, 2026. 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…
When was CVE-2026-46307 disclosed?
CVE-2026-46307 was first published in the National Vulnerability Database on June 8, 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-46307 actively exploited?
CVE-2026-46307 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46307?
CVE-2026-46307 has a CVSS v4.0 base score of 8.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46307?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46307, 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-46307

Explore →

Is Your Infrastructure Affected by CVE-2026-46307?

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

Start Free Scan →Browse All CVEs