From: Jason Wang <jasowang@redhat.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
mst@redhat.com, jasowang@redhat.com
Cc: davem@davemloft.net, kuba@kernel.org, erwan.yvin@stericsson.com
Subject: [PATCH 3/3] caif_virtio: fix the race between reset and netdev unregister
Date: Mon, 20 Jun 2022 13:11:15 +0800 [thread overview]
Message-ID: <20220620051115.3142-4-jasowang@redhat.com> (raw)
In-Reply-To: <20220620051115.3142-1-jasowang@redhat.com>
We use to do the following steps during .remove():
static void cfv_remove(struct virtio_device *vdev)
{
struct cfv_info *cfv = vdev->priv;
rtnl_lock();
dev_close(cfv->ndev);
rtnl_unlock();
tasklet_kill(&cfv->tx_release_tasklet);
debugfs_remove_recursive(cfv->debugfs);
vringh_kiov_cleanup(&cfv->ctx.riov);
virtio_reset_device(vdev);
vdev->vringh_config->del_vrhs(cfv->vdev);
cfv->vr_rx = NULL;
vdev->config->del_vqs(cfv->vdev);
unregister_netdev(cfv->ndev);
}
This is racy since device could be re-opened after dev_close() but
before unregister_netdevice():
1) RX vringh is cleaned before resetting the device, rx callbacks that
is called after the vringh_kiov_cleanup() will result a UAF
2) Network stack can still try to use TX virtqueue even if it has been
deleted after dev_vqs()
Fixing this by unregistering the network device first to make sure not
device access from both TX and RX side.
Fixes: 0d2e1a2926b18 ("caif_virtio: Introduce caif over virtio")
Signed-off-by: Jason Wang <jasowang@redhat.com>
---
drivers/net/caif/caif_virtio.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/net/caif/caif_virtio.c b/drivers/net/caif/caif_virtio.c
index 66375bea2fcd..a29f9b2df5b1 100644
--- a/drivers/net/caif/caif_virtio.c
+++ b/drivers/net/caif/caif_virtio.c
@@ -752,9 +752,8 @@ static void cfv_remove(struct virtio_device *vdev)
{
struct cfv_info *cfv = vdev->priv;
- rtnl_lock();
- dev_close(cfv->ndev);
- rtnl_unlock();
+ /* Make sure NAPI/TX won't try to access the device */
+ unregister_netdev(cfv->ndev);
tasklet_kill(&cfv->tx_release_tasklet);
debugfs_remove_recursive(cfv->debugfs);
@@ -764,7 +763,6 @@ static void cfv_remove(struct virtio_device *vdev)
vdev->vringh_config->del_vrhs(cfv->vdev);
cfv->vr_rx = NULL;
vdev->config->del_vqs(cfv->vdev);
- unregister_netdev(cfv->ndev);
}
static struct virtio_device_id id_table[] = {
--
2.25.1
next prev parent reply other threads:[~2022-06-20 5:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 5:11 [PATCH 0/3] Fixing races in probe/remove Jason Wang
2022-06-20 5:11 ` [PATCH 1/3] caif_virtio: remove virtqueue_disable_cb() in probe Jason Wang
2022-06-20 9:02 ` Michael S. Tsirkin
2022-06-21 3:10 ` Jason Wang
2022-06-20 5:11 ` [PATCH 2/3] caif_virtio: fix the race between virtio_device_ready() and ndo_open() Jason Wang
2022-06-20 9:04 ` Michael S. Tsirkin
2022-06-20 5:11 ` Jason Wang [this message]
2022-06-20 9:09 ` [PATCH 3/3] caif_virtio: fix the race between reset and netdev unregister Michael S. Tsirkin
2022-06-20 9:18 ` Jason Wang
2022-06-20 10:18 ` Michael S. Tsirkin
2022-06-21 3:09 ` Jason Wang
2022-06-21 6:00 ` Michael S. Tsirkin
2022-06-21 6:25 ` Jason Wang
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=20220620051115.3142-4-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=davem@davemloft.net \
--cc=erwan.yvin@stericsson.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).