From: Stefano Garzarella <sgarzare@redhat.com>
To: netdev@vger.kernel.org
Cc: Eric Dumazet <edumazet@google.com>,
linux-kernel@vger.kernel.org,
Bobby Eshleman <bobbyeshleman@meta.com>,
Jakub Kicinski <kuba@kernel.org>,
Stefano Garzarella <sgarzare@redhat.com>,
virtualization@lists.linux.dev, Paolo Abeni <pabeni@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Simon Horman <horms@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: [PATCH net 0/2] vsock: fix child netns mode initialization and restriction
Date: Thu, 12 Feb 2026 21:59:14 +0100 [thread overview]
Message-ID: <20260212205916.97533-1-sgarzare@redhat.com> (raw)
This series fixes two issues in the vsock network namespace support
recently introduced by commit eafb64f40ca4 ("vsock: add netns to vsock
core").
Patch 1 fixes `child_ns_mode` being always hardcoded to "global" for new
namespaces, breaking propagation of the "local" mode through nested
namespaces.
Patch 2 prevents a "local" namespace from switching `child_ns_mode` to
"global", which would allow nested namespaces to escape vsock isolation
and access global CIDs.
Stefano Garzarella (2):
vsock: fix child netns mode initialization
vsock: prevent child netns mode switch from local to global
net/vmw_vsock/af_vsock.c | 20 +++++++++++++++-----
1 file changed, 15 insertions(+), 5 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-12 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 20:59 Stefano Garzarella [this message]
2026-02-12 20:59 ` [PATCH net 1/2] vsock: fix child netns mode initialization Stefano Garzarella
2026-02-13 1:14 ` Bobby Eshleman
2026-02-12 20:59 ` [PATCH net 2/2] vsock: prevent child netns mode switch from local to global Stefano Garzarella
2026-02-13 1:19 ` Bobby Eshleman
2026-02-13 20:40 ` [PATCH net 0/2] vsock: fix child netns mode initialization and restriction patchwork-bot+netdevbpf
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=20260212205916.97533-1-sgarzare@redhat.com \
--to=sgarzare@redhat.com \
--cc=bobbyeshleman@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
/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