From: Dan Carpenter <dan.carpenter@linaro.org>
To: Sungwoo Kim <iam@sung-woo.kim>
Cc: daveti@purdue.edu, Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_send_cmd
Date: Fri, 26 Apr 2024 12:16:45 +0300 [thread overview]
Message-ID: <cff764c2-a3d1-4a12-9260-54122e7a1fef@moroto.mountain> (raw)
In-Reply-To: <20240426072006.358802-1-iam@sung-woo.kim>
On Fri, Apr 26, 2024 at 03:20:05AM -0400, Sungwoo Kim wrote:
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index 84fc70862..a8f414ab8 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -3953,6 +3953,9 @@ static struct l2cap_chan *l2cap_connect(struct l2cap_conn *conn,
> if (!chan)
> goto response;
>
> + l2cap_chan_hold(chan);
> + l2cap_chan_lock(chan);
> +
> /* For certain devices (ex: HID mouse), support for authentication,
> * pairing and bonding is optional. For such devices, inorder to avoid
> * the ACL alive for too long after L2CAP disconnection, reset the ACL
> @@ -4041,6 +4044,11 @@ static struct l2cap_chan *l2cap_connect(struct l2cap_conn *conn,
> chan->num_conf_req++;
> }
>
> + if (chan) {
> + l2cap_chan_unlock(chan);
> + l2cap_chan_put(chan);
> + }
> +
> return chan;
^^^^^^^^^^^^
This doesn't fix the bug because we're returning chan.
As soon as you call l2cap_chan_put() then chan will be freed by in the
other thread which is doing l2cap_conn_del() resulting in a use after
free in the caller.
regards,
dan carpenter
next prev parent reply other threads:[~2024-04-26 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 7:20 Sungwoo Kim
2024-04-26 7:31 ` Sungwoo Kim
2024-04-26 7:55 ` Paul Menzel
2024-04-26 8:25 ` Markus Elfring
2024-04-26 8:38 ` Sungwoo Kim
2024-04-26 9:38 ` Dan Carpenter
2024-04-26 9:48 ` Sungwoo Kim
2024-04-26 10:01 ` Markus Elfring
2024-04-26 9:16 ` Dan Carpenter [this message]
2024-04-26 9:35 ` [PATCH] " Sungwoo Kim
2024-04-26 10:24 ` Dan Carpenter
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=cff764c2-a3d1-4a12-9260-54122e7a1fef@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=daveti@purdue.edu \
--cc=iam@sung-woo.kim \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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
all inboxes | Powered by JetHome®