From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46269: pinctrl: canaan: k230: Fix NULL pointer dereference when parsing devicetree
Date: Wed, 3 Jun 2026 17:49:58 +0200 [thread overview]
Message-ID: <2026060338-CVE-2026-46269-3ec0@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: canaan: k230: Fix NULL pointer dereference when parsing devicetree
When probing the k230 pinctrl driver, the kernel triggers a NULL pointer
dereference. The crash trace showed:
[ 0.732084] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000068
[ 0.740737] ...
[ 0.776296] epc : k230_pinctrl_probe+0x1be/0x4fc
In k230_pinctrl_parse_functions(), we attempt to retrieve the device
pointer via info->pctl_dev->dev, but info->pctl_dev is only initialized
after k230_pinctrl_parse_dt() completes.
At the time of DT parsing, info->pctl_dev is still NULL, leading to
the invalid dereference of info->pctl_dev->dev.
Use the already available device pointer from platform_device
instead of accessing through uninitialized pctl_dev.
The Linux kernel CVE team has assigned CVE-2026-46269 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.17 with commit d94a32ac688f953dc9a9f12b5b4139ecad841bbb and fixed in 6.18.14 with commit 3c7d637bfc3dfbd6471c68bd767f7eb8b5b09eba
Issue introduced in 6.17 with commit d94a32ac688f953dc9a9f12b5b4139ecad841bbb and fixed in 6.19.4 with commit 1d0d361f4dbc2bb2003594f84e4b101fc6b508c0
Issue introduced in 6.17 with commit d94a32ac688f953dc9a9f12b5b4139ecad841bbb and fixed in 7.0 with commit d8c128fb6c2277d95f3f6a4ce28b82c8370031f6
Issue introduced in 6.15.10 with commit 02c1deb1bff2b6d242e29a51e56107495979a2b8
Issue introduced in 6.16.1 with commit 0ec03251d01494ef207089b5bd626becfd05fd86
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-46269
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-k230.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/3c7d637bfc3dfbd6471c68bd767f7eb8b5b09eba
https://git.kernel.org/stable/c/1d0d361f4dbc2bb2003594f84e4b101fc6b508c0
https://git.kernel.org/stable/c/d8c128fb6c2277d95f3f6a4ce28b82c8370031f6
reply other threads:[~2026-06-03 15:51 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=2026060338-CVE-2026-46269-3ec0@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