From: Michal Simek <michal.simek@amd.com>
To: Dan Carpenter <dan.carpenter@linaro.org>,
Abhyuday Godhasara <abhyuday.godhasara@xilinx.com>
Cc: Michal Simek <michal.simek@xilinx.com>,
Rajan Vaja <rajan.vaja@xilinx.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tejas Patel <tejas.patel@xilinx.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] driver: soc: xilinx: use _safe loop iterator to avoid a use after free
Date: Fri, 12 May 2023 13:08:55 +0200 [thread overview]
Message-ID: <58711e80-8720-0a92-2e9e-5ae0a23368c3@amd.com> (raw)
In-Reply-To: <761e0e4a-4caf-4a71-8f47-1c6ad908a848@kili.mountain>
On 4/21/23 12:44, Dan Carpenter wrote:
> CAUTION: This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
>
>
> The hash_for_each_possible() loop dereferences "eve_data" to get the
> next item on the list. However the loop frees eve_data so it leads to
> a use after free. Use hash_for_each_possible_safe() instead.
>
> Fixes: c7fdb2404f66 ("drivers: soc: xilinx: add xilinx event management driver")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> Found by static analysis and not tested.
>
> drivers/soc/xilinx/xlnx_event_manager.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/soc/xilinx/xlnx_event_manager.c b/drivers/soc/xilinx/xlnx_event_manager.c
> index c76381899ef4..f9d9b82b562d 100644
> --- a/drivers/soc/xilinx/xlnx_event_manager.c
> +++ b/drivers/soc/xilinx/xlnx_event_manager.c
> @@ -192,11 +192,12 @@ static int xlnx_remove_cb_for_suspend(event_cb_func_t cb_fun)
> struct registered_event_data *eve_data;
> struct agent_cb *cb_pos;
> struct agent_cb *cb_next;
> + struct hlist_node *tmp;
>
> is_need_to_unregister = false;
>
> /* Check for existing entry in hash table for given cb_type */
> - hash_for_each_possible(reg_driver_map, eve_data, hentry, PM_INIT_SUSPEND_CB) {
> + hash_for_each_possible_safe(reg_driver_map, eve_data, tmp, hentry, PM_INIT_SUSPEND_CB) {
> if (eve_data->cb_type == PM_INIT_SUSPEND_CB) {
> /* Delete the list of callback */
> list_for_each_entry_safe(cb_pos, cb_next, &eve_data->cb_list_head, list) {
> @@ -228,11 +229,12 @@ static int xlnx_remove_cb_for_notify_event(const u32 node_id, const u32 event,
> u64 key = ((u64)node_id << 32U) | (u64)event;
> struct agent_cb *cb_pos;
> struct agent_cb *cb_next;
> + struct hlist_node *tmp;
>
> is_need_to_unregister = false;
>
> /* Check for existing entry in hash table for given key id */
> - hash_for_each_possible(reg_driver_map, eve_data, hentry, key) {
> + hash_for_each_possible_safe(reg_driver_map, eve_data, tmp, hentry, key) {
> if (eve_data->key == key) {
> /* Delete the list of callback */
> list_for_each_entry_safe(cb_pos, cb_next, &eve_data->cb_list_head, list) {
> --
> 2.39.2
>
Applied.
M
prev parent reply other threads:[~2023-05-12 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 10:44 Dan Carpenter
2023-05-12 11:08 ` Michal Simek [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=58711e80-8720-0a92-2e9e-5ae0a23368c3@amd.com \
--to=michal.simek@amd.com \
--cc=abhyuday.godhasara@xilinx.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=rajan.vaja@xilinx.com \
--cc=tejas.patel@xilinx.com \
/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
all inboxes | Powered by JetHome®