mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Cen Zhang <blbllhy@gmail.com>
Cc: jmaloy@redhat.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	AutonomousCodeSecurity@microsoft.com,
	tgopinath@linux.microsoft.com, kys@microsoft.com
Subject: Re: [PATCH net] tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream()
Date: Thu, 23 Jul 2026 17:20:05 +0000	[thread overview]
Message-ID: <178482720565.2793774.13858678723222545565.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260720214103.47732-1-blbllhy@gmail.com>

Hello:

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

On Mon, 20 Jul 2026 17:41:03 -0400 you wrote:
> In tipc_recvmsg(), the copy length is computed as:
> 
>   copy = min_t(int, dlen - offset, buflen);
> 
> buflen is size_t but min_t(int, ...) casts it to int. When buflen
> exceeds INT_MAX (e.g. 0xFFFFFFFF via io_uring provided buffers), it
> wraps negative, wins the comparison, and the negative copy length
> propagates to simple_copy_to_iter() where int-to-size_t promotion
> makes it SIZE_MAX, triggering a WARN_ON. tipc_recvstream() has the
> same pattern.
> 
> [...]

Here is the summary with links:
  - [net] tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream()
    https://git.kernel.org/netdev/net/c/47f42ff521b4

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



      parent reply	other threads:[~2026-07-23 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 21:41 Cen Zhang (Microsoft)
2026-07-22  2:26 ` Tung Quang Nguyen
2026-07-23 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=178482720565.2793774.13858678723222545565.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=AutonomousCodeSecurity@microsoft.com \
    --cc=blbllhy@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tgopinath@linux.microsoft.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    /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
all inboxes | Powered by JetHome®