CVE-2024-27391

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.

• https://git.kernel.org/stable/c/328efda22af81130c2ad981c110518cb29ff2f1dPatch
• https://git.kernel.org/stable/c/4041c60a9d543b3ad50225385b072ba68e96166ePatch
• https://git.kernel.org/stable/c/515cc676dfbce40d93c92b1ff3c1070e917f4e52Patch
• https://git.kernel.org/stable/c/90ae293d1d255f622318fce6eeea2e18f9fde5c1Patch
• https://git.kernel.org/stable/c/9ab0c303ccabfd6bdce14432792d41090070008cPatch
• https://git.kernel.org/stable/c/328efda22af81130c2ad981c110518cb29ff2f1dPatch
• https://git.kernel.org/stable/c/4041c60a9d543b3ad50225385b072ba68e96166ePatch
• https://git.kernel.org/stable/c/515cc676dfbce40d93c92b1ff3c1070e917f4e52Patch
• https://git.kernel.org/stable/c/90ae293d1d255f622318fce6eeea2e18f9fde5c1Patch
• https://git.kernel.org/stable/c/9ab0c303ccabfd6bdce14432792d41090070008cPatch

Published

May 1, 2024

Last Modified

Jun 17, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2024-27386A vulnerability was discovered in the slsi_handle_nan_rx_eve…6.7
• CVE-2024-27387An issue was discovered in Samsung Mobile Processor Exynos 9…7.8
• CVE-2024-27388In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-27389In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-2739The Advanced Search WordPress plugin through 1.1.6 does not …8.7
• CVE-2024-27390In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-27392In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2024-27393In the Linux kernel, the following vulnerability has been re…7.5
• CVE-2024-27394In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2024-27395In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2024-27396In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2024-27397In the Linux kernel, the following vulnerability has been re…7