CVE-2026-74650
staging: rtl8723bs: fix OOB read in WMM_param_handler()
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.
INFO
Published Date :
Aug. 22, 2026, 4:16 p.m.
Last Modified :
Aug. 22, 2026, 4:16 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Solution
- Validate WMM element length before copying data.
- Ensure pIE->length is checked by the handler.
- Update kernel to include the fix.
- Apply security patches promptly.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-74650.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-74650 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-74650
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-74650 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-74650 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 22, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '554c0a3abf216c991c5ebddcdb2c08689ecd290b', 'lessThan': '6cdca4c8b64c15a3ab9ad7a85f482e9519eadf93', 'versionType': 'git'}, {'status': 'affected', 'version': '554c0a3abf216c991c5ebddcdb2c08689ecd290b', 'lessThan': '2bee6f7a0f0125238951e31da2e96d06fe359043', 'versionType': 'git'}, {'status': 'affected', 'version': '554c0a3abf216c991c5ebddcdb2c08689ecd290b', 'lessThan': '1158b9931207392d6dd136aa0c4be18893b50fa1', 'versionType': 'git'}, {'status': 'affected', 'version': '554c0a3abf216c991c5ebddcdb2c08689ecd290b', 'lessThan': 'ce2399717de242344880044b91a20a712644fdfb', 'versionType': 'git'}, {'status': 'affected', 'version': '554c0a3abf216c991c5ebddcdb2c08689ecd290b', 'lessThan': 'e5b7610008f4e6a80c8b071aa77ddbd5e17ea472', 'versionType': 'git'}, {'status': 'affected', 'version': '554c0a3abf216c991c5ebddcdb2c08689ecd290b', 'lessThan': 'e429c6dfd5d2324cd866daaf4c29d5cfe4dea0e4', 'versionType': 'git'}, {'status': 'affected', 'version': '554c0a3abf216c991c5ebddcdb2c08689ecd290b', 'lessThan': 'ae21407350151bddfd4fea7aa39bd0643c0ca9d3', 'versionType': 'git'}], 'programFiles': ['drivers/staging/rtl8723bs/core/rtw_wlan_util.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4.12'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.12', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.15.216', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.183', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.152', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.104', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.45', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.9', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/staging/rtl8723bs/core/rtw_wlan_util.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/1158b9931207392d6dd136aa0c4be18893b50fa1 Added Reference https://git.kernel.org/stable/c/2bee6f7a0f0125238951e31da2e96d06fe359043 Added Reference https://git.kernel.org/stable/c/6cdca4c8b64c15a3ab9ad7a85f482e9519eadf93 Added Reference https://git.kernel.org/stable/c/ae21407350151bddfd4fea7aa39bd0643c0ca9d3 Added Reference https://git.kernel.org/stable/c/ce2399717de242344880044b91a20a712644fdfb Added Reference https://git.kernel.org/stable/c/e429c6dfd5d2324cd866daaf4c29d5cfe4dea0e4 Added Reference https://git.kernel.org/stable/c/e5b7610008f4e6a80c8b071aa77ddbd5e17ea472