From: Simon Horman <horms@kernel.org>
To: Arnaud Lecomte <contact@arnaud-lcm.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
syzbot+29fc8991b0ecb186cf40@syzkaller.appspotmail.com
Subject: Re: [PATCH] net: ppp: Add bound checking for skb d on ppp_sync_txmung
Date: Tue, 8 Apr 2025 16:33:52 +0100 [thread overview]
Message-ID: <20250408153352.GY395307@horms.kernel.org> (raw)
In-Reply-To: <20250407-bound-checking-ppp_txmung-v1-1-cfcd2efe39e3@arnaud-lcm.com>
On Mon, Apr 07, 2025 at 05:26:21PM +0200, Arnaud Lecomte wrote:
> Ensure we have enough data in linear buffer from skb before accessing
> initial bytes. This prevents potential out-of-bounds accesses
> when processing short packets.
>
> When ppp_sync_txmung receives an incoming package with an empty
> payload:
> (remote) gef➤ p *(struct pppoe_hdr *) (skb->head + skb->network_header)
> $18 = {
> type = 0x1,
> ver = 0x1,
> code = 0x0,
> sid = 0x2,
> length = 0x0,
> tag = 0xffff8880371cdb96
> }
>
> from the skb struct (trimmed)
> tail = 0x16,
> end = 0x140,
> head = 0xffff88803346f400 "4",
> data = 0xffff88803346f416 ":\377",
> truesize = 0x380,
> len = 0x0,
> data_len = 0x0,
> mac_len = 0xe,
> hdr_len = 0x0,
>
> it is not safe to access data[2].
>
> Reported-by: syzbot+29fc8991b0ecb186cf40@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=29fc8991b0ecb186cf40
> Tested-by: syzbot+29fc8991b0ecb186cf40@syzkaller.appspotmail.com
> Fixes: 9946eaf552b1 ("Merge tag 'hardening-v6.14-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux")
It doesn't seem right to use a Merge commit in a fixes tag.
Looking over the code, the access to data[2] seems to have existed since
the beginning of git history, in which case I think we can use this:
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Arnaud Lecomte <contact@arnaud-lcm.com>
> ---
> drivers/net/ppp/ppp_synctty.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/net/ppp/ppp_synctty.c b/drivers/net/ppp/ppp_synctty.c
> index 644e99fc3623..520d895acc60 100644
> --- a/drivers/net/ppp/ppp_synctty.c
> +++ b/drivers/net/ppp/ppp_synctty.c
> @@ -506,6 +506,11 @@ ppp_sync_txmunge(struct syncppp *ap, struct sk_buff *skb)
> unsigned char *data;
> int islcp;
>
> + /* Ensure we can safely access protocol field and LCP code */
> + if (!skb || !pskb_may_pull(skb, 3)) {
I doubt that skb can be NULL.
> + kfree_skb(skb);
> + return NULL;
> + }
> data = skb->data;
> proto = get_unaligned_be16(data);
>
>
> ---
> base-commit: 9946eaf552b194bb352c2945b54ff98c8193b3f1
> change-id: 20250405-bound-checking-ppp_txmung-4807c854ed85
>
> Best regards,
> --
> Arnaud Lecomte <contact@arnaud-lcm.com>
>
>
next prev parent reply other threads:[~2025-04-08 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 15:26 [PATCH] net: ppp: Add bound checking for skb d on ppp_sync_txmung Arnaud Lecomte
2025-04-08 15:33 ` Simon Horman [this message]
2025-04-08 15:58 ` Arnaud Lecomte
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=20250408153352.GY395307@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=contact@arnaud-lcm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+29fc8991b0ecb186cf40@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).