linux-kernel - Re: [PATCH] Bluetooth: fix use-after-free in hci_conn

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] [day] [month] [year] [list]

Message-ID: <CAKZCeSWxJxuRfNntgm16SrY0BX9TNG2JZAUR93h+_TXwKjUpEg@mail.gmail.com>
Date: Tue, 10 Feb 2026 23:50:14 +0900
From: kawada <youjingxiaogao2@...il.com>
To: Hillf Danton <hdanton@...a.com>
Cc: linux-bluetooth@...r.kernel.org, luiz.dentz@...il.com, marcel@...tmann.org, 
	johan.hedberg@...il.com, linux-kernel@...r.kernel.org, 
	syzbot+3609b9b48e68e1fe47fd@...kaller.appspotmail.com
Subject: Re: [PATCH] Bluetooth: fix use-after-free in hci_conn_drop

Apologies for the top-posting.

> Better not before spotting the reason why conn->refcnt
> failed to make the entry->destroy callback safe.

hci_conn_hold() increments conn->refcnt, but the actual
freeing of conn is done by put_device() called from
hci_conn_del(). hci_conn_del() does not check conn->refcnt
at all, so the hold/drop refcount cannot prevent the UAF
in entry->destroy callbacks.