All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: willemdebruijn.kernel@gmail.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, johann.baudy@gnu-log.net, kuni1840@gmail.com,
	netdev@vger.kernel.org,
	syzbot+73df3f89e1e13089e466@syzkaller.appspotmail.com
Subject: Re: [PATCH v1 net] af_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header().
Date: Tue, 01 Sep 2026 08:50:13 +0000	[thread overview]
Message-ID: <178825261387.1041503.18296517355721988030.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260830180915.260225-1-kuniyu@google.com>

Hello:

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

On Sun, 30 Aug 2026 18:09:12 +0000 you wrote:
> syzbot reported BUG() in sock_sendmsg_nosec(). [0]
> 
> The problem is that tpacket_parse_header() casts user-provided
> tpacket_hdr.tp_len, which is u32, to int.
> 
> If the length is larger than INT_MAX, the following condition
> in tpacket_parse_header() passes,
> 
> [...]

Here is the summary with links:
  - [v1,net] af_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header().
    https://git.kernel.org/netdev/net/c/73e594c19b4f

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-09-01  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-30 18:09 [PATCH v1 net] af_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header() Kuniyuki Iwashima
2026-08-30 18:25 ` Eric Dumazet
2026-08-30 18:36   ` Kuniyuki Iwashima
2026-08-31 15:32 ` Willem de Bruijn
2026-09-01  8:50 ` 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=178825261387.1041503.18296517355721988030.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=johann.baudy@gnu-log.net \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+73df3f89e1e13089e466@syzkaller.appspotmail.com \
    --cc=willemdebruijn.kernel@gmail.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.