First published: Fri May 17 2024(Updated: )
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 cfg80211_change_iface() 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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/kernel | <4.19.309 | 4.19.309 |
redhat/kernel | <5.4.271 | 5.4.271 |
redhat/kernel | <5.10.212 | 5.10.212 |
redhat/kernel | <5.15.151 | 5.15.151 |
redhat/kernel | <6.1.81 | 6.1.81 |
redhat/kernel | <6.6.21 | 6.6.21 |
redhat/kernel | <6.7.9 | 6.7.9 |
redhat/kernel | <6.8 | 6.8 |
debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.128-1 6.12.21-1 | |
IBM Security Verify Governance - Identity Manager | <=ISVG 10.0.2 | |
IBM Security Verify Governance, Identity Manager Software Stack | <=ISVG 10.0.2 | |
IBM Security Verify Governance, Identity Manager Virtual Appliance | <=ISVG 10.0.2 | |
IBM Security Verify Governance Identity Manager Container | <=ISVG 10.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-27410 has been rated as a medium severity vulnerability due to the potential for unauthorized mesh ID manipulation.
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.
CVE-2024-27410 affects various kernel versions up to and including 6.8.
CVE-2024-27410 primarily impacts Linux-based systems that utilize the affected kernel versions.
There are no known workarounds for CVE-2024-27410, so upgrading to a patched version is recommended.