October 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1003613] New: Qemu virtio-gpu: memory leak in virtio_gpu_resource_create_2d
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1003613 Bug ID: 1003613 Summary: Qemu virtio-gpu: memory leak in virtio_gpu_resource_create_2d Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Reference: http://seclists.org/oss-sec/2016/q4/53 =================================== Hello, Quick Emulator(Qemu) built with the Virtio GPU Device support is vulnerable to a memory leakage issue. It could occur while processing virtio GPU command VIRTIO_GPU_CMD_RESOURCE_CREATE_2D. A privileged user/process inside guest could use this flaw to exhaust host memory resulting in DoS. Upstream fix: ------------- -> https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg04129.html This issue was reported by Li Qiang of 360.cn Inc. Thank you. -- Prasad J Pandit / Red Hat Product Security Team 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F =================================== -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003612] New: Qemu: usb: hcd-ehci: memory leak in ehci_process_itd
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1003612 Bug ID: 1003612 Summary: Qemu: usb: hcd-ehci: memory leak in ehci_process_itd Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Reference: http://seclists.org/oss-sec/2016/q4/54 =========================== Hello, Qemu emulator(Qemu) built with the USB EHCI emulation support is vulnerable to a memory leakage flaw. It could occur while processing isochronous transfer descriptors(iTD), with buffer page select(PG) index that falls beyond buffer page array area. A privileged user inside guest could use this flaw to leak Qemu memory bytes leading to a DoS on the host. Upstream fix: ------------- -> https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg06609.html Reference: ---------- -> https://bugzilla.redhat.com/show_bug.cgi?id=1382668 This issue was reported by Li Qiang of 360.cn Inc. Thank you. -- Prasad J Pandit / Red Hat Product Security Team 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F =========================== -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003602] New: IP address blocked, links pointing nowhere
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1003602 Bug ID: 1003602 Summary: IP address blocked, links pointing nowhere Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Wiki Assignee: ddemaio(a)novell.com Reporter: aschnell(a)suse.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- I wanted to edit the wiki so I logged in as "aschnell" but the wiki refuses me to do edits: You do not have permission to edit this page, for the following reason: Your IP address has been automatically blocked because it was used by another user, who was blocked by Abuse filter. The reason given is: Autoblocked because your IP address has been recently used by "Xboxonenumber". This is very annoying and blocks work. I authenticated as "aschnell" so I don't see a reasen to be blocked because another user was blocked and had the same IP address. The text suggest to contact "Abuse filter" but the link directs to a non-existing page (so I see a general error page). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 962980] Cannot enable "exec" service in xinetd (rsh-server not installed; available online but not on DVD)
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=962980 http://bugzilla.suse.com/show_bug.cgi?id=962980#c9 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com --- Comment #9 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- After reading the comments, it sounds to me like yast2-inetd is doing what is expected from it. It's quite usual than a given YaST module, to ensure a successful execution, asks for installation of a package it needs. The fact that the user has a "reduced" set of software sources does not make invalid the attempt of yast2-inetd to install a package that is part of the distribution. Maybe the error message can be slightly improved with something like "Not able to install X, make sure your repositories include all the software of the distribution" (with better wording, of course). But other than that improvement, I see no bug here (neither in the content of the ISO or yast2-inetd). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1000094] New: build syzkaller kernel flavor
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1000094 Bug ID: 1000094 Summary: build syzkaller kernel flavor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To use syzkaller package, we need a syzkaller-enabled kernel. Let's provide one. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 995730] iptables -L segfaults from samba winbind name resolution
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=995730 http://bugzilla.suse.com/show_bug.cgi?id=995730#c16 --- Comment #16 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (995730) was mentioned in https://build.opensuse.org/request/show/433727 Factory / samba -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003381] grub2 selected by trying to configure "bootloader" despite "no bootloader can be installed"
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1003381 http://bugzilla.suse.com/show_bug.cgi?id=1003381#c5 --- Comment #5 from Josef Reidinger <jreidinger(a)suse.com> --- question is what is correct way. Propose to use no bootloader or use grub2 and skip doing action there. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003381] grub2 selected by trying to configure "bootloader" despite "no bootloader can be installed"
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1003381 http://bugzilla.suse.com/show_bug.cgi?id=1003381#c4 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger(a)suse.com Assignee|yast2-maintainers(a)suse.de |jreidinger(a)suse.com --- Comment #4 from Josef Reidinger <jreidinger(a)suse.com> --- it should be handled automatic. Problem here is that it sets grub2 bootloader, but in fact for nfs root, it is special handling, but not in packages list. Will fix it for TW -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003381] grub2 selected by trying to configure "bootloader" despite "no bootloader can be installed"
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1003381 http://bugzilla.suse.com/show_bug.cgi?id=1003381#c3 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com, | |per(a)computer.org Flags| |needinfo?(per(a)computer.org) --- Comment #3 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- Per. Even if it's not possible, the installer is trying to install grub2 because that is what is selected in the "booting" section of the final installation settings. If you click on "booting" and select "Not Managed" in the "Boot Loader" field of the "Boot Loader Settings" screen, grub2 should not be installed. Can you please try that? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003195] New: MESA 11.0.8 of LEAP 42.2 beta2 doesn't support AMD RX480 graphics card
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1003195 Bug ID: 1003195 Summary: MESA 11.0.8 of LEAP 42.2 beta2 doesn't support AMD RX480 graphics card Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: Michael.Born(a)aei.mpg.de QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- LEAP 42.2 beta2 doesn't support the new AMD Polaris graphics cards. For the kernel part see [1]. According to [2], a MESA 12 is required. Is it possible, to get support for these newer AMD cards into LEAP 42.2? [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1003192 [2] http://www.phoronix.com/scan.php?page=news_item&px=RX-480-OSS-Steps -- You are receiving this mail because: You are on the CC list for the bug.

1 3