CVE-2024-27391: wifi: wilc1000: do not realloc workqueue everytime an interface is added
In the Linux kernel, the following vulnerability has been resolved:
wifi: wilc1000: do not realloc workqueue everytime an interface is added
Commit 09ed8bfc5215 ("wilc1000: Rename workqueue from "WILC_wq" to
"NETDEV-wq"") moved workqueue creation in wilc_netdev_ifc_init in order to
set the interface name in the workqueue name. However, while the driver
needs only one workqueue, the wilc_netdev_ifc_init is called each time we
add an interface over a phy, which in turns overwrite the workqueue with a
new one. This can be observed with the following commands:
for i in $(seq 0 10)
do
iw phy phy0 interface add wlan1 type managed
iw dev wlan1 del
done
ps -eo pid,comm|grep wlan
39 kworker/R-wlan0
98 kworker/R-wlan1
102 kworker/R-wlan1
105 kworker/R-wlan1
108 kworker/R-wlan1
111 kworker/R-wlan1
114 kworker/R-wlan1
117 kworker/R-wlan1
120 kworker/R-wlan1
123 kworker/R-wlan1
126 kworker/R-wlan1
129 kworker/R-wlan1
Fix this leakage by putting back hif_workqueue allocation in
wilc_cfg80211_init. Regarding the workqueue name, it is indeed relevant to
set it lowercase, however it is not attached to a specific netdev, so
enforcing netdev name in the name is not so relevant. Still, enrich the
name with the wiphy name to make it clear which phy is using the workqueue.
Security readout for executives and security teams
Plain-English summary
CVE-2024-27391 is a Linux kernel Wi-Fi driver resource leak. On affected systems using the wilc1000 driver, repeatedly adding interfaces can leave extra kernel workqueues behind, consuming resources over time. The supplied sources do not show remote exploitation, public weaponization, or active exploitation.
Executive priority
Treat as a targeted maintenance issue, not an emergency. Patch affected embedded or wireless Linux assets during the next normal kernel update cycle unless those systems are multi-tenant, exposed to untrusted local users, or resource constrained.
Technical view
The wilc1000 driver created a workqueue each time an interface was initialized, although only one workqueue was needed per phy. New allocations overwrote the previous workqueue reference, leaking kernel worker resources. Stable kernel commits move allocation back to wilc_cfg80211_init and name the queue by wiphy rather than netdev.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the wilc1000 Wi-Fi driver present and used. General Linux servers without this driver or hardware path are unlikely to be exposed. Exact distro impact depends on kernel backports.
Exploitation context
The bundle provides no KEV listing and no cited evidence of active exploitation. The described behavior involves repeated wireless interface creation and deletion on an affected phy, suggesting a local or privileged operational trigger rather than a demonstrated remote attack.
Researcher notes
Evidence supports a kernel resource leak in wilc1000 workqueue allocation. Severity, CVSS, and CWE are absent from the bundle. Do not infer broader Wi-Fi stack exposure; scope analysis to systems using this driver and verify distro-specific backports.
Mitigation direction
Update to a vendor kernel containing the cited stable fixes.
Confirm Linux distribution advisories for backported wilc1000 patches.
Disable or avoid unused wilc1000 driver support where operationally safe.
Prioritize embedded or Wi-Fi appliances using WILC1000-class hardware.
Validation and detection
Inventory kernels and identify systems with wilc1000 driver support enabled.
Check whether vendor kernels include one of the cited stable commits.
Review affected device classes that permit wireless interface lifecycle changes.
In lab only, monitor for persistent workqueue growth after controlled interface lifecycle testing.
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-2024-27391 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.