From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72024: mac802154: remove interfaces with RCU list deletion
Date: Sat, 15 Aug 2026 15:01:43 +0900 [thread overview]
Message-ID: <2026081510-CVE-2026-72024-7fde@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mac802154: remove interfaces with RCU list deletion
Queue wake, stop, and disable paths walk local->interfaces under RCU.
The bulk hardware teardown path removes entries with list_del(), so an
asynchronous transmit completion can follow a poisoned list node in
ieee802154_wake_queue().
Use list_del_rcu() as in the single-interface removal path. The following
unregister_netdevice() waits for in-flight RCU readers before freeing the
netdevice, so no separate grace-period wait is needed.
The Linux kernel CVE team has assigned CVE-2026-72024 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.19 with commit 592dfbfc72f5352437c883aa11ab579d10cdb595 and fixed in 5.10.261 with commit 72ac5af9ad09662bd0ea91cb8845d490c8ef9c01
Issue introduced in 3.19 with commit 592dfbfc72f5352437c883aa11ab579d10cdb595 and fixed in 5.15.212 with commit 2039f27b1a0c997137a5de7f8a3cee0e80fbf952
Issue introduced in 3.19 with commit 592dfbfc72f5352437c883aa11ab579d10cdb595 and fixed in 6.1.178 with commit 4bf231f459b542414629b64f63d5cad6701bd07c
Issue introduced in 3.19 with commit 592dfbfc72f5352437c883aa11ab579d10cdb595 and fixed in 6.6.145 with commit b91e5248dd7af09b500879a46d22a36b60db3a57
Issue introduced in 3.19 with commit 592dfbfc72f5352437c883aa11ab579d10cdb595 and fixed in 6.12.97 with commit c7c031b75218b3ba3014a0f6b9849888994528d6
Issue introduced in 3.19 with commit 592dfbfc72f5352437c883aa11ab579d10cdb595 and fixed in 6.18.40 with commit 77caf2d6eba7cb94a7ecd7b369a5974fd7d7c054
Issue introduced in 3.19 with commit 592dfbfc72f5352437c883aa11ab579d10cdb595 and fixed in 7.1.5 with commit d8b5b66388a51febe4b8505b0ecd9da15b4ba639
Issue introduced in 3.19 with commit 592dfbfc72f5352437c883aa11ab579d10cdb595 and fixed in 7.2-rc3 with commit 539dfcf69105d8d3d4d677b71de6e5ede2e6dfa0
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-2026-72024
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:
net/mac802154/iface.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/72ac5af9ad09662bd0ea91cb8845d490c8ef9c01
https://git.kernel.org/stable/c/2039f27b1a0c997137a5de7f8a3cee0e80fbf952
https://git.kernel.org/stable/c/4bf231f459b542414629b64f63d5cad6701bd07c
https://git.kernel.org/stable/c/b91e5248dd7af09b500879a46d22a36b60db3a57
https://git.kernel.org/stable/c/c7c031b75218b3ba3014a0f6b9849888994528d6
https://git.kernel.org/stable/c/77caf2d6eba7cb94a7ecd7b369a5974fd7d7c054
https://git.kernel.org/stable/c/d8b5b66388a51febe4b8505b0ecd9da15b4ba639
https://git.kernel.org/stable/c/539dfcf69105d8d3d4d677b71de6e5ede2e6dfa0
reply other threads:[~2026-08-15 6:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081510-CVE-2026-72024-7fde@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.