From: patchwork-bot+netdevbpf@kernel.org
To: None <kovalev@altlinux.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
edumazet@google.com, pablo@netfilter.org, laforge@gnumonks.org,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
nickel@altlinux.org, oficerovas@altlinux.org,
dutyrok@altlinux.org, stable@vger.kernel.org
Subject: Re: [PATCH ver.2] gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp()
Date: Wed, 21 Feb 2024 22:30:29 +0000 [thread overview]
Message-ID: <170855462910.28356.12191334633977961990.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240214162733.34214-1-kovalev@altlinux.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 14 Feb 2024 19:27:33 +0300 you wrote:
> From: Vasiliy Kovalev <kovalev@altlinux.org>
>
> The gtp_net_ops pernet operations structure for the subsystem must be
> registered before registering the generic netlink family.
>
> Syzkaller hit 'general protection fault in gtp_genl_dump_pdp' bug:
>
> [...]
Here is the summary with links:
- [ver.2] gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp()
https://git.kernel.org/netdev/net/c/136cfaca2256
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-02-21 22:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 16:27 [PATCH ver.2] gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp() kovalev
2024-02-14 16:49 ` Pablo Neira Ayuso
2024-02-14 17:06 ` kovalev
2024-02-14 17:13 ` Pablo Neira Ayuso
2024-02-14 17:30 ` kovalev
2024-02-15 17:43 ` Pablo Neira Ayuso
2024-02-21 0:04 ` Jakub Kicinski
2024-02-21 10:47 ` Pablo Neira Ayuso
2024-02-21 11:03 ` Pablo Neira Ayuso
2024-02-21 22:30 ` patchwork-bot+netdevbpf [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=170855462910.28356.12191334633977961990.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dutyrok@altlinux.org \
--cc=edumazet@google.com \
--cc=kovalev@altlinux.org \
--cc=kuba@kernel.org \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nickel@altlinux.org \
--cc=oficerovas@altlinux.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.