From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Chenyuan Yang <chenyuan0y@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, u.kleine-koenig@baylibre.com,
paul@crapouillou.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, zijie98@gmail.com
Subject: Re: [PATCH] net: davicom: fix UAF in dm9000_drv_remove
Date: Tue, 21 Jan 2025 07:36:47 +0100 [thread overview]
Message-ID: <Z49Af0yc6gbsyIyW@mev-dev.igk.intel.com> (raw)
In-Reply-To: <20250120222557.833100-1-chenyuan0y@gmail.com>
On Mon, Jan 20, 2025 at 04:25:57PM -0600, Chenyuan Yang wrote:
> dm is netdev private data and it cannot be
> used after free_netdev() call. Using adpt after free_netdev()
> can cause UAF bug. Fix it by moving free_netdev() at the end of the
> function.
>
> This is similar to the issue fixed in commit
> ad297cd2db8953e2202970e9504cab247b6c7cb4 ("net: qcom/emac: fix UAF in emac_remove").
>
> Fixes: cf9e60aa69ae ("net: davicom: Fix regulator not turned off on driver removal")
> Signed-off-by: Chenyuan Yang <chenyuan0y@gmail.com>
> ---
> drivers/net/ethernet/davicom/dm9000.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/davicom/dm9000.c b/drivers/net/ethernet/davicom/dm9000.c
> index 8735e333034c..b87eaf0c250c 100644
> --- a/drivers/net/ethernet/davicom/dm9000.c
> +++ b/drivers/net/ethernet/davicom/dm9000.c
> @@ -1777,10 +1777,11 @@ static void dm9000_drv_remove(struct platform_device *pdev)
>
> unregister_netdev(ndev);
> dm9000_release_board(pdev, dm);
> - free_netdev(ndev); /* free device structure */
> if (dm->power_supply)
> regulator_disable(dm->power_supply);
>
> + free_netdev(ndev); /* free device structure */
> +
> dev_dbg(&pdev->dev, "released and freed device\n");
> }
Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
>
> --
> 2.34.1
next prev parent reply other threads:[~2025-01-21 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 22:25 Chenyuan Yang
2025-01-21 6:36 ` Michal Swiatkowski [this message]
2025-01-21 7:33 ` Uwe Kleine-König
2025-01-21 20:04 ` Chenyuan Yang
2025-01-23 9:56 ` Paolo Abeni
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=Z49Af0yc6gbsyIyW@mev-dev.igk.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=chenyuan0y@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@crapouillou.net \
--cc=u.kleine-koenig@baylibre.com \
--cc=zijie98@gmail.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®