Strix
69.2K

CVE-2026-98407

Unknown

Last modified

CVE-2026-98407 is a vulnerability of currently unknown severity. 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.

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= dad0d04fa7ba41ce603a01e8e64967650303e9a2, < b79e2f6585c014c42384f4caa7a37b3e5d26179c; >= dad0d04fa7ba41ce603a01e8e64967650303e9a2, < c67fb3b875a83f9ba92afea4036c7b541f77512a; >= dad0d04fa7ba41ce603a01e8e64967650303e9a2, < 62d40db89180cfab7a917395f9ffc1dac62b0019; >= dad0d04fa7ba41ce603a01e8e64967650303e9a2, < 00bea3589255603c38766cac4a4d6d36493b2556; >= dad0d04fa7ba41ce603a01e8e64967650303e9a2, < ac599cf8edf8aa2dae546f04d3f1849e32c2e738; >= dad0d04fa7ba41ce603a01e8e64967650303e9a2, < f4f2852b664c3ff1436785cd11258a0ce25b74b3; >= dad0d04fa7ba41ce603a01e8e64967650303e9a2, < 8dab6ee020b2cd951b670626ba44a95cd4deac3d; >= dad0d04fa7ba41ce603a01e8e64967650303e9a2, < e6c5ed7a98d7bc8b0f7918246f1c90ddb3f79dfa
LinuxLinux3.15

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98407?
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.
How severe is CVE-2026-98407?
Severity scoring for CVE-2026-98407 is pending analysis.
How do I fix CVE-2026-98407?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-98407?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST