From: Philipp Zabel <p.zabel@pengutronix.de>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] reset: Fix potential use-after-free in __of_reset_control_get()
Date: Mon, 08 Oct 2018 14:56:15 +0200 [thread overview]
Message-ID: <1539003375.11512.19.camel@pengutronix.de> (raw)
In-Reply-To: <20181008111435.25994-1-geert+renesas@glider.be>
Hi Geert,
On Mon, 2018-10-08 at 13:14 +0200, Geert Uytterhoeven wrote:
> Calling of_node_put() decreases the reference count of a device tree
> object, and may free some data.
>
> However, the of_phandle_args structure embedding it is passed to
> reset_controller_dev.of_xlate() after that, so it may still be accessed.
>
> Move the call to of_node_put() down to fix this.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/reset/core.c | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/reset/core.c b/drivers/reset/core.c
> index 225e34c56b94a2e3..bc9df10d31b4bae1 100644
> --- a/drivers/reset/core.c
> +++ b/drivers/reset/core.c
> @@ -496,27 +496,28 @@ struct reset_control *__of_reset_control_get(struct device_node *node,
> break;
> }
> }
> - of_node_put(args.np);
>
> if (!rcdev) {
> - mutex_unlock(&reset_list_mutex);
> - return ERR_PTR(-EPROBE_DEFER);
> + rstc = ERR_PTR(-EPROBE_DEFER);
> + goto out;
> }
>
> if (WARN_ON(args.args_count != rcdev->of_reset_n_cells)) {
> - mutex_unlock(&reset_list_mutex);
> - return ERR_PTR(-EINVAL);
> + rstc = ERR_PTR(-EINVAL);
> + goto out;
> }
>
> rstc_id = rcdev->of_xlate(rcdev, &args);
> if (rstc_id < 0) {
> - mutex_unlock(&reset_list_mutex);
> - return ERR_PTR(rstc_id);
> + rstc = ERR_PTR(rstc_id);
> + goto out;
> }
>
> /* reset_list_mutex also protects the rcdev's reset_control list */
> rstc = __reset_control_get_internal(rcdev, rstc_id, shared);
>
> +out:
> + of_node_put(args.np);
> mutex_unlock(&reset_list_mutex);
Thank you for the patch. I'd like to move of_node_put after mutex_unlock
for symmetry. If you agree, I can switch the two when applying.
regards
Philipp
next prev parent reply other threads:[~2018-10-08 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 11:14 [PATCH] reset: Fix potential use-after-free in __of_reset_control_get() Geert Uytterhoeven
2018-10-08 12:56 ` Philipp Zabel [this message]
2018-10-08 13:12 ` Geert Uytterhoeven
2018-10-08 13:28 ` Philipp Zabel
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=1539003375.11512.19.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--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;
as well as URLs for NNTP newsgroup(s).