June 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 982484] New: VUL-0: CVE-2016-4450: [nginx] A specially crafted request might result in worker process crash due to a NULL pointer dereference while writing client request body to a temporary file
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=982484 Bug ID: 982484 Summary: VUL-0: CVE-2016-4450: [nginx] A specially crafted request might result in worker process crash due to a NULL pointer dereference while writing client request body to a temporary file Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: All OS: All 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: --- Info from http://mailman.nginx.org/pipermail/nginx-announce/2016/000179.html : ========================= Hello! A problem was identified in nginx code responsible for saving client request body to a temporary file. A specially crafted request might result in worker process crash due to a NULL pointer dereference while writing client request body to a temporary file (CVE-2016-4450). The problem affects nginx 1.3.9 - 1.11.0. The problem is fixed in nginx 1.11.1, 1.10.1. Patch for nginx 1.9.13 - 1.11.0 can be found here: http://nginx.org/download/patch.2016.write.txt Patch for older nginx versions (1.3.9 - 1.9.12): http://nginx.org/download/patch.2016.write2.txt -- Maxim Dounin http://nginx.org/ ========================= -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 981632] Initial partition setup makes /tmp a btrfs subvolume
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=981632 http://bugzilla.suse.com/show_bug.cgi?id=981632#c2 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |aschnell(a)suse.com Resolution|--- |FEATURE --- Comment #2 from Arvin Schnell <aschnell(a)suse.com> --- The issue was discussed many times. Changing it requires a feature request. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 952621] alx ethernet driver crashes with fatal interrupt 0x4019607, resetting
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=952621 http://bugzilla.opensuse.org/show_bug.cgi?id=952621#c28 --- Comment #28 from Takashi Iwai <tiwai(a)suse.com> --- Only work_around_dma_issue.patch. The new skb alloc isn't enabled in KMP. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 980750] Plymouth prevents loading DRM/KMS driver for newly installed graphics card
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=980750 http://bugzilla.suse.com/show_bug.cgi?id=980750#c3 --- Comment #3 from Ismail Donmez <idonmez(a)suse.com> --- (In reply to Max Staudt from comment #1) > This bug occurs because the DRM driver for the new graphics card is not in > the initrd. > > Plymouth waits for udev to clear its queue, assuming that this means "all > devices in the system have been detected and initialized". When booting the > system with the "plymouth:debug" kernel option, Plymouth's log in > /var/log/plymouth-debug.log shows this as "udev coldplug complete". > > As discussed in the thread referenced in upstream bug > https://bugs.freedesktop.org/show_bug.cgi?id=95356 this situation happens > when switching root from the initrd to the real root. > > At this point, Plymouth will start displaying the splash screen on the > graphics devices existing at that time. If the DRM driver for the graphics > card is included in the initrd, it will have been loaded and replaced any > vesafb/efifb used at early boot time. If, however, the DRM driver is *not* > in the initrd, Plymouth will display its splash screen via vesafb/efifb. > > Next, the system will find the DRM driver for the new card on disk, after > switching to the real root. It will attempt to load it, and in the usual > case it will replace vesafb/efifb (see do_remove_conflicting_framebuffers() > in the Linux kernel). However, since Plymouth has opened /dev/fb0 from > userspace, the driver will be unloaded, but the memory region will not be > freed. Thus, the DRM driver cannot reserve all of the card's VRAM, and will > error out: > > [ 10.375907] fb: switching to bochsdrmfb from EFI VGA > [ 10.375929] Console: switching to colour dummy device 80x25 > [ 10.377266] bochs-drm 0000:00:02.0: BAR 0: can't reserve [mem > 0xfc000000-0xfdffffff pref] > [ 10.377269] [drm:bochs_hw_init [bochs_drm]] *ERROR* Cannot request > framebuffer > [ 10.377275] Trying to free nonexistent resource > <00000000fc000000-00000000fdffffff> > [ 10.377753] bochs-drm: probe of 0000:00:02.0 failed with error -16 > > The result is a system where X accesses the GPU directly using the VESA > driver, and the kernel is unable to display its VTs as /dev/fb0 is already > gone. > > As a workaround, the system can be booted once with "plymouth.enable=0", and > then the initrd can be rebuilt with "mkinitrd". On the next boot, everything > should be working as expected. The upstream "fix" here is just adding a timeout which is well hacky at best. I don't know what would be the right fix here. Any ideas? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982295] signature verification failed repomd.xml (42.1 update oss metadata)
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=982295 http://bugzilla.suse.com/show_bug.cgi?id=982295#c1 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abittner(a)opensuse.org, | |meissner(a)suse.com Flags| |needinfo?(abittner@opensuse | |.org) --- Comment #1 from Marcus Meissner <meissner(a)suse.com> --- i checked this right now, and it seems to be fine now. is this still a problem? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 952621] alx ethernet driver crashes with fatal interrupt 0x4019607, resetting
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=952621 http://bugzilla.opensuse.org/show_bug.cgi?id=952621#c27 --- Comment #27 from Rainer Klier <rainer.klier(a)gmx.at> --- hi Takashi, i installed the new module, and there are no problems yet. but as i am using it only a few hours, this does not really tell us much. but i have a question to you: which patches does the current module you made include? only the latest work_around_dma_issue.patch, or also all the previous patches? do the patches mutually exclude each other, or are they intended to be used together, or can they, but don't have to be used together? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 981836] virt-manager does not support all boot methods for AArch64
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=981836 http://bugzilla.suse.com/show_bug.cgi?id=981836#c3 --- Comment #3 from Andrew Wafaa <awafaa(a)opensuse.org> --- I've use the firmware from Gerd Hoffman and followed the following blog to get the firmware installed which allows me to access the other options (installation failed but for a different reason now) - https://marcin.juszkiewicz.com.pl/2015/04/17/running-vms-on-fedoraaarch64/ What is the best way to improve the out of box experience for people? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982461] New: Plasmashell crashing when waking up multi monitor setup
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=982461 Bug ID: 982461 Summary: Plasmashell crashing when waking up multi monitor setup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: piotrekjuzwiak(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Plasmashell crashes if having a multi monitor setup/display port. When letting the PC to sleep or turn off the display the plasmashell will crash. -- You are receiving this mail because: You are on the CC list for the bug.

1 4