From: Johan Hedberg <johan.hedberg@gmail.com>
To: Harish Jenny K N <harish_kandiga@mentor.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fix use after free in l2cap_chan_timeout
Date: Thu, 19 Mar 2015 10:25:39 +0200 [thread overview]
Message-ID: <20150319082539.GA29243@t440s.lan> (raw)
In-Reply-To: <1426753191-9468-1-git-send-email-harish_kandiga@mentor.com>
Hi,
On Thu, Mar 19, 2015, Harish Jenny K N wrote:
> There is a potential use after free in bt_sock_poll when a
> socket gets killed without getting unlinked from accept_q.
> Hence added code to unlink from accpept_q by calling teardown
> before freeing the socket for channel type L2CAP_CHAN_CONN_ORIENTED.
>
> Signed-off-by: Harish Jenny K N <harish_kandiga@mentor.com>
> ---
> net/bluetooth/l2cap_core.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index 6ba33f9..c6955fb 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -415,6 +415,11 @@ static void l2cap_chan_timeout(struct work_struct *work)
>
> l2cap_chan_close(chan, reason);
>
> + if ((chan->state == BT_CONNECTED || chan->state == BT_CONFIG) &&
> + chan->chan_type == L2CAP_CHAN_CONN_ORIENTED) {
> + chan->ops->teardown(chan, 0);
> + }
Looks quite ok to me, except for a minor issue: we generally don't use
{} for single-line branches.
Do you have some simple way to reproduce this? It'd be nice if we could
add a test case for it to our user space l2cap-tester tool.
Johan
next prev parent reply other threads:[~2015-03-19 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 8:19 [PATCH] Bluetooth: Fix use after free in l2cap_chan_timeout Harish Jenny K N
2015-03-19 8:25 ` Johan Hedberg [this message]
2015-03-19 8:57 ` Harish Jenny Kandiga Nagaraj
2015-03-19 8:59 ` Harish Jenny Kandiga Nagaraj
2015-03-19 14:59 ` Sergei Shtylyov
-- strict thread matches above, loose matches on Subject: below --
2015-03-26 9:10 Harish Jenny K N
2015-03-18 11:59 Harish Jenny K N
2015-03-18 14:22 ` Sergei Shtylyov
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=20150319082539.GA29243@t440s.lan \
--to=johan.hedberg@gmail.com \
--cc=harish_kandiga@mentor.com \
--cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox