public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Hodges <hodgesd@meta.com>
Cc: jmaloy@redhat.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	tuong.t.lien@dektech.com.au, netdev@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH RESEND] tipc: use kfree_sensitive() for session key material
Date: Tue, 03 Feb 2026 02:00:04 +0000	[thread overview]
Message-ID: <177008400463.1271965.16783467877403840640.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260131180114.2121438-1-hodgesd@meta.com>

Hello:

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

On Sat, 31 Jan 2026 10:01:14 -0800 you wrote:
> The rx->skey field contains a struct tipc_aead_key with GCM-AES
> encryption keys used for TIPC cluster communication. Using plain
> kfree() leaves this sensitive key material in freed memory pages
> where it could potentially be recovered.
> 
> Switch to kfree_sensitive() to ensure the key material is zeroed
> before the memory is freed.
> 
> [...]

Here is the summary with links:
  - [RESEND] tipc: use kfree_sensitive() for session key material
    https://git.kernel.org/netdev/net/c/74d9391e8849

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



      reply	other threads:[~2026-02-03  2:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-31 18:01 [PATCH RESEND] tipc: use kfree_sensitive() for session key material Daniel Hodges
2026-02-03  2:00 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=177008400463.1271965.16783467877403840640.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hodgesd@meta.com \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tuong.t.lien@dektech.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox