Linux Kernel up to 7.1-rc2 wifi base.c __ubsan_handle_out_of_bounds.cold+0x46/0x4b ts_final_idx out-of-bounds write

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 7.1-rc2. The impacted element is the function __ubsan_handle_out_of_bounds.cold+0x46/0x4b of the file drivers/net/wireless/ath/ath5k/base.c of the component wifi. Such manipulation of the argument ts_final_idx leads to out-of-bounds write. This vulnerability is documented as CVE-2026-46307. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.1-rc2 and classified as critical. Affected by this issue is the function __ubsan_handle_out_of_bounds.cold+0x46/0x4b of the file drivers/net/wireless/ath/ath5k/base.c of the component wifi. The manipulation of the argument ts_final_idx with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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 advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-46307 since 05/13/2026. The exploitation is known to be easy. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 06/08/2026).

Upgrading to version 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7 or 7.1-rc3 eliminates this vulnerability. Applying the patch ecb1c163166759dec004c1fdb9709b8a5992fc8e/9dd6aae4bc7bfa11088d928670a3315eae542769/744c19e266b0d2628c5951439195dcef27eadacf/83226c71af53fb9b3cad40cb9a9a79f36d68c020/d6869537013b1f21b292342752d97868b79b5934/e9f1081bc775146156def0dbc821b92f35d56afb/568173ad9bd0b46cc6cd937dea8791e9b5eefa57/d748603f12baff112caa3ab7d39f50100f010dbd is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds write
CWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.258/5.15.209/6.1.175/6.6.140/6.12.88/6.18.30/7.0.7/7.1-rc3
Patch: ecb1c163166759dec004c1fdb9709b8a5992fc8e/9dd6aae4bc7bfa11088d928670a3315eae542769/744c19e266b0d2628c5951439195dcef27eadacf/83226c71af53fb9b3cad40cb9a9a79f36d68c020/d6869537013b1f21b292342752d97868b79b5934/e9f1081bc775146156def0dbc821b92f35d56afb/568173ad9bd0b46cc6cd937dea8791e9b5eefa57/d748603f12baff112caa3ab7d39f50100f010dbd

Timelineinfo

05/13/2026 CVE reserved
06/08/2026 +26 days Advisory disclosed
06/08/2026 +0 days VulDB entry created
06/08/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-46307 (🔒)
GCVE (CVE): GCVE-0-2026-46307
GCVE (VulDB): GCVE-100-369266

Entryinfo

Created: 06/08/2026 20:15
Changes: 06/08/2026 20:15 (61)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!