SECUFOCUSNOW
Home›CVE index›CVE-2026-46307
Review reviewHigh

CVE-2026-46307

Linux Linux, linux kernel

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_fin...

CVSS
8.3
EPSS
0.22%
12.7% percentile
CISA KEV
Not listed
Published
2026.06.09
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.22%
Technical severityCVSS 8.3

Vulnerability overview

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_fin...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 6d7b97b23e114c8fbb825e6721164d228c1af3fc < ecb1c163166759dec004c1fdb9709b8a5992fc8e, >= 6d7b97b23e114c8fbb825e6721164d228c1af3fc < 9dd6aae4bc7bfa11088d928670a3315eae542769, >= 6d7b97b23e114c8fbb825e6721164d228c1af3fc < 744c19e266b0d2628c5951439195dcef27eadacf, >= 6d7b97b23e114c8fbb825e6721164d228c1af3fc < 83226c71af53fb9b3cad40cb9a9a79f36d68c020, >= 6d7b97b23e114c8fbb825e6721164d228c1af3fc < d6869537013b1f21b292342752d97868b79b5934, >= 6d7b97b23e114c8fbb825e6721164d228c1af3fc < e9f1081bc775146156def0dbc821b92f35d56afb, >= 6d7b97b23e114c8fbb825e6721164d228c1af3fc < 568173ad9bd0b46cc6cd937dea8791e9b5eefa57, >= 6d7b97b23e114c8fbb825e6721164d228c1af3fc < d748603f12baff112caa3ab7d39f50100f010dbd, >= 3.0, >= 3.0 < 5.10.258, >= 5.11 < 5.15.209, >= 5.16 < 6.1.175, >= 6.2 < 6.6.140, >= 6.7 < 6.12.88, >= 6.13 < 6.18.30, >= 6.19 < 7.0.7, 7.1
Fixed versions
5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
CWE
CWE-125