From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Acs <acsjakub@amazon.de>
Cc: netdev@vger.kernel.org, aws-security@amazon.com,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
security@kernel.org, stable@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net, hsr: reject HSR frame if skb can't hold tag
Date: Thu, 21 Aug 2025 02:40:11 +0000 [thread overview]
Message-ID: <175574401150.482952.15665339291483545385.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250819082842.94378-1-acsjakub@amazon.de>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 19 Aug 2025 08:28:42 +0000 you wrote:
> Receiving HSR frame with insufficient space to hold HSR tag in the skb
> can result in a crash (kernel BUG):
>
> [ 45.390915] skbuff: skb_under_panic: text:ffffffff86f32cac len:26 put:14 head:ffff888042418000 data:ffff888042417ff4 tail:0xe end:0x180 dev:bridge_slave_1
> [ 45.392559] ------------[ cut here ]------------
> [ 45.392912] kernel BUG at net/core/skbuff.c:211!
> [ 45.393276] Oops: invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI
> [ 45.393809] CPU: 1 UID: 0 PID: 2496 Comm: reproducer Not tainted 6.15.0 #12 PREEMPT(undef)
> [ 45.394433] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014
> [ 45.395273] RIP: 0010:skb_panic+0x15b/0x1d0
>
> [...]
Here is the summary with links:
- net, hsr: reject HSR frame if skb can't hold tag
https://git.kernel.org/netdev/net/c/7af76e9d18a9
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:[~2025-08-21 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 8:28 Jakub Acs
2025-08-20 18:21 ` Eric Dumazet
2025-08-21 2: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=175574401150.482952.15665339291483545385.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acsjakub@amazon.de \
--cc=aws-security@amazon.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=security@kernel.org \
--cc=stable@kernel.org \
/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®