diff options
| author | Eric Biggers <ebiggers@google.com> | 2023-03-13 15:12:29 -0700 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com> | 2023-03-14 10:30:30 -0700 |
| commit | ccb820dc7d2236b1af0d54ae038a27b5b6d5ae5a (patch) | |
| tree | c31e6fba690d9cf7d956293b2858461a2a0c432c /fs/crypto | |
| parent | fe15c26ee26efa11741a7b632e9f23b01aca4cc6 (diff) | |
| download | linux-ccb820dc7d2236b1af0d54ae038a27b5b6d5ae5a.tar.gz linux-ccb820dc7d2236b1af0d54ae038a27b5b6d5ae5a.tar.bz2 linux-ccb820dc7d2236b1af0d54ae038a27b5b6d5ae5a.zip | |
fscrypt: destroy keyring after security_sb_delete()
fscrypt_destroy_keyring() must be called after all potentially-encrypted
inodes were evicted; otherwise it cannot safely destroy the keyring.
Since inodes that are in-use by the Landlock LSM don't get evicted until
security_sb_delete(), this means that fscrypt_destroy_keyring() must be
called *after* security_sb_delete().
This fixes a WARN_ON followed by a NULL dereference, only possible if
Landlock was being used on encrypted files.
Fixes: d7e7b9af104c ("fscrypt: stop using keyrings subsystem for fscrypt_master_key")
Cc: stable@vger.kernel.org
Reported-by: syzbot+93e495f6a4f748827c88@syzkaller.appspotmail.com
Link: https://lore.kernel.org/r/00000000000044651705f6ca1e30@google.com
Reviewed-by: Christian Brauner <brauner@kernel.org>
Link: https://lore.kernel.org/r/20230313221231.272498-2-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
Diffstat (limited to 'fs/crypto')
0 files changed, 0 insertions, 0 deletions