CVE-2023-54286
Description
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: dvm: Fix memcpy: detected field-spanning write backtrace
A received TKIP key may be up to 32 bytes because it may contain MIC rx/tx keys too. These are not used by iwl and copying these over overflows the iwl_keyinfo.key field.
Add a check to not copy more data to iwl_keyinfo.key then will fit.
This fixes backtraces like this one:
memcpy: detected field-spanning write (size 32) of single field "sta_cmd.key.key" at drivers/net/wireless/intel/iwlwifi/dvm/sta.c:1103 (size 16) WARNING: CPU: 1 PID: 946 at drivers/net/wireless/intel/iwlwifi/dvm/sta.c:1103 iwlagn_send_sta_key+0x375/0x390 [iwldvm]
Hardware name: Dell Inc. Latitude E6430/0H3MT5, BIOS A21 05/08/2017 RIP: 0010:iwlagn_send_sta_key+0x375/0x390 [iwldvm]
Call Trace:
iwl_set_dynamic_key+0x1f0/0x220 [iwldvm] iwlagn_mac_set_key+0x1e4/0x280 [iwldvm] drv_set_key+0xa4/0x1b0 [mac80211] ieee80211_key_enable_hw_accel+0xa8/0x2d0 [mac80211] ieee80211_key_replace+0x22d/0x8e0 [mac80211]
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A buffer overflow in iwlwifi's dvm driver occurs when copying TKIP keys up to 32 bytes into a 16-byte field, leading to a kernel warning.
Vulnerability
In the Linux kernel's iwlwifi driver for Intel wireless devices, the iwl_keyinfo.key field is only 16 bytes, but a received TKIP key may be up to 32 bytes because it can contain MIC (Message Integrity Code) keys for RX and TX. During processing in iwlagn_send_sta_key, the full key is copied via memcpy without size checking, causing a field-spanning write overflow [1].
Exploitation
The overflow is triggered when a TKIP key is set via the mac80211 subsystem's key management functions. The attacker would need the ability to supply a crafted TKIP key, such as through a malicious access point or by having local privileges to configure keys. No authentication is required beyond that needed to interact with the wireless interface.
Impact
A field-spanning write leads to a kernel warning (as shown in the backtrace) and can corrupt adjacent memory, potentially causing a system crash or denial of service. The bug does not appear to allow arbitrary code execution, but it degrades system stability.
Mitigation
The fix adds a bounds check to copy no more than the size of the key field, preventing the overflow. Patches have been applied to the stable kernel tree [1]. Users should update to a kernel version containing the fix.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
876b5ea43ad2f3ed3c1c2fc34fa57021262e991ad1ab3cc7e87940e4030e457189c8851496cd644f66b43ef1679964086Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/3ed3c1c2fc3482b72e755820261779cd2e2c5a3envd
- git.kernel.org/stable/c/57189c885149825be8eb8c3524b5af017fdeb941nvd
- git.kernel.org/stable/c/6cd644f66b43709816561d63e0173cb0c7aab159nvd
- git.kernel.org/stable/c/76b5ea43ad2fb4f726ddfaff839430a706e7d7c2nvd
- git.kernel.org/stable/c/87940e4030e4705e1f3fd2bbb1854eae8308314bnvd
- git.kernel.org/stable/c/91ad1ab3cc7e981cb6d6ee100686baed64e1277envd
- git.kernel.org/stable/c/ef16799640865f937719f0771c93be5dca18adc6nvd
- git.kernel.org/stable/c/fa57021262e998e2229d6383b1081638df2fe238nvd
News mentions
0No linked articles in our index yet.