From: Mimi Zohar <zohar@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] integrity: subsystem fixes for v5.19
Date: Thu, 14 Jul 2022 11:58:22 -0400 [thread overview]
Message-ID: <32baeee1b12e620693c10d89dac5a8c1de6d61a2.camel@linux.ibm.com> (raw)
Hi Linus,
Here are a number of fixes for recently found bugs. Only "ima: fix
violation measurement list record" was introduced in the current
release. The rest address existing bugs.
thanks,
Mimi
The following changes since commit b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3:
Linux 5.19-rc2 (2022-06-12 16:11:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git tags/integrity-v5.19-fix
for you to fetch changes up to 067d2521874135267e681c19d42761c601d503d6:
ima: Fix potential memory leak in ima_init_crypto() (2022-07-13 10:13:58 -0400)
----------------------------------------------------------------
integrity-v5.19-fix
----------------------------------------------------------------
Coiby Xu (1):
ima: force signature verification when CONFIG_KEXEC_SIG is configured
Huaxin Lu (1):
ima: Fix a potential integer overflow in ima_appraise_measurement
Jianglei Nie (1):
ima: Fix potential memory leak in ima_init_crypto()
Mimi Zohar (1):
ima: fix violation measurement list record
Xiu Jianfeng (1):
Revert "evm: Fix memleak in init_desc"
include/linux/kexec.h | 6 ++++++
kernel/kexec_file.c | 11 ++++++++++-
security/integrity/evm/evm_crypto.c | 7 ++-----
security/integrity/ima/ima_appraise.c | 3 ++-
security/integrity/ima/ima_crypto.c | 1 +
security/integrity/ima/ima_efi.c | 2 ++
security/integrity/ima/ima_template_lib.c | 6 +++---
7 files changed, 26 insertions(+), 10 deletions(-)
next reply other threads:[~2022-07-14 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 15:58 Mimi Zohar [this message]
2022-07-14 20:42 ` [GIT PULL] integrity: subsystem fixes for v5.19 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=32baeee1b12e620693c10d89dac5a8c1de6d61a2.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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