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>,
Roberto Sassu <roberto.sassu@huaweicloud.com>
Subject: [GIT PULL] integrity: subsystem fixes for v7.3
Date: Wed, 19 Aug 2026 20:10:38 -0400 [thread overview]
Message-ID: <6246d8de26d1cce22b4c2e5f53891fff44af02ca.camel@linux.ibm.com> (raw)
Hi Linus,
There are two main changes:
- TPM initialization is sometimes delayed until deferred_probe_initcall. Since
ordering is not guaranteed within the same initcall level, IMA may initialize
before the TPM and fall back to TPM-bypass mode. A new config option,
CONFIG_IMA_INIT_LATE_SYNC, allows those building the kernel to defer IMA
initialization to late_initcall_sync, accepting the integrity risk of missing
early measurements in exchange for avoiding TPM-bypass mode.
- The raw policy rules are now measured, as well as the complete policy, closing
a gap in integrity measurement coverage.
thanks,
Mimi
The following changes since commit b80bed5c871a80151351342c065579405ce77145:
ima: Instantiate file_truncate and path_truncate hooks (2026-08-04 12:35:02 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git/ tags/integrity-v7.3
for you to fetch changes up to f1e10b10874051e4d99911dae0dd7b75a9f8ae66:
ima: measure userspace policy writes before parsing (2026-08-04 12:35:03 -0400)
----------------------------------------------------------------
integrity-v7.3
----------------------------------------------------------------
Enrico Bravi (2):
ima: add critical data measurement for loaded policy
ima: measure userspace policy writes before parsing
Jonathan McDowell (1):
security: ima: rename boot_aggregate when ima is initialised at late_sync
Yeoreum Yun (2):
security: lsm: allow LSMs to register for late_initcall_sync init
security: ima: introduce IMA_INIT_LATE_SYNC option
include/linux/lsm_hooks.h | 2 +
security/integrity/ima/Kconfig | 10 ++++
security/integrity/ima/ima.h | 5 ++
security/integrity/ima/ima_efi.c | 2 +
security/integrity/ima/ima_fs.c | 9 ++-
security/integrity/ima/ima_init.c | 15 +++--
security/integrity/ima/ima_main.c | 26 +++++++++
security/integrity/ima/ima_policy.c | 95 ++++++++++++++++++++++++++++++-
security/integrity/ima/ima_template_lib.c | 3 +-
security/lsm_init.c | 13 ++++-
10 files changed, 170 insertions(+), 10 deletions(-)
next reply other threads:[~2026-08-20 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 0:10 Mimi Zohar [this message]
2026-08-20 0:55 ` [GIT PULL] integrity: subsystem fixes for v7.3 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=6246d8de26d1cce22b4c2e5f53891fff44af02ca.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roberto.sassu@huaweicloud.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.