{"id":"CVE-2026-99454","summary":"staging: rtl8723bs: fix protected RX frame validation in decrypt path","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nstaging: rtl8723bs: fix protected RX frame validation in decrypt path\n\nThe RX software decrypt path mishandles crafted protected frames from a\nmalicious AP in two ways:\n\n1) decryptor() never checks that a protected frame is long enough to\nhold the 802.11 header plus the per-cipher trailer.  All of\nrtw_wep_decrypt(), rtw_tkip_decrypt() and rtw_aes_decrypt() compute\n\n\tlength = hdr.len - hdrlen - iv_len;\n\nand act on the result, and recvframe_chkmic() similarly computes\n\n\tdatalen = hdr.len - hdrlen - iv_len - icv_len - 8;\n\nfor TKIP (the 8-byte Michael MIC is not accounted for in icv_len).\nA frame shorter than hdrlen + iv_len + icv_len (+ 8 for TKIP) underflows\nthese unsigned subtractions, turning into a ~4 GiB iteration count in\naes_decipher()/arc4_crypt()/rtw_seccalctkipmic() or a ~4 GiB crc32_le()\nlength, causing out-of-bounds reads/writes of up to ~4 GiB starting from\nthe rx skb.  Reject such frames in decryptor() before touching the IV;\nthis covers all three ciphers and the TKIP MIC check, and also keeps the\nunconditional iv[3] access within the frame.\n\n2) validate_80211w_mgmt() keeps using the frame - two memcpys through\nthe stale rx_data pointer and a pkt_len update - before checking\nwhether decryptor() returned NULL.  On decrypt failure (e.g. a unicast\nprotected deauth/disassoc/action frame with a bad MIC, which this path\nalways software-decrypts) the skb has already been freed, so this is a\nuse-after-free read/write, and the caller's error path frees the frame\na second time, drifting free_recvframe_cnt.  Bail out immediately when\ndecryptor() fails, freeing the temporary mgmt_DATA buffer first.\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.","modified":"2026-11-19T17:01:19.269958311Z","published":"2026-11-19T14:41:54.397Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99454.json"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/33e8f5740319996788395d85a4c100f61593cb75"},{"type":"WEB","url":"https://git.kernel.org/stable/c/495cb31c791bdf3f9efef255a9587b05b0526c9d"},{"type":"WEB","url":"https://git.kernel.org/stable/c/60e3352593f224306dfab578bf586b301642265f"},{"type":"WEB","url":"https://git.kernel.org/stable/c/b0e79d0ed03ee2e2b9bc0b637fcb87567ff46112"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99454.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99454"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"554c0a3abf216c991c5ebddcdb2c08689ecd290b"},{"fixed":"60e3352593f224306dfab578bf586b301642265f"},{"fixed":"33e8f5740319996788395d85a4c100f61593cb75"},{"fixed":"b0e79d0ed03ee2e2b9bc0b637fcb87567ff46112"},{"fixed":"495cb31c791bdf3f9efef255a9587b05b0526c9d"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99454.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.12.0"},{"fixed":"6.12.117"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.63"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.3.2"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99454.json"}}],"schema_version":"1.9.2"}