CVE-2024-27391 json
wifi: wilc1000: do not realloc workqueue everytime an interface is added
published 2024-05-01 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-24595
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9
- linux Debian 12 6.1.85-1
- linux Debian 14, Debian 13 6.7.12-1
debian advisories DEBIAN-CVE-2024-27391
- linux Ubuntu 24.04 LTS 6.8.0-35.35
- linux-aws Ubuntu 24.04 LTS 6.8.0-1009.9
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1008.9
- linux-gke Ubuntu 24.04 LTS 6.8.0-1004.7
- linux-ibm Ubuntu 24.04 LTS 6.8.0-1006.6
- linux-azure Ubuntu 24.04 LTS 6.8.0-1008.8
- linux-raspi Ubuntu 24.04 LTS 6.8.0-1005.5
- linux-riscv Ubuntu 24.04 LTS 6.8.0-35.35.1
ubuntu advisories UBUNTU-CVE-2024-27391
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.0 6.4.0-9.1
- kernel-source-rt Linux Micro 6.0 6.4.0-9.1
- kernel-source Linux Micro 6.0 6.4.0-18.1
- kernel-default Linux Micro 6.0 6.4.0-18.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-18.1
- kernel-default-base Linux Micro 6.0 6.4.0-17.1.1.51
suse advisories SUSE-SU-2025:20028-1SUSE-SU-2025:20008-1
- hyperv-daemons Azure Linux 3.0 6.6.29.1-1
azure linux advisories AZL-40325
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/515cc676dfbce40d93c92b1ff3c1070e917f4e52 commit
- git.kernel.org/stable/c/4041c60a9d543b3ad50225385b072ba68e96166e commit
- git.kernel.org/stable/c/90ae293d1d255f622318fce6eeea2e18f9fde5c1 commit
- git.kernel.org/stable/c/9ab0c303ccabfd6bdce14432792d41090070008c commit
- git.kernel.org/stable/c/328efda22af81130c2ad981c110518cb29ff2f1d commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-27391 updated cvss 5.5
kernel: wifi: wilc1000: do not realloc workqueue everytime an interface is added
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/515cc676dfbce40d93c92b1ff3c1070e917f4e52
patch
-
git.kernel.org
/stable/c/4041c60a9d543b3ad50225385b072ba68e96166e
patch
-
git.kernel.org
/stable/c/90ae293d1d255f622318fce6eeea2e18f9fde5c1
patch
-
git.kernel.org
/stable/c/9ab0c303ccabfd6bdce14432792d41090070008c
patch
-
git.kernel.org
/stable/c/328efda22af81130c2ad981c110518cb29ff2f1d
patch
Sources
- CVE List CVE-2024-27391
- NVD CVE-2024-27391
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.