From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Kaixin Wang <kxwang23@m.fudan.edu.cn>
Cc: <wtdeng24@m.fudan.edu.cn>, <21210240012@m.fudan.edu.cn>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<edumazet@google.com>, <kuba@kernel.org>, <davem@davemloft.net>
Subject: Re: [PATCH] net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition
Date: Wed, 11 Sep 2024 11:29:44 +0200 [thread overview]
Message-ID: <26614b92-4d24-4aff-8fc3-25aa8ed83cb6@intel.com> (raw)
In-Reply-To: <20240909175821.2047-1-kxwang23@m.fudan.edu.cn>
On 9/9/24 19:58, Kaixin Wang wrote:
> In the ether3_probe function, a timer is initialized with a callback
> function ether3_ledoff, bound to &prev(dev)->timer. Once the timer is
> started, there is a risk of a race condition if the module or device
> is removed, triggering the ether3_remove function to perform cleanup.
> The sequence of operations that may lead to a UAF bug is as follows:
>
> CPU0 CPU1
>
> | ether3_ledoff
> ether3_remove |
> free_netdev(dev); |
> put_devic |
> kfree(dev); |
> | ether3_outw(priv(dev)->regs.config2 |= CFG2_CTRLO, REG_CONFIG2);
> | // use dev
>
> Fix it by ensuring that the timer is canceled before proceeding with
> the cleanup in ether3_remove.
this code change indeed prevents UAF bug
but as is, the CFG2_CTRLO flag of REG_CONFIG2 will be left in state "ON"
it would be better to first turn the LED off unconditionally
>
> Signed-off-by: Kaixin Wang <kxwang23@m.fudan.edu.cn>
> ---
> drivers/net/ethernet/seeq/ether3.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ethernet/seeq/ether3.c b/drivers/net/ethernet/seeq/ether3.c
> index c672f92d65e9..f9d27c9d6808 100644
> --- a/drivers/net/ethernet/seeq/ether3.c
> +++ b/drivers/net/ethernet/seeq/ether3.c
> @@ -850,6 +850,7 @@ static void ether3_remove(struct expansion_card *ec)
> ecard_set_drvdata(ec, NULL);
>
> unregister_netdev(dev);
> + del_timer_sync(&priv(dev)->timer);
> free_netdev(dev);
> ecard_release_resources(ec);
> }
next prev parent reply other threads:[~2024-09-11 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 17:58 [PATCH] net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition Kaixin Wang
2024-09-11 9:29 ` Przemek Kitszel [this message]
2024-09-12 16:46 ` Kaixin Wang
2024-09-13 11:37 ` Simon Horman
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=26614b92-4d24-4aff-8fc3-25aa8ed83cb6@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=21210240012@m.fudan.edu.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kxwang23@m.fudan.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wtdeng24@m.fudan.edu.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