From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-97599: ieee802154: hwsim: serialize pib updates to fix double-free
Date: Fri, 25 Sep 2026 12:22:59 +0200 [thread overview]
Message-ID: <2026092500-CVE-2026-97599-a745@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ieee802154: hwsim: serialize pib updates to fix double-free
hwsim_update_pib() does an unserialized read-swap-free of phy->pib:
pib_old = rtnl_dereference(phy->pib);
...
rcu_assign_pointer(phy->pib, pib);
kfree_rcu(pib_old, rcu);
It assumes the RTNL is held, but ->set_channel is not always called
under it: the mac802154 scan worker changes channels via
drv_set_channel() without the RTNL. Such an update can race an
RTNL-held one on the same phy; both read the same pib_old and both
kfree_rcu() it, double-freeing the object. With SLUB percpu sheaves
batching kfree_rcu(), this surfaces as a KASAN invalid-free in
rcu_free_sheaf().
struct hwsim_phy has no lock for pib. Add one and make the swap atomic
with rcu_replace_pointer() under it, dropping the misleading
rtnl_dereference().
The Linux kernel CVE team has assigned CVE-2026-97599 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.19 with commit f25da51fdc381ca2863248c7060b3662632f0872 and fixed in 6.12.111 with commit 9973b3a67a7592a780ea12b08334539a900deec1
Issue introduced in 4.19 with commit f25da51fdc381ca2863248c7060b3662632f0872 and fixed in 6.18.53 with commit d3b8f264ce09573aededd0a97dc41c8147797d8f
Issue introduced in 4.19 with commit f25da51fdc381ca2863248c7060b3662632f0872 and fixed in 7.2.7 with commit db6442deecb1f13aeaf4f9d77746ea7555630fb3
Issue introduced in 4.19 with commit f25da51fdc381ca2863248c7060b3662632f0872 and fixed in 7.3-rc3 with commit 979d5b8de8ed4e1f997aef12da5694b99be7b871
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-97599
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/mac802154_hwsim.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/9973b3a67a7592a780ea12b08334539a900deec1
https://git.kernel.org/stable/c/d3b8f264ce09573aededd0a97dc41c8147797d8f
https://git.kernel.org/stable/c/db6442deecb1f13aeaf4f9d77746ea7555630fb3
https://git.kernel.org/stable/c/979d5b8de8ed4e1f997aef12da5694b99be7b871
reply other threads:[~2026-09-25 10:26 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=2026092500-CVE-2026-97599-a745@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.