cbcvebase.
CVE-2022-49290
published 2025-02-26

CVE-2022-49290: In the Linux kernel, the following vulnerability has been resolved: mac80211: fix potential double free on mesh join While commit 6a01afcf8468 ("mac80211…

PriorityP340high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.24%
15.5th percentile
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

32 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 5.17.3-1 (bookworm)linux 5.17.3-1 (bookworm)
linuxlinux——
linuxlinux——
linuxlinux——
linuxlinux>= 3212d6248faf0efce6b7a718e198feecce0eea05 < 615716af8644813355e014314a0bc1e961250f5a615716af8644813355e014314a0bc1e961250f5a
linuxlinux>= 37bccfa89559a70c044b5ccde3c916a91388e14a < 273ebddc5fda2967492cb0b6cdd7d81cfb821b76273ebddc5fda2967492cb0b6cdd7d81cfb821b76
linuxlinux>= 3f15e3e62c80e180282f0cbc5559264e11c328b7 < 3bbd0000d012f92aec423b224784fbf0f7bf40f83bbd0000d012f92aec423b224784fbf0f7bf40f8
linuxlinux>= 4.14.192 < 4.14.2744.14.274
linuxlinux>= 4.19.137 < 4.19.2374.19.237
linuxlinux>= 4.4.233 < 4.54.5
linuxlinux>= 4.9.233 < 4.9.3094.9.309
linuxlinux>= 5.4.56 < 5.4.1885.4.188
linuxlinux>= 5.7.13 < 5.85.8
linuxlinux>= 6a01afcf8468d3ca2bd8bbb27503f60dcf643b20 < 5d3ff9542a40ce034416bca03864709540a360165d3ff9542a40ce034416bca03864709540a36016
linuxlinux>= 6a01afcf8468d3ca2bd8bbb27503f60dcf643b20 < 12e407a8ef17623823fd0c066fbd7f103953d28d12e407a8ef17623823fd0c066fbd7f103953d28d
linuxlinux>= 6a01afcf8468d3ca2bd8bbb27503f60dcf643b20 < 582d8c60c0c053684f7138875e8150d5749ffc17582d8c60c0c053684f7138875e8150d5749ffc17
linuxlinux>= 6a01afcf8468d3ca2bd8bbb27503f60dcf643b20 < 46bb87d40683337757a2f902fcd4244b32bb4e8646bb87d40683337757a2f902fcd4244b32bb4e86
linuxlinux>= 6a01afcf8468d3ca2bd8bbb27503f60dcf643b20 < 4a2d4496e15ea5bb5c8e83b94ca8ca7fb045e7d34a2d4496e15ea5bb5c8e83b94ca8ca7fb045e7d3
linuxlinux>= 86e7d4cd2ed5f4b0188afce8199faffcf1ae7c7e < c1d9c3628ef0a0ca197595d0f9e01cd3b5dda186c1d9c3628ef0a0ca197595d0f9e01cd3b5dda186
linuxlinux_kernel>= 0 < 5.10.113-15.10.113-1
linuxlinux_kernel>= 0 < 5.17.3-15.17.3-1
linuxlinux_kernel>= 0 < 5.17.3-15.17.3-1
linuxlinux_kernel>= 0 < 5.17.3-15.17.3-1
linuxlinux_kernel>= 4.14.192 < 4.14.2744.14.274
linuxlinux_kernel>= 4.19.137 < 4.19.2374.19.237

CVSS provenance

nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.