mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Zheng Wang <zyytlz.wz@163.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<pabeni@redhat.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <hackerzheng666@gmail.com>,
	<1395428693sheep@gmail.com>, <alex000young@gmail.com>
Subject: Re: [PATCH net] net: ravb: Fix possible UAF bug in ravb_remove
Date: Thu, 9 Mar 2023 18:47:27 +0300	[thread overview]
Message-ID: <9054b170-8ed2-445c-6150-82f98af5808b@omp.ru> (raw)
In-Reply-To: <20230309100248.3831498-1-zyytlz.wz@163.com>

Hello!

On 3/9/23 1:02 PM, Zheng Wang wrote:

> In ravb_probe, priv->work was bound with ravb_tx_timeout_work.
> If timeout occurs, it will start the work. And if we call
> ravb_remove without finishing the work, ther may be a use
> after free bug on ndev.

   Have you actually encountered it?

> Fix it by finishing the job before cleanup in ravb_remove.
> 
> Fixes: c156633f1353 ("Renesas Ethernet AVB driver proper")

   Hm... sorry about that. :-)

> Signed-off-by: Zheng Wang <zyytlz.wz@163.com>

Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru>

[...]
> diff --git a/drivers/net/ethernet/renesas/ravb_main.c b/drivers/net/ethernet/renesas/ravb_main.c
> index 0f54849a3823..07a08e72f440 100644
> --- a/drivers/net/ethernet/renesas/ravb_main.c
> +++ b/drivers/net/ethernet/renesas/ravb_main.c
> @@ -2892,6 +2892,7 @@ static int ravb_remove(struct platform_device *pdev)
>  	struct ravb_private *priv = netdev_priv(ndev);
>  	const struct ravb_hw_info *info = priv->info;
>  
> +	cancel_work_sync(&priv->work);

   I think we need an empty line here...

>  	/* Stop PTP Clock driver */
>  	if (info->ccc_gac)
>  		ravb_ptp_stop(ndev);

MBR, Sergey

  reply	other threads:[~2023-03-09 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 10:02 Zheng Wang
2023-03-09 15:47 ` Sergey Shtylyov [this message]
2023-03-10 16:33   ` Zheng Hacker
2023-03-10  1:12 ` Yunsheng Lin
2023-03-10 16:38   ` Zheng Hacker
2023-09-02 14:34     ` Salvatore Bonaccorso
2023-09-03 17:11       ` Sergei Shtylyov
2023-09-03 17:13         ` Sergei Shtylyov

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=9054b170-8ed2-445c-6150-82f98af5808b@omp.ru \
    --to=s.shtylyov@omp.ru \
    --cc=1395428693sheep@gmail.com \
    --cc=alex000young@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hackerzheng666@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=zyytlz.wz@163.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®