[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061816-CVE-2022-49968-6e78@gregkh>
Date: Wed, 18 Jun 2025 13:00:33 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-49968: ieee802154/adf7242: defer destroy_workqueue call
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ieee802154/adf7242: defer destroy_workqueue call
There is a possible race condition (use-after-free) like below
(FREE) | (USE)
adf7242_remove | adf7242_channel
cancel_delayed_work_sync |
destroy_workqueue (1) | adf7242_cmd_rx
| mod_delayed_work (2)
|
The root cause for this race is that the upper layer (ieee802154) is
unaware of this detaching event and the function adf7242_channel can
be called without any checks.
To fix this, we can add a flag write at the beginning of adf7242_remove
and add flag check in adf7242_channel. Or we can just defer the
destructive operation like other commit 3e0588c291d6 ("hamradio: defer
ax25 kfree after unregister_netdev") which let the
ieee802154_unregister_hw() to handle the synchronization. This patch
takes the second option.
runs")
The Linux kernel CVE team has assigned CVE-2022-49968 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.18 with commit 58e9683d14752debc6f22daf6b23e031787df31f and fixed in 4.19.258 with commit dede80aaf01f4b6e8657d23726cb4a3da226ec4c
Issue introduced in 4.18 with commit 58e9683d14752debc6f22daf6b23e031787df31f and fixed in 5.4.213 with commit bed12d7531df1417fc92c691999ff95e03835008
Issue introduced in 4.18 with commit 58e9683d14752debc6f22daf6b23e031787df31f and fixed in 5.10.142 with commit 23a29932715ca43bceb2eae1bdb770995afe7271
Issue introduced in 4.18 with commit 58e9683d14752debc6f22daf6b23e031787df31f and fixed in 5.15.66 with commit 9f8558c5c642c62c450c98c99b7d18a709fff485
Issue introduced in 4.18 with commit 58e9683d14752debc6f22daf6b23e031787df31f and fixed in 5.19.8 with commit 15f3b89bd521d5770d36a61fc04a77c293138ba6
Issue introduced in 4.18 with commit 58e9683d14752debc6f22daf6b23e031787df31f and fixed in 6.0 with commit afe7116f6d3b888778ed6d95e3cf724767b9aedf
Issue introduced in 4.17.19 with commit a2363e2d88bf50022ee643c49ee5d4f7e8c915ea
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-49968
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/net/ieee802154/adf7242.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/dede80aaf01f4b6e8657d23726cb4a3da226ec4c
https://git.kernel.org/stable/c/bed12d7531df1417fc92c691999ff95e03835008
https://git.kernel.org/stable/c/23a29932715ca43bceb2eae1bdb770995afe7271
https://git.kernel.org/stable/c/9f8558c5c642c62c450c98c99b7d18a709fff485
https://git.kernel.org/stable/c/15f3b89bd521d5770d36a61fc04a77c293138ba6
https://git.kernel.org/stable/c/afe7116f6d3b888778ed6d95e3cf724767b9aedf
Powered by blists - more mailing lists