This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.26
---
qemu (1:2.5+dfsg-5ubuntu10.26) xenial; urgency=medium
* d/p/ubuntu/lp-1705743-fix-vnc-crash.patch: fix crash when using long or
invalid vnc connection setups (LP: #1705743)
-- Christian Ehrhardt
Using the repro steps above:
1. as-is in Xenial:
ii qemu-system-x86 1:2.5+dfsg-5ubuntu10.25 amd64QEMU full
system emulation binaries (x86)
$ qemu-system-x86_64 -enable-kvm -vnc
unix:/tmp/service/../service/../service/../service/vnc-sock
# due to socat in other shell:
*** Error in
** Description changed:
[Impact]
- * some more uncommon vnc configurations (e.g. very long names, but also
-potentially various other cases that make
-vnc_init_basic_info_from_server_addr fail) will lead to random data
-(after alloc) in a struct that will then be used on
Hello halfdog, or anyone else affected,
Accepted qemu into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-
5ubuntu10.26 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Note just passed regression test run from the ppa fine as expected.
SRU template prepared.
Making it available to the SRU team for evaluation now.
Uploaded as qemu_2.5+dfsg-5ubuntu10.26_source.changes
** Description changed:
+ [Impact]
+
+ * some more uncommon vnc configurations (e.g. very
Ok, I can confirm the ppa fixing this case.
And OTOH it is fixed in qemu >=2.7.
Furthermore the change is very small and easily reviewable (essentially
only changing a malloc to a malloc0 to initialize properly).
I'm marking the tasks accordingly and prep this as an SRU.
** Also affects: qemu
Thanks Sergeev, that is an interesting insight.
$ mkdir /tmp/service
# works
$ qemu-system-x86_64 -enable-kvm -vnc unix:/tmp/service/vnc-sock
# fails
$ qemu-system-x86_64 -enable-kvm -vnc
unix:/tmp/service/../service/../service/../service/vnc-sock
And while these are running in another shell
** Changed in: qemu (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705743
Title:
qemu-system-x86 crashes when VNC connection is established
To manage
I just ran into the same bug (Ubuntu 16.04.4 LTS, fully updated at time
of the comment).
I've played with cmd arguments a little and it seems that the bug is
triggered at some length of the vnc socket path.
This is running okay:
$ qemu-system-x86_64 -enable-kvm -vnc unix:./service/vnc-sock
Also
[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705743
Hi, thanks for taking the time to report the issue!
Can you verify that you have a fully updated system? Also, is this
running on bare-metal, in a container, or in a VM?
I tried reproducing in a lxc container, a uvt image, and on baremetal. I
launched the qemu cli you have, then in another
11 matches
Mail list logo
