CVE-2026-99454
staging: rtl8723bs: fix protected RX frame validation in decrypt path
What happened?
In the Linux kernel, the following vulnerability has been resolved:
staging: rtl8723bs: fix protected RX frame validation in decrypt path
The RX software decrypt path mishandles crafted protected frames from a malicious AP in two ways:
1) decryptor() never checks that a protected frame is long enough to hold the 802.11 header plus the per-cipher trailer. All of rtw_wep_decrypt(), rtw_tkip_decrypt() and rtw_aes_decrypt() compute
length = hdr.len - hdrlen - iv_len;
and act on the result, and recvframe_chkmic() similarly computes
datalen = hdr.len - hdrlen - iv_len - icv_len - 8;
for TKIP (the 8-byte Michael MIC is not accounted for in icv_len). A frame shorter than hdrlen + iv_len + icv_len (+ 8 for TKIP) underflows these unsigned subtractions, turning into a ~4 GiB iteration count in aes_decipher()/arc4_crypt()/rtw_seccalctkipmic() or a ~4 GiB crc32_le() length, causing out-of-bounds reads/writes of up to ~4 GiB starting from the rx skb. Reject such frames in decryptor() before touching the IV; this covers all three ciphers and the TKIP MIC check, and also keeps the unconditional iv[3] access within the frame.
2) validate_80211w_mgmt() keeps using the frame - two memcpys through the stale rx_data pointer and a pkt_len update - before checking whether decryptor() returned NULL. On decrypt failure (e.g. a unicast protected deauth/disassoc/action frame with a bad MIC, which this path always software-decrypts) the skb has already been freed, so this is a use-after-free read/write, and the caller's error path frees the frame a second time, drifting free_recvframe_cnt. Bail out immediately when decryptor() fails, freeing the temporary mgmt_DATA buffer first.
Discovered by Atuin - Automated Vulnerability Discovery Engine.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 554c0a3abf216c991c5ebddcdb2c08689ecd290b to < 60e3352593f224306dfab578bf586b301642265f; affected: 554c0a3abf216c991c5ebddcdb2c08689ecd290b to < 33e8f5740319996788395d85a4c100f61593cb75; affected: 554c0a3abf216c991c5ebddcdb2c08689ecd290b to < b0e79d0ed03ee2e2b9bc0b637fcb87567ff46112; affected: 554c0a3abf216c991c5ebddcdb2c08689ecd290b to < 495cb31c791bdf3f9efef255a9587b05b0526c9d | See vendor advisory |
| LinuxLinux | affected: 4.12; unaffected: 0 to < 4.12; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.63 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99454
- https://git.kernel.org/stable/c/60e3352593f224306dfab578bf586b301642265f
- https://git.kernel.org/stable/c/33e8f5740319996788395d85a4c100f61593cb75
- https://git.kernel.org/stable/c/b0e79d0ed03ee2e2b9bc0b637fcb87567ff46112
- https://git.kernel.org/stable/c/495cb31c791bdf3f9efef255a9587b05b0526c9d