cveboard RSS feed

CVE-2024-27391

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2024
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

wifi: wilc1000: do not realloc workqueue everytime an interface is added

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
09ed8bfc5215ad5aac91c50008277b5586b9ef24affectedgit515cc676dfbce40d93c92b1ff3c1070e917f4e52UnavailableNone listed
09ed8bfc5215ad5aac91c50008277b5586b9ef24affectedgit4041c60a9d543b3ad50225385b072ba68e96166eUnavailableNone listed
09ed8bfc5215ad5aac91c50008277b5586b9ef24affectedgit90ae293d1d255f622318fce6eeea2e18f9fde5c1UnavailableNone listed
09ed8bfc5215ad5aac91c50008277b5586b9ef24affectedgit9ab0c303ccabfd6bdce14432792d41090070008cUnavailableNone listed
09ed8bfc5215ad5aac91c50008277b5586b9ef24affectedgit328efda22af81130c2ad981c110518cb29ff2f1dUnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
5.17affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver5.17UnavailableNone listed
6.1.83unaffectedsemverUnavailable6.1.*None listed
6.6.23unaffectedsemverUnavailable6.6.*None listed
6.7.11unaffectedsemverUnavailable6.7.*None listed
6.8.2unaffectedsemverUnavailable6.8.*None listed
6.9unaffectedoriginal_commit_for_fixUnavailable*None listed