Skip to content

Commit 8ed0579

Browse files
gregkhtorvalds
authored andcommitted
kvm: properly check debugfs dentry before using it
debugfs can now report an error code if something went wrong instead of just NULL. So if the return value is to be used as a "real" dentry, it needs to be checked if it is an error before dereferencing it. This is now happening because of ff9fb72 ("debugfs: return error values, not NULL"). syzbot has found a way to trigger multiple debugfs files attempting to be created, which fails, and then the error code gets passed to dentry_path_raw() which obviously does not like it. Reported-by: Eric Biggers <ebiggers@kernel.org> Reported-and-tested-by: syzbot+7857962b4d45e602b8ad@syzkaller.appspotmail.com Cc: "Radim Krčmář" <rkrcmar@redhat.com> Cc: kvm@vger.kernel.org Acked-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
1 parent 0a1d529 commit 8ed0579

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

virt/kvm/kvm_main.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4044,7 +4044,7 @@ static void kvm_uevent_notify_change(unsigned int type, struct kvm *kvm)
40444044
}
40454045
add_uevent_var(env, "PID=%d", kvm->userspace_pid);
40464046

4047-
if (kvm->debugfs_dentry) {
4047+
if (!IS_ERR_OR_NULL(kvm->debugfs_dentry)) {
40484048
char *tmp, *p = kmalloc(PATH_MAX, GFP_KERNEL);
40494049

40504050
if (p) {

0 commit comments

Comments
 (0)