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: 
 <173016963603.250007.13782396385062066656.git-patchwork-notify@kernel.org>
Date: Tue, 29 Oct 2024 02:40:36 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Eric Dumazet <edumazet@...gle.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
 netdev@...r.kernel.org, eric.dumazet@...il.com, syzkaller@...glegroups.com,
 ignat@...udflare.com, kuniyu@...zon.com
Subject: Re: [PATCH net-next] vsock: do not leave dangling sk pointer in
 vsock_create()

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Tue, 22 Oct 2024 13:48:19 +0000 you wrote:
> syzbot was able to trigger the following warning after recent
> core network cleanup.
> 
> On error vsock_create() frees the allocated sk object, but sock_init_data()
> has already attached it to the provided sock object.
> 
> We must clear sock->sk to avoid possible use-after-free later.
> 
> [...]

Here is the summary with links:
  - [net-next] vsock: do not leave dangling sk pointer in vsock_create()
    https://git.kernel.org/netdev/net-next/c/ba4e469e42fe

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ