qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: "Миронов Сергей Владимирович" <mironov@fintech.ru>,
	"libvir-list@redhat.com" <libvir-list@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"sdl.qemu@linuxtesting.org" <sdl.qemu@linuxtesting.org>,
	"libvirt-security@redhat.com" <libvirt-security@redhat.com>
Subject: Re: [sdl-qemu] [PATCH 1/1] No checks, dereferencing possible
Date: Thu, 14 Sep 2023 16:10:14 +0100	[thread overview]
Message-ID: <ZQMiVrok25txP4mH@redhat.com> (raw)
In-Reply-To: <ZQLe4uI2xu1cKkB5@angien.pipo.sk>

On Thu, Sep 14, 2023 at 12:22:26PM +0200, Peter Krempa wrote:
> On Thu, Sep 14, 2023 at 09:44:16 +0000, Миронов Сергей Владимирович wrote:
> > No checks, dereferencing possible.
> > 
> > 
> > Return value of a function 'virDomainChrSourceDefNew'
> > is dereferenced at qemu_command.c without checking
> > for NULL, but it is usually checked for this function.
> 
> This description here doesn't make sense. You are checking the presence
> of 'privateData' in 'virDomainVideoDef'.
> 
> > 
> > 
> > Found by Linux Verification Center (linuxtesting.org) with SVACE.
> > 
> > 
> > Fixes: 1f85f0967b ("ci: jobs.sh: Add back '--no-suite syntax-check --print-errorlogs'")
> > 
> > Signed-off-by: Sergey Mironov <mironov@fintech.ru>
> > 
> > ---
> > src/qemu/qemu_command.c | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/src/qemu/qemu_command.c b/src/qemu/qemu_command.c
> > index e84374b4cf..8d11972c88 100644
> > --- a/src/qemu/qemu_command.c
> > +++ b/src/qemu/qemu_command.c
> > @@ -4698,6 +4698,8 @@ qemuBuildVideoCommandLine(virCommand *cmd,
> >              g_autofree char *name = g_strdup_printf("%s-vhost-user", video->info.alias);
> >              qemuDomainChrSourcePrivate *chrsrcpriv = QEMU_DOMAIN_CHR_SOURCE_PRIVATE(chrsrc);
> > 
> > +           if (chrsrc == NULL)
> > +                   return -1;
> 
> This addition doesn't make sense as it's dead code. The private data is
> always allocated and checked that it's non-NULL in the qemu driver via
> the callback in virDomainVideoDefNew.


This is checking the result of  virDomainChrSourceDefNew(), which can
fail as virDomainChrSourceDefInitialize() can fail if virClassNew()
fails its sanity checks.

The check is too late though, as we de-referenced chrsrc in the line
above when we accessed the private data.

> 
> Do you have a call trace that would prove me otherwise?
> 

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2023-09-14 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14  9:44 [sdl-qemu] [PATCH 1/1] No checks, dereferencing possible Миронов Сергей Владимирович
2023-09-14 10:22 ` Peter Krempa
2023-09-14 15:10   ` Daniel P. Berrangé [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZQMiVrok25txP4mH@redhat.com \
    --to=berrange@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=libvirt-security@redhat.com \
    --cc=mironov@fintech.ru \
    --cc=pkrempa@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sdl.qemu@linuxtesting.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).