CVE - CVE-2024-27391

CVE-ID
CVE-2024-27391	Learn more at National Vulnerability Database (NVD) • CVSS Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings • CPE Information
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.
References
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
MISC:https://git.kernel.org/stable/c/328efda22af81130c2ad981c110518cb29ff2f1d URL:https://git.kernel.org/stable/c/328efda22af81130c2ad981c110518cb29ff2f1d MISC:https://git.kernel.org/stable/c/4041c60a9d543b3ad50225385b072ba68e96166e URL:https://git.kernel.org/stable/c/4041c60a9d543b3ad50225385b072ba68e96166e MISC:https://git.kernel.org/stable/c/515cc676dfbce40d93c92b1ff3c1070e917f4e52 URL:https://git.kernel.org/stable/c/515cc676dfbce40d93c92b1ff3c1070e917f4e52 MISC:https://git.kernel.org/stable/c/90ae293d1d255f622318fce6eeea2e18f9fde5c1 URL:https://git.kernel.org/stable/c/90ae293d1d255f622318fce6eeea2e18f9fde5c1 MISC:https://git.kernel.org/stable/c/9ab0c303ccabfd6bdce14432792d41090070008c URL:https://git.kernel.org/stable/c/9ab0c303ccabfd6bdce14432792d41090070008c
Assigning CNA
kernel.org
Date Record Created
20240225	Disclaimer: The record creation date may reflect when the CVE ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Assigned (20240225)
Votes (Legacy)

Comments (Legacy)

Proposed (Legacy)
N/A
This is an record on the CVE List, which provides common identifiers for publicly known cybersecurity vulnerabilities.
Search CVE Using Keywords: You can also search by reference using the CVE Reference Maps.
For More Information: CVE Request Web Form (select "Other" from dropdown)