From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-45868: pinctrl: single: fix refcount leak in pcs_add_gpio_func()
Date: Wed, 27 May 2026 14:18:30 +0200 [thread overview]
Message-ID: <2026052712-CVE-2026-45868-26cc@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: single: fix refcount leak in pcs_add_gpio_func()
of_parse_phandle_with_args() returns a device_node pointer with refcount
incremented in gpiospec.np. The loop iterates through all phandles but
never releases the reference, causing a refcount leak on each iteration.
Add of_node_put() calls to release the reference after extracting the
needed arguments and on the error path when devm_kzalloc() fails.
This bug was detected by our static analysis tool and verified by my
code review.
The Linux kernel CVE team has assigned CVE-2026-45868 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.10 with commit a1a277eb76b3507df7c41774048a644aa4dfd096 and fixed in 5.10.252 with commit 191bfd5710d6a7f48ba4315d8d3e908dcc15243c
Issue introduced in 3.10 with commit a1a277eb76b3507df7c41774048a644aa4dfd096 and fixed in 5.15.202 with commit 3e3b28bb0b6ddc521a4fdd1c1ba0d35017a0796b
Issue introduced in 3.10 with commit a1a277eb76b3507df7c41774048a644aa4dfd096 and fixed in 6.1.165 with commit 456a60d06c09a92680dc35fabca68024badcc28e
Issue introduced in 3.10 with commit a1a277eb76b3507df7c41774048a644aa4dfd096 and fixed in 6.6.128 with commit 99cc7352156c65201c675f750e0e77c4c73d93f5
Issue introduced in 3.10 with commit a1a277eb76b3507df7c41774048a644aa4dfd096 and fixed in 6.12.75 with commit 7814b1431848854b56717086e2b61bea3c59753d
Issue introduced in 3.10 with commit a1a277eb76b3507df7c41774048a644aa4dfd096 and fixed in 6.18.14 with commit e2e367e56bacb93ce5ac73f0b3297d5c83d38dd4
Issue introduced in 3.10 with commit a1a277eb76b3507df7c41774048a644aa4dfd096 and fixed in 6.19.4 with commit 5b9e84d27e310f22c4ba45fedbc4f5baf43dd823
Issue introduced in 3.10 with commit a1a277eb76b3507df7c41774048a644aa4dfd096 and fixed in 7.0 with commit 353353309b0f7afa407df29e455f9d15b5acc296
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-45868
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/pinctrl/pinctrl-single.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/191bfd5710d6a7f48ba4315d8d3e908dcc15243c
https://git.kernel.org/stable/c/3e3b28bb0b6ddc521a4fdd1c1ba0d35017a0796b
https://git.kernel.org/stable/c/456a60d06c09a92680dc35fabca68024badcc28e
https://git.kernel.org/stable/c/99cc7352156c65201c675f750e0e77c4c73d93f5
https://git.kernel.org/stable/c/7814b1431848854b56717086e2b61bea3c59753d
https://git.kernel.org/stable/c/e2e367e56bacb93ce5ac73f0b3297d5c83d38dd4
https://git.kernel.org/stable/c/5b9e84d27e310f22c4ba45fedbc4f5baf43dd823
https://git.kernel.org/stable/c/353353309b0f7afa407df29e455f9d15b5acc296
reply other threads:[~2026-05-27 12:20 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=2026052712-CVE-2026-45868-26cc@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.