May 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1185624] System freezing, Several Memory Management issues, and Shutdown problem after Kernel updated to 5.12.0
by bugzilla_noreply＠suse.com 06 May '21

06 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185624 https://bugzilla.suse.com/show_bug.cgi?id=1185624#c8 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(behzad.a_ir@hotma | |il.com) | --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Behzad A from comment #6) > If you report these issues to the upstream source I think it would be better > than I do it, especially for easier tracking the issue, of course, if you > want, I can do it. Yes, please report from your side, and tell us the issues URL. It's usually a pain to report without the hardware in question locally. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185746] New: [Build 20210505] libyui segfault
by bugzilla_noreply＠suse.com 06 May '21

06 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185746 Bug ID: 1185746 Summary: [Build 20210505] libyui segfault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1729867/modules/yast 2_system_settings/steps/33 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_gui@64bit fails in [yast2_system_settings](https://openqa.opensuse.org/tests/1729867/modules/ya… [ 384.772788] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/yast.rb:204: [BUG] Segmentation fault at 0x0000000000000008 [ 384.774115] gnome-shell[3835]: ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x86_64-linux-gnu] [ 384.775085] gnome-shell[3835]: -- Control frame information ----------------------------------------------- [ 384.775796] gnome-shell[3835]: c:0024 p:---- s:0167 e:000166 CFUNC :call_yast_function [ 384.776428] gnome-shell[3835]: c:0023 p:0060 s:0159 e:000158 BLOCK /usr/lib64/ruby/vendor_ruby/2.7.0/yast/yast.rb:204 [FINISH] [ 384.777295] gnome-shell[3835]: c:0022 p:0138 s:0155 e:000154 METHOD /usr/share/YaST2/modules/CWM.rb:793 [ 384.778006] gnome-shell[3835]: c:0021 p:0375 s:0141 E:001ee8 METHOD /usr/share/YaST2/modules/CWM.rb:975 [ 384.778733] gnome-shell[3835]: c:0020 p:0272 s:0124 e:000123 METHOD /usr/share/YaST2/include/hwinfo/system_settings_dialogs.rb:158 [ 384.783640] gnome-shell[3835]: c:0019 p:0004 s:0117 e:000116 BLOCK /usr/share/YaST2/clients/system_settings.rb:39 [ 384.784480] gnome-shell[3835]: c:0018 p:0012 s:0114 e:000113 METHOD /usr/lib64/ruby/vendor_ruby/2.7.0/yast/builtins.rb:546 [ 384.785253] gnome-shell[3835]: c:0017 p:0081 s:0109 e:000108 METHOD /usr/share/YaST2/modules/Sequencer.rb:249 [ 384.785977] gnome-shell[3835]: c:0016 p:0089 s:0101 e:000100 BLOCK /usr/share/YaST2/modules/Sequencer.rb:320 [FINISH] [ 384.786767] gnome-shell[3835]: c:0015 p:---- s:0095 e:000094 CFUNC :loop [ 384.787341] gnome-shell[3835]: c:0014 p:0098 s:0091 e:000090 METHOD /usr/share/YaST2/modules/Sequencer.rb:312 [ 384.788138] gnome-shell[3835]: c:0013 p:0043 s:0083 e:000082 METHOD /usr/share/YaST2/clients/system_settings.rb:66 [FINISH] [ 384.788940] gnome-shell[3835]: c:0012 p:---- s:0078 e:000077 CFUNC :call [ 384.789485] gnome-shell[3835]: c:0011 p:0009 s:0074 e:000073 METHOD /usr/lib64/ruby/vendor_ruby/2.7.0/yast/fun_ref.rb:33 [ 384.790351] gnome-shell[3835]: c:0010 p:0234 s:0069 e:000068 METHOD /usr/share/YaST2/modules/CommandLine.rb:1566 [ 384.791111] gnome-shell[3835]: c:0009 p:0205 s:0054 E:000c00 METHOD /usr/share/YaST2/clients/system_settings.rb:56 [ 384.791868] gnome-shell[3835]: c:0008 p:0025 s:0050 e:000049 EVAL /usr/share/YaST2/clients/system_settings.rb:76 [FINISH] [ 384.792734] gnome-shell[3835]: c:0007 p:---- s:0047 e:000046 CFUNC :eval [ 384.793373] gnome-shell[3835]: c:0006 p:0073 s:0040 e:000039 METHOD /usr/lib64/ruby/vendor_ruby/2.7.0/yast/wfm.rb:346 [FINISH] [ 384.794333] gnome-shell[3835]: c:0005 p:---- s:0032 e:000031 CFUNC :call_builtin [ 384.794945] gnome-shell[3835]: c:0004 p:0041 s:0023 e:000022 METHOD /usr/lib64/ruby/vendor_ruby/2.7.0/yast/wfm.rb:207 [ 384.795813] gnome-shell[3835]: c:0003 p:0117 s:0017 e:000016 METHOD /usr/lib64/ruby/vendor_ruby/2.7.0/yast/wfm.rb:196 [ 384.796613] gnome-shell[3835]: c:0002 p:0455 s:0011 E:001188 EVAL /usr/lib/YaST2/bin/y2start:60 [FINISH] [ 384.797338] gnome-shell[3835]: c:0001 p:0000 s:0003 E:000b20 (none) [FINISH] [ 384.797956] gnome-shell[3835]: -- Ruby level backtrace information ---------------------------------------- [ 384.798807] gnome-shell[3835]: /usr/lib/YaST2/bin/y2start:60:in `<main>' [ 384.799413] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/wfm.rb:196:in `CallFunction' [ 384.800101] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/wfm.rb:207:in `call_builtin_wrapper' [ 384.800964] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/wfm.rb:207:in `call_builtin' [ 384.801644] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/wfm.rb:346:in `run_client' [ 384.802389] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/wfm.rb:346:in `eval' [ 384.803048] gnome-shell[3835]: /usr/share/YaST2/clients/system_settings.rb:76:in `<top (required)>' [ 384.803826] gnome-shell[3835]: /usr/share/YaST2/clients/system_settings.rb:56:in `main' [ 384.804480] gnome-shell[3835]: /usr/share/YaST2/modules/CommandLine.rb:1566:in `Run' [ 384.805092] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/fun_ref.rb:33:in `call' [ 384.807118] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/fun_ref.rb:33:in `call' [ 384.807766] gnome-shell[3835]: /usr/share/YaST2/clients/system_settings.rb:66:in `GUIhandler' [ 384.808433] gnome-shell[3835]: /usr/share/YaST2/modules/Sequencer.rb:312:in `Run' [ 384.809025] gnome-shell[3835]: /usr/share/YaST2/modules/Sequencer.rb:312:in `loop' [ 384.809641] gnome-shell[3835]: /usr/share/YaST2/modules/Sequencer.rb:320:in `block in Run' [ 384.810410] gnome-shell[3835]: /usr/share/YaST2/modules/Sequencer.rb:249:in `WS_run' [ 384.811088] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/builtins.rb:546:in `eval' [ 384.811857] gnome-shell[3835]: /usr/share/YaST2/clients/system_settings.rb:39:in `block in main' [ 384.812573] gnome-shell[3835]: /usr/share/YaST2/include/hwinfo/system_settings_dialogs.rb:158:in `SystemSettingsDialog' [ 384.813397] gnome-shell[3835]: /usr/share/YaST2/modules/CWM.rb:975:in `ShowAndRun' [ 384.814095] gnome-shell[3835]: /usr/share/YaST2/modules/CWM.rb:793:in `Run' [ 384.814705] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/yast.rb:204:in `block (2 levels) in import' [ 384.815448] gnome-shell[3835]: /usr/lib64/ruby/vendor_ruby/2.7.0/yast/yast.rb:204:in `call_yast_function' [ 384.816169] gnome-shell[3835]: -- Machine register context ------------------------------------------------ [ 384.816866] gnome-shell[3835]: RIP: 0x00007fa6f495c17e RBP: 0x00007fa6ec466550 RSP: 0x00007fa6f137cc38 [ 384.817555] gnome-shell[3835]: RAX: 0x0000000000000000 RBX: 0x00007fa6ec3f5e70 RCX: 0x0000000000000006 [ 384.818312] gnome-shell[3835]: RDX: 0x00007fa6ec466550 RDI: 0x00007fa6f137ceb0 RSI: 0x00007fa6f137cd20 [ 384.818997] gnome-shell[3835]: R8: 0x00007fa6ec466550 R9: 0x00007fa6f49a8458 R10: 0x0000000000000000 [ 384.819731] gnome-shell[3835]: R11: 0xfffffffffffff70e R12: 0x00007fa6ec466550 R13: 0x00007fa6ec646b20 [ 384.820490] gnome-shell[3835]: R14: 0x00007fa6f49a8458 R15: 0x00007fa6f137cdf8 EFL: 0x0000000000010246 [ 384.821206] gnome-shell[3835]: -- C level backtrace information ------------------------------------------- libyui was updated in snapshot 0505, but the changelog is: Version update (4.2.8 -> 4.2.10) - Added pkgconfig files for libyui-qt and libyui-ncurses for writing extensions of the Qt and NCurses plug-ins (GitHub issue #9 / bsc#1139747) - 4.2.10 This does not indicate in any way that an ABI break could be expected (and there was, a soname bump would have been in order) ## Test suite description Maintainer: qsf-y Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests. Temporarily added YAST2_GUI_TERMINATE_PREVIOUS_INSTANCES to see if helps. This variable triggers code which terminates all yast2 processes before starting new one. (see poo#26104). ## Reproducible Fails since (at least) Build [20210505](https://openqa.opensuse.org/tests/1729595) ## Expected result Last good: [20210504](https://openqa.opensuse.org/tests/1728189) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177395] New: gnome-software defunct/hangs after resume from suspend (affects checking for updates)
by bugzilla_noreply＠suse.com 06 May '21

06 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 Bug ID: 1177395 Summary: gnome-software defunct/hangs after resume from suspend (affects checking for updates) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: kwizzz(a)googlemail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 842334 --> http://bugzilla.opensuse.org/attachment.cgi?id=842334&action=edit output of gnome-software --verbose Usually, gnome-software initiates the check for updates once a day. However, after suspending and then resuming my laptop the next day, gnome-software is kinda dead: 1. No active checks for updates are performed (confirmed via dconf dump /org/gnome/software/) 2. gnome-software UI hangs anyways: - listing the Software Repositories results in a forever-and-ever loading pop-up window - clicking on Updates shows that last check has been performed yesterday; clicking on the refresh button ends up in forever-and-ever "checking for updates" Attached is output of `gnome-software --verbose`, including my annotations. This is packagekit status: .............................................. linux:~ # systemctl status packagekit ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: inactive (dead) Oct 06 13:00:31 localhost.localdomain systemd[1]: Starting PackageKit Daemon... Oct 06 13:00:31 localhost.localdomain PackageKit[11090]: daemon start Oct 06 13:00:31 localhost.localdomain systemd[1]: Started PackageKit Daemon. Oct 06 13:00:31 localhost.localdomain PackageKit[11090]: uid 1001 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Oct 06 13:00:31 localhost.localdomain PackageKit[11090]: uid 1001 obtained auth for org.freedesktop.packagekit.system-sources-refresh Oct 06 13:00:49 linux.fritz.box PackageKit[11090]: refresh-cache transaction /1_abeeeddb from uid 1001 finished with success after 18176ms Oct 06 13:00:49 linux.fritz.box PackageKit[11090]: uid 1001 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Oct 06 13:00:49 linux.fritz.box PackageKit[11090]: uid 1001 obtained auth for org.freedesktop.packagekit.system-sources-refresh Oct 06 13:00:53 linux.fritz.box PackageKit[11090]: refresh-cache transaction /2_dcaabaec from uid 1001 finished with success after 3350ms Oct 06 13:05:56 linux.fritz.box PackageKit[11090]: daemon quit .............................................. (My time zone is UTC+2 (for comparing gnome-software's output with above packagekit status)) After this, I started Package Updater => found updates and installed them. This is packagekit status after this: .............................................. linux:~ # systemctl status packagekit ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: inactive (dead) Oct 06 18:21:10 linux.fritz.box PackageKit[16906]: in /2_cbcbecab for update-packages package libdevmapper1_03;1.02.163-lp152.7.6.1;x86_64;repo-update was installing fo> Oct 06 18:21:10 linux.fritz.box PackageKit[16906]: in /2_cbcbecab for update-packages package liblvm2cmd2_03;2.03.05-lp152.7.6.1;x86_64;repo-update was installing for u> Oct 06 18:21:10 linux.fritz.box PackageKit[16906]: in /2_cbcbecab for update-packages package libopenssl1_1;1.1.1d-lp152.7.3.1;x86_64;repo-update was installing for uid> Oct 06 18:21:10 linux.fritz.box PackageKit[16906]: in /2_cbcbecab for update-packages package libdevmapper-event1_03;1.02.163-lp152.7.6.1;x86_64;repo-update was install> Oct 06 18:21:10 linux.fritz.box PackageKit[16906]: in /2_cbcbecab for update-packages package openssl-1_1;1.1.1d-lp152.7.3.1;x86_64;repo-update was installing for uid 1> Oct 06 18:21:10 linux.fritz.box PackageKit[16906]: in /2_cbcbecab for update-packages package device-mapper;1.02.163-lp152.7.6.1;x86_64;repo-update was installing for u> Oct 06 18:21:10 linux.fritz.box PackageKit[16906]: in /2_cbcbecab for update-packages package lvm2;2.03.05-lp152.7.6.1;x86_64;repo-update was installing for uid 1001 Oct 06 18:21:10 linux.fritz.box PackageKit[16906]: update-packages transaction /2_cbcbecab from uid 1001 finished with success after 30586ms Oct 06 18:21:13 linux.fritz.box PackageKit[16906]: get-updates transaction /3_dccdebeb from uid 1001 finished with success after 2951ms Oct 06 18:21:32 linux.fritz.box PackageKit[16906]: daemon quit .............................................. -- You are receiving this mail because: You are on the CC list for the bug.

1 34

[Bug 1185735] New: cifs-utils: crash when non existant mountpoint
by bugzilla_noreply＠suse.com 06 May '21

06 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185735 Bug ID: 1185735 Summary: cifs-utils: crash when non existant mountpoint Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: mrueckert(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- ``` #5 0x00007f12c320e9bb in __GI___libc_free (mem=mem@entry=0x7ffcb27736c4) at malloc.c:3302 #6 0x0000563a5fbfe8de in main (argc=<optimized out>, argv=<optimized out>) at mount.cifs.c:2351 ``` ``` (gdb) l 2346 mount_child_exit: 2347 /* Objects to be freed both in main process and child */ 2348 free(reinit_parsed_info); 2349 free(options); 2350 free(orgoptions); 2351 free(mountpoint); 2352 return rc; 2353 } ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1185693] Kernel 5.12: sound not working on Baytrail chipset - soundcard chtmax98090
by bugzilla_noreply＠suse.com 06 May '21

06 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185693 https://bugzilla.suse.com/show_bug.cgi?id=1185693#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Could you install sof-firmware package and reboot? The Intel sound system has been migrated from SST to SOF, and it requires the firmware files. sof-firmware package has the hardware Supplements tag, so this should have been installed if you run zypper install-recommends, too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185745] kernel firmware bug
by bugzilla_noreply＠suse.com 06 May '21

06 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185745 https://bugzilla.suse.com/show_bug.cgi?id=1185745#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(werwolf131313@gma | |il.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Please elaborate what's exactly a problem. Also, please attach to Bugzilla instead of external URLs for the data. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185744] New: System hangs at reboot and shutdown, waiting for network
by bugzilla_noreply＠suse.com 06 May '21

06 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185744 Bug ID: 1185744 Summary: System hangs at reboot and shutdown, waiting for network Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dutchkind(a)txoriaskea.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since a week or so (maybe since kernel 5.12) one of my laptops with tumbleweed hangs at shutdown with a systemd message telling me it is waiting for networkmanager to finish. The only thing that works to come out is a forced shutdown with the power button, not really nice for my SSD. As a workaround I found is a shutdown script in Plasma "nmcli radio wifi off" after which the shutdown completes without problem. This happens on one laptop, a newer one with basically the same system doesn't have a problem, but in both systems I find in journalctl the following: mei 06 13:27:16 systemd[1]: iscsi.service: Succeeded. mei 06 13:27:16 systemd[1]: Stopped Login and scanning of iSCSI devices. mei 06 13:27:16 systemd[1]: Stopped target Network is Online. mei 06 13:27:16 systemd[1]: Stopped target Network. mei 06 13:27:16 systemd[1]: Stopping Network Manager... mei 06 13:27:16 systemd[1]: Stopping Network Service... mei 06 13:27:16 NetworkManager[1318]: <info> [1620300436.7159] caught SIGTERM, shutting down normally. mei 06 13:27:16 NetworkManager[1318]: <info> [1620300436.7165] device (wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed') mei 06 13:27:16 systemd[1]: systemd-networkd.service: Succeeded. mei 06 13:27:16 systemd[1]: Stopped Network Service. mei 06 13:27:16 systemd[1]: Requested transaction contradicts existing jobs: Transaction for systemd-networkd.service/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction). mei 06 13:27:16 systemd[1]: systemd-networkd.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction for systemd-networkd.service/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction). After this last sentence on the problem system I get a dump of the iwlwifi and the system is hung waiting eternally for the networkmanager to start again. I haven't found where the contradictory command is found, have been looking through systemd service files to no avail. Any help would be appreciated. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185730] VUL-0: CVE-2021-29478: redis: Integer overflow via COPY command for large intsets
by bugzilla_noreply＠suse.com 06 May '21

06 May '21

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

1 0

[Bug 1182657] New: VUL-0: CVE-2021-21309: redis: Integer overflow on 32-bit systems
by bugzilla_noreply＠suse.com 06 May '21

06 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182657 Bug ID: 1182657 Summary: VUL-0: CVE-2021-21309: redis: Integer overflow on 32-bit systems Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: i586 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: ro(a)suse.de Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- Integer overflow on 32-bit systems (CVE-2021-21309): Redis 4.0 or newer uses a configurable limit for the maximum supported bulk input size. By default, it is 512MB which is a safe value for all platforms. If the limit is significantly increased, receiving a large request from a client may trigger several integer overflow scenarios, which would result with buffer overflow and heap corruption. References: https://groups.google.com/g/redis-db/c/tFldUlOt8D8/m/HrZAfUB0AgAJ https://github.com/redis/redis/blob/6.2.0/00-RELEASENOTES -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1178205] New: VUL-0: redis: potential heap overflow when using a heap allocator other than jemalloc or glibc's malloc
by bugzilla_noreply＠suse.com 06 May '21

06 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1178205 Bug ID: 1178205 Summary: VUL-0: redis: potential heap overflow when using a heap allocator other than jemalloc or glibc's malloc Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mrueckert(a)suse.com Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- Redis 6.0.9 fixes a potential heap overflow when using a heap allocator other than jemalloc or glibc's malloc. When using a system with no malloc_usable_size(), zmalloc_size() assumed that the heap allocator always returns blocks that are long-padded. This may not always be the case, and will result with zmalloc_size() returning a size that is bigger than allocated. At least in one case this leads to out of bound write, process crash and a potential security vulnerability. Effectively this does not affect the vast majority of users, who use jemalloc or glibc. https://raw.githubusercontent.com/redis/redis/6.0/00-RELEASENOTES https://github.com/redis/redis/pull/7963 -- You are receiving this mail because: You are on the CC list for the bug.

1 2