[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <D1EVFNB6HJZ8.2ZRZB8Y0K3TV5@kernel.org>
Date: Tue, 21 May 2024 02:47:08 +0300
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Linus Torvalds" <torvalds@...ux-foundation.org>
Cc: "Jason Gunthorpe" <jgg@...pe.ca>, "David Howells" <dhowells@...hat.com>,
<linux-integrity@...r.kernel.org>, <linux-kernel@...r.kernel.org>, "James
Bottomley" <James.Bottomley@...senPartnership.com>, "Mimi Zohar"
<zohar@...ux.ibm.com>, <keyrings@...r.kernel.org>
Subject: [GIT PULL] KEYS-TRUSTED: keys-trusted-next-6.10-rc1-part2
The following changes since commit 8f6a15f095a63a83b096d9b29aaff4f0fbe6f6e6:
Merge tag 'cocci-for-6.10' of git://git.kernel.org/pub/scm/linux/kernel/git/jlawall/linux (2024-05-20 16:00:04 -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.10-rc1-part2
for you to fetch changes up to 050bf3c793a07f96bd1e2fd62e1447f731ed733b:
KEYS: trusted: Do not use WARN when encode fails (2024-05-21 02:35:10 +0300)
----------------------------------------------------------------
Hi,
These are couple of bugs I found from trusted keys while working on a new
asymmetric key type for TPM2 [1]. Both originate form v5.13. Memory leak is
more crucial but I don't think it is either good idea if kernel throws WARN
when ASN.1 parser fails, even if it is related to programming error, as it
is not that mature code yet.
There's at least two WARN's in that code but I picked just the one more
likely to trigger. Planning to fix the other one too over time.
BR, Jarkko
[1] https://lore.kernel.org/linux-integrity/D1ERDC16XLUO.578U4ZE7VXW@kernelorg/T/#t
----------------------------------------------------------------
Jarkko Sakkinen (2):
KEYS: trusted: Fix memory leak in tpm2_key_encode()
KEYS: trusted: Do not use WARN when encode fails
security/keys/trusted-keys/trusted_tpm2.c | 25 +++++++++++++++++++------
1 file changed, 19 insertions(+), 6 deletions(-)
Powered by blists - more mailing lists