Linux Kernel up to 7.1.8 rtl8723bs rtw_mlme_ext.c WMM_param_handler length out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k0.43-

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.1.8. It has been rated as critical. This affects the function WMM_param_handler of the file rtw_mlme_ext.c of the component rtl8723bs. This manipulation of the argument length causes out-of-bounds. The identification of this vulnerability is CVE-2026-74650. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 7.1.8 and classified as critical. Affected by this vulnerability is the function WMM_param_handler of the file rtw_mlme_ext.c of the component rtl8723bs. The manipulation of the argument length with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-74650 since 08/15/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/22/2026).

Upgrading to version 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45 or 7.1.9 eliminates this vulnerability. Applying the patch 6cdca4c8b64c15a3ab9ad7a85f482e9519eadf93/2bee6f7a0f0125238951e31da2e96d06fe359043/1158b9931207392d6dd136aa0c4be18893b50fa1/ce2399717de242344880044b91a20a712644fdfb/e5b7610008f4e6a80c8b071aa77ddbd5e17ea472/e429c6dfd5d2324cd866daaf4c29d5cfe4dea0e4/ae21407350151bddfd4fea7aa39bd0643c0ca9d3 is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.216/6.1.183/6.6.152/6.12.104/6.18.45/7.1.9
Patch: 6cdca4c8b64c15a3ab9ad7a85f482e9519eadf93/2bee6f7a0f0125238951e31da2e96d06fe359043/1158b9931207392d6dd136aa0c4be18893b50fa1/ce2399717de242344880044b91a20a712644fdfb/e5b7610008f4e6a80c8b071aa77ddbd5e17ea472/e429c6dfd5d2324cd866daaf4c29d5cfe4dea0e4/ae21407350151bddfd4fea7aa39bd0643c0ca9d3

Timelineinfo

08/15/2026 CVE reserved
08/22/2026 +7 days Advisory disclosed
08/22/2026 +0 days VulDB entry created
08/22/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-74650 (🔒)
GCVE (CVE): GCVE-0-2026-74650
GCVE (VulDB): GCVE-100-394429

Entryinfo

Created: 08/22/2026 18:38
Changes: 08/22/2026 18:38 (61)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!