From: "Миронов Сергей Владимирович" <mironov@fintech.ru>
To: "libvirt-security@redhat.com" <libvirt-security@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"libvir-list@redhat.com" <libvir-list@redhat.com>
Cc: "sdl.qemu@linuxtesting.org" <sdl.qemu@linuxtesting.org>
Subject: [sdl-qemu] [PATCH 1/1] No checks, dereferencing possible
Date: Thu, 14 Sep 2023 09:44:16 +0000 [thread overview]
Message-ID: <59e6590ea8a04de788f69709ea4c54f8@fintech.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
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.
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;
chrsrc->type = VIR_DOMAIN_CHR_TYPE_UNIX;
chrsrcpriv->directfd = qemuFDPassDirectNew(name, &videopriv->vhost_user_fd);
--
2.31.1
[-- Attachment #2: Type: text/html, Size: 8560 bytes --]
next reply other threads:[~2023-09-14 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 9:44 Миронов Сергей Владимирович [this message]
2023-09-14 10:22 ` [sdl-qemu] [PATCH 1/1] No checks, dereferencing possible Peter Krempa
2023-09-14 15:10 ` Daniel P. Berrangé
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=59e6590ea8a04de788f69709ea4c54f8@fintech.ru \
--to=mironov@fintech.ru \
--cc=libvir-list@redhat.com \
--cc=libvirt-security@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.