From: GUO Zihua <guozihua@huawei.com>
To: <stable@vger.kernel.org>, <gregkh@linuxfoundation.org>,
<zohar@linux.ibm.com>
Cc: <paul@paul-moore.com>, <linux-integrity@vger.kernel.org>,
<luhuaxin1@huawei.com>
Subject: [PATCH v6 0/3] ima: Fix IMA mishandling of LSM based rule during
Date: Thu, 5 Jan 2023 14:23:09 +0800 [thread overview]
Message-ID: <20230105062312.14325-1-guozihua@huawei.com> (raw)
Backports the following three patches to fix the issue of IMA mishandling
LSM based rule during LSM policy update, causing a file to match an
unexpected rule.
v6:
Removed the redundent i in ima_free_rule().
v5:
goes back to ima_lsm_free_rule() instead to avoid freeing
rule->fsname.
v4:
Make use of the exisiting ima_free_rule() instead of backported
ima_lsm_free_rule(). Which resolves additional memory leak issues.
v3:
Backport "LSM: switch to blocking policy update notifiers" as well, as
the prerequsite of "ima: use the lsm policy update notifier".
v2:
Re-adjust the bacported logic.
GUO Zihua (1):
ima: Handle -ESTALE returned by ima_filter_rule_match()
Janne Karhunen (2):
LSM: switch to blocking policy update notifiers
ima: use the lsm policy update notifier
drivers/infiniband/core/device.c | 4 +-
include/linux/security.h | 12 +--
security/integrity/ima/ima.h | 2 +
security/integrity/ima/ima_main.c | 8 ++
security/integrity/ima/ima_policy.c | 151 ++++++++++++++++++++++------
security/security.c | 23 +++--
security/selinux/hooks.c | 2 +-
security/selinux/selinuxfs.c | 2 +-
8 files changed, 155 insertions(+), 49 deletions(-)
--
2.17.1
next reply other threads:[~2023-01-05 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 6:23 GUO Zihua [this message]
2023-01-05 6:23 ` [PATCH v6 1/3] LSM: switch to blocking policy update notifiers GUO Zihua
2023-01-05 6:23 ` [PATCH v6 2/3] ima: use the lsm policy update notifier GUO Zihua
2023-01-05 17:35 ` Mimi Zohar
2023-01-05 6:23 ` [PATCH v6 3/3] ima: Handle -ESTALE returned by ima_filter_rule_match() GUO Zihua
2023-01-05 11:47 ` [PATCH v6 0/3] ima: Fix IMA mishandling of LSM based rule during Greg KH
2023-01-10 13:30 ` Mimi Zohar
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=20230105062312.14325-1-guozihua@huawei.com \
--to=guozihua@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-integrity@vger.kernel.org \
--cc=luhuaxin1@huawei.com \
--cc=paul@paul-moore.com \
--cc=stable@vger.kernel.org \
--cc=zohar@linux.ibm.com \
/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