CVE-2026-74650

staging: rtl8723bs: fix OOB read in WMM_param_handler()

N/A
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 14, 2026 at 01:10 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: staging: rtl8723bs: fix OOB read in WMM_param_handler() WMM_param_handler() copies a fixed-size WMM parameter element out of a received information element without checking that the element is long enough, causing an out-of-bounds read for a short WMM IE. The handler reads sizeof(struct WMM_para_element) (18) bytes at pIE->data + 6, so it requires pIE->length to be at least 24 (WLAN_WMM_LEN), but it never validates the length. Two of its three callers reach it after matching only the WMM OUI: OnAssocRsp() in rtw_mlme_ext.c matches a 6-byte OUI, and join_cmd_hdl() matches a 4-byte OUI, before calling the handler. A vendor-specific IE carrying the WMM OUI but a length between 6 and 23, placed in an association response or in the IE blob handed to join_cmd_hdl(), passes the OUI check and then makes the memcmp() and memcpy() at pIE->data + 6 read past the end of the element. OnAssocRsp() parses a frame received from the AP, so this is reachable from a remote peer. The remaining caller in rtw_wlan_util.c already guards the handler with "pIE->length == WLAN_WMM_LEN". Move the equivalent check into the handler itself so every caller is covered; the sibling IE handlers in the same parsing loop (HT_caps_handler(), HT_info_handler(), ERP_IE_handler()) likewise bound their accesses by pIE->length.

Affected

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

4.12554c0a3abf216c991c5ebddcdb2c08689ecd290b
Vendor states this is fixed in 1158b9931207392d6dd136aa0c4be18893b50fa1 (fixed)
Vendor states this is fixed in 2bee6f7a0f0125238951e31da2e96d06fe359043 (fixed)
Vendor states this is fixed in 5df2fd06567df5f178c8faae0bdaefd203618d21 (fixed)
Vendor states this is fixed in 6cdca4c8b64c15a3ab9ad7a85f482e9519eadf93 (fixed)
Vendor states this is fixed in ae21407350151bddfd4fea7aa39bd0643c0ca9d3 (fixed)
Vendor states this is fixed in ce2399717de242344880044b91a20a712644fdfb (fixed)
Vendor states this is fixed in e429c6dfd5d2324cd866daaf4c29d5cfe4dea0e4 (fixed)
Vendor states this is fixed in e5b7610008f4e6a80c8b071aa77ddbd5e17ea472 (fixed)
Vendor states this is fixed in 4.12 (unaffected)
Vendor states this is fixed in 5.10.267 (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.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (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