From: Kuniyuki Iwashima <kuniyu@google.com>
To: "David S . Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
Kuniyuki Iwashima <kuni1840@gmail.com>,
netdev@vger.kernel.org
Subject: [PATCH v2 net 0/3] fou/gue: Fix skb memleak with inner protocol 0.
Date: Thu, 15 Jan 2026 17:24:45 +0000 [thread overview]
Message-ID: <20260115172533.693652-1-kuniyu@google.com> (raw)
syzbot reported memleak for a GUE packet with its inner
protocol number 0.
Patch 1 fixes the issue, and patch 3 fixes the same issue
in FOU.
Changes:
v2:
* Add patch 2 for ynl-regen.sh (Jakub)
* Patch 3
* Updated ynl spec and regenerated fou_nl.c (Jakub)
v1: https://lore.kernel.org/netdev/20260112200736.1884171-1-kuniyu@google.com/
Kuniyuki Iwashima (3):
gue: Fix skb memleak with inner IP protocol 0.
tools: ynl: Specify --no-line-number in ynl-regen.sh.
fou: Don't allow 0 for FOU_ATTR_IPPROTO.
Documentation/netlink/specs/fou.yaml | 2 ++
net/ipv4/fou_core.c | 3 +++
net/ipv4/fou_nl.c | 2 +-
tools/net/ynl/ynl-regen.sh | 2 +-
4 files changed, 7 insertions(+), 2 deletions(-)
--
2.52.0.457.g6b5491de43-goog
next reply other threads:[~2026-01-15 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 17:24 Kuniyuki Iwashima [this message]
2026-01-15 17:24 ` [PATCH v2 net 1/3] gue: Fix skb memleak with inner IP protocol 0 Kuniyuki Iwashima
2026-01-15 17:24 ` [PATCH v2 net 2/3] tools: ynl: Specify --no-line-number in ynl-regen.sh Kuniyuki Iwashima
2026-01-15 17:31 ` Eric Dumazet
2026-01-15 17:24 ` [PATCH v2 net 3/3] fou: Don't allow 0 for FOU_ATTR_IPPROTO Kuniyuki Iwashima
2026-01-15 17:27 ` Eric Dumazet
2026-01-19 14:18 ` [PATCH v2 net 0/3] fou/gue: Fix skb memleak with inner protocol 0 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=20260115172533.693652-1-kuniyu@google.com \
--to=kuniyu@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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