linux-kernel - Re: [PATCH v2] Bluetooth: msft: fix slab-use-after-free in msft_do

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c9bd5c39-ce8d-4c4b-8a1d-ae90298c4f92@web.de>
Date: Sun, 28 Apr 2024 18:38:36 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Sungwoo Kim <iam@...g-woo.kim>, linux-bluetooth@...r.kernel.org,
 kernel-janitors@...r.kernel.org, Johan Hedberg <johan.hedberg@...il.com>,
 Luiz Augusto von Dentz <luiz.dentz@...il.com>,
 Marcel Holtmann <marcel@...tmann.org>
Cc: LKML <linux-kernel@...r.kernel.org>, "Dave (Jing) Tian"
 <daveti@...due.edu>
Subject: Re: [PATCH v2] Bluetooth: msft: fix slab-use-after-free in
 msft_do_close()

Will an other distribution of email addresses over recipient lists be more helpful?

> Hi, could you review this patch?

I suggest to reconsider such a question once for the final commit message.

> Now *not static* msft functions hold and put hdev->msft_data.
> It prevents from potential and real use-after-free bugs.

Is another corresponding imperative wording desirable for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc5#n94

Regards,
Markus