From: Greg KH <gregkh@linuxfoundation.org>
To: Zubin Mithra <zsm@chromium.org>
Cc: stable@vger.kernel.org, groeck@chromium.org, edumazet@google.com,
davem@davemloft.net, kuznet@ms2.inr.ac.ru,
herbert@gondor.apana.org.au
Subject: Re: 30c7be26fd35 ("udplite: call proper backlog handlers")
Date: Tue, 12 Mar 2019 11:55:35 -0700 [thread overview]
Message-ID: <20190312185535.GA13892@kroah.com> (raw)
In-Reply-To: <20190312174249.GA185472@google.com>
On Tue, Mar 12, 2019 at 10:42:50AM -0700, Zubin Mithra wrote:
> Hello,
>
> Syzkaller has triggered a GPF when fuzzing a 4.4 kernel with the following calltrace.
>
> Call Trace:
> [<ffffffff8225c7cb>] sk_backlog_rcv include/net/sock.h:874 [inline]
> [<ffffffff8225c7cb>] __release_sock net/core/sock.c:2059 [inline]
> [<ffffffff8225c7cb>] release_sock+0x16b/0x520 net/core/sock.c:2507
> [<ffffffff826d171b>] udp_sendmsg+0x115b/0x1c70 net/ipv4/udp.c:1107
> [<ffffffff82700efc>] inet_sendmsg+0x20c/0x4d0 net/ipv4/af_inet.c:780
> [<ffffffff8224b7f1>] sock_sendmsg_nosec net/socket.c:638 [inline]
> [<ffffffff8224b7f1>] sock_sendmsg+0xd1/0x110 net/socket.c:648
> [<ffffffff8224c4bc>] SYSC_sendto+0x21c/0x370 net/socket.c:1678
> [<ffffffff82251635>] SyS_sendto+0x45/0x60 net/socket.c:1646
> [<ffffffff82a62a67>] entry_SYSCALL_64_fastpath+0x1e/0xa0
> Code: 74 24 58 41 f6 c6 01 0f 85 b2 08 00 00 e8 65 d2 c3 fe 49 83 e6 fe 48 b8 00 00 00 00 00 fc ff df 49 8d 7e 60 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 08 3c 01 0f 8e b9 0e 00 00 41 f6 46 60 04
> RIP [<ffffffff826d3014>] __xfrm_policy_check2 include/net/xfrm.h:1070 [inline]
> RIP [<ffffffff826d3014>] xfrm_policy_check include/net/xfrm.h:1076 [inline]
> RIP [<ffffffff826d3014>] xfrm4_policy_check include/net/xfrm.h:1081 [inline]
> RIP [<ffffffff826d3014>] udp_queue_rcv_skb+0x194/0x1590 net/ipv4/udp.c:1520
> RSP <ffff8800b987f930>
>
> Could the following patch be applied to v4.4.y? It is present in v4.9.y.
> * 30c7be26fd35 ("udplite: call proper backlog handlers")
>
> Tests run:
> * Chrome OS tryjob tests
> * Syzkaller reproducer
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2019-03-12 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 17:42 30c7be26fd35 ("udplite: call proper backlog handlers") Zubin Mithra
2019-03-12 18:55 ` Greg KH [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=20190312185535.GA13892@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=groeck@chromium.org \
--cc=herbert@gondor.apana.org.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=stable@vger.kernel.org \
--cc=zsm@chromium.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 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.