CVE-2024-27391
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2024-27391
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-27391.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2024-27391
- Downstream
- Published
- 2024-05-01T13:05:16Z
- Modified
- 2025-10-17T03:43:47.184458Z
- Summary
- wifi: wilc1000: do not realloc workqueue everytime an interface is added
- Details
-
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 "WILCwq" to "NETDEV-wq"") moved workqueue creation in wilcnetdevifcinit in order to set the interface name in the workqueue name. However, while the driver needs only one workqueue, the wilcnetdevifc_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 hifworkqueue allocation in wilccfg80211_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
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/328efda22af81130c2ad981c110518cb29ff2f1d
- https://git.kernel.org/stable/c/4041c60a9d543b3ad50225385b072ba68e96166e
- https://git.kernel.org/stable/c/515cc676dfbce40d93c92b1ff3c1070e917f4e52
- https://git.kernel.org/stable/c/90ae293d1d255f622318fce6eeea2e18f9fde5c1
- https://git.kernel.org/stable/c/9ab0c303ccabfd6bdce14432792d41090070008c
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced09ed8bfc5215ad5aac91c50008277b5586b9ef24Fixed515cc676dfbce40d93c92b1ff3c1070e917f4e52
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced09ed8bfc5215ad5aac91c50008277b5586b9ef24Fixed4041c60a9d543b3ad50225385b072ba68e96166e
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced09ed8bfc5215ad5aac91c50008277b5586b9ef24Fixed90ae293d1d255f622318fce6eeea2e18f9fde5c1
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced09ed8bfc5215ad5aac91c50008277b5586b9ef24Fixed9ab0c303ccabfd6bdce14432792d41090070008c
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced09ed8bfc5215ad5aac91c50008277b5586b9ef24Fixed328efda22af81130c2ad981c110518cb29ff2f1d