From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ziyang Xuan <william.xuanziyang@huawei.com>,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org
Cc: edumazet@google.com, brianvv@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/3] net: ipvlan: fix potential UAF problem for phy_dev
Date: Tue, 22 Mar 2022 07:03:59 -0700 [thread overview]
Message-ID: <92e86620-3457-6ca1-6888-fdbcdf0a4e4e@gmail.com> (raw)
In-Reply-To: <abef9f7ad2c6e6b8ae053225766d34f3fc930ddf.1647664114.git.william.xuanziyang@huawei.com>
On 3/19/22 02:52, Ziyang Xuan wrote:
> There is a known scenario can trigger UAF problem for lower
> netdevice as following:
But this known scenario never happens.
So maybe you should not add it 'in the future'
>
> Someone module puts the NETDEV_UNREGISTER event handler to a
> work, and lower netdevice is accessed in the work handler. But
> when the work is excuted, lower netdevice has been destroyed
> because upper netdevice did not get reference to lower netdevice
> correctly.
Again, whoever would like to use a work queue would also
need to hold a reference on the device.
Regardless of ipvlan being used or not.
>
> Although it can not happen for ipvlan now because there is no
> way to access phy_dev outside ipvlan. But it is necessary to
> add the reference operation to phy_dev to avoid the potential
> UAF problem in the future.
>
> Signed-off-by: Ziyang Xuan <william.xuanziyang@huawei.com>
> ---
Your patch makes no sense to me really.
next prev parent reply other threads:[~2022-03-22 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 9:52 [PATCH net-next v3 0/3] " Ziyang Xuan
2022-03-19 9:52 ` [PATCH net-next v3 1/3] " Ziyang Xuan
2022-03-22 14:03 ` Eric Dumazet [this message]
2022-03-19 9:53 ` [PATCH net-next v3 2/3] net: ipvlan: add net device refcount tracker Ziyang Xuan
2022-03-22 14:01 ` Eric Dumazet
2022-03-19 9:53 ` [PATCH net-next v3 3/3] net: ipvtap: fix error comments Ziyang Xuan
2022-03-22 9:15 ` [PATCH net-next v3 0/3] net: ipvlan: fix potential UAF problem for phy_dev 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=92e86620-3457-6ca1-6888-fdbcdf0a4e4e@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=brianvv@google.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=william.xuanziyang@huawei.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®