Hello,
On Thu, Jun 09, 2022 at 07:15:27PM -0400, Mimi Zohar wrote:
> On Thu, 2022-05-12 at 15:01 +0800, Coiby Xu wrote:
> > Currently, a problem faced by arm64 is if a kernel image is signed by a
> > MOK key, loading it via the kexec_file_load() system call would be
> > rejected with the error "Lockdown: kexec: kexec of unsigned images is
> > restricted; see man kernel_lockdown.7".
> >
> > This happens because image_verify_sig uses only the primary keyring that
> > contains only kernel built-in keys to verify the kexec image.
>
> From the git history it's clear that .platform keyring was upstreamed
> during the same open window as commit 732b7b93d849 ("arm64: kexec_file:
> add kernel signature verification support"). Loading the MOK keys
> onto the .platform keyring was upstreamed much later. For this reason,
> commit 732b7b93d849 only used keys on the .builtin_trusted_keys
> keyring. This patch is now addressing it and the newly upstreamed
> .machine keyring.
>
> Only using the .builtin_trusted_keys is the problem statement, which
> should be one of the first lines of the patch description, if not the
> first line.
>
> >
> > This patch allows to verify arm64 kernel image signature using not only
> > .builtin_trusted_keys but also .platform and .secondary_trusted_keys
> > keyring.
>
> Please remember to update this to include the .machine keyring.
>
> >
> > Fixes: 732b7b93d849 ("arm64: kexec_file: add kernel signature verification support")
>
> Since the MOK keys weren't loaded onto the .platform keyring until much
> later, I would not classify this as a fix.
It's definitely a fix
ea93102f32244e3f45c8b26260be77ed0cc1d16c v4.19-rc1 Fix kexec forbidding kernels signed with keys in the secondary keyring to boot
732b7b93d849f8a44886ead563dfb6adec7f4419 v5.0-rc1 arm64: kexec_file: add kernel signature verification support
the arm code does not reflect the preexisting use of the secondary keyring.
278311e417be60f7caef6fcb12bda4da2711ceff v5.1-rc1 kexec, KEYS: Make use of platform keyring for signature
This was added a bit later, indeed.
Cherry-picking the changes one by one to the arm code you can get
separate fixes tag for each change.
Replacing the arm code with the x86 code by code deduplication you get
whatever is the state of the art in the kernel in question. In 5.0 you
get the secondary keyring, and since 5.1 you also get the platform
keyring.
Nonetheless, it's a fix for the arm code which is deficient from the
very start.
Thanks
Michal
