netdev - Re: [PATCH net v2] net: zero-initialize tc skb extension on allocation

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: <162198240925.22762.3522660607313028652.git-patchwork-notify@kernel.org>
Date:   Tue, 25 May 2021 22:40:09 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Vlad Buslov <vladbu@...dia.com>
Cc:     davem@...emloft.net, kuba@...nel.org, jhs@...atatu.com,
        jiri@...nulli.us, xiyou.wangcong@...il.com, saeedm@...lanox.com,
        fw@...len.de, wenxu@...oud.cn, netdev@...r.kernel.org
Subject: Re: [PATCH net v2] net: zero-initialize tc skb extension on allocation

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Tue, 25 May 2021 16:21:52 +0300 you wrote:
> Function skb_ext_add() doesn't initialize created skb extension with any
> value and leaves it up to the user. However, since extension of type
> TC_SKB_EXT originally contained only single value tc_skb_ext->chain its
> users used to just assign the chain value without setting whole extension
> memory to zero first. This assumption changed when TC_SKB_EXT extension was
> extended with additional fields but not all users were updated to
> initialize the new fields which leads to use of uninitialized memory
> afterwards. UBSAN log:
> 
> [...]

Here is the summary with links:
  - [net,v2] net: zero-initialize tc skb extension on allocation
    https://git.kernel.org/netdev/net/c/9453d45ecb6c

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