7.8
CWE
415
Advisory Published
Updated

CVE-2022-49290: mac80211: fix potential double free on mesh join

First published: Wed Feb 26 2025(Updated: )

In the Linux kernel, the following vulnerability has been resolved: mac80211: fix potential double free on mesh join While commit 6a01afcf8468 ("mac80211: mesh: Free ie data when leaving mesh") fixed a memory leak on mesh leave / teardown it introduced a potential memory corruption caused by a double free when rejoining the mesh: ieee80211_leave_mesh() -> kfree(sdata->u.mesh.ie); ... ieee80211_join_mesh() -> copy_mesh_setup() -> old_ie = ifmsh->ie; -> kfree(old_ie); This double free / kernel panics can be reproduced by using wpa_supplicant with an encrypted mesh (if set up without encryption via "iw" then ifmsh->ie is always NULL, which avoids this issue). And then calling: $ iw dev mesh0 mesh leave $ iw dev mesh0 mesh join my-mesh Note that typically these commands are not used / working when using wpa_supplicant. And it seems that wpa_supplicant or wpa_cli are going through a NETDEV_DOWN/NETDEV_UP cycle between a mesh leave and mesh join where the NETDEV_UP resets the mesh.ie to NULL via a memcpy of default_mesh_setup in cfg80211_netdev_notifier_call, which then avoids the memory corruption, too. The issue was first observed in an application which was not using wpa_supplicant but "Senf" instead, which implements its own calls to nl80211. Fixing the issue by removing the kfree()'ing of the mesh IE in the mesh join function and leaving it solely up to the mesh leave to free the mesh IE.

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel
Linux Kernel>=4.4.233<4.5
Linux Kernel>=4.9.233<4.9.309
Linux Kernel>=4.14.192<4.14.274
Linux Kernel>=4.19.137<4.19.237
Linux Kernel>=5.4.56<5.4.188
Linux Kernel>=5.7.13<5.10.109
Linux Kernel>=5.11<5.15.32
Linux Kernel>=5.16<5.16.18
Linux Kernel>=5.17<5.17.1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2022-49290?

    CVE-2022-49290 has been classified as a medium severity vulnerability.

  • How do I fix CVE-2022-49290?

    To fix CVE-2022-49290, ensure you upgrade the Linux kernel to a version that includes the patch resolving this vulnerability.

  • What systems are affected by CVE-2022-49290?

    CVE-2022-49290 affects various versions of the Linux kernel, specifically in the range from 4.4.233 to 5.17.1.

  • What type of vulnerability is CVE-2022-49290?

    CVE-2022-49290 is a memory corruption vulnerability related to the mac80211 subsystem in the Linux kernel.

  • Can CVE-2022-49290 be exploited remotely?

    CVE-2022-49290 could potentially be exploited by attackers on local networks due to its nature affecting wireless mesh networking.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203