From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
andrew+netdev@lunn.ch, ilkka.lappetelainen@gmail.com,
willemb@google.com
Subject: Re: [PATCH net-next] net: downgrade BUG_ON EIOCBQUEUED in sock_sendmsg_nosec
Date: Tue, 29 Sep 2026 13:40:06 +0000 [thread overview]
Message-ID: <179068920628.499886.774355714944793924.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928020420.3097018-1-willemdebruijn.kernel@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 27 Sep 2026 22:03:29 -0400 you wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> sock_sendmsg_nosec() runs in syscall context but calls BUG_ON() if
> proto_ops->sendmsg() returns -EIOCBQUEUED. Crashing the kernel on an
> unexpected return value is dangerous for production workloads.
>
> This risk is real: any signed integer overflow in a sendmsg handler
> that returns 0xfffffdef (-529, -EIOCBQUEUED) triggers this BUG_ON. In
> one month, two such bugs were reported in PF_PACKET, reachable by
> a local user with CAP_NET_RAW in a user namespace:
> - Commit 73e594c19b4f ("af_packet: Don't cast tpacket_hdr.tp_len to int
> in tpacket_parse_header().")
> - In review ("net/packet: prevent TX_RING byte count overflow")
> https://lore.kernel.org/netdev/20260925124829.6595-1-ilkka.lappetelainen@gmail.com/
>
> [...]
Here is the summary with links:
- [net-next] net: downgrade BUG_ON EIOCBQUEUED in sock_sendmsg_nosec
https://git.kernel.org/netdev/net-next/c/ee1972def665
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:[~2026-09-29 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 2:03 [PATCH net-next] net: downgrade BUG_ON EIOCBQUEUED in sock_sendmsg_nosec Willem de Bruijn
2026-09-29 13:40 ` 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=179068920628.499886.774355714944793924.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ilkka.lappetelainen@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox