CVE-2026-74651

staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie()

HIGH
8.1
CVSS Score
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 16, 2026 at 08:17 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
HIGH8.1
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie() rtw_get_wpa_ie() reads bytes at fixed offsets into a vendor-specific information element without checking that the element is long enough, causing an out-of-bounds read for a short trailing IE. The function locates a vendor-specific IE (EID 221) with rtw_get_ie() and then compares a 4-byte OUI+type at pbuf + 2 and reads a 2-byte version word at pbuf + 6. Those accesses require the IE body to be at least 6 bytes, but rtw_get_ie() only guarantees that the element fits within the buffer; it does not enforce a minimum body length. A vendor-specific IE whose length byte is 0 to 5, placed at the end of the buffer, therefore makes these reads run past the end of the IE and past the end of the buffer itself. The buffer holds information elements taken from received management frames and from the IE blob passed to rtw_cfg80211_set_wpa_ie(), which is kmemdup'd to its exact length, so the read can run off the end of the allocation. The sibling helpers rtw_get_sec_ie(), rtw_get_wapi_ie() and rtw_get_wps_ie() in this file already reject too-short vendor-specific IEs before their OUI memcmp(); rtw_get_wpa_ie() was never brought in line with them, and needs a minimum of 6 rather than 4 bytes because of the version word. Add the missing length check.

Affected

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

4.12554c0a3abf216c991c5ebddcdb2c08689ecd290b
Vendor states this is fixed in 01ab275f8f3e497a13ebbe4ded44ec0623bccde3 (fixed)
Vendor states this is fixed in 0d19f0600fbb610c42f2a86f95c35706dc04691b (fixed)
Vendor states this is fixed in 1c3e23e78862493e8cf1adad02b10ffcb8b9921c (fixed)
Vendor states this is fixed in 42c5a0d454aa5b54fec17162d9a1f8c30f8af45a (fixed)
Vendor states this is fixed in 4fc459c5cd8767ca4d9bf2f7becbd562639ba4d9 (fixed)
Vendor states this is fixed in b45be82387bf759931acdd21ca7dfe740f16eb97 (fixed)
Vendor states this is fixed in c9068f82a0906b29c905e8788edb62c3208c7c8a (fixed)
Vendor states this is fixed in e167a38a8a8f50f137721fef1a1fbba0f4588b5d (fixed)
Vendor states this is fixed in 4.12 (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.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.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.1HIGHLinux
Vector?

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