From: Simon Horman <horms@kernel.org>
To: ssrane_b23@ee.vjti.ac.in
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Felix Maurer <fmaurer@redhat.com>,
Jaakko Karrenpalo <jkarrenpalo@gmail.com>,
Arvid Brodin <arvid.brodin@alten.se>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
david.hunter.linux@gmail.com, khalid@kernel.org,
syzbot+2fa344348a579b779e05@syzkaller.appspotmail.com
Subject: Re: [PATCH] hsr: fix NULL pointer dereference in skb_clone with hw tag insertion
Date: Thu, 27 Nov 2025 14:54:44 +0000 [thread overview]
Message-ID: <aShmNNgam3bJ2yMO@horms.kernel.org> (raw)
In-Reply-To: <20251125210158.224431-1-ssranevjti@gmail.com>
On Wed, Nov 26, 2025 at 02:31:58AM +0530, ssrane_b23@ee.vjti.ac.in wrote:
> From: Shaurya Rane <ssrane_b23@ee.vjti.ac.in>
>
> When hardware HSR tag insertion is enabled (NETIF_F_HW_HSR_TAG_INS) and
> frame->skb_std is NULL, both hsr_create_tagged_frame() and
> prp_create_tagged_frame() will call skb_clone() with a NULL skb pointer,
> causing a kernel crash.
>
> Fix this by adding NULL checks for frame->skb_std before calling
> skb_clone() in the functions.
I think it would be worth including the trace reported by syzcaller here.
(Say, up to but not including the "Modules linked in" line.)
I can see it at the link. But maybe the link will go away some day.
>
> Reported-by: syzbot+2fa344348a579b779e05@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=2fa344348a579b779e05
> Fixes: f266a683a480 ("net/hsr: Better frame dispatch")
> Signed-off-by: Shaurya Rane <ssrane_b23@ee.vjti.ac.in>
As a fix Networking code present in the net tree, this should be
targeted at the net tree. Like this.
[PATCH net] ...
> ---
> net/hsr/hsr_forward.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/net/hsr/hsr_forward.c b/net/hsr/hsr_forward.c
> index 339f0d220212..4c1a311b900f 100644
> --- a/net/hsr/hsr_forward.c
> +++ b/net/hsr/hsr_forward.c
> @@ -211,6 +211,9 @@ struct sk_buff *prp_get_untagged_frame(struct hsr_frame_info *frame,
> __FILE__, __LINE__, port->dev->name);
> return NULL;
> }
> +
> + if (!frame->skb_std)
> + return NULL;
I think this can only occur if __pskb_copy() returns NULL.
So, for clarity, I think this condition should be moved to immediately
after the call to __pskb_copy().
> }
>
> return skb_clone(frame->skb_std, GFP_ATOMIC);
...
--
pw-bot: changes-requested
next prev parent reply other threads:[~2025-11-27 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 21:01 [PATCH] hsr: fix NULL pointer dereference in skb_clone with hw tag insertion ssrane_b23
2025-11-27 14:54 ` Simon Horman [this message]
2025-11-27 15:20 ` Greg KH
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=aShmNNgam3bJ2yMO@horms.kernel.org \
--to=horms@kernel.org \
--cc=arvid.brodin@alten.se \
--cc=davem@davemloft.net \
--cc=david.hunter.linux@gmail.com \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=jkarrenpalo@gmail.com \
--cc=khalid@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.org \
--cc=ssrane_b23@ee.vjti.ac.in \
--cc=syzbot+2fa344348a579b779e05@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).