Vulnerability · Published Feb 26, 2025 · Assigned by Linux

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

High 7.8

In plain English

A high-severity double free in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 18% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.3%top 82.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux5.17.3-1DEBIAN-CVE-2022-49290
Debian:13linux5.17.3-1DEBIAN-CVE-2022-49290
Debian:14linux5.17.3-1DEBIAN-CVE-2022-49290
Ubuntu:22.04:LTSlinux5.15.0-37.39UBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-aws5.15.0-1011.14UBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-azure5.15.0-1010.12UBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-gcp5.15.0-1008.12UBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-gke5.15.0-1008.10UBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-ibm5.15.0-1007.8UBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1008.11UBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-kvm5.15.0-1010.11UBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-37.39UBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-oracle5.15.0-1009.12UBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-raspi5.15.0-1011.13UBUNTU-CVE-2022-49290
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2022-49290
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2022-49290

Affected products (as reported)

VendorProductVersions
Linux Linux 3212d6248faf0efce6b7a718e198feecce0eea05 – before 615716af8644813355e014314a0bc1e961250f5a86e7d4cd2ed5f4b0188afce8199faffcf1ae7c7e – before c1d9c3628ef0a0ca197595d0f9e01cd3b5dda18637bccfa89559a70c044b5ccde3c916a91388e14a – before 273ebddc5fda2967492cb0b6cdd7d81cfb821b763f15e3e62c80e180282f0cbc5559264e11c328b7 – before 3bbd0000d012f92aec423b224784fbf0f7bf40f86a01afcf8468d3ca2bd8bbb27503f60dcf643b20 – before 5d3ff9542a40ce034416bca03864709540a360166a01afcf8468d3ca2bd8bbb27503f60dcf643b20 – before 12e407a8ef17623823fd0c066fbd7f103953d28d6a01afcf8468d3ca2bd8bbb27503f60dcf643b20 – before 582d8c60c0c053684f7138875e8150d5749ffc176a01afcf8468d3ca2bd8bbb27503f60dcf643b20 – before 46bb87d40683337757a2f902fcd4244b32bb4e86
Linux Linux 5.8

Weakness: CWE-415 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References