From: Greg KH <gregkh@linuxfoundation.org>
To: Zubin Mithra <zsm@chromium.org>
Cc: stable@vger.kernel.org, groeck@chromium.org,
apusaka@chromium.org, luiz.von.dentz@intel.com,
marcel@holtmann.org
Subject: Re: [v5.4.y] Bluetooth: L2CAP: Fix handling LE modes by L2CAP_OPTIONS
Date: Mon, 24 May 2021 14:48:27 +0200 [thread overview]
Message-ID: <YKugm0CAEVC+JVSJ@kroah.com> (raw)
In-Reply-To: <20210519175502.602799-1-zsm@chromium.org>
On Wed, May 19, 2021 at 10:55:02AM -0700, Zubin Mithra wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> L2CAP_OPTIONS shall only be used with BR/EDR modes.
>
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> (cherry picked from commit b86b0b150fed840c376145383ef5105116c81b0c)
> Signed-off-by: Zubin Mithra <zsm@chromium.org>
> ---
> * Syzkaller triggered a GPF with the following stacktrace:
> l2cap_chan_send+0xa6e/0x1c30 net/bluetooth/l2cap_core.c:2532
> l2cap_sock_sendmsg+0x1da/0x1fd net/bluetooth/l2cap_sock.c:985
> sock_sendmsg_nosec+0x88/0xb4 net/socket.c:638
> sock_sendmsg+0x5e/0x6f net/socket.c:658
> ____sys_sendmsg+0x45c/0x5a5 net/socket.c:2298
> ___sys_sendmsg+0x13e/0x19f net/socket.c:2352
> __sys_sendmmsg+0x298/0x38c net/socket.c:2455
> __do_sys_sendmmsg net/socket.c:2484 [inline]
> __se_sys_sendmmsg net/socket.c:2481 [inline]
> __x64_sys_sendmmsg+0xad/0xb6 net/socket.c:2481
> do_syscall_64+0x10b/0x144 arch/x86/entry/common.c:299
> entry_SYSCALL_64_after_hwframe+0x49/0xbe
>
> * This commit is present in 5.10.y and newer. 4.19.y
> and older do not need this fix.
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2021-05-24 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 17:55 [v5.4.y] Bluetooth: L2CAP: Fix handling LE modes by L2CAP_OPTIONS Zubin Mithra
2021-05-24 12:48 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-19 17:52 Zubin Mithra
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=YKugm0CAEVC+JVSJ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apusaka@chromium.org \
--cc=groeck@chromium.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--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.