From: Takashi Iwai <tiwai@suse.de>
To: Roberto Sassu <roberto.sassu@huawei.com>
Cc: "linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Silviu Vlasceanu" <Silviu.Vlasceanu@huawei.com>
Subject: Re: Oops at boot with linux-next kernel with IMA boot options
Date: Thu, 28 May 2020 20:02:27 +0200 [thread overview]
Message-ID: <s5hblm8lyz0.wl-tiwai@suse.de> (raw)
In-Reply-To: <4de686af78e94893b3578f6970d783d5@huawei.com>
On Thu, 28 May 2020 19:36:55 +0200,
Roberto Sassu wrote:
>
> > From: linux-integrity-owner@vger.kernel.org [mailto:linux-integrity-
> > owner@vger.kernel.org] On Behalf Of Takashi Iwai
> > On Thu, 28 May 2020 17:35:16 +0200,
> > Takashi Iwai wrote:
> > >
> > > Hi Roberto,
> > >
> > > it seems that the recent changes in IMA in linux-next caused a
> > > regression: namely it triggers an Oops when booting with the options
> > > ima_policy=tcb ima_template_fmt='d-ng|n-ng|d|ng'
> >
> > And further experiment revealed that passing only ima_template_fmt=d
> > is enough for triggering the bug. Other formats don't matter.
> >
> > (snip)
> > > It's a KVM instance without any TPM stuff, just passed the options
> > > above. I could trigger the same bug on a bare metal, too.
> > >
> > > Then I performed bisection and it spotted the commit:
> > > 6f1a1d103b48b1533a9c804e7a069e2c8e937ce7
> > > ima: Switch to ima_hash_algo for boot aggregate
> > >
> > > Actually reverting this commit fixed the Oops again.
> >
> > So, looking at the fact above (triggered by "d") and this bisection
> > result, it seems that the issue is specific to ima_eventdigest_init().
> > The difference from others is that this has a check by
> > ima_template_hash_algo_allowed(), and currently the check allows only
> > SHA1 and MD5, while now SHA256 is assigned as default. So I tested
> > adding SHA256 there like below, and it seems working.
> >
> > Hopefully I'm heading to a right direction...
>
> Hi Takashi
>
> boot_aggregate is the only entry for which there is no file descriptor.
> The file descriptor is used to recalculate the digest if it is not SHA1
> or MD5. For boot_aggregate, we should use instead
> ima_calc_boot_aggregate(). I will provide a patch.
>
> I see that the .file member of event_data in
> ima_add_boot_aggregate() is not initialized. Can you please try
> to set .file to NULL?
Tested and it didn't help. The field was already zero-initialized via
C99-style initialization, I believe.
thanks,
Takashi
>
> Thanks
>
> Roberto
>
> HUAWEI TECHNOLOGIES Duesseldorf GmbH, HRB 56063
> Managing Director: Li Peng, Li Jian, Shi Yanli
>
> > thanks,
> >
> > Takashi
> >
> > --- a/security/integrity/ima/ima_template_lib.c
> > +++ b/security/integrity/ima/ima_template_lib.c
> > @@ -13,7 +13,8 @@
> >
> > static bool ima_template_hash_algo_allowed(u8 algo)
> > {
> > - if (algo == HASH_ALGO_SHA1 || algo == HASH_ALGO_MD5)
> > + if (algo == HASH_ALGO_SHA1 || algo == HASH_ALGO_SHA256 ||
> > + algo == HASH_ALGO_MD5)
> > return true;
> >
> > return false;
>
next prev parent reply other threads:[~2020-05-28 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 15:35 Oops at boot with linux-next kernel with IMA boot options Takashi Iwai
2020-05-28 16:37 ` Takashi Iwai
2020-05-28 17:36 ` Roberto Sassu
2020-05-28 18:02 ` Takashi Iwai [this message]
2020-05-29 7:33 ` Roberto Sassu
2020-05-29 7:45 ` Takashi Iwai
2020-05-31 18:50 ` 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=s5hblm8lyz0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Silviu.Vlasceanu@huawei.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roberto.sassu@huawei.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;
as well as URLs for NNTP newsgroup(s).