From: Chris Arges <carges@cloudflare.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org,
"Willem de Bruijn" <willemdebruijn.kernel@gmail.com>,
"Björn Töpel" <bjorn@kernel.org>, "Phil Sutter" <phil@nwl.cc>,
"Jason Wang" <jasowangio@gmail.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
netdev@vger.kernel.org, virtualization@lists.linux.dev,
"Max Krasnyansky" <maxk@qualcomm.com>,
"Rusty Russell" <rusty@rustcorp.com.au>
Subject: Re: [PATCH net v3 0/8] more virtio-net csum hardening
Date: Mon, 19 Oct 2026 11:51:46 -0500 [thread overview]
Message-ID: <atZKogiEAkStdgQ2@20HS2G4> (raw)
In-Reply-To: <cover.1792411304.git.mst@redhat.com>
On 2026-10-19 08:03:00, Michael S. Tsirkin wrote:
>
> As reported first by Paulos Yibelo <habte.yibelo@gmail.com> (after which
> others, credited below, found more ways the bug can affect users):
>
> allowing untrusted hardware to specify csum start/offset for
> CHECKSUM_PARTIAL was not a good idea, because, if it edits the packet
> outside the actual checksum, and depending on the setup, the networking
> stack could be looking at the packet both before and after the edit, and
> seeing different results.
>
> Previously, commit 6785011f8b16 ("ipv4: validate checksum_start before
> completing checksum") validated all known instances where this
> causes the most grief, but the real fix is to make sure
> that either only actual checksum fields are ever edited,
> or the checksum is completed before the net stack looks at it,
> so it is always consistent.
>
>
> This basically goes back to
> what we did before f43798c27684 ("tun: Allow GSO using virtio_net_hdr"),
> except in a narrow list of specified known good cases.
>
>
> Summary of the patchset:
>
> These are definitely net material (and seem to be too big for stable,
> or I would recommend backporting there, too):
>
> net: account for ingress-resolved virtio net hdr state
> - accounting, not the fix itself, dependency of the next one
> net: resolve uncommon partial checksums at ingress
> - fix itself
> net: add a sysctl to opt out of virtio net hdr checksum validation
> - reducing risk of the fix by adding a sysctl to disable it
>
> These are cleanups, can be deferred to net-next, too:
>
> net: add ip4_parse()
> virtio_net: cleanup protocol calculation
> - cleanup resulting code duplication
> (kept separate to simplify backporting)
>
> Fixes: f43798c27684 ("tun: Allow GSO using virtio_net_hdr")
>
> Changes since v1:
> - reorder patches to fix bisectability, addressing
> a comment by Björn Töpel.
> - code refactoring, different patch splitup,
> a sysctl knob to disable as suggested by Willem de Bruijn.
> - fix a bunch of minor issues spotted by LLMs
>
>
> Changes since v2:
>
> virtio_net: parse tunnel csum_start little-endian
> - new patch. correctly parsing the header is a dependency
> of validating it, otherwise i do not know what to validate
>
> net: account for ingress-resolved virtio net hdr state
> - make rx_csum_sw counter 64 bit so it won't wrap
> (spotted by LLM review)
>
> net: resolve uncommon partial checksums at ingress
> - tunnel fixes to bugs noticed by Willem de Bruijn and
> Chris Arges
> - restore the csum_offset checks as suggested by Willem
> - parse csum_start in the tunnel header little-endian like
> the rest of it (spotted by LLM review)
>
> net: add a sysctl to opt out of virtio net hdr checksum validation
> - the knob is no longer writable by root inside a user
> namespace: changing it now requires capable(CAP_NET_ADMIN)
> suggested by Willem de Bruijn
>
> net: add ip4_parse()
> - comment converted to kernel-doc format (Willem de Bruijn)
>
> um: vector: honor virtio net hdr conversion failures
> - commit log tweaks
>
> New patch:
> um: vector: trim skbs before verifying the header
> found by code review
>
> Somewhat tested, tunnel also tested now, um part compiled only
>
I was able to run my tests and can confirm no more KASAN errors. I did
not test the um patches.
Tested-by: Chris Arges <carges@cloudflare.com>
>
> Michael S. Tsirkin (8):
> net: account for ingress-resolved virtio net hdr state
> um: vector: honor virtio net hdr conversion failures
> um: vector: trim skbs before verifying the header
> virtio_net: parse tunnel csum_start little-endian
> net: resolve uncommon partial checksums at ingress
> net: add a sysctl to opt out of virtio net hdr checksum validation
> net: add ip4_parse()
> virtio_net: cleanup protocol calculation
>
> Documentation/admin-guide/sysctl/net.rst | 19 ++
> arch/um/drivers/vector_kern.c | 6 +-
> arch/um/drivers/vector_transports.c | 4 +-
> drivers/net/tap.c | 4 +-
> drivers/net/tun.c | 41 +++-
> drivers/net/virtio_net.c | 2 +-
> include/linux/ip.h | 27 +++
> include/linux/virtio_net.h | 272 ++++++++++++++++++++++-
> include/net/netns/core.h | 1 +
> net/bridge/br_netfilter_hooks.c | 15 +-
> net/core/dev.c | 6 +
> net/core/net_namespace.c | 1 +
> net/core/sysctl_net_core.c | 60 +++++
> net/ipv4/ip_input.c | 13 +-
> net/ipv4/netfilter/nf_reject_ipv4.c | 13 +-
> net/packet/af_packet.c | 4 +-
> 16 files changed, 445 insertions(+), 43 deletions(-)
>
> --
> MST
>
prev parent reply other threads:[~2026-10-19 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 12:03 Michael S. Tsirkin
2026-10-19 12:03 ` [PATCH net v3 1/8] net: account for ingress-resolved virtio net hdr state Michael S. Tsirkin
2026-10-19 12:03 ` [PATCH net v3 2/8] um: vector: honor virtio net hdr conversion failures Michael S. Tsirkin
2026-10-19 12:03 ` [PATCH net v3 3/8] um: vector: trim skbs before verifying the header Michael S. Tsirkin
2026-10-19 12:03 ` [PATCH net v3 4/8] virtio_net: parse tunnel csum_start little-endian Michael S. Tsirkin
2026-10-19 12:03 ` [PATCH net v3 5/8] net: resolve uncommon partial checksums at ingress Michael S. Tsirkin
2026-10-19 12:03 ` [PATCH net v3 6/8] net: add a sysctl to opt out of virtio net hdr checksum validation Michael S. Tsirkin
2026-10-19 14:19 ` Björn Töpel
2026-10-19 12:03 ` [PATCH net v3 7/8] net: add ip4_parse() Michael S. Tsirkin
2026-10-19 12:03 ` [PATCH net v3 8/8] virtio_net: cleanup protocol calculation Michael S. Tsirkin
2026-10-19 12:09 ` [PATCH net v3 0/8] more virtio-net csum hardening netdev-bot+sinfo
2026-10-19 12:21 ` Michael S. Tsirkin
2026-10-19 16:51 ` Chris Arges [this message]
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=atZKogiEAkStdgQ2@20HS2G4 \
--to=carges@cloudflare.com \
--cc=andrew+netdev@lunn.ch \
--cc=bjorn@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phil@nwl.cc \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux.dev \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xuanzhuo@linux.alibaba.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®