CVE-2026-68362: wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin

Published Aug 10, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

wifi: ath11k: fix NULL pointer dereference in ath11khalsrngaccessbegin

In ATH11KQMIEVENTFWREADY, ATH11KFLAGREGISTERED is set unconditionally even when ath11kcoreqmifirmwareready() 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: ath11khalsrngaccessbegin+0xc/0x60 [ath11k] (P) ath11kcecleanuppipes+0x17c/0x180 [ath11k] ath11kcorerestart+0x40/0x168 [ath11k]

Fix this by: - skipping firmwareready if ATH11KFLAGREGISTERED is already set - setting ATH11KFLAGREGISTERED only when firmwareready succeeds - setting ATH11KFLAGQMIFAIL and aborting the FWREADY handling on error

Tested-on: WCN6750 hw1.0 AHB WLAN.MSL.2.0.c2-00204-QCAMSLSWPLZ-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ath11k (Linux kernel driver) to a version that resolves this vulnerability.

    Patch WCN6750 hw1.0 AHB WLAN.MSL.2.0.c2-00204-QCAMSLSWPLZ-1
  2. Configuration

    In ATH11K_QMI_EVENT_FW_READY, when ATH11K_FLAG_QMI_FAIL is set, abort the FW_READY handling.

    ath11k ATH11K_FLAG_QMI_FAIL = aborting FW_READY handling
  3. Configuration

    In ATH11K_QMI_EVENT_FW_READY, set ATH11K_FLAG_REGISTERED only after ath11k_core_qmi_firmware_ready() succeeds.

    ath11k ATH11K_FLAG_REGISTERED = set only when firmware_ready succeeds
  4. Configuration

    In ATH11K_QMI_EVENT_FW_READY, skip/avoid calling firmware_ready if ATH11K_FLAG_REGISTERED is already set (to prevent inconsistent restart path behavior).

    ath11k firmware_ready execution = skip if ATH11K_FLAG_REGISTERED already set

Event History

Aug 10, 2026
CVE Published
via MITRE·12:03 PM
Data Sourced
via MITRE·12:03 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68362?

CVE-2026-68362 has a risk rating of 27, indicating it is a relatively low-severity vulnerability.

2

How do I fix CVE-2026-68362?

To fix CVE-2026-68362, update the Linux kernel to a version where the NULL pointer dereference issue has been resolved.

3

What impact does CVE-2026-68362 have on systems?

CVE-2026-68362 may result in a system crash or instability due to a NULL pointer dereference in the ath11k driver.

4

Which versions of the Linux kernel are affected by CVE-2026-68362?

CVE-2026-68362 affects specific versions of the Linux kernel that include the ath11k driver prior to the fix.

5

What components are involved in CVE-2026-68362?

CVE-2026-68362 primarily involves the ath11k wireless driver and its interaction with QMI events in the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203