linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] kvm: properly check debugfs dentry before using it
@ 2019-02-28 15:34 Greg Kroah-Hartman
  2019-02-28 16:58 ` Linus Torvalds
  2019-02-28 17:17 ` Eric Biggers
  0 siblings, 2 replies; 7+ messages in thread
From: Greg Kroah-Hartman @ 2019-02-28 15:34 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Paolo Bonzini, Radim Krčmář,
	Eric Biggers, kvm, syzbot, linux-fsdevel, linux-kernel,
	penguin-kernel, syzkaller-bugs, viro

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 ff9fb72bc077 ("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>
---

Linus, this should go in before 5.0-final is out, as it resolves a
problem found by syzbot.  Paolo has given his ack for me to send this
directly to you.  If you want this in [GIT PULL] format, I can do that
as well.

 virt/kvm/kvm_main.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -4044,7 +4044,7 @@ static void kvm_uevent_notify_change(uns
 	}
 	add_uevent_var(env, "PID=%d", kvm->userspace_pid);
 
-	if (kvm->debugfs_dentry) {
+	if (!IS_ERR_OR_NULL(kvm->debugfs_dentry)) {
 		char *tmp, *p = kmalloc(PATH_MAX, GFP_KERNEL);
 
 		if (p) {

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH] kvm: properly check debugfs dentry before using it
  2019-02-28 15:34 [PATCH] kvm: properly check debugfs dentry before using it Greg Kroah-Hartman
@ 2019-02-28 16:58 ` Linus Torvalds
  2019-02-28 17:17 ` Eric Biggers
  1 sibling, 0 replies; 7+ messages in thread
From: Linus Torvalds @ 2019-02-28 16:58 UTC (permalink / raw)
  To: Greg Kroah-Hartman
  Cc: Paolo Bonzini, Radim Krčmář,
	Eric Biggers, KVM list, syzbot, linux-fsdevel,
	Linux List Kernel Mailing, Tetsuo Handa, syzkaller-bugs, Al Viro

On Thu, Feb 28, 2019 at 7:34 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> Linus, this should go in before 5.0-final is out, as it resolves a
> problem found by syzbot.  Paolo has given his ack for me to send this
> directly to you.  If you want this in [GIT PULL] format, I can do that
> as well.

Applied, thanks,

           Linus

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH] kvm: properly check debugfs dentry before using it
  2019-02-28 15:34 [PATCH] kvm: properly check debugfs dentry before using it Greg Kroah-Hartman
  2019-02-28 16:58 ` Linus Torvalds
@ 2019-02-28 17:17 ` Eric Biggers
  2019-02-28 18:04   ` Greg Kroah-Hartman
  1 sibling, 1 reply; 7+ messages in thread
From: Eric Biggers @ 2019-02-28 17:17 UTC (permalink / raw)
  To: Greg Kroah-Hartman
  Cc: Linus Torvalds, Paolo Bonzini, Radim Krčmář,
	kvm, syzbot, linux-fsdevel, linux-kernel, penguin-kernel,
	syzkaller-bugs, viro

On Thu, Feb 28, 2019 at 04:34:37PM +0100, Greg Kroah-Hartman wrote:
> 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 ff9fb72bc077 ("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>
> ---
> 
> Linus, this should go in before 5.0-final is out, as it resolves a
> problem found by syzbot.  Paolo has given his ack for me to send this
> directly to you.  If you want this in [GIT PULL] format, I can do that
> as well.
> 
>  virt/kvm/kvm_main.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -4044,7 +4044,7 @@ static void kvm_uevent_notify_change(uns
>  	}
>  	add_uevent_var(env, "PID=%d", kvm->userspace_pid);
>  
> -	if (kvm->debugfs_dentry) {
> +	if (!IS_ERR_OR_NULL(kvm->debugfs_dentry)) {
>  		char *tmp, *p = kmalloc(PATH_MAX, GFP_KERNEL);
>  
>  		if (p) {

So what about the other checks of kvm->debugfs_dentry, in
kvm_destroy_vm_debugfs() and kvm_create_vcpu_debugfs()?

- Eric

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH] kvm: properly check debugfs dentry before using it
  2019-02-28 17:17 ` Eric Biggers
@ 2019-02-28 18:04   ` Greg Kroah-Hartman
  0 siblings, 0 replies; 7+ messages in thread
From: Greg Kroah-Hartman @ 2019-02-28 18:04 UTC (permalink / raw)
  To: Eric Biggers
  Cc: Linus Torvalds, Paolo Bonzini, Radim Krčmář,
	kvm, syzbot, linux-fsdevel, linux-kernel, penguin-kernel,
	syzkaller-bugs, viro

On Thu, Feb 28, 2019 at 09:17:28AM -0800, Eric Biggers wrote:
> On Thu, Feb 28, 2019 at 04:34:37PM +0100, Greg Kroah-Hartman wrote:
> > 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 ff9fb72bc077 ("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>
> > ---
> > 
> > Linus, this should go in before 5.0-final is out, as it resolves a
> > problem found by syzbot.  Paolo has given his ack for me to send this
> > directly to you.  If you want this in [GIT PULL] format, I can do that
> > as well.
> > 
> >  virt/kvm/kvm_main.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > --- a/virt/kvm/kvm_main.c
> > +++ b/virt/kvm/kvm_main.c
> > @@ -4044,7 +4044,7 @@ static void kvm_uevent_notify_change(uns
> >  	}
> >  	add_uevent_var(env, "PID=%d", kvm->userspace_pid);
> >  
> > -	if (kvm->debugfs_dentry) {
> > +	if (!IS_ERR_OR_NULL(kvm->debugfs_dentry)) {
> >  		char *tmp, *p = kmalloc(PATH_MAX, GFP_KERNEL);
> >  
> >  		if (p) {
> 
> So what about the other checks of kvm->debugfs_dentry, in
> kvm_destroy_vm_debugfs() and kvm_create_vcpu_debugfs()?

Those are fine, they do not matter as they are only calling other
debugfs calls which can handle error codes just fine.  The only issue is
when you try to use the dentry for something "real" like this that bad
things can happen.

Luckily this was only the case in about 4 places in the kernel, all of
which should be fixed now.

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH] kvm: properly check debugfs dentry before using it
  2019-02-28 15:14       ` Paolo Bonzini
@ 2019-02-28 15:32         ` Greg Kroah-Hartman
  0 siblings, 0 replies; 7+ messages in thread
From: Greg Kroah-Hartman @ 2019-02-28 15:32 UTC (permalink / raw)
  To: Paolo Bonzini
  Cc: Radim Krčmář,
	Eric Biggers, kvm, syzbot, linux-fsdevel, linux-kernel,
	penguin-kernel, syzkaller-bugs, viro

On Thu, Feb 28, 2019 at 04:14:50PM +0100, Paolo Bonzini wrote:
> On 28/02/19 16:08, Greg Kroah-Hartman wrote:
> > 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 ff9fb72bc077 ("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: Paolo Bonzini <pbonzini@redhat.com>
> > Cc: "Radim Krčmář" <rkrcmar@redhat.com>
> > Cc: kvm@vger.kernel.org
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > 
> > ---
> > 
> > Paolo, this should be merged into 5.0-final, and if not there, then
> > 5.1-rc1 and then backported to 5.0 through the stable tree.  If you
> > want me to send this to Linus, I will be glad to do so.
> > 
> > 
> > diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> > index 585845203db8..076bc38963bf 100644
> > --- a/virt/kvm/kvm_main.c
> > +++ b/virt/kvm/kvm_main.c
> > @@ -4044,7 +4044,7 @@ static void kvm_uevent_notify_change(unsigned int type, struct kvm *kvm)
> >  	}
> >  	add_uevent_var(env, "PID=%d", kvm->userspace_pid);
> >  
> > -	if (kvm->debugfs_dentry) {
> > +	if (!IS_ERR_OR_NULL(kvm->debugfs_dentry)) {
> >  		char *tmp, *p = kmalloc(PATH_MAX, GFP_KERNEL);
> >  
> >  		if (p) {
> > 
> 
> Sure, go ahead.
> 
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>

Wonderful, will do so right now, thanks!

greg k-h

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH] kvm: properly check debugfs dentry before using it
  2019-02-28 15:08     ` [PATCH] kvm: properly check debugfs dentry before using it Greg Kroah-Hartman
@ 2019-02-28 15:14       ` Paolo Bonzini
  2019-02-28 15:32         ` Greg Kroah-Hartman
  0 siblings, 1 reply; 7+ messages in thread
From: Paolo Bonzini @ 2019-02-28 15:14 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Radim Krčmář, Eric Biggers
  Cc: kvm, syzbot, linux-fsdevel, linux-kernel, penguin-kernel,
	syzkaller-bugs, viro

On 28/02/19 16:08, Greg Kroah-Hartman wrote:
> 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 ff9fb72bc077 ("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: Paolo Bonzini <pbonzini@redhat.com>
> Cc: "Radim Krčmář" <rkrcmar@redhat.com>
> Cc: kvm@vger.kernel.org
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> ---
> 
> Paolo, this should be merged into 5.0-final, and if not there, then
> 5.1-rc1 and then backported to 5.0 through the stable tree.  If you
> want me to send this to Linus, I will be glad to do so.
> 
> 
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 585845203db8..076bc38963bf 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -4044,7 +4044,7 @@ static void kvm_uevent_notify_change(unsigned int type, struct kvm *kvm)
>  	}
>  	add_uevent_var(env, "PID=%d", kvm->userspace_pid);
>  
> -	if (kvm->debugfs_dentry) {
> +	if (!IS_ERR_OR_NULL(kvm->debugfs_dentry)) {
>  		char *tmp, *p = kmalloc(PATH_MAX, GFP_KERNEL);
>  
>  		if (p) {
> 

Sure, go ahead.

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

Paolo

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [PATCH] kvm: properly check debugfs dentry before using it
  2019-02-26 19:19   ` Eric Biggers
@ 2019-02-28 15:08     ` Greg Kroah-Hartman
  2019-02-28 15:14       ` Paolo Bonzini
  0 siblings, 1 reply; 7+ messages in thread
From: Greg Kroah-Hartman @ 2019-02-28 15:08 UTC (permalink / raw)
  To: Paolo Bonzini, Radim Krčmář, Eric Biggers
  Cc: kvm, syzbot, linux-fsdevel, linux-kernel, penguin-kernel,
	syzkaller-bugs, viro

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 ff9fb72bc077 ("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: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: kvm@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

---

Paolo, this should be merged into 5.0-final, and if not there, then
5.1-rc1 and then backported to 5.0 through the stable tree.  If you
want me to send this to Linus, I will be glad to do so.


diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index 585845203db8..076bc38963bf 100644
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -4044,7 +4044,7 @@ static void kvm_uevent_notify_change(unsigned int type, struct kvm *kvm)
 	}
 	add_uevent_var(env, "PID=%d", kvm->userspace_pid);
 
-	if (kvm->debugfs_dentry) {
+	if (!IS_ERR_OR_NULL(kvm->debugfs_dentry)) {
 		char *tmp, *p = kmalloc(PATH_MAX, GFP_KERNEL);
 
 		if (p) {

^ permalink raw reply related	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2019-02-28 18:04 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-28 15:34 [PATCH] kvm: properly check debugfs dentry before using it Greg Kroah-Hartman
2019-02-28 16:58 ` Linus Torvalds
2019-02-28 17:17 ` Eric Biggers
2019-02-28 18:04   ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2019-01-30 10:35 general protection fault in __dentry_path syzbot
2019-02-21  4:14 ` syzbot
2019-02-26 19:19   ` Eric Biggers
2019-02-28 15:08     ` [PATCH] kvm: properly check debugfs dentry before using it Greg Kroah-Hartman
2019-02-28 15:14       ` Paolo Bonzini
2019-02-28 15:32         ` Greg Kroah-Hartman

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).