linux-kernel - Re: [PATCH v3] Bluetooth: L2CAP: Fix slab-use-after-free in l2cap

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 for Android: free password hash cracker in your pocket

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

Message-ID: <8b274e8b-ca1b-47a6-90f9-eb2c9d4a538e@web.de>
Date: Tue, 30 Apr 2024 09:33:14 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Sungwoo Kim <iam@...g-woo.kim>, linux-bluetooth@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org,
 Dan Carpenter <dan.carpenter@...aro.org>,
 "Dave (Jing) Tian" <daveti@...due.edu>,
 Johan Hedberg <johan.hedberg@...il.com>,
 Luiz Augusto von Dentz <luiz.dentz@...il.com>,
 Marcel Holtmann <marcel@...tmann.org>
Subject: Re: [PATCH v3] Bluetooth: L2CAP: Fix slab-use-after-free in
 l2cap_connect()

> Extend a critical section to prevent chan from early freeing.
…

Such a data processing improvement is nice.


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

Can you imagine that the usage of the message field “To” would occasionally be
more appropriate for subsequent patch communication?

Regards,
Markus