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  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]
Date:   Tue, 29 Mar 2022 11:40:11 +0000
To:     Ying Hsu <>
Subject: Re: [PATCH v2] Bluetooth: fix dangling sco_conn and use-after-free in


This patch was applied to bluetooth/bluetooth-next.git (master)
by Marcel Holtmann <>:

On Sat, 26 Mar 2022 07:09:28 +0000 you wrote:
> Connecting the same socket twice consecutively in sco_sock_connect()
> could lead to a race condition where two sco_conn objects are created
> but only one is associated with the socket. If the socket is closed
> before the SCO connection is established, the timer associated with the
> dangling sco_conn object won't be canceled. As the sock object is being
> freed, the use-after-free problem happens when the timer callback
> function sco_sock_timeout() accesses the socket. Here's the call trace:
> [...]

Here is the summary with links:
  - [v2] Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout

You are awesome, thank you!
Deet-doot-dot, I am a bot.

Powered by blists - more mailing lists