January 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201179] VUL-0: CVE-2021-41688: dcmtk: object in the program is free but its address is still used in other locations
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1201179 Stoyan Manolov <stoyan.manolov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stoyan.manolov(a)suse.com Assignee|security-team(a)suse.de |kde-maintainers(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201180] VUL-0: CVE-2021-41689: dcmtk: sending specific requests to the dcmqrdb program, it would query its database and copy the result even if the result is null
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1201180 Stoyan Manolov <stoyan.manolov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stoyan.manolov(a)suse.com Assignee|security-team(a)suse.de |kde-maintainers(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201178] VUL-0: CVE-2021-41687: dcmtk: the program malloc a heap memory for parsing data, but does not free it when error in parsing
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1201178 Stoyan Manolov <stoyan.manolov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stoyan.manolov(a)suse.com Assignee|security-team(a)suse.de |kde-maintainers(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206070] VUL-0: CVE-2022-43272: dcmtk: memory leak via the T_ASC_Association object.
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206070 Stoyan Manolov <stoyan.manolov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kde-maintainers(a)suse.de Flags| |needinfo?(kde-maintainers@s | |use.de) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206697] Wireless network disappears on Raspberry Pi 4B after kernel-default 6.0.12
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206697 https://bugzilla.suse.com/show_bug.cgi?id=1206697#c7 --- Comment #7 from Stefan Wahren <stefan.wahren(a)i2se.com> --- Could you try this pending fix: https://patchwork.kernel.org/project/linux-wireless/patch/20221230075139.56… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206070] VUL-0: CVE-2022-43272: dcmtk: memory leak via the T_ASC_Association object.
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206070 Stoyan Manolov <stoyan.manolov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|security-team(a)suse.de |kde-maintainers(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205698] irqbalance.service recently started to take 90 seconds to stop
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1205698 https://bugzilla.suse.com/show_bug.cgi?id=1205698#c3 --- Comment #3 from Chang Seok Bae <chang.seok.bae(a)intel.com> --- I don't see any hang on my side -- stopping the daemon via systemctl when a burst of Netlink events coming from the kernel: ... /var/log/syslog:Jan 3 16:55:50 d8bbc18b833c /usr/sbin/irqbalance: thermal: event - CPU 22, efficiency 1, perf 1. /var/log/syslog:Jan 3 16:55:50 d8bbc18b833c /usr/sbin/irqbalance: thermal: event - CPU 23, efficiency 1, perf 1. /var/log/syslog:Jan 3 16:55:50 d8bbc18b833c systemd[1]: Stopping irqbalance daemon... /var/log/syslog:Jan 3 16:55:50 d8bbc18b833c systemd[1]: irqbalance.service: Deactivated successfully. /var/log/syslog:Jan 3 16:55:50 d8bbc18b833c systemd[1]: Stopped irqbalance daemon. BTW, looks like that whitelisting is needed. Without that, I got these: ... /var/log/syslog:Jan 3 15:55:14 d8bbc18b833c /usr/sbin/irqbalance: thermal: socket bind failed. /var/log/syslog:Jan 3 15:55:14 d8bbc18b833c /usr/sbin/irqbalance: Failed to initialize thermal events. Also, curious about which CPU model you had that issue with. Thanks, Chang -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206172] mhvtl fails to build on Leap 15.5 error: too few arguments to function 'mhvtl_queuecommand_lck'
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206172 https://bugzilla.suse.com/show_bug.cgi?id=1206172#c1 Lee Duncan <lduncan(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Lee Duncan <lduncan(a)suse.com> --- Changes submitted to Factory -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c10 --- Comment #10 from Pablo Sanchez <pablo(a)blueoakdb.com> --- (In reply to Oliver Neukum from comment #8) > The failure you are seeing is on the PCI level. From your logs it is unclear > whether the HC that fails to resume is hosting other busses. It is possible > that it is just not resumed without a device. Hi, My work-around is to resume, *then* connect the device. > Do you have other devices to test to make sure it is not specific to your > phone? What an excellent idea. As my phone is a Samsung S21, non-root, I hadn't thought it might be an issue. Using another phone (OnePlus Nord), it works. > Alternatively, if not, it would be necessary to set the "control" > attribute for your root hub to "on". I think you're saying a work-around is for me to create a udev rule. I can certainly do this but given that my phone is very generic, non-rooted, I'm not sure whether that's a good solution for regular users. Thoughts? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c9 Pablo Sanchez <pablo(a)blueoakdb.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(pablo(a)blueoakdb.c | |om) | --- Comment #9 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Created attachment 863813 --> https://bugzilla.suse.com/attachment.cgi?id=863813&action=edit hwinfo, lspci and dmesg Hi, This data was captured with the latest kernel (6.1.1.1-default) This tar-ball contains the following files: 2/hwinfo.phone.bad.txt 2/hwinfo.phone.ok.txt 2/lspci.phone.bad.txt 2/lspci.phone.ok.txt 2/dmesg.bad.txt where, o hwinfo: hwinfo --all --log ... o lspci: lspci -vvxxx o Files with 'ok' are the /before/ state o Files with 'bad' are the /after/, borked state and 'dmesg.txt' is trimmed to capture the resume with the phone connected (borking the driver). Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

1 0