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
| ||
|
Message-Id: <166211821507.29115.10248294582452708288.git-patchwork-notify@kernel.org> Date: Fri, 02 Sep 2022 11:30:15 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Toke Høiland-Jørgensen <toke@...e.dk>@ci.codeaurora.org Cc: jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us, eric.dumazet@...il.com, davem@...emloft.net, zdi-disclosures@...ndmicro.com, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org Subject: Re: [PATCH net v2] sch_sfb: Don't assume the skb is still around after enqueueing to child Hello: This patch was applied to netdev/net.git (master) by David S. Miller <davem@...emloft.net>: On Wed, 31 Aug 2022 23:52:18 +0200 you wrote: > The sch_sfb enqueue() routine assumes the skb is still alive after it has > been enqueued into a child qdisc, using the data in the skb cb field in the > increment_qlen() routine after enqueue. However, the skb may in fact have > been freed, causing a use-after-free in this case. In particular, this > happens if sch_cake is used as a child of sfb, and the GSO splitting mode > of CAKE is enabled (in which case the skb will be split into segments and > the original skb freed). > > [...] Here is the summary with links: - [net,v2] sch_sfb: Don't assume the skb is still around after enqueueing to child https://git.kernel.org/netdev/net/c/9efd23297cca 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