December 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1179905] New: Laptop screen flickers sporadically
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179905 Bug ID: 1179905 Summary: Laptop screen flickers sporadically Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: max(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just installed a Dell Latitude E5270 laptop and noticed that the builtin screen flickers sporadically� for a fraction of a second on both, text console and X. It looks a bit like a lose monitor cable, but I can exclude a hardware problem, because it also happens when I don't even touch the device, but it does not happen under Windows 10 that came preinstalled on the device. I discussed this with Stefan Dirsch and he suspected a bug in KMS. Please let me know what other information you need for tracking this down. ___ � intervals vary between a few seconds and several minutes -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1179946] New: VUL-1: CVE-2020-26266: tensorflow, tensorflow2: Use of unitialized values
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179946 Bug ID: 1179946 Summary: VUL-1: CVE-2020-26266: tensorflow, tensorflow2: Use of unitialized values Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/273147/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: cgoll(a)suse.com Reporter: jsegitz(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2020-26266 In affected versions of TensorFlow under certain cases a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers be filled with the default value of the type but forgetting to default initialize the quantized floating point types in Eigen. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0. Leap and Factory affected References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-26266 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26266 https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eab… https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhxx-j73r… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179944] New: VUL-1: CVE-2020-26267: tensorflow, tensorflow2: tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes leading to DoS if not a permutation
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179944 Bug ID: 1179944 Summary: VUL-1: CVE-2020-26267: tensorflow, tensorflow2: tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes leading to DoS if not a permutation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/273148/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: cgoll(a)suse.com Reporter: jsegitz(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2020-26267 In affected versions of TensorFlow the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0. Leap and Factory affected References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-26267 https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c9f3-9wfr… http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26267 https://github.com/tensorflow/tensorflow/commit/ebc70b7a592420d3d2f359e4b16… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179943] New: VUL-1: CVE-2020-26268: tensorflow, tensorflow2: Segfault due to invalid assumption (immutable memory mapped file)
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179943 Bug ID: 1179943 Summary: VUL-1: CVE-2020-26268: tensorflow, tensorflow2: Segfault due to invalid assumption (immutable memory mapped file) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/273149/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: cgoll(a)suse.com Reporter: jsegitz(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2020-26268 In affected versions of TensorFlow the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-26268 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26268 https://github.com/tensorflow/tensorflow/commit/c1e1fc899ad5f8c725dcbb64700… https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hhvc-g5hv… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179938] VUL-1: CVE-2020-26270: tensorflow, tensorflow2: zero-length input in LSTM/GRU layer can cause DoS
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179938 Maintenance Robot <maint-coord+maintenance_robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179940] New: Gnome Desktop does not keep desktop scaling factor set using the GNOME settings application after a reboot
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179940 Bug ID: 1179940 Summary: Gnome Desktop does not keep desktop scaling factor set using the GNOME settings application after a reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: marc(a)msys.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- If the desktop scaling factor is set to eg. 200% using the GNOME settings application, the setting is lost after a reboot. It is always reset to 100%. If the scaling factor is set using the command line as follows, the setting "survives" a reboot: $ gsettings set org.gnome.desktop.interface scaling-factor 2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178287] Cannot install either tensorflow or tensorflow2 due to missing libgrpc.so.8
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1178287 https://bugzilla.suse.com/show_bug.cgi?id=1178287#c3 --- Comment #3 from Christian Goll <cgoll(a)suse.com> --- > > We should probably update Tensorflow2 to 2.3 or 2.4(-rcX). > > @Christian, any ETA for an update? As there is now also CVE-2020-26270 in bsc#1179938 I will try to speed things up on this. kind regards, Christian -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179938] New: VUL-1: CVE-2020-26270: tensorflow, tensorflow2: zero-length input in LSTM/GRU layer can cause DoS
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179938 Bug ID: 1179938 Summary: VUL-1: CVE-2020-26270: tensorflow, tensorflow2: zero-length input in LSTM/GRU layer can cause DoS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/273151/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: cgoll(a)suse.com Reporter: jsegitz(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2020-26270 In affected versions of TensorFlow running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0. Leap and Factory affected References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-26270 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26270 https://github.com/tensorflow/tensorflow/commit/14755416e364f17fb1870882fa7… https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m648-33qf… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179734] Emulators/wine: Bug /usr/lib*/libwine.so are missing in devel package wine-6.0-rc1
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179734 https://bugzilla.suse.com/show_bug.cgi?id=1179734#c5 --- Comment #5 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1179734) was mentioned in https://build.opensuse.org/request/show/854813 Factory / carla -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179935] New: wpa_ supplicant option -u for dbus support seem to disable socket communication for e.g. wpa_cli
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179935 Bug ID: 1179935 Summary: wpa_ supplicant option -u for dbus support seem to disable socket communication for e.g. wpa_cli Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: aarch64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It drives me creazy as wpa_cli reports always "Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory" and now I've found in the manual page (not installed in the ARM boot images) -u Enable DBus control interface. If enabled, interface definitions may be omitted. (This is only available if wpa_supplicant was built with the CON-FIG_CTRL_IFACE_DBUS_NEW option.) ... means no sockets below /var/run/wpa_supplicant/ ... even no directory /var/run/wpa_supplicant/ at all. This makes wpa_cli as well ad wpa_gui useless ... or all tools have to be movedd forward to use dbus address of the running wpa_ supplicant -- You are receiving this mail because: You are on the CC list for the bug.

1 0