All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, kuni1840@gmail.com, netdev@vger.kernel.org,
	syzbot+444ca0907e96f7c5e48b@syzkaller.appspotmail.com
Subject: Re: [PATCH v1 net] udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated().
Date: Thu, 25 May 2023 09:20:20 +0000	[thread overview]
Message-ID: <168500642082.5673.17391735214772212214.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230523163305.66466-1-kuniyu@amazon.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 23 May 2023 09:33:05 -0700 you wrote:
> syzbot reported [0] a null-ptr-deref in sk_get_rmem0() while using
> IPPROTO_UDPLITE (0x88):
> 
>   14:25:52 executing program 1:
>   r0 = socket$inet6(0xa, 0x80002, 0x88)
> 
> We had a similar report [1] for probably sk_memory_allocated_add()
> in __sk_mem_raise_allocated(), and commit c915fe13cbaa ("udplite: fix
> NULL pointer dereference") fixed it by setting .memory_allocated for
> udplite_prot and udplitev6_prot.
> 
> [...]

Here is the summary with links:
  - [v1,net] udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated().
    https://git.kernel.org/netdev/net/c/ad42a35bdfc6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-05-25  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 16:33 [PATCH v1 net] udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated() Kuniyuki Iwashima
2023-05-25  8:59 ` Paolo Abeni
2023-05-25 15:10   ` Kuniyuki Iwashima
2023-05-25 15:18     ` Florian Westphal
2023-05-25 16:21       ` Kuniyuki Iwashima
2023-05-25 16:33         ` Florian Westphal
2023-05-25 17:06           ` Kuniyuki Iwashima
2023-05-25  9:20 ` 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=168500642082.5673.17391735214772212214.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+444ca0907e96f7c5e48b@syzkaller.appspotmail.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 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.