From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64023: gpio: aggregator: fix a potential use-after-free
Date: Sun, 19 Jul 2026 17:38:05 +0200 [thread overview]
Message-ID: <2026071902-CVE-2026-64023-8096@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
gpio: aggregator: fix a potential use-after-free
On error we free aggr->lookups->dev_id before removing the entry from
the lookup table. If a concurrent thread calls gpiod_find() before we
remove the entry, it could iterate over the list and call
gpiod_match_lookup_table() which unconditionally dereferences dev_id
when calling strcmp(). Reverse the order of cleanup.
The Linux kernel CVE team has assigned CVE-2026-64023 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit 86f162e73d2d81ef6d819c06a3b6c2fda77a79b8 and fixed in 6.18.34 with commit ea28b286649b70618e9dd3e895812417a7712a11
Issue introduced in 6.16 with commit 86f162e73d2d81ef6d819c06a3b6c2fda77a79b8 and fixed in 7.0.11 with commit 7ac4183a41ba048af89eddd82fe8be64619d0871
Issue introduced in 6.16 with commit 86f162e73d2d81ef6d819c06a3b6c2fda77a79b8 and fixed in 7.1 with commit 30c073cab97afb31901f94de9605177b6b84367e
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-64023
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/gpio/gpio-aggregator.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/ea28b286649b70618e9dd3e895812417a7712a11
https://git.kernel.org/stable/c/7ac4183a41ba048af89eddd82fe8be64619d0871
https://git.kernel.org/stable/c/30c073cab97afb31901f94de9605177b6b84367e
reply other threads:[~2026-07-19 15:41 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=2026071902-CVE-2026-64023-8096@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox