From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] tpm2-tss: Version bump. 4.0.1 -> 4.1.0
Date: Sun, 12 May 2024 15:16:37 +0200 [thread overview]
Message-ID: <20240512131637.3703429-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20240428163837.824589-1-christian.melki@t2data.com>
Thanks, applied as 49ebd974a8945b69ecca784e06485524178c1acb.
Michael
[sent from post-receive hook]
On Sun, 12 May 2024 15:16:37 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> https://github.com/tpm2-software/tpm2-tss/releases/tag/4.1.0
> Nothing fancy, a bunch of fixes mostly.
>
> Plugs CVE:
> CVE-2024-29040 - In tmu_set_table of tmu.c, there is a possible out of bounds write due to a missing bounds check.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20240428163837.824589-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/tpm2-tss.make b/rules/tpm2-tss.make
> index 729172b4c47c..cf37742c4232 100644
> --- a/rules/tpm2-tss.make
> +++ b/rules/tpm2-tss.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_TPM2_TSS) += tpm2-tss
> #
> # Paths and names
> #
> -TPM2_TSS_VERSION := 4.0.1
> -TPM2_TSS_MD5 := fff676c669519097906bd8ce28fc4238
> +TPM2_TSS_VERSION := 4.1.0
> +TPM2_TSS_MD5 := 97e91ce0c77d361409502badb1023e80
> TPM2_TSS := tpm2-tss-$(TPM2_TSS_VERSION)
> TPM2_TSS_SUFFIX := tar.gz
> TPM2_TSS_URL := https://github.com/tpm2-software/tpm2-tss/releases/download/$(TPM2_TSS_VERSION)/$(TPM2_TSS).$(TPM2_TSS_SUFFIX)
prev parent reply other threads:[~2024-05-12 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 16:38 [ptxdist] [PATCH] " Christian Melki
2024-05-12 13:16 ` Michael Olbrich [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=20240512131637.3703429-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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