From: Simon Horman <horms@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-hams@vger.kernel.org, Yizhe Zhuang <yizhe@darknavy.com>,
stable <stable@kernel.org>
Subject: Re: [PATCH net] netrom: do some basic forms of validation on incoming frames
Date: Fri, 10 Apr 2026 11:28:27 +0100 [thread overview]
Message-ID: <20260410102827.GT469338@kernel.org> (raw)
In-Reply-To: <2026041026-excuse-slashing-c4ee@gregkh>
On Fri, Apr 10, 2026 at 07:24:36AM +0200, Greg Kroah-Hartman wrote:
> On Thu, Apr 09, 2026 at 08:32:35PM -0700, Jakub Kicinski wrote:
> > On Thu, 9 Apr 2026 20:03:28 +0100 Simon Horman wrote:
> > > I expect that checking skb->len isn't sufficient here
> > > and pskb_may_pull needs to be used to ensure that
> > > the data is also available in the linear section of the skb.
> >
> > Or for simplicity we could also be testing against skb_headlen()
> > since we don't expect any legit non-linear frames here? Dunno.
Sure, that's find by me if it leads to simpler code than
using pskb_may_pull(). Else I'd lean towards pskb_may_pull()
as it is a more general approach that feels worth proliferating.
> I'll be glad to change this either way, your call. Given that this is
> an obsolete protocol that seems to only be a target for drive-by fuzzers
> to attack, whatever the simplest thing to do to quiet them up I'll be
> glad to implement.
>
> Or can we just delete this stuff entirely? :)
Deleting sounds good to me.
But we likely need a deprecation process.
In which case fixing these bugs still makes sense for the short term.
next prev parent reply other threads:[~2026-04-10 10:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 8:45 [PATCH net] netrom: do some basic forms of validation on incoming frames Greg Kroah-Hartman
2026-04-09 19:03 ` Simon Horman
2026-04-10 3:32 ` Jakub Kicinski
2026-04-10 5:24 ` Greg Kroah-Hartman
2026-04-10 10:28 ` Simon Horman [this message]
2026-04-10 15:12 ` jj
2026-04-10 16:38 ` David Ranch
2026-04-10 17:21 ` Dan Carpenter
2026-04-10 18:23 ` Dan Cross
2026-04-10 21:30 ` Jakub Kicinski
2026-04-10 21:54 ` Jakub Kicinski
2026-04-10 22:11 ` Kuniyuki Iwashima
2026-04-10 22:25 ` Hugh Blemings
2026-04-10 22:51 ` Craig
2026-04-10 23:38 ` Hugh Blemings
[not found] ` <CANnsUMEniMzLnp5h=Gz83=Wcegc-jGz9vqyWyEpWx-OH=Dij1w@mail.gmail.com>
2026-04-11 20:33 ` Chris Maness
2026-04-12 14:41 ` Jakub Kicinski
2026-04-11 5:50 ` Greg KH
2026-04-11 7:24 ` Hugh Blemings
2026-04-11 8:58 ` Greg KH
2026-04-12 2:32 ` Hugh Blemings
2026-04-12 12:56 ` Chris Maness
2026-04-16 16:58 ` Jakub Kicinski
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=20260410102827.GT469338@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@kernel.org \
--cc=yizhe@darknavy.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.