CVE-2024-27053: wifi: wilc1000: fix RCU usage in connect path
In the Linux kernel, the following vulnerability has been resolved:
wifi: wilc1000: fix RCU usage in connect path
With lockdep enabled, calls to the connect function from cfg802.11 layer
lead to the following warning:
=============================
WARNING: suspicious RCU usage
6.7.0-rc1-wt+ #333 Not tainted
-----------------------------
drivers/net/wireless/microchip/wilc1000/hif.c:386
suspicious rcu_dereference_check() usage!
[...]
stack backtrace:
CPU: 0 PID: 100 Comm: wpa_supplicant Not tainted 6.7.0-rc1-wt+ #333
Hardware name: Atmel SAMA5
unwind_backtrace from show_stack+0x18/0x1c
show_stack from dump_stack_lvl+0x34/0x48
dump_stack_lvl from wilc_parse_join_bss_param+0x7dc/0x7f4
wilc_parse_join_bss_param from connect+0x2c4/0x648
connect from cfg80211_connect+0x30c/0xb74
cfg80211_connect from nl80211_connect+0x860/0xa94
nl80211_connect from genl_rcv_msg+0x3fc/0x59c
genl_rcv_msg from netlink_rcv_skb+0xd0/0x1f8
netlink_rcv_skb from genl_rcv+0x2c/0x3c
genl_rcv from netlink_unicast+0x3b0/0x550
netlink_unicast from netlink_sendmsg+0x368/0x688
netlink_sendmsg from ____sys_sendmsg+0x190/0x430
____sys_sendmsg from ___sys_sendmsg+0x110/0x158
___sys_sendmsg from sys_sendmsg+0xe8/0x150
sys_sendmsg from ret_fast_syscall+0x0/0x1c
This warning is emitted because in the connect path, when trying to parse
target BSS parameters, we dereference a RCU pointer whithout being in RCU
critical section.
Fix RCU dereference usage by moving it to a RCU read critical section. To
avoid wrapping the whole wilc_parse_join_bss_param under the critical
section, just use the critical section to copy ies data
Security readout for executives and security teams
Plain-English summary
A Linux Wi-Fi driver flaw can mishandle shared memory while a device using Microchip WILC1000 connects to a network. The supplied CVSS rates possible confidentiality loss and system disruption as critical. Exposure is limited to systems using this driver and affected kernels; the bundle does not demonstrate practical exploitation.
Executive priority
Treat confirmed WILC1000 deployments as urgent because the supplied score is 9.1, but avoid fleet-wide emergency action for Linux systems without this hardware or driver. Require rapid inventory, vendor-supported updates, and evidence that the stable fix is present.
Technical view
The wilc1000 connection path dereferences an RCU-protected pointer while parsing target BSS parameters without entering an RCU read-side critical section. Stable fixes protect the dereference and copy information-element data inside that section. Lockdep exposed the defect during a wpa_supplicant connection operation.
Likely exposure
Prioritize Linux appliances, embedded systems, and other devices using Microchip WILC1000 Wi-Fi hardware with the wilc1000 driver. Affected-version data in the bundle is not sufficiently clear for reliable range matching, so verify the deployed kernel against vendor packages or the cited stable commits.
Exploitation context
The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. The report documents a lockdep warning and a defective connection-path memory access. Whether an attacker can reliably obtain the CVSS-described confidentiality or availability impact is not established here.
Researcher notes
The bundle attributes CWE-476 and CVSS 9.1, although the technical description specifically shows an RCU lifetime violation detected by lockdep. Eight stable-kernel commits are cited. Exact vulnerable and fixed ranges are ambiguous in the supplied affected-version records, and no proof of remotely achievable impact is included.
Mitigation direction
Install a vendor-supported kernel containing the applicable cited stable fix.
Check Linux distribution and device-vendor advisories for corrected package versions.
Prioritize internet-facing or safety-critical devices that rely on WILC1000 Wi-Fi.
If patching is delayed, obtain vendor-approved compensating controls; none are specified in the bundle.
Validation and detection
Confirm whether each device loads or includes the wilc1000 driver.
Record exact kernel builds and compare them with vendor-fixed packages or cited commits.
Verify the applicable RCU fix is present in deployed kernel source or package metadata.
After updating, test Wi-Fi connections and review kernel diagnostics for recurring RCU warnings.
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.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.