CVE-2024-27391: Vulnerability in Linux Linux
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.
AI Analysis
Technical Summary
CVE-2024-27391 is a vulnerability identified in the Linux kernel's wireless driver for the WILC1000 Wi-Fi chipset. The issue arises from improper management of workqueues within the driver code. Specifically, the function wilc_netdev_ifc_init, which is called each time a new network interface is added over a physical device (phy), reallocates the workqueue repeatedly instead of reusing a single instance. This leads to a resource leak where multiple workqueues are created and overwritten without proper cleanup. The vulnerability was introduced by a commit that renamed the workqueue and moved its creation to wilc_netdev_ifc_init to include the interface name in the workqueue's name. However, since only one workqueue is needed per driver instance, this approach caused unnecessary reallocations. The leak can be observed by repeatedly adding and deleting wireless interfaces, resulting in multiple kernel worker threads (kworker) associated with wlan interfaces. The fix involves moving the workqueue allocation back to wilc_cfg80211_init, ensuring only one workqueue is created per device, and adjusting the naming convention to include the wiphy name instead of the netdev name. This correction prevents resource exhaustion and potential instability in the kernel's wireless subsystem. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability primarily poses a risk of resource exhaustion and potential denial of service on systems using the affected Linux kernel versions with the WILC1000 wireless driver. Systems that frequently add and remove wireless interfaces dynamically, such as embedded devices, IoT gateways, or network appliances running Linux with this driver, could experience degraded performance or kernel instability. While this does not directly lead to privilege escalation or remote code execution, the resulting resource leak could be exploited by an attacker with local access to cause denial of service, impacting availability. Organizations relying on Linux-based infrastructure with wireless connectivity, especially in industrial, telecommunications, or critical infrastructure sectors, should be aware of this issue. The impact is more pronounced in environments where wireless interfaces are dynamically managed or where system uptime and reliability are critical.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Apply the patch provided by the Linux kernel maintainers that moves the workqueue allocation back to wilc_cfg80211_init and corrects the naming scheme. 2) Update Linux kernel versions to the fixed releases as soon as they become available, prioritizing systems using the WILC1000 wireless chipset. 3) Monitor systems for unusual numbers of kworker threads related to wlan interfaces, which may indicate the presence of the resource leak. 4) Limit the ability of unprivileged users to add or remove wireless interfaces dynamically, reducing the risk of triggering the leak. 5) For embedded or IoT devices using custom Linux builds, ensure that the kernel source is updated and rebuilt with the fix integrated. 6) Implement system monitoring and alerting for kernel resource exhaustion symptoms to detect potential exploitation attempts early. These steps go beyond generic advice by focusing on the specific driver and usage patterns involved in this vulnerability.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2024-27391: Vulnerability in Linux Linux
Description
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.
AI-Powered Analysis
Technical Analysis
CVE-2024-27391 is a vulnerability identified in the Linux kernel's wireless driver for the WILC1000 Wi-Fi chipset. The issue arises from improper management of workqueues within the driver code. Specifically, the function wilc_netdev_ifc_init, which is called each time a new network interface is added over a physical device (phy), reallocates the workqueue repeatedly instead of reusing a single instance. This leads to a resource leak where multiple workqueues are created and overwritten without proper cleanup. The vulnerability was introduced by a commit that renamed the workqueue and moved its creation to wilc_netdev_ifc_init to include the interface name in the workqueue's name. However, since only one workqueue is needed per driver instance, this approach caused unnecessary reallocations. The leak can be observed by repeatedly adding and deleting wireless interfaces, resulting in multiple kernel worker threads (kworker) associated with wlan interfaces. The fix involves moving the workqueue allocation back to wilc_cfg80211_init, ensuring only one workqueue is created per device, and adjusting the naming convention to include the wiphy name instead of the netdev name. This correction prevents resource exhaustion and potential instability in the kernel's wireless subsystem. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability primarily poses a risk of resource exhaustion and potential denial of service on systems using the affected Linux kernel versions with the WILC1000 wireless driver. Systems that frequently add and remove wireless interfaces dynamically, such as embedded devices, IoT gateways, or network appliances running Linux with this driver, could experience degraded performance or kernel instability. While this does not directly lead to privilege escalation or remote code execution, the resulting resource leak could be exploited by an attacker with local access to cause denial of service, impacting availability. Organizations relying on Linux-based infrastructure with wireless connectivity, especially in industrial, telecommunications, or critical infrastructure sectors, should be aware of this issue. The impact is more pronounced in environments where wireless interfaces are dynamically managed or where system uptime and reliability are critical.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Apply the patch provided by the Linux kernel maintainers that moves the workqueue allocation back to wilc_cfg80211_init and corrects the naming scheme. 2) Update Linux kernel versions to the fixed releases as soon as they become available, prioritizing systems using the WILC1000 wireless chipset. 3) Monitor systems for unusual numbers of kworker threads related to wlan interfaces, which may indicate the presence of the resource leak. 4) Limit the ability of unprivileged users to add or remove wireless interfaces dynamically, reducing the risk of triggering the leak. 5) For embedded or IoT devices using custom Linux builds, ensure that the kernel source is updated and rebuilt with the fix integrated. 6) Implement system monitoring and alerting for kernel resource exhaustion symptoms to detect potential exploitation attempts early. These steps go beyond generic advice by focusing on the specific driver and usage patterns involved in this vulnerability.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-02-25T13:47:42.677Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982ac4522896dcbe332e
Added to database: 5/21/2025, 9:08:58 AM
Last enriched: 6/29/2025, 3:24:49 PM
Last updated: 8/16/2025, 4:16:57 AM
Views: 13
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.