From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, butterflyhuangxx@gmail.com,
marc.dionne@auristor.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] rxrpc: fix some null-ptr-deref bugs in server_key.c
Date: Thu, 31 Mar 2022 13:30:11 +0000 [thread overview]
Message-ID: <164873341173.16728.1025951051499150339.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <164865013439.2941502.8966285221215590921.stgit@warthog.procyon.org.uk>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 30 Mar 2022 15:22:14 +0100 you wrote:
> From: Xiaolong Huang <butterflyhuangxx@gmail.com>
>
> Some function calls are not implemented in rxrpc_no_security, there are
> preparse_server_key, free_preparse_server_key and destroy_server_key.
> When rxrpc security type is rxrpc_no_security, user can easily trigger a
> null-ptr-deref bug via ioctl. So judgment should be added to prevent it
>
> [...]
Here is the summary with links:
- [net] rxrpc: fix some null-ptr-deref bugs in server_key.c
https://git.kernel.org/netdev/net/c/ff8376ade4f6
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:[~2022-03-31 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 14:22 [PATCH net] rxrpc: fix some null-ptr-deref bugs in server_key.c David Howells
2022-03-31 10:43 ` Paolo Abeni
2022-03-31 12:16 ` David Howells
2022-03-31 13:20 ` Paolo Abeni
2022-03-31 13: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=164873341173.16728.1025951051499150339.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=butterflyhuangxx@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.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).