Eric Biggers
authored
commit 919dc320 upstream. If an fsverity builtin signature is given for a file but the ".fs-verity" keyring is empty, there's no real reason to run the PKCS#7 parser. Skip this to avoid the PKCS#7 attack surface when builtin signature support is configured into the kernel but is not being used. This is a hardening improvement, not a fix per se, but I've added Fixes and Cc stable to get it out to more users. Fixes: 432434c9 ("fs-verity: support builtin file signatures") Cc: stable@vger.kernel.org Reviewed-by:Jarkko Sakkinen <jarkko@kernel.org> Link: https://lore.kernel.org/r/20230820173237.2579-1-ebiggers@kernel.org Signed-off-by:
Eric Biggers <ebiggers@google.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| Name | Last commit | Last update |
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| enable.c | ||
| fsverity_private.h | ||
| hash_algs.c | ||
| init.c | ||
| measure.c | ||
| open.c | ||
| read_metadata.c | ||
| signature.c | ||
| verify.c | ||