CVE-2026-68197

wifi: mwifiex: fix NULL dereference when the AP has HT-cap but no HT-oper

N/A
Published: August 10, 2026 at 12:00 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: mwifiex: fix NULL dereference when the AP has HT-cap but no HT-oper mwifiex_tdls_add_ht_oper() gates its follow-the-AP-bandwidth path on bss_desc->bcn_ht_cap being present, but then dereferences a different pointer, bss_desc->bcn_ht_oper: if (ISSUPP_CHANWIDTH40(priv->adapter->hw_dot_11n_dev_cap) && bss_desc->bcn_ht_cap && ISALLOWED_CHANWIDTH40(bss_desc->bcn_ht_oper->ht_param)) bcn_ht_cap and bcn_ht_oper are populated independently while parsing the associated AP's beacon in mwifiex_update_bss_desc_with_ie(): an AP that advertises an HT Capabilities element but no HT Operation element leaves bcn_ht_cap non-NULL and bcn_ht_oper NULL. Setting up a TDLS link to a peer while associated to such an AP then dereferences the NULL bcn_ht_oper and crashes the kernel. Every other bcn_ht_oper user in the driver NULL-checks it first. Guard on the pointer that is actually dereferenced. Found by 0sec automated security-research tooling (https://0sec.ai).

Affected

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

3.16 ≤ v < 5.10.2653.16 ≤ v < 5.15.2163.16 ≤ v < 6.1.1833.16 ≤ v < 6.12.1013.16 ≤ v < 6.18.423.16 ≤ v < 6.6.1483.16 ≤ v < 7.1.63.16 ≤ v < 7.23.16396939f94084d5923d558e9f22db48bc51156e47
Vendor states this is fixed in 45011e4d9ba3f2182e5df64be65888044fa20771 (fixed)
Vendor states this is fixed in 8c2058717fd06f05d421c2d3adf1dff3c3abcda1 (fixed)
Vendor states this is fixed in 9375a4ea4121625ef27a46b74781cda66a5cc61b (fixed)
Vendor states this is fixed in c3d68e294cbb6a4090bb219d3dcaca85a011809b (fixed)
Vendor states this is fixed in cca4398aa305c22016d1714f388e2fa6ea4e5ad4 (fixed)
Vendor states this is fixed in e1770f7410b4232a0267924f99751dc9c5ca31af (fixed)
Vendor states this is fixed in eb42c3c8fd479166c42984728754cd779c71fd60 (fixed)
Vendor states this is fixed in fba7eb7b248ea0618235f504158b685d752a153a (fixed)
Vendor states this is fixed in 3.16 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (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