CVE-2026-74554

HighCVSS 8.8

Published: 15/08/2026(UTC)Updated: 17/08/2026(UTC)Translated: 15/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.20%

11th percentile - higher than 11% of all known CVEs

Summary

In the Linux kernel, the ath12k driver had an out-of-bounds error in ath12k_mac_dp_peer_cleanup(), where indexing the free_ml_peer_id_map bitmap used peer_id with the ATH12K_PEER_ML_ID_VALID bit (BIT(13)) set, leading to writes beyond the bitmap memory (256 bits). This caused memory corruption and exhaustion of ML peer IDs.

Risk Assessment

A local attacker with access to the Wi-Fi interface can cause kernel memory corruption, potentially leading to system crash or privilege escalation.

Recommendation

Install the kernel patch that uses the correct ID (without the VALID bit) for bitmap clearing and resets ml_peer_id to an invalid value.

Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix out-of-bounds clear_bit in ath12k_mac_dp_peer_cleanup() ath12k_mac_dp_peer_cleanup() clears the ML peer ID slot on the free_ml_peer_id_map bitmap by indexing it with dp_peer->peer_id. That is wrong: dp_peer->peer_id for an MLO peer always carries the ATH12K_PEER_ML_ID_VALID bit (BIT(13)), so clear_bit() is invoked with index >= 0x2000, which is far outside the bitmap of ATH12K_MAX_MLO_PEERS (256) bits and corrupts memory adjacent to ah->free_ml_peer_id_map. The intended bitmap entry also never gets cleared, so subsequent ath12k_peer_ml_alloc() calls eventually run out of IDs. The ID without the VALID bit is what ath12k_peer_ml_alloc() returned and is stored in ahsta->ml_peer_id. Use that instead. While there, also reset ahsta->ml_peer_id to ATH12K_MLO_PEER_ID_INVALID so the bitmap and ahsta->ml_peer_id stay in sync. Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.3