From: "Jarkko Sakkinen" <jarkko.sakkinen@iki.fi>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "David Howells" <dhowells@redhat.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
<keyrings@vger.kernel.org>, <linux-integrity@vger.kernel.org>,
"David Gstir" <david@sigma-star.at>
Subject: [GIT PULL] KEYS-TRUSTED: keys-trusted-next-6.11-rc4
Date: Fri, 16 Aug 2024 14:14:45 +0300 [thread overview]
Message-ID: <D3HAJIMUJEVC.154RCMPVU2URD@iki.fi> (raw)
The following changes since commit a4a35f6cbebbf9466b6c412506ab89299d567f51:
Merge tag 'net-6.11-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2024-08-15 10:35:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/keys-trusted-next-6.11-rc4
for you to fetch changes up to 0e28bf61a5f9ab30be3f3b4eafb8d097e39446bb:
KEYS: trusted: dcp: fix leak of blob encryption key (2024-08-15 22:01:14 +0300)
----------------------------------------------------------------
Hi,
Contains two bug fixes for a memory corruption bug and a memory leak bug
in the DCP trusted keys type. Just as a remainder DCP was a crypto
coprocessor in i.MX SoC's.
BR, Jarkko
----------------------------------------------------------------
David Gstir (2):
KEYS: trusted: fix DCP blob payload length assignment
KEYS: trusted: dcp: fix leak of blob encryption key
security/keys/trusted-keys/trusted_dcp.c | 35 ++++++++++++++++++++------------
1 file changed, 22 insertions(+), 13 deletions(-)
next reply other threads:[~2024-08-16 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 11:14 Jarkko Sakkinen [this message]
2024-08-16 18:28 ` [GIT PULL] KEYS-TRUSTED: keys-trusted-next-6.11-rc4 pr-tracker-bot
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=D3HAJIMUJEVC.154RCMPVU2URD@iki.fi \
--to=jarkko.sakkinen@iki.fi \
--cc=davem@davemloft.net \
--cc=david@sigma-star.at \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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