From: Srinivas Kandagatla <srini@kernel.org>
To: Haotian Zhang <vulab@iscas.ac.cn>, srini@kernel.org
Cc: linkmauve@linkmauve.fr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmem: nintendo-otp: Fix potential NULL pointer dereference in nintendo_otp_probe()
Date: Mon, 5 Jan 2026 07:59:13 +0000 [thread overview]
Message-ID: <f23a8d2c-7bfc-4a07-9f18-45c9c3b18834@kernel.org> (raw)
In-Reply-To: <20251210033803.1720-1-vulab@iscas.ac.cn>
On 12/10/25 3:38 AM, Haotian Zhang wrote:
> of_match_device() may return NULL if no match is found.
> Dereferencing the return value of_id in nintendo_otp_probe()
This does not make sense, nintendo_otp_probe() will never be called
without a dt compatible match.
Why do you think this will be null?
--srini
> without a check could lead to a NULL pointer dereference.
>
> Add a check for of_id and return -ENODEV upon failure.
>
> Fixes: 3683b761fe3a ("nvmem: nintendo-otp: Add new driver for the Wii and Wii U OTP")
> Signed-off-by: Haotian Zhang <vulab@iscas.ac.cn>
> ---
> drivers/nvmem/nintendo-otp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/nvmem/nintendo-otp.c b/drivers/nvmem/nintendo-otp.c
> index 355e7f1fc6d5..89b15a58bf88 100644
> --- a/drivers/nvmem/nintendo-otp.c
> +++ b/drivers/nvmem/nintendo-otp.c
> @@ -87,6 +87,9 @@ static int nintendo_otp_probe(struct platform_device *pdev)
> .root_only = true,
> };
>
> + if (!of_id)
> + return -ENODEV;
> +
> priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
> if (!priv)
> return -ENOMEM;
prev parent reply other threads:[~2026-01-05 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 3:38 [PATCH] nvmem: nintendo-otp: Fix potential NULL pointer dereference in nintendo_otp_probe() Haotian Zhang
2025-12-11 13:37 ` Link Mauve
2026-01-05 7:59 ` Srinivas Kandagatla [this message]
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=f23a8d2c-7bfc-4a07-9f18-45c9c3b18834@kernel.org \
--to=srini@kernel.org \
--cc=linkmauve@linkmauve.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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