CVE-2024-27410: wifi: nl80211: reject iftype change with mesh ID change
In the Linux kernel, the following vulnerability has been resolved:
wifi: nl80211: reject iftype change with mesh ID change
It's currently possible to change the mesh ID when the interface isn't yet in mesh mode, at the same time as changing it into mesh mode. This leads to an overwrite of data in the wdev->u union for the interface type it currently has, causing cfg80211changeiface() to do wrong things when switching.
We could probably allow setting an interface to mesh while setting the mesh ID at the same time by doing a different order of operations here, but realistically there's no userspace that's going to do this, so just disallow changes in iftype when setting mesh ID.
Other sources
In the Linux kernel, the following vulnerability has been resolved:
wifi: nl80211: reject iftype change with mesh ID change
The Linux kernel CVE team has assigned CVE-2024-27410 to this issue.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024051701-CVE-2024-27410-874a@gregkh/T
— Red Hat
Linux Kernel is vulnerable to a denial of service, caused by a flaw when change the mesh ID and change interface to mesh mode at the same time in the WiFi module. By sending a specially crafted request, a local authenticated attacker could exploit this vulnerability to cause a denial of service condition.
— IBM
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-27410?
CVE-2024-27410 has been rated as a medium severity vulnerability due to the potential for unauthorized mesh ID manipulation.
How do I fix CVE-2024-27410?
To resolve CVE-2024-27410, upgrade to the latest kernel versions: 4.19.309, 5.4.271, 5.10.212, 5.15.151, 6.1.81, 6.6.21, 6.7.9, or 6.8.
Which Linux kernel versions are affected by CVE-2024-27410?
CVE-2024-27410 affects various kernel versions up to and including 6.8.
What types of systems are impacted by CVE-2024-27410?
CVE-2024-27410 primarily impacts Linux-based systems that utilize the affected kernel versions.
Is there a workaround for CVE-2024-27410?
There are no known workarounds for CVE-2024-27410, so upgrading to a patched version is recommended.