February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 842093] systemd crash during zypper dup
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=842093 http://bugzilla.opensuse.org/show_bug.cgi?id=842093#c6 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |fbui(a)suse.com Resolution|--- |WONTFIX --- Comment #6 from Franck Bui <fbui(a)suse.com> --- 13.1 has reached EOL and is not supported anymore. Feel free to open a new bug report if this still can be reproduced on a newer/supported distro such as Leap or Tumbleweed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 907715] New: Predictable iSCSI device links are not being created any more in /dev/disks/by-path
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=907715 Bug ID: 907715 Summary: Predictable iSCSI device links are not being created any more in /dev/disks/by-path Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: f+novell(a)congenio.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When an iSCSI target is connected, its corresponding device link under /dev/disk/by-path/ip-<IP_ADDR>:<PORT>-iscsi-<IQN>-iscsi-lun-<LUN#>-part<PART#> is not being created any more. This is extremely limiting, because the real scsi device (say, /dev/sdg1) is quite unpredictable. The reason for this is a patch in upstream systemd: http://cgit.freedesktop.org/systemd/systemd/commit/?id=e98bbfd2074e2b1079b7… Lee Duncan of SuSE Labs has pointed that one out to upstream maintainers (http://lists.freedesktop.org/archives/systemd-devel/2014-October/024155.html) but the bug is still in openSUSE 13.2. Fedora had that one fixed as well (see https://bugzilla.redhat.com/show_bug.cgi?id=1161779) In order to fix this, this patch should be applied: Index: systemd-210/src/udev/udev-builtin-path_id.c =================================================================== --- systemd-210.orig/src/udev/udev-builtin-path_id.c +++ systemd-210/src/udev/udev-builtin-path_id.c @@ -547,6 +547,7 @@ } else if (streq(subsys, "scsi")) { parent = handle_scsi(parent, &path); supported_transport = true; + supported_parent = true; } else if (streq(subsys, "cciss")) { parent = handle_cciss(parent, &path); supported_transport = true; -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1003821] New: [i915] vblank wait timed out on crtc
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1003821 Bug ID: 1003821 Summary: [i915] vblank wait timed out on crtc Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: bpesavento(a)infinito.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Testing Leap 42.2 Beta3 on a laptop with 965GM Intel graphics, /var/lib/systemd/coredump is filling up with dumps. dmesg fills with dumps beginning with: [CODE] [ 7.028052] WARNING: CPU: 1 PID: 33 at ../drivers/gpu/drm/drm_irq.c:1326 drm_wait_one_vblank+0x149/0x180 [drm]() [ 7.028053] vblank wait timed out on crtc 0 [ 7.028073] Modules linked in: ata_piix pcmcia ahci libahci serio_raw firewire_ohci libata yenta_socket firewire_core pcmcia_rsrc crc_itu_t pcmcia_core wmi uhci_hcd ehci_pci i915 video ehci_hcd usbcore usb_common button i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm sg scsi_mod autofs4 [ 7.028076] CPU: 1 PID: 33 Comm: kworker/u4:1 Not tainted 4.4.22-1-default #1 [ 7.028077] Hardware name: Hewlett-Packard HP Compaq 6510b (GB867ET#ABZ)/30C0, BIOS 68DDU Ver. F.20 12/01/2011 [/CODE] typically at boot and apparently when switching from Xorg to VTx consoles. Seems the very same problem already reported in the following bugs: https://bugzilla.suse.com/show_bug.cgi?id=980429 https://bugs.freedesktop.org/show_bug.cgi?id=96441 https://bugs.freedesktop.org/show_bug.cgi?id=93782 Reported here just to make aware that 42.2 is affected too and that coredump filling might prevent smaller systems from booting after a few hours of operation (I had some 5 GiB of dumps after a few days of testing 42.2 beta). -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 960682] systemd-journald warnings on boot
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=960682 http://bugzilla.opensuse.org/show_bug.cgi?id=960682#c1 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui(a)suse.com --- Comment #1 from Franck Bui <fbui(a)suse.com> --- Hi Fabian, can you still reproduce with the latest update ? If so, any idea on how to reproduce ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 976941] journalctl -b shows wrong log entries
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=976941 http://bugzilla.opensuse.org/show_bug.cgi?id=976941#c1 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fbui(a)suse.com Resolution|--- |WONTFIX --- Comment #1 from Franck Bui <fbui(a)suse.com> --- 13.2 has reached EOL and is not supported anymore. Feel free to open a new bug report if this still can be reproduced on a newer/supported distro such as Leap or Tumbleweed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 980324] New: System is booting up. See pam_nologin(8)
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=980324 Bug ID: 980324 Summary: System is booting up. See pam_nologin(8) Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please see this thread: https://lists.opensuse.org/opensuse/2016-05/msg00275.html specifically Andrei's response: https://lists.opensuse.org/opensuse/2016-05/msg00334.html I won't pretend to understand what's going on, it seems to be an issue wrt systemd in the initrd and systemd from root. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1023072] New: VUL-1: podofo: NULL pointer dereference in PdfInfo::GuessFormat (pdfinfo.cpp)
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023072 Bug ID: 1023072 Summary: VUL-1: podofo: NULL pointer dereference in PdfInfo::GuessFormat (pdfinfo.cpp) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 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: --- Ref: http://seclists.org/oss-sec/2017/q1/267 ============================================== Description: podofo is a C++ library to work with the PDF file format. A fuzz on it discovered a NULL pointer access. The upstream project denies me to open a new ticket. So, I’m unable to communicate with them. The complete ASan output: # podofopdfinfo $FILE ==24654==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x0000005149a7 bp 0x7ffe59e91e70 sp 0x7ffe59e91d80 T0) ==24654==The signal is caused by a READ memory access. ==24654==Hint: address points to the zero page. #0 0x5149a6 in PdfInfo::GuessFormat() /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/tools/podofopdfinfo/pdfinfo.cpp:210:19 #1 0x512351 in PdfInfo::OutputDocumentInfo(std::ostream&) /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/tools/podofopdfinfo/pdfinfo.cpp:40:35 #2 0x522132 in main /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/tools/podofopdfinfo/podofopdfinfo.cpp:117:18 #3 0x7fcaaf4b861f in __libc_start_main /var/tmp/portage/sys- libs/glibc-2.22-r4/work/glibc-2.22/csu/libc-start.c:289 #4 0x41e8f8 in _start (/usr/bin/podofopdfinfo+0x41e8f8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/tools/podofopdfinfo/pdfinfo.cpp:210:19 in PdfInfo::GuessFormat() ==24654==ABORTING Affected version: 0.9.4 Fixed version: N/A Commit fix: N/A Credit: This bug was discovered by Agostino Sarubbo of Gentoo. CVE: N/A Reproducer: https://github.com/asarubbo/poc/blob/master/00133-podofo-nullptr-pdfinfo-cpp Timeline: 2017-01-05: bug discovered 2017-02-01: blog post about the issue Note: This bug was found with American Fuzzy Lop. Permalink: https://blogs.gentoo.org/ago/2017/02/01/podofo-null-pointer-dereference-in-… -- Agostino Sarubbo Gentoo Linux Developer ============================================== https://software.opensuse.org/package/podofo TW: 0.9.4 42.(1|2): 0.9.3 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1023071] New: VUL-1: podofo: NULL pointer dereference in PoDoFo::PdfParser::ReadXRefSubsection (PdfParser.cpp)
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023071 Bug ID: 1023071 Summary: VUL-1: podofo: NULL pointer dereference in PoDoFo::PdfParser::ReadXRefSubsection (PdfParser.cpp) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 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: --- Ref: http://seclists.org/oss-sec/2017/q1/266 ============================================================ Description: podofo is a C++ library to work with the PDF file format. A fuzz on it discovered a NULL pointer access. The upstream project denies me to open a new ticket. So, I’m unable to communicate with them. The complete ASan output: # podofopdfinfo $FILE ==9418==ERROR: AddressSanitizer: SEGV on unknown address 0x0000000000d8 (pc 0x7f496cb0ab76 bp 0x7ffff028f9d0 sp 0x7ffff028f148 T0) ==9418==The signal is caused by a WRITE memory access. ==9418==Hint: address points to the zero page. #0 0x7f496cb0ab75 /var/tmp/portage/sys-libs/glibc-2.22- r4/work/glibc-2.22/string/../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1989 #1 0x4c063e in __asan_memcpy /tmp/portage/sys-devel/llvm-3.9.0- r1/work/llvm-3.9.0.src/projects/compiler-rt/lib/asan/asan_interceptors.cc:413 #2 0x7f496dde143c in void std::_Construct(PoDoFo::PdfParser::TXRefEntry*, PoDoFo::PdfParser::TXRefEntry const&) /usr/lib/gcc/x86_64-pc-linux- gnu/4.9.3/include/g++-v4/bits/stl_construct.h:83:38 #3 0x7f496dde143c in void std::__uninitialized_fill_n::__uninit_fill_n(PoDoFo::PdfParser::TXRefEntry*, unsigned long, PoDoFo::PdfParser::TXRefEntry const&) /usr/lib/gcc/x86_64-pc- linux-gnu/4.9.3/include/g++-v4/bits/stl_uninitialized.h:202 #4 0x7f496dde143c in void std::uninitialized_fill_n(PoDoFo::PdfParser::TXRefEntry*, unsigned long, PoDoFo::PdfParser::TXRefEntry const&) /usr/lib/gcc/x86_64-pc-linux- gnu/4.9.3/include/g++-v4/bits/stl_uninitialized.h:244 #5 0x7f496dde143c in void std::__uninitialized_fill_n_a(PoDoFo::PdfParser::TXRefEntry*, unsigned long, PoDoFo::PdfParser::TXRefEntry const&, std::allocator&) /usr/lib/gcc/x86_64-pc- linux-gnu/4.9.3/include/g++-v4/bits/stl_uninitialized.h:355 #6 0x7f496dde143c in std::vector<PoDoFo::PdfParser::TXRefEntry, std::allocator ::_M_fill_insert(__gnu_cxx::__normal_iterator<PoDoFo::PdfParser::TXRefEntry*, std::vector<PoDoFo::PdfParser::TXRefEntry, std::allocator > >, unsigned long, PoDoFo::PdfParser::TXRefEntry const&) /usr/lib/gcc/x86_64-pc-linux- gnu/4.9.3/include/g++-v4/bits/vector.tcc:496 #7 0x7f496ddd4a67 in std::vector<PoDoFo::PdfParser::TXRefEntry, std::allocator ::insert(__gnu_cxx::__normal_iterator<PoDoFo::PdfParser::TXRefEntry*, std::vector<PoDoFo::PdfParser::TXRefEntry, std::allocator > >, unsigned long, PoDoFo::PdfParser::TXRefEntry const&) /usr/lib/gcc/x86_64-pc-linux- gnu/4.9.3/include/g++-v4/bits/stl_vector.h:1073:9 #8 0x7f496ddd4a67 in std::vector<PoDoFo::PdfParser::TXRefEntry, std::allocator >::resize(unsigned long, PoDoFo::PdfParser::TXRefEntry) /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include/g++-v4/bits/stl_vector.h:716 #9 0x7f496ddd4a67 in PoDoFo::PdfParser::ReadXRefSubsection(long&, long&) /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/src/base/PdfParser.cpp:772 #10 0x7f496ddc60bd in PoDoFo::PdfParser::ReadXRefContents(long, bool) /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/src/base/PdfParser.cpp:725:17 #11 0x7f496ddbfaae in PoDoFo::PdfParser::ReadDocumentStructure() /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/src/base/PdfParser.cpp:337:9 #12 0x7f496ddbce1f in PoDoFo::PdfParser::ParseFile(PoDoFo::PdfRefCountedInputDevice const&, bool) /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/src/base/PdfParser.cpp:220:9 #13 0x7f496ddbb1e4 in PoDoFo::PdfParser::ParseFile(char const*, bool) /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/src/base/PdfParser.cpp:164:11 #14 0x7f496e018393 in PoDoFo::PdfMemDocument::Load(char const*) /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/src/doc/PdfMemDocument.cpp:186:16 #15 0x7f496e018062 in PoDoFo::PdfMemDocument::PdfMemDocument(char const*) /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/src/doc/PdfMemDocument.cpp:88:11 #16 0x511b44 in PdfInfo::PdfInfo(std::string const&) /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/tools/podofopdfinfo/pdfinfo.cpp:25:16 #17 0x521ac8 in main /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/tools/podofopdfinfo/podofopdfinfo.cpp:110:15 #18 0x7f496c9f461f in __libc_start_main /var/tmp/portage/sys- libs/glibc-2.22-r4/work/glibc-2.22/csu/libc-start.c:289 #19 0x41e8f8 in _start (/usr/bin/podofopdfinfo+0x41e8f8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /var/tmp/portage/sys-libs/glibc-2.22- r4/work/glibc-2.22/string/../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1989 ==9418==ABORTING Affected version: 0.9.4 Fixed version: N/A Commit fix: N/A Credit: This bug was discovered by Agostino Sarubbo of Gentoo. CVE: N/A Reproducer: https://github.com/asarubbo/poc/blob/master/00134-podofo-nullptr-pdfparser-… Timeline: 2017-01-05: bug discovered 2017-02-01: blog post about the issue Note: This bug was found with American Fuzzy Lop. Permalink: https://blogs.gentoo.org/ago/2017/02/01/podofo-null-pointer-dereference-in-… -- Agostino Sarubbo Gentoo Linux Developer ============================================================ https://software.opensuse.org/package/podofo TW: 0.9.4 42.(1|2): 0.9.3 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1023070] New: VUL-1: podofo: NULL pointer dereference in PdfOutputStream.cpp
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023070 Bug ID: 1023070 Summary: VUL-1: podofo: NULL pointer dereference in PdfOutputStream.cpp Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 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: --- Ref: http://seclists.org/oss-sec/2017/q1/265 =============================================== Description: podofo is a C++ library to work with the PDF file format. A fuzz on it with the UBSAN discovered a NULL pointer access. The upstream project denies me to open a new ticket. So, I’m unable to communicate with them. The complete UBSan output: # podofopdfinfo $FILE /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/src/base/PdfOutputStream.cpp:116:33: runtime error: null pointer passed as argument 2, which is declared to never be null Affected version: 0.9.4 Fixed version: N/A Commit fix: N/A Credit: This bug was discovered by Agostino Sarubbo of Gentoo. CVE: N/A Reproducer: https://github.com/asarubbo/poc/blob/master/00143-podofo-nullptr-PdfOutputS… Timeline: 2017-01-05: bug discovered 2017-02-01: blog post about the issue Note: This bug was found with American Fuzzy Lop. Permalink: https://blogs.gentoo.org/ago/2017/02/01/podofo-null-pointer-dereference-in-… -- Agostino Sarubbo Gentoo Linux Developer =============================================== https://software.opensuse.org/package/podofo TW: 0.9.4 42.(1|2): 0.9.3 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1023069] New: VUL-1: podofo: signed integer overflow in PdfParser.cpp
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023069 Bug ID: 1023069 Summary: VUL-1: podofo: signed integer overflow in PdfParser.cpp Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 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: --- Ref: http://seclists.org/oss-sec/2017/q1/264 =============================================== Description: podofo is a C++ library to work with the PDF file format. A fuzz on it with the UBSAN discovered a signed integer overflow. The upstream project denies me to open a new ticket. So, I’m unable to communicate with them. The complete UBSan output: # podofopdfinfo $FILE /tmp/portage/app- text/podofo-0.9.4/work/podofo-0.9.4/src/base/PdfParser.cpp:757:23: runtime error: signed integer overflow: 9223372036854775807 + 9 cannot be represented in type 'long' Affected version: 0.9.4 Fixed version: N/A Commit fix: N/A Credit: This bug was discovered by Agostino Sarubbo of Gentoo. CVE: N/A Reproducer: https://github.com/asarubbo/poc/blob/master/00144-podofo-signintoverflow-Pd… Timeline: 2017-01-05: bug discovered 2017-02-01: blog post about the issue Note: This bug was found with American Fuzzy Lop. Permalink: https://blogs.gentoo.org/ago/2017/02/01/podofo-signed-integer-overflow-in-p… -- Agostino Sarubbo Gentoo Linux Developer =============================================== https://software.opensuse.org/package/podofo TW: 0.9.4 42.(1|2): 0.9.3 -- You are receiving this mail because: You are on the CC list for the bug.

1 0