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]
<snip>
Hardware name: Dell Inc. Latitude E6430/0H3MT5, BIOS A21 05/08/2017
RIP: 0010:iwlagn_send_sta_key+0x375/0x390 [iwldvm]
<snip>
Call Trace:
<TASK>
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]
<snip>
Security readout for executives and security teams
Plain-English summary
CVE-2023-54286 is a Linux kernel Wi-Fi driver memory overwrite bug in Intel iwlwifi dvm handling of TKIP keys. The source describes a resolved kernel issue, but provides no CVSS score and no evidence of active exploitation. Business urgency is highest for Linux fleets using affected kernels with Intel wireless hardware and TKIP-capable Wi-Fi configurations.
Executive priority
Treat as a targeted kernel maintenance item, not an emergency, unless affected Linux endpoints rely on Intel wireless and TKIP-capable networks. Patch through normal kernel update channels, with higher priority for mobile endpoint fleets.
Technical view
The iwlwifi dvm code could copy a received TKIP key up to 32 bytes into the 16-byte iwl_keyinfo.key field, causing a field-spanning write in iwlagn_send_sta_key. The kernel fix adds a bounds check so only data fitting the destination field is copied. Impact details beyond the warning/backtrace are not provided.
Likely exposure
Likely exposure is Linux systems running affected kernel versions with the Intel iwlwifi dvm wireless driver path active, especially where TKIP keys may be processed. Server exposure is likely low unless Wi-Fi is enabled with relevant hardware. The bundle does not identify specific distributions, device models, or package versions.
Exploitation context
The source bundle does not show KEV listing, public exploitation, exploit code, or remote attack confirmation. The described trigger is handling a received TKIP key that includes unused MIC rx/tx material, causing an oversized copy into a smaller driver field.
Researcher notes
Evidence supports a bounds-check defect in drivers/net/wireless/intel/iwlwifi/dvm/sta.c. The bundle gives stable fix commits and affected kernel version markers, but lacks CVSS, confirmed impact beyond overflow warning, exploitability analysis, and distribution-specific fixed releases.
Mitigation direction
Update to a kernel or distribution package containing the referenced stable iwlwifi fix.
Check Linux distribution security advisories for the exact fixed kernel package.
Prioritize laptops and workstations using Intel iwlwifi dvm wireless hardware.
Review whether TKIP is still enabled in managed Wi-Fi environments.
If no vendor package is available, follow vendor kernel guidance before applying custom patches.
Validation and detection
Inventory Linux hosts for affected kernel versions listed in the CVE record.
Confirm whether Intel iwlwifi dvm modules or hardware are present.
Check kernel changelogs for the referenced stable commit in deployed packages.
Review kernel logs for iwlagn_send_sta_key or field-spanning write warnings.
Verify Wi-Fi security configuration where TKIP remains enabled.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-54286 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 30, 2025, 12:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.