From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-97600: ieee802154: cc2520: fix FIFOP work use-after-free
Date: Fri, 25 Sep 2026 12:23:00 +0200 [thread overview]
Message-ID: <2026092500-CVE-2026-97600-3585@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ieee802154: cc2520: fix FIFOP work use-after-free
The FIFOP interrupt handler queues cc2520_fifop_irqwork. On removal,
cc2520_remove() only flushes the work. The devm-managed FIFOP IRQ
remains active until after ->remove() returns and can queue the work
again after that flush, allowing it to run after the private data is
released.
Disable the work with disable_work_sync() instead of flushing it, so
the handler can no longer queue it once removal begins. Destroy the
buffer mutex last, since the worker and the stop callback invoked
through ieee802154_unregister_hw() both take it.
Found by an in-house static analysis tool.
The Linux kernel CVE team has assigned CVE-2026-97600 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.17 with commit 0da6bc8cc3417a5e452efb886ff2c61e72b743d6 and fixed in 6.12.111 with commit 56a9919d8494fb118eebf167bef0622528fbf2e7
Issue introduced in 3.17 with commit 0da6bc8cc3417a5e452efb886ff2c61e72b743d6 and fixed in 6.18.53 with commit c68fd52c73b676aee67020011e98fea125a978f4
Issue introduced in 3.17 with commit 0da6bc8cc3417a5e452efb886ff2c61e72b743d6 and fixed in 7.2.7 with commit 890a80d516a1447db5c21bf92841a82914ea897d
Issue introduced in 3.17 with commit 0da6bc8cc3417a5e452efb886ff2c61e72b743d6 and fixed in 7.3-rc3 with commit ff5891b266a7fc6a062710836be84f1cc19338b5
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-97600
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/cc2520.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/56a9919d8494fb118eebf167bef0622528fbf2e7
https://git.kernel.org/stable/c/c68fd52c73b676aee67020011e98fea125a978f4
https://git.kernel.org/stable/c/890a80d516a1447db5c21bf92841a82914ea897d
https://git.kernel.org/stable/c/ff5891b266a7fc6a062710836be84f1cc19338b5
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-97600-3585@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.