From: Takashi Iwai <tiwai@suse.de>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
LinMa <linma@zju.edu.cn>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
tiwai@suse.com
Subject: Re: [PATCH] Bluetooth: avoid page fault from sco_send_frame()
Date: Mon, 11 Oct 2021 09:13:24 +0200 [thread overview]
Message-ID: <s5h7dek590r.wl-tiwai@suse.de> (raw)
In-Reply-To: <YWPg8Ck2ZbXZxOtD@eldamar.lan>
On Mon, 11 Oct 2021 09:00:00 +0200,
Salvatore Bonaccorso wrote:
>
> Hi,
>
> On Sat, Sep 04, 2021 at 11:02:58AM +0900, Tetsuo Handa wrote:
> > Commit 99c23da0eed4fd20 ("Bluetooth: sco: Fix lock_sock() blockage
> > by memcpy_from_msg()") in linux-next.git should be sent to linux.git
> > now as a mitigation for CVE-2021-3640.
> >
> > But I think "[PATCH v3 3/4] Bluetooth: SCO: Replace use of
> > memcpy_from_msg with bt_skb_sendmsg" still contains bug.
>
> Did his one felt through the cracks? I'm confused about the statement
> in https://bugzilla.suse.com/show_bug.cgi?id=1188172#c8 so Cc'ing
> Takashi Iwai as well.
The quite similar fix has been already in the subsystem tree,
commit 99c23da0eed4 ("Bluetooth: sco: Fix lock_sock() blockage by
memcpy_from_msg()"). The particular CVE should be covered by that and
prerequisite patches.
Takashi
next prev parent reply other threads:[~2021-10-11 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 12:33 Help needed in patching CVE-2021-3640 LinMa
2021-09-02 15:32 ` Tetsuo Handa
2021-09-03 2:44 ` [PATCH] Bluetooth: avoid page fault from sco_send_frame() Tetsuo Handa
2021-09-03 3:48 ` Luiz Augusto von Dentz
2021-09-03 4:40 ` Tetsuo Handa
2021-09-04 2:02 ` Tetsuo Handa
2021-10-11 7:00 ` Salvatore Bonaccorso
2021-10-11 7:13 ` Takashi Iwai [this message]
2021-09-02 18:46 ` Help needed in patching CVE-2021-3640 Luiz Augusto von Dentz
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=s5h7dek590r.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=carnil@debian.org \
--cc=johan.hedberg@gmail.com \
--cc=linma@zju.edu.cn \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=tiwai@suse.com \
--cc=torvalds@linux-foundation.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.