CVE-2026-68362

wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin

N/A
Published: August 10, 2026 at 12:03 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin In ATH11K_QMI_EVENT_FW_READY, ATH11K_FLAG_REGISTERED is set unconditionally even when ath11k_core_qmi_firmware_ready() fails. This leaves the driver in an inconsistent state where initialization is considered complete although the firmware ready handling did not finish successfully. During the subsequent SSR, the driver enters the restart path based on this incorrect state and dereferences uninitialized srng members, resulting in a NULL pointer dereference. Call trace: ath11k_hal_srng_access_begin+0xc/0x60 [ath11k] (P) ath11k_ce_cleanup_pipes+0x17c/0x180 [ath11k] ath11k_core_restart+0x40/0x168 [ath11k] Fix this by: - skipping firmware_ready if ATH11K_FLAG_REGISTERED is already set - setting ATH11K_FLAG_REGISTERED only when firmware_ready succeeds - setting ATH11K_FLAG_QMI_FAIL and aborting the FW_READY handling on error Tested-on: WCN6750 hw1.0 AHB WLAN.MSL.2.0.c2-00204-QCAMSLSWPLZ-1

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1 ≤ v < 6.1.1836.1 ≤ v < 6.12.1016.1 ≤ v < 6.18.426.1 ≤ v < 6.6.1486.1 ≤ v < 7.1.66.1 ≤ v < 7.26.16fe62a8cec51c756159c71be35a16b2cc8cbd4c0
Vendor states this is fixed in 4abb4e284d8897176e91d7a3168ee29ed876bb41 (fixed)
Vendor states this is fixed in 66bf998b18334ca97321433e4ab783b6ff267e9d (fixed)
Vendor states this is fixed in d6bba659ac30d862ee7bab92862cd6e514f07521 (fixed)
Vendor states this is fixed in e517e207300edcf7f3a8f6c45f9155c0e419ffb9 (fixed)
Vendor states this is fixed in e5394605f9a985cc3a8263e610ba84b33cbe7b0c (fixed)
Vendor states this is fixed in e8d85672dd7e2523f774caafba8f858384e18df7 (fixed)
Vendor states this is fixed in 6.1 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card