Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	lena.wang@mediatek.com, maze@google.com
Subject: Re: [PATCH net] udp6: fix potential access to stale information
Date: Thu, 13 Apr 2023 17:20:17 +0000	[thread overview]
Message-ID: <168140641762.8255.15958713357480902639.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230412130308.1202254-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 12 Apr 2023 13:03:08 +0000 you wrote:
> lena wang reported an issue caused by udpv6_sendmsg()
> mangling msg->msg_name and msg->msg_namelen, which
> are later read from ____sys_sendmsg() :
> 
> 	/*
> 	 * If this is sendmmsg() and sending to current destination address was
> 	 * successful, remember it.
> 	 */
> 	if (used_address && err >= 0) {
> 		used_address->name_len = msg_sys->msg_namelen;
> 		if (msg_sys->msg_name)
> 			memcpy(&used_address->name, msg_sys->msg_name,
> 			       used_address->name_len);
> 	}
> 
> [...]

Here is the summary with links:
  - [net] udp6: fix potential access to stale information
    https://git.kernel.org/netdev/net/c/1c5950fc6fe9

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-04-13 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 13:03 [PATCH net] udp6: fix potential access to stale information Eric Dumazet
2023-04-12 13:08 ` Maciej Żenczykowski
2023-04-13 17: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=168140641762.8255.15958713357480902639.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=lena.wang@mediatek.com \
    --cc=maze@google.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