From: David Miller <davem@davemloft.net>
To: dvyukov@gmail.com
Cc: f6bvp@free.fr, linux-hams@vger.kernel.org,
netdev@vger.kernel.org, dvyukov@google.com,
syzbot+1a2c456a1ea08fa5b5f7@syzkaller.appspotmail.com,
ralf@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/rose: fix NULL ax25_cb kernel panic
Date: Sun, 27 Jan 2019 10:41:42 -0800 (PST) [thread overview]
Message-ID: <20190127.104142.813336159923265386.davem@davemloft.net> (raw)
In-Reply-To: <20190125104640.253862-1-dvyukov@gmail.com>
From: Dmitry Vyukov <dvyukov@gmail.com>
Date: Fri, 25 Jan 2019 11:46:40 +0100
> From: Bernard Pidoux <f6bvp@free.fr>
>
> When an internally generated frame is handled by rose_xmit(),
> rose_route_frame() is called:
>
> if (!rose_route_frame(skb, NULL)) {
> dev_kfree_skb(skb);
> stats->tx_errors++;
> return NETDEV_TX_OK;
> }
>
> We have the same code sequence in Net/Rom where an internally generated
> frame is handled by nr_xmit() calling nr_route_frame(skb, NULL).
> However, in this function NULL argument is tested while it is not in
> rose_route_frame().
> Then kernel panic occurs later on when calling ax25cmp() with a NULL
> ax25_cb argument as reported many times and recently with syzbot.
>
> We need to test if ax25 is NULL before using it.
>
> Testing:
> Built kernel with CONFIG_ROSE=y.
>
> Signed-off-by: Bernard Pidoux <f6bvp@free.fr>
> Acked-by: Dmitry Vyukov <dvyukov@google.com>
> Reported-by: syzbot+1a2c456a1ea08fa5b5f7@syzkaller.appspotmail.com
Applied and queued up for -stable, thanks.
prev parent reply other threads:[~2019-01-27 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 10:46 Dmitry Vyukov
2019-01-27 18:41 ` David Miller [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=20190127.104142.813336159923265386.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dvyukov@gmail.com \
--cc=dvyukov@google.com \
--cc=f6bvp@free.fr \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=syzbot+1a2c456a1ea08fa5b5f7@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
all inboxes | Powered by JetHome®