CVE-2026-93064
Published Sep 17, 2026
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix off-by-one in TXF key sanitiser iwl_mvm_frob_txf_key_iter() tracks the last matched byte position in loop variable 'i'. When a full key match is found (match == keylen), 'i' points at the last byte of the matched key. The memset start offset should therefore be i + 1 - keylen, not i - keylen; the current code zeroes one byte before the match and leaves the final key byte un-sanitised.
Is your site exposed to CVE-2026-93064?
Run a free security scan — no signup, results in seconds.
References
Other References
https://git.kernel.org/stable/c/1af000d75b1c96f7cbdf23f14d0ee1c51b12f8e6
https://git.kernel.org/stable/c/2a77cb320e3998afa5e1ed0e95908b226aae9ed6
https://git.kernel.org/stable/c/4c582ed61325135f841ca93667d7551a8e31e58d
https://git.kernel.org/stable/c/5bcc933c6d47d795dab27458b9001c2d97130fd3
https://git.kernel.org/stable/c/c9d8641aea01c3b2516483e128e1f557cfbcf44a
https://git.kernel.org/stable/c/f6a6c01cbc046f68e6916a7e047a1bc881c8c9ab
Frequently Asked Questions
What is CVE-2026-93064? +
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: mvm: fix off-by-one in TXF key sanitiser
iwl_mvm_frob_txf_key_iter() tracks the last matched byte position
in loop variable 'i'. When a full key match is found (match ==
keylen), 'i' points at the last byte of the matched key. The
memset start offset should therefore be i + 1 - keylen, not
i - keylen; the current code zeroes one byte before the match
and leaves the final key byte un-sanitised.
How do I check if I'm vulnerable to CVE-2026-93064? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.