From: <Andreas.Fuchs@infineon.com>
To: <tpm2@lists.linux.dev>
Subject: [SECURITY][RELEASE] tpm2-tss 4.2.0 and 4.1.4
Date: Wed, 15 Jul 2026 15:24:58 +0000 [thread overview]
Message-ID: <31df17559ce44ff6bcc5d5a5d38b7750@infineon.com> (raw)
Hi all,
I just tagged and released
https://github.com/tpm2-software/tpm2-tss/releases/tag/4.2.0
and
https://github.com/tpm2-software/tpm2-tss/releases/tag/4.1.4
Note that these fix several Security Advisories.
Also, note that CVE-IDs have not been assigned yet, since the workflow of the GH CNA increased from 3 days to 3 weeks.
Once the CVE-IDs are assigned, I'll update the changelog accordingly.
Bests,
Andreas
reply other threads:[~2026-07-15 15:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=31df17559ce44ff6bcc5d5a5d38b7750@infineon.com \
--to=andreas.fuchs@infineon.com \
--cc=tpm2@lists.linux.dev \
/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