wifi: rsi: fix heap OOB write on key removal
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: fix heap OOB write on key removal When a key is removed (data == NULL), rsi_hal_load_key() runs: memset(&set_key[FRAME_DESC_SZ], 0, frame_len - FRAME_DESC_SZ); set_key is a struct rsi_set_key *, so the subscript is scaled by sizeof(struct rsi_set_key) (160 bytes): &set_key[FRAME_DESC_SZ] is skb->data + 2560, and the memset writes 144 zero bytes starting 2.4KB past the end of the 160-byte skb data buffer, corrupting unrelated heap objects. The intended byte offset would have been (u8 *)set_key + FRAME_DESC_SZ. The write fires on every DISABLE_KEY callback, so plain disconnects, roams and interface teardowns trigger it on real networks. The memset is redundant: the whole buffer is zeroed right after allocation, so the frame sent to the device is byte-identical without it. Drop the else branch; normal operation is unaffected. Discovered by Atuin - Automated Vulnerability Discovery Engine.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From dad0d04fa7ba41ce603a01e8e64967650303e9a2 · fixed in b79e2f6585c014c42384f4caa7a37b3e5d26179c; From dad0d04fa7ba41ce603a01e8e64967650303e9a2 · fixed in c67fb3b875a83f9ba92afea4036c7b541f77512a; From dad0d04fa7ba41ce603a01e8e64967650303e9a2 · fixed in 62d40db89180cfab7a917395f9ffc1dac62b0019; From dad0d04fa7ba41ce603a01e8e64967650303e9a2 · fixed in 00bea3589255603c38766cac4a4d6d36493b2556; From dad0d04fa7ba41ce603a01e8e64967650303e9a2 · fixed in ac599cf8edf8aa2dae546f04d3f1849e32c2e738; From dad0d04fa7ba41ce603a01e8e64967650303e9a2 · fixed in f4f2852b664c3ff1436785cd11258a0ce25b74b3; From dad0d04fa7ba41ce603a01e8e64967650303e9a2 · fixed in 8dab6ee020b2cd951b670626ba44a95cd4deac3d; From dad0d04fa7ba41ce603a01e8e64967650303e9a2 · fixed in e6c5ed7a98d7bc8b0f7918246f1c90ddb3f79dfa
- Linux Linux
3.15
- KernelLinux
From 3.15.0 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8
References 8
git.kernel.org
- stable/c/b79e2f6585c014c42384f4caa7a37b3e5d26179c
- stable/c/c67fb3b875a83f9ba92afea4036c7b541f77512a
- stable/c/62d40db89180cfab7a917395f9ffc1dac62b0019
- stable/c/00bea3589255603c38766cac4a4d6d36493b2556
- stable/c/ac599cf8edf8aa2dae546f04d3f1849e32c2e738
- stable/c/f4f2852b664c3ff1436785cd11258a0ce25b74b3
- stable/c/8dab6ee020b2cd951b670626ba44a95cd4deac3d
- stable/c/e6c5ed7a98d7bc8b0f7918246f1c90ddb3f79dfa