May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220096] New: VUL-0: CVE-2024-26134: python-cbor2: potential crash when hashing a CBORTag
by bugzilla_noreply＠suse.com 29 Jan '25

29 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1220096 Bug ID: 1220096 Summary: VUL-0: CVE-2024-26134: python-cbor2: potential crash when hashing a CBORTag Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/394540/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: dmueller(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: carlos.lopez(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- cbor2 provides encoding and decoding for the Concise Binary Object Representation (CBOR) (RFC 8949) serialization format. Starting in version 5.5.1 and prior to version 5.6.2, an attacker can crash a service using cbor2 to parse a CBOR binary by sending a long enough object. Version 5.6.2 contains a patch for this issue. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-26134 https://www.cve.org/CVERecord?id=CVE-2024-26134 https://github.com/agronholm/cbor2/commit/387755eacf0be35591a478d3c67fe1061… https://github.com/agronholm/cbor2/commit/4de6991ba29bf2290d7b9d83525eda7d0… https://github.com/agronholm/cbor2/pull/204 https://github.com/agronholm/cbor2/releases/tag/5.6.2 https://github.com/agronholm/cbor2/security/advisories/GHSA-375g-39jq-vq7m https://bugzilla.redhat.com/show_bug.cgi?id=2265034 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214053] New: Wrong Permissions for Package xmrig-6.18.1-bp155.1.8.x86_64.rpm (Download Error)
by bugzilla_noreply＠suse.com 28 Jan '25

28 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1214053 Bug ID: 1214053 Summary: Wrong Permissions for Package xmrig-6.18.1-bp155.1.8.x86_64.rpm (Download Error) Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: stephan.kreuz(a)bwi.de QA Contact: packagehub-bugs(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Sine 07/01/23 (not sure when problem occure first Time) I get Permission denied for Package xmrig-6.18.1-bp155.1.8.x86_64.rpm from suse-packagehub-15-sp5-backports-pool-x86_64(-sap). Please verify that the correct Permisions set for that Package. kind regards Stephan -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1219306] New: [Tracker[ Remove python2 from openSUSE:Factory
by bugzilla_noreply＠suse.com 28 Jan '25

28 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1219306 Bug ID: 1219306 Summary: [Tracker[ Remove python2 from openSUSE:Factory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This bug report serves as parent to file tickets against packages still using python2 (our long-awaited gimp 3 should be coming out in May - let's collect what else is still in need of python2, trying to eliminate these things) -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1224434] New: Page cache invalidation failure during direct I/O write
by bugzilla_noreply＠suse.com 22 Jan '25

22 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1224434 Bug ID: 1224434 Summary: Page cache invalidation failure during direct I/O write Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 URL: https://openqa.opensuse.org/tests/4202483/modules/AD03 3/steps/8 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: avinesh.kumar(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-ltp_aiodio_part1@ppc64le fails in [AD033](https://openqa.opensuse.org/tests/4202483/modules/AD033/steps/8) ## Test suite description LTP_ENV=TMPDIR=/var/tmp is to test on btrfs instead of tmpfs ## Reproducible Fails since (at least) Build [20240131](https://openqa.opensuse.org/tests/3907534) Last good: Unknown ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&distri=opensu… -------- LTP Test - https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/io/l… we run this test with various combinations of write block size and I/O numbers (https://github.com/linux-test-project/ltp/blob/master/runtest/ltp-aiodio.pa…) failing scenarios on ppc64le: AD033 aiocp -b 4k -n 4 -f DIRECT AD035 aiocp -b 4k -n 8 -f DIRECT AD037 aiocp -b 4k -n 16 -f DIRECT (few times doesn't fail) AD039 aiocp -b 4k -n 32 -f DIRECT (few times doesn't fail) AD047 aiocp -b 8k -n 4 -f DIRECT AD049 aiocp -b 8k -n 8 -f DIRECT AD051 aiocp -b 8k -n 16 -f DIRECT (few times doesn't fail) AD061 aiocp -b 16k -n 4 -f DIRECT AD063 aiocp -b 16k -n 8 -f DIRECT AD075 aiocp -b 32k -n 4 -f DIRECT dmesg log during each of these failures: OpenQA::run_ltp.pm: Starting AD032 OpenQA::run_ltp.pm: Starting AD033 [ 48.470444][ T62] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O! [ 48.471404][ T62] File: /var/tmp/LTP_aioTBsaEH/dstfile.bin PID: 62 Comm: kworker/1:1 OpenQA::run_ltp.pm: Starting AD034 OpenQA::run_ltp.pm: Starting AD035 This issue is not present on aarch64 and x86_64 tumbleweed builds. And on SLE15-SP6, we are not seeing this on ppc64le also. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1216739] New: sssd: support configs and drop-ins in /usr
by bugzilla_noreply＠suse.com 21 Jan '25

21 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1216739 Bug ID: 1216739 Summary: sssd: support configs and drop-ins in /usr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: scabrero(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ckowalczyk(a)suse.com, jengelh(a)inai.de, scabrero(a)suse.com Target Milestone: --- Found By: --- Blocker: --- sssd ships configs in /etc. In order to be able to ship configs as packages, support for having configs in /usr is desireable as well. Any chance to simplement /usr/etc support? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1221429] New: Presence dialog for ssh id_ed25519_sk keys not showing up
by bugzilla_noreply＠suse.com 21 Jan '25

21 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1221429 Bug ID: 1221429 Summary: Presence dialog for ssh id_ed25519_sk keys not showing up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When logging in via ssh using a id_ed25519_sk key (e.g. Yubikey), typically ssh prompts a dialog, prompting the user to push the presence key on the hardware dongle. In Plasma6 when doing ssh against a host that requires this presence button to be pushed, the dialog does not show up. The login still works, ssh just blocks and when I push the button it works, but the confirmation dialog does not show up anymore. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1222473] New: VUL-0: CVE-2024-22189: dnscrypt-proxy: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
by bugzilla_noreply＠suse.com 20 Jan '25

20 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222473 Bug ID: 1222473 Summary: VUL-0: CVE-2024-22189: dnscrypt-proxy: quic-go: memory exhaustion attack against QUIC's connection ID mechanism Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/400376/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: cunix(a)mail.de Reporter: camila.matos(a)suse.com QA Contact: qa-bugs(a)suse.de CC: camila.matos(a)suse.com, security-team(a)suse.de, smash_bz(a)suse.de Blocks: 1222461 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1222461 +++ quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-22189 https://www.cve.org/CVERecord?id=CVE-2024-22189 https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c… https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478 https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-manageme… https://www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s https://bugzilla.redhat.com/show_bug.cgi?id=2273513 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222505] New: ckermit: cannot create lock file in /var/lock
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222505 Bug ID: 1222505 Summary: ckermit: cannot create lock file in /var/lock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ceggers(a)arri.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Kermit needs to create a lock file for the used serial port (e.g. /dev/ttyUSB0) under /var/lock (symlink to /run/lock). Until Leap 15.5, that directory was owned by group "lock", so it was sufficient to add the current user to the "lock" group. But now the directory is owned by group "root", so using the "lock" group is not sufficient anymore. Reproducible: Always Steps to Reproduce: 1. Add current user to "dialout" group (and create re-login after that). 2. Ensure that step 1. was successful (e.g. by using the "id" command). 3. kermit -l /dev/ttyUSB0 Actual Results: Kermit gives an error "can't open device". Using "set line /dev/ttyUSB0" in kermit's interactive mode gives a more precise error message: "Sorry, write access to UUCP lockfile directory denied." Expected Results: kermit should have created the lock file and open /dev/ttyUSB0 A workaround is to change the group of /run/lock to "dialout" (and to add the current user to this group). But this change is lost after every reboot. Possibly related to https://bugzilla.opensuse.org/show_bug.cgi?id=624290 ("ckermit from contrib repository does not use lockdev, so cannot write to /var/lock"). The packet installed is: $ rpm -q ckermit --info Name : ckermit Version : 9.0.302 Release : 150000.3.3.1 Architecture: x86_64 Install Date: Mo 08 Apr 2024 09:44:42 CEST Group : Hardware/Modem Size : 2621762 License : BSD-3-Clause Signature : RSA/SHA256, Fr 01 Apr 2022 13:39:36 CEST, Key ID 70af9e8139db7c82 Source RPM : ckermit-9.0.302-150000.3.3.1.src.rpm Build Date : Fr 01 Apr 2022 13:39:14 CEST Build Host : goat10 Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : SUSE LLC <https://www.suse.com/> URL : http://www.kermitproject.org/ Summary : A Combined Serial and Network Communication Software Package Description : C-Kermit is a combined serial and network communication software package offering a consistent, medium-independent, and cross-platform approach to connection establishment, terminal sessions, file transfer, character-set translation, and automation of communication tasks. Distribution: SUSE Linux Enterprise 15 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1225509] New: AUDIT-FIND: 4Pane: predictable /tmp path in PreviewPopup::DisplayImage
by bugzilla_noreply＠suse.com 16 Jan '25

16 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1225509 Bug ID: 1225509 Summary: AUDIT-FIND: 4Pane: predictable /tmp path in PreviewPopup::DisplayImage Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- 4Pane uses predictable /tmp paths in PreviewPopup::DisplayImage() > 2054 pngfilepath = "/tmp/" + fn.GetName() + ".png"; > 2055 if (SvgToPng(filepath, pngfilepath, handle)) > 2056 image = wxImage(pngfilepath); > 2057 wxRemoveFile(pngfilepath); If fs.protected_symlinks=1, an unprivileged user can prevent 4Pane from displaying previews for SVG images. If fs.protected_symlinks=0, an unprivileged user can overwrite arbitrary world-readable files owned by the 4Pane user. Steps to reproduce: nobody@localhost:/tmp> ln -s /home/user/somefile foo.png # ... wait until the user previews a file named foo.svg # somefile will be overwritten An attacker can pre-create symlinks for the names of all existing SVG files on the system to increase the likelihood of triggering the bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1223420] New: VUL-0: CVE-2024-31755: cJSON: NULL pointer dereference via cJSON_SetValuestring()
by bugzilla_noreply＠suse.com 15 Jan '25

15 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1223420 Bug ID: 1223420 Summary: VUL-0: CVE-2024-31755: cJSON: NULL pointer dereference via cJSON_SetValuestring() Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/403222/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: carlos.lopez(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- cJSON v1.7.17 was discovered to contain a segmentation violation, which can trigger through the second parameter of function cJSON_SetValuestring at cJSON.c. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-31755 https://www.cve.org/CVERecord?id=CVE-2024-31755 https://github.com/DaveGamble/cJSON/issues/839 https://bugzilla.redhat.com/show_bug.cgi?id=2277268 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221095] New: Go application packages can no longer set CGO_ENABLED=0 if external linker will be used
by bugzilla_noreply＠suse.com 14 Jan '25

14 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1221095 Bug ID: 1221095 Summary: Go application packages can no longer set CGO_ENABLED=0 if external linker will be used Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Per Go upstream change https://go-review.googlesource.com/c/website/+/569296, as of go1.21.8+ and go1.22.1+ go build commands cannot set CGO_ENABLED=0 if the external linker will be used. (Cgo lets Go packages call C code, see https://go.dev/blog/cgo, 2011) The most commonly used option that triggers the external linker is -buildmode=pie, which we aspirationally use in most Go application packages behind conditionals for architectures where it is unsupported, currently only ppc64le. We first encountered this issue when trying to set the go metapackage from go1.21 to go1.22. Approximately 40+ Go application packages in Factory set CGO_ENABLED=0 and -buildmode=pie together. On arch i586, builds started to fail with error: -buildmode=pie requires external (cgo) linking, but cgo is not enabled This tracking bug will be referenced for SR submissions to Go application packages to adapt to the new requirements. Most of these submissions will to remove CGO_ENABLED=0 absent a requirement for its use by a specific package. Upstream comments from the above change: https://go.dev/issue/31544, CL 477839 When using an external (C) linker with cgo enabled, the `runtime/cgo` package is now supplied to the Go linker as an additional dependency to ensure that the Go runtime is compatible with any additional libraries added by the C linker. https://go.dev/issue/46330, CL 522239 go build commands that invoke the linker now error out if an external (C) linker will be used but cgo is not enabled. (The Go runtime requires cgo support to ensure that it is compatible with any additional libraries added by the C linker.) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223838] New: Nonfunctional brightness keys on Apple Macbook 5.1 (mcp79,nouveau)
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1223838 Bug ID: 1223838 Summary: Nonfunctional brightness keys on Apple Macbook 5.1 (mcp79,nouveau) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de CC: kernel-bugs(a)suse.de, qa-bugs(a)suse.de, tiwai(a)suse.com, variable_valuables761(a)simplelogin.com Depends on: 1217750, 1217716 Target Milestone: --- Found By: --- Blocker: --- Created attachment 874641 --> https://bugzilla.suse.com/attachment.cgi?id=874641&action=edit current dmesg output +++ This bug was initially created as a clone of Bug #1217750 +++ It seems the brightness keys (Fn+F1,Fn+F2) do not work in Tumbleweed with current 6.8 kernel series. This should have been reported rather long time ago. This has started happening in ~6.5 series I've attached the output of "brightnessctl -l",> which only shows keyboard (caps lock) key and several non-existent LEDs on keyboard. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1220086] New: xfce4-terminal does not honor --geometry parameter under wayland
by bugzilla_noreply＠suse.com 09 Jan '25

09 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1220086 Bug ID: 1220086 Summary: xfce4-terminal does not honor --geometry parameter under wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I decided to play around with wayland instead of x11 to find out, if everything works as expected for me. On thing I found, is that xfce4-terminal does not honor --geometry parameter under wayland. It is always started centered, it seems to use the size parameters, though. Operating System: openSUSE Tumbleweed 20240216 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.4-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222194] New: kubo ipfs tries to start before the network appears and fails with an error
by bugzilla_noreply＠suse.com 09 Jan '25

09 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222194 Bug ID: 1222194 Summary: kubo ipfs tries to start before the network appears and fails with an error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- kubo ipfs tries to start before the network appears and fails with an error > [werwolf@power] ~ > ❯ sudo LANG=c zypper info kubo > Refreshing service 'openSUSE'. > Loading repository data... > Reading installed packages... > > > Information for package kubo: > ----------------------------- > Repository : filesystems > Name : kubo > Version : 0.26.0-16.17 > Arch : x86_64 > Vendor : obs://build.opensuse.org/filesystems > Installed Size : 79.2 MiB > Installed : Yes > Status : up-to-date > Source package : kubo-0.26.0-16.17.src > Upstream URL : https://github.com/ipfs/kubo > Summary : IPFS implementation in Go > Description : > IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single bittorrent swarm, exchanging git objects. IPFS provides an interface as simple as the HTTP web, but with permanence > built in. You can also mount the world at /ipfs. As far as I understand, the problem can be solved by simply adding one line to the systemd service file > Wants=network-online.target > After=network-online.target -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218455] New: kernel: NOHZ tick-stop error: local softirq work is pending
by bugzilla_noreply＠suse.com 08 Jan '25

08 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1218455 Bug ID: 1218455 Summary: kernel: NOHZ tick-stop error: local softirq work is pending Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with kernel 6.6.6 (and continuing with 6.6.7) I get kernel: NOHZ tick-stop error: local softirq work is pending, handler #08!!! a few times within one or two minutes and during this time performance is degraded heavily. This happens about every two days, so it is not that much of a problem, but a bit annoying. system is: Operating System: openSUSE Tumbleweed 20231226 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1219817] New: GNOME 45.3 session crashed when changing sound output
by bugzilla_noreply＠suse.com 08 Jan '25

08 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1219817 Bug ID: 1219817 Summary: GNOME 45.3 session crashed when changing sound output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872650 --> https://bugzilla.suse.com/attachment.cgi?id=872650&action=edit journal.txt OS: Tumbleweed 20240209 gnome-shell version: 45.3-2.2 System: Dell Latitude 5440 laptop Had Bluetooth headphones connected, in the top-right GNOME "tray" area I changed the sound output to the Handsfree option of my headphones and my session immediately crashed, I was returned to the GDM login screen. Logged back in, everything seemed to be working again, changed the sound output without crashes. First time I've had this happen. There are some errors about code being reached that shouldn't be, stack traces and core dumps in the journal (attached file). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1220727] New: VUL-0: CVE-2023-51774: rubygem-json-jwt: JWE can sometimes be used to bypass JSON:JWT.decode
by bugzilla_noreply＠suse.com 07 Jan '25

07 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1220727 Bug ID: 1220727 Summary: VUL-0: CVE-2023-51774: rubygem-json-jwt: JWE can sometimes be used to bypass JSON:JWT.decode Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/395627/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: abergmann(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- The json-jwt (aka JSON::JWT) gem 1.16.3 for Ruby sometimes allows bypass of identity checks via a sign/encryption confusion attack. For example, JWE can sometimes be used to bypass JSON::JWT.decode. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-51774 https://www.cve.org/CVERecord?id=CVE-2023-51774 https://github.com/P3ngu1nW/CVE_Request/blob/main/novjson-jwt.md -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1212947] New: Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 06 Jan '25

06 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 Bug ID: 1212947 Summary: Disable fbdev userspace interfaces and programs 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: tzimmermann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We want to remove fbdev from kernel and userspace as far as possible. Linux 6.6 will allow us to disable fbdev's userspace interfaces, most noteably /dev/fb*. Enable this feature in the TW kernel. Framebuffer support has been an endless source of bugs. Not giving userspace access to it's internals and framebuffer memory will close a possible entry point for all sorts of malware. Please note that the framebuffer console is implemented entirely within the kernel and will not be affected by this change. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1217920] New: QT_IM_MODULE is always set on plasma 5.27.9
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1217920 Bug ID: 1217920 Summary: QT_IM_MODULE is always set on plasma 5.27.9 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: i(a)xuzhao.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- According to the fcitx5 on wayland wiki page: https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland QT_IM_MODULE and GTK_IM_MODULE and SDL_IM_MODULE are not suggested to be set on fcitx5+plasma_wayland>5.27. However, after I install fcitx5 on opensuse 20231117, these environment variables are still being set by default. Is there a way that I can disable setting these environment variables on startup? -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222902] New: Monitor detection fails after hard reset
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222902 Bug ID: 1222902 Summary: Monitor detection fails after hard reset Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: david.mulder(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a hard reset (laptop locked up when I tried to suspend it), my external monitors are no longer detected. I've seen this happen 3 times in as many weeks (on several recent versions of TW), and the only solution I've found is reinstalling TW. > sudo hwinfo --monitor 45: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.iVNqLoWlvi7 Parent ID: _Znp.TcrQYGYoBS2 Hardware Class: monitor Model: "BOE CQ LCD Monitor" Vendor: BOE "BOE CQ" Device: eisa 0x0a7d Serial ID: "0" Resolution: 1920x1200@60Hz Size: 345x215 mm Year of Manufacture: 2021 Week of Manufacture: 27 Detailed Timings #0: Resolution: 1920x1200 Horizontal: 1920 1968 2000 2140 (+48 +80 +220) -hsync Vertical: 1200 1203 1209 1260 (+3 +9 +60) +vsync Frequencies: 161.79 MHz, 75.60 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 1920x1200 Vert. Sync Range: 40-60 Hz Hor. Sync Range: 76-76 kHz Bandwidth: 161 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #39 (VGA compatible controller) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217428] New: VUL-0: CVE-2023-6258: pkcs11-provider: Side-channel proofing PKCS#1 1.5 paths
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1217428 Bug ID: 1217428 Summary: VUL-0: CVE-2023-6258: pkcs11-provider: Side-channel proofing PKCS#1 1.5 paths Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/385844/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: luca.boccassi(a)gmail.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: thomas.leroy(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Side-channel proofing PKCS#1 1.5 paths (Marvin) Ref: https://github.com/latchset/pkcs11-provider/pull/308 References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6258 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1220119] New: Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:"
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220119 Bug ID: 1220119 Summary: Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jwiesner(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Some tests running on o3 (openQA instance on https://openqa.opensuse.org/) triggers in dmesg. All tests run in VM via qemu. This is on x86_64 on my private openQA worker by ltp_net_tcp_cmds, triggered for 2 tests: arp and host (both tests did not fail): OpenQA::run_ltp.pm: Starting ipneigh01_arp [ 410.818828][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 410.820365][ C0] clocksource: 'kvm-clock' wd_nsec: 506724586 wd_now: 610448443a wd_last: 60e6144350 mask: ffffffffffffffff [ 410.821824][ C0] clocksource: 'tsc' cs_nsec: 49302930542 cs_now: 17c1364ba0a cs_last: 153fdc32526 mask: ffffffffffffffff [ 410.823293][ C0] clocksource: Clocksource 'tsc' skewed 48796205956 ns (48796 ms) over watchdog 'kvm-clock' interval of 506724586 ns (506 ms) [ 410.824843][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 410.825707][ C0] tsc: Marking TSC unstable due to clocksource watchdog [ 411.109710][T28135] Initializing XFRM netlink socket OpenQA::run_ltp.pm: Starting ipneigh01_ip OpenQA::run_ltp.pm: Starting arping01 OpenQA::run_ltp.pm: Starting clockdiff01 OpenQA::run_ltp.pm: Starting ftp OpenQA::run_ltp.pm: Starting host [ 410.818845][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 410.820687][ C0] clocksource: 'kvm-clock' wd_nsec: 506741379 wd_now: 61044885d3 wd_last: 60e6144350 mask: ffffffffffffffff [ 410.821794][ C0] clocksource: 'tsc' cs_nsec: 804834172 cs_now: 154a546a082 cs_last: 153fdc32526 mask: ffffffffffffffff [ 410.822919][ C0] clocksource: Clocksource 'tsc' skewed 298092793 ns (298 ms) over watchdog 'kvm-clock' interval of 506741379 ns (506 ms) [ 410.824088][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 410.824768][ C0] tsc: Marking TSC unstable due to clocksource watchdog [ 411.126759][T28138] Initializing XFRM netlink socket Also, originally I noted this on ltp_net_tcp_cmds running on ppc64le on o3 (kernel tests in https://openqa.opensuse.org/group_overview/32) where host test keeps failing (but arp test is working), I don't see it on ltp_net_tcp_cmds on x86_64 on o3. I was not able to trigger this on VM on my laptop (x86_64). Others found that systemd-networkd test on Tumbleweed on x86_64 (https://openqa.opensuse.org/group_overview/1) [ 570.754611][ C0] Showing busy workqueues and worker pools: [ 570.755654][ C0] workqueue events: flags=0x0 [ 570.756580][ C0] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 [ 570.756586][ C0] pending: drm_fb_helper_damage_work [ 570.759551][ C0] sysrq: Show Blocked State zDBFr-0- [ 311.682306][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 311.684482][ C0] clocksource: 'kvm-clock' wd_nsec: 621509306 wd_now: 49d9caac63 wd_last: 49b4bf31a9 mask: ffffffffffffffff [ 311.686513][ C0] clocksource: 'tsc' cs_nsec: 952336665 cs_now: a3a422af12 cs_last: a327415f8e mask: ffffffffffffffff [ 311.688559][ C0] clocksource: Clocksource 'tsc' skewed 330827359 ns (330 ms) over watchdog 'kvm-clock' interval of 621509306 ns (621 ms) [ 311.690452][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 311.691559][ C0] tsc: Marking TSC unstable due to clocksource watchdog Test runs also on aarch64, but error is not there. Is it a problem of openQA setup? There are other bugs. -- You are receiving this mail because: You are on the CC list for the bug.

1 41

[Bug 1222490] New: Kruner and Home Menu only show krusader in root mode
by bugzilla_noreply＠suse.com 25 Dec '24

25 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1222490 Bug ID: 1222490 Summary: Kruner and Home Menu only show krusader in root mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: smartinds(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874135 --> https://bugzilla.suse.com/attachment.cgi?id=874135&action=edit Screenshot Why Kruner and the "Home Menu" only show “krusader” in root mode? I have krusader in my path :~> ls -l /bin/kru* -rwxr-xr-x 1 root root 85016 mar 26 13:06 /bin/krunner -rwxr-xr-x 1 root root 84520 abr 1 13:21 /bin/krunner-plugininstaller -rwxr-xr-x 1 root root 2832680 mar 13 03:21 /bin/krusader ~> ls -l /usr/bin/kru* -rwxr-xr-x 1 root root 85016 mar 26 13:06 /usr/bin/krunner -rwxr-xr-x 1 root root 84520 abr 1 13:21 /usr/bin/krunner-plugininstaller -rwxr-xr-x 1 root root 2832680 mar 13 03:21 /usr/bin/krusader Krusader works if I run it with the terminal, but is weird that don show in "Kruner" nor "Home Menu". Note: Sometimes (random) both show me Krusader in "Normal Mode", but not the "Root Mode". -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1220490] New: GCC 14: gdb package fails
by bugzilla_noreply＠suse.com 23 Dec '24

23 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220490 Bug ID: 1220490 Summary: GCC 14: gdb package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mjambor(a)suse.com, tdevries(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Building gdb with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: gdb-13.2/gdb/configure: line 418: test: too many arguments configure: error: 18086 gdb-13.2/gdb/configure: line 307: return: Specific: numeric argument required gdb-13.2/gdb/configure: line 317: exit: Specific: numeric argument required gdb-13.2/gdb/configure: conftest.c: In function 'main': gdb-13.2/gdb/configure: conftest.c:54:18: error: implicit declaration of function 'strerror'; did you mean 'Fstrerror'? [-Wimplicit-function-declaration] gdb-13.2/gdb/configure: 54 | strerror (errno)); gdb-13.2/gdb/configure: | ^~~~~~~~ gdb-13.2/gdb/configure: | Fstrerror gdb-13.2/gdb/configure: conftest.c:75:9: error: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration] gdb-13.2/gdb/configure: 75 | if (strcmp ("librpm.so", "/lib64/librpm.so.10") != 0) gdb-13.2/gdb/configure: | ^~~~~~ gdb-13.2/gdb/configure: conftest.c:41:1: note: include '<string.h>' or provide a declaration of 'strcmp' gdb-13.2/gdb/configure: 40 | #include <errno.h> gdb-13.2/gdb/configure: +++ |+#include <string.h> gdb-13.2/gdb/configure: 41 | Builds with: Index: gdb.spec_dir/gdb-13.2/gdb/configure =================================================================== --- gdb.spec_dir.orig/gdb-13.2/gdb/configure +++ gdb.spec_dir/gdb-13.2/gdb/configure @@ -17942,6 +17942,7 @@ else #include <rpm/rpmlib.h> #include <dlfcn.h> #include <errno.h> +#include <string.h> int main () -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1224452] New: installing audacious pulls in -devel packages
by bugzilla_noreply＠suse.com 21 Dec '24

21 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224452 Bug ID: 1224452 Summary: installing audacious pulls in -devel packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: kocelfc(a)tutanota.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874956 --> https://bugzilla.suse.com/attachment.cgi?id=874956&action=edit zypper.log When trying to install the audacious package, zypper tries to pull in a lot of -devel packages: The following recommended package was automatically selected: audacious-plugins-extra The following 64 NEW packages are going to be installed: at-spi2-core-devel audacious audacious-plugins audacious-plugins-extra dbus-1-devel glib2-devel libaudcore5 libaudgui5 libaudqt2 libaudtag3 libblkid-devel libcddb2 libcue2 libdrm-devel libeconf-devel libffi-devel libfluidsynth3 libgirepository-2_0-0 libglvnd-devel libinstpatch-1_0-2 liblirc_client0 libmms0 libmodplug1 libmount-devel libopusfile0 libpciaccess-devel libpcre2-32-0 libpcre2-posix3 libselinux-devel libsepol-devel libsidplayfp6 libsndio7 libstdc++-devel libX11-devel libXau-devel libxcb-dbe0 libxcb-devel libxcb-screensaver0 libxcb-xf86dri0 libxcb-xtest0 libxcb-xvmc0 libXext-devel libXfixes-devel libXi-devel libxkbcommon-devel libXrandr-devel libXrender-devel libXtst-devel Mesa-KHR-devel Mesa-libEGL-devel Mesa-libGL-devel pcre2-devel qt6-core-devel qt6-dbus-devel qt6-gui-devel qt6-svg-devel qt6-widgets-devel typelib-1_0-Atspi-2_0 typelib-1_0-GIRepository-3_0 typelib-1_0-GLibUnix-2_0 vulkan-devel vulkan-headers wayland-devel xorgproto-devel -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1224150] New: [Build 20240511] boot_encrypt: grub does not ask for encryption key
by bugzilla_noreply＠suse.com 19 Dec '24

19 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224150 Bug ID: 1224150 Summary: [Build 20240511] boot_encrypt: grub does not ask for encryption key Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4179275/modules/boot _encrypt/steps/2 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Grub no longer asks for the decryption key. The snapshot contained a grub2 change: +- Fix gcc error with CFLAGS=-Og + * grub2-grubenv-in-btrfs-header.patch + Which sounds harmless there were also plymouth changes, but the failure seems too early for plymouth openQA test in scenario opensuse-Tumbleweed-NET-x86_64-lvm-encrypt-separate-boot@64bit fails in [boot_encrypt](https://openqa.opensuse.org/tests/4179275/modules/boot_encryp… ## Test suite description Same as lvm-full-encrypt, but with separate boot not encrypted partition. Maintainer: riafarov INSTALLONLY=1 UNENCRYPTED_BOOT=1 DESKTOP=gnome ENCRYPT=1 FULL_LVM_ENCRYPT=1 ## Reproducible Fails since (at least) Build [20240509](https://openqa.opensuse.org/tests/4172240) ## Expected result Last good: [20240508](https://openqa.opensuse.org/tests/4169788) (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 10

[Bug 1219720] New: VUL-0: CVE-2024-24815: python-django-ckeditor: attackers could inject malformed HTML content bypassing Advanced Content Filtering mechanism
by bugzilla_noreply＠suse.com 18 Dec '24

18 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1219720 Bug ID: 1219720 Summary: VUL-0: CVE-2024-24815: python-django-ckeditor: attackers could inject malformed HTML content bypassing Advanced Content Filtering mechanism Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/393367/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: dmueller(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: andrea.mattiazzo(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- CKEditor4 is an open source what-you-see-is-what-you-get HTML editor. A cross-site scripting vulnerability has been discovered in the core HTML parsing module in versions of CKEditor4 prior to 4.24.0-lts. It may affect all editor instances that enabled full-page editing mode or enabled CDATA elements in Advanced Content Filtering configuration (defaults to `script` and `style` elements). The vulnerability allows attackers to inject malformed HTML content bypassing Advanced Content Filtering mechanism, which could result in executing JavaScript code. An attacker could abuse faulty CDATA content detection and use it to prepare an intentional attack on the editor. A fix is available in version 4.24.0-lts. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24815 https://www.cve.org/CVERecord?id=CVE-2024-24815 https://ckeditor.com/docs/ckeditor4/latest/api/CKEDITOR_dtd.html#property-S… https://ckeditor.com/docs/ckeditor4/latest/features/fullpage.html) https://ckeditor.com/docs/ckeditor4/latest/guide/dev_advanced_content_filte… https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-fq6h-4g8v-qq… https://ckeditor.com/docs/ckeditor4/latest/features/fullpage.html Patch: https://github.com/ckeditor/ckeditor4/commit/8ed1a3c93d0ae5f49f4ecff5738ab8… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1212877] New: [RPi4] cannot wake up after suspend triggered
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1212877 Bug ID: 1212877 Summary: [RPi4] cannot wake up after suspend triggered Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: zluo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867900 --> https://bugzilla.suse.com/attachment.cgi?id=867900&action=edit yast2 logs ssh to my RPi 4 Model B, later I see following -- p200300ea3707b36b055205817bcf9853:~ # Broadcast message from root@localhost (Fri 2023-06-30 06:03:37 UTC): The system will suspend now! -- then I try to wake it up by hitting keyboard and click on mouse, nothing happened on screen. attache yast2logs. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1220088] New: Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 14 Dec '24

14 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 Bug ID: 1220088 Summary: Hibernate completes shuts machine off *then* machine automatically turns back on. 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: pj.opensuse(a)gmx.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, when hibernate is envoked from the Tumbleweed menu the hibernate feature seems to complete and shutoff the machine for 2 seconds...... Then the machine automatically powers back on. I enter the LUKS password and the machine continues to boot. I enter the user password at SDDM screen. After loading KDE I can then see that Hibernate has indeed worked. Largest issue is machine is cycling, (powering back on) after hibernation has been envoked. I have shut off all wake-on power options in the bios settings. The machine is kept very current with the latest updates. What are your thoughts on this? -Best Regards -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1224773] New: Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 Bug ID: 1224773 Summary: Cannot install NVIDIA drivers in latest Aeon RC2 Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: sunscape1(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Installing NVIDIA drivers in Aeon RC2 (https://en.opensuse.org/SDB:NVIDIA_drivers) fails because the MOK cannot be enrolled after boot. Error during installation using pkg is: SKIP: /var/lib/nvidia-pubkeys/MOK-nvidia-driver-G06-550.78-22.1-default.der is not in MokList Without the nvidia-pubkeys folder it is impossible to enroll the MOK or try to enable it after reboot. The key doesn't exist :( -- You are receiving this mail because: You are on the CC list for the bug.

1 38

[Bug 1223794] New: VUL-0: CVE-2023-46565: TRACKERBUG: gobgp: buffer overflow via handlingError() function in pkg/server/fsm.go
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1223794 Bug ID: 1223794 Summary: VUL-0: CVE-2023-46565: TRACKERBUG: gobgp: buffer overflow via handlingError() function in pkg/server/fsm.go Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/403566/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: asarai(a)suse.com Reporter: camila.matos(a)suse.com QA Contact: qa-bugs(a)suse.de CC: camila.matos(a)suse.com, qa-bugs(a)suse.de, screening-team-bugs(a)suse.de, smash_bz(a)suse.de Blocks: 1223793 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1223793 +++ Buffer Overflow vulnerability in osrg gobgp commit 419c50dfac578daa4d11256904d0dc182f1a9b22 allows a remote attacker to cause a denial of service via the handlingError function in pkg/server/fsm.go. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-46565 https://www.cve.org/CVERecord?id=CVE-2023-46565 https://github.com/osrg/gobgp/issues/2725 https://bugzilla.redhat.com/show_bug.cgi?id=2278569 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1216919] New: dkimproxy broken after upgrade to Leap 15.4/conversion to systemd services
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1216919 Bug ID: 1216919 Summary: dkimproxy broken after upgrade to Leap 15.4/conversion to systemd services Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: All OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have upgrade to Leap 15.4 to find my dkimproxy setup broken. I noticed the following things: 1. there was one dkimproxy service, now there are two dkimproxy-in and dkimproxy-out. The new services are disabled even though the old one was enabled 2. The dkimproxy_in.service file references the /run/sysconfig/dkimproxy environment file 2a. The dkimproxy_env.sh script is supposed to create that file, but /run/sysconfig is not created at all to that script fails 2b. The dkimproxy_env.sh sets "HFQHN=$( hostname -f )" dkimproxy-in.service uses --hostname=${FQHN} While problem 1 is a one-time fix, the problems from 2 are more persistent and are ideally solved in the package. Note: systemd integration was contributed in bug #1116007 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1223697] New: VUL-0: CVE-2023-26793: libmodbus: heap-based buffer overflow vulnerability in read_io_status function in src/modbus.c.
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1223697 Bug ID: 1223697 Summary: VUL-0: CVE-2023-26793: libmodbus: heap-based buffer overflow vulnerability in read_io_status function in src/modbus.c. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/403923/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: sbrabec(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: andrea.mattiazzo(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- libmodbus v3.1.10 has a heap-based buffer overflow vulnerability in read_io_status function in src/modbus.c. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26793 https://www.cve.org/CVERecord?id=CVE-2023-26793 https://github.com/stephane/libmodbus/issues/683 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1224062] New: VUL-0: CVE-2024-34244: libmodbus: buffer overflow via the modbus_write_bits function
by bugzilla_noreply＠suse.com 08 Dec '24

08 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224062 Bug ID: 1224062 Summary: VUL-0: CVE-2024-34244: libmodbus: buffer overflow via the modbus_write_bits function Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/404865/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: sbrabec(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- libmodbus v3.1.10 is vulnerable to Buffer Overflow via the modbus_write_bits function. This issue can be triggered when the function is fed with specially crafted input, which leads to out-of-bounds read and can potentially cause a crash or other unintended behaviors. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-34244 https://www.cve.org/CVERecord?id=CVE-2024-34244 https://github.com/stephane/libmodbus/issues/743 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1213380] New: Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1213380 Bug ID: 1213380 Summary: Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: samcon(a)protonmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I encountered a black screen issue while attempting to boot the openSUSE Tumbleweed ISO after the BIOS on my system. This issue specifically occurs when using a DP-HDMI video output. This problem does not arise when using the same video output with other operating systems like Leap, Fedora, and Ubuntu LTS. In those cases, I am able to get video output without any black screen problems. Steps to Reproduce: 1. Start the computer and access the BIOS. 2. Configure the boot order to prioritize booting from the openSUSE Tumbleweed ISO. 3. Save the changes and exit the BIOS. 4. The system attempts to boot from the ISO. 5. First I see the kernal or bootloader messages, then it jumps to a black screen - with waiting for source message on projector. Expected Behavior: Upon booting from the openSUSE Tumbleweed ISO, the system should display zypper installer instead of a black screen, just like other operating systems do when using the DP-HDMI video output. Additional Information: - Operating System: openSUSE Tumbleweed - Video Output: DP-HDMI - Other operating systems (Leap, Fedora, Ubuntu LTS) do not exhibit the black screen issue with the same video output. - When I connect the same system to the monitor using DP-to-DP instead of DP-to-HDMI, the video output is successfully displayed. - Have used tried with iso from few weeks back and latest Snapshot20230714-Media.iso Kind regards, Sam -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1215927] New: kernel-default-6.5.4 reboots instead of resuming from suspend
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215927 Bug ID: 1215927 Summary: kernel-default-6.5.4 reboots instead of resuming from suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de CC: mrmazda(a)earthlink.net Target Milestone: --- Found By: --- Blocker: --- I upgraded from Tumbleweed 20230908 to 20230921, which included an upgrade from kernel-default-6.4.12 to kernel-default-6.5.4. I always suspend my computer at night (with systemctl suspend) and wake it the next morning. With the new kernel, the computer always restarts instead of resuming from suspend. The problem does not occur with the old kernel. Interestingly, the problem is reproducible only when I leave the computer suspended overnight. Simply suspending the computer and then waking it a few seconds later does not trigger the bug. hwinfo output (with the old kernel) is available in Attachment 869836 of Bug 1215826. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219444] New: amdgpu critical error
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1219444 Bug ID: 1219444 Summary: amdgpu critical error Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: teuniz(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872372 --> https://bugzilla.suse.com/attachment.cgi?id=872372&action=edit Output of dmesg The kernel crashes approx every 5 minutes. I reverted back to kernel 5.14.21-150500.55.19-default because with that one it crashes approx once a day. Operating System: openSUSE Leap 15.5 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.14.21-150500.55.44-default (64-bit) Graphics Platform: X11 Processors: 32 × 13th Gen Intel Core i9-13900K Memory: 31.0 GiB of RAM Graphics Processor: AMD Radeon Pro W6600 Manufacturer: HP Product Name: HP Z2 Tower G9 Workstation Desktop PC dmesg | grep amdgpu [ 1.540640] [drm] amdgpu kernel modesetting enabled. [ 1.540703] amdgpu: CRAT table not found [ 1.540705] amdgpu: Virtual CRAT table created for CPU [ 1.540712] amdgpu: Topology: Add CPU node [ 1.542670] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT [ 1.542671] amdgpu: ATOM BIOS: 113-D5330400-100 [ 1.542770] amdgpu 0000:03:00.0: vgaarb: deactivate vga console [ 1.542771] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default) [ 1.542799] amdgpu 0000:03:00.0: amdgpu: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used) [ 1.542800] amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF [ 1.542801] amdgpu 0000:03:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF [ 1.542845] [drm] amdgpu: 8176M of VRAM memory ready [ 1.542845] [drm] amdgpu: 15892M of GTT memory ready. [ 1.548699] amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist [ 1.548704] amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist [ 2.854516] amdgpu 0000:03:00.0: amdgpu: STB initialized to 2048 entries [ 2.895100] amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware [ 3.094413] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 3.115717] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 3.115740] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b2b00 (59.43.0) [ 3.115745] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched [ 3.115777] amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable [ 3.165133] amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully! [ 3.268063] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [ 3.268478] amdgpu: sdma_bitmap: ffff [ 3.302091] amdgpu: HMM registered 8176MB device memory [ 3.302135] amdgpu: SRAT table not found [ 3.302136] amdgpu: Virtual CRAT table created for GPU [ 3.302599] amdgpu: Topology: Add dGPU node [0x73e3:0x1002] [ 3.302601] kfd kfd: amdgpu: added device 1002:73e3 [ 3.302617] amdgpu 0000:03:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 8, active_cu_number 28 [ 3.302658] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 3.302659] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 3.302659] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 3.302660] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 3.302660] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 3.302661] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 3.302661] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 3.302662] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 3.302662] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 3.302663] amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 3.302663] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [ 3.302664] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 [ 3.302665] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1 [ 3.302665] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1 [ 3.302666] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1 [ 3.302666] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1 [ 3.303573] [drm] Initialized amdgpu 3.49.0 20150101 for 0000:03:00.0 on minor 0 [ 3.308709] fbcon: amdgpudrmfb (fb0) is primary device [ 3.505728] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 3.505731] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 3.505733] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x0000073A [ 3.505733] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: DCEDMC (0x3) [ 3.505734] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x5 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x1 [ 3.505736] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 [ 3.524299] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device [ 4.537456] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [ 5.416287] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 5.416312] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 5.416319] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00000000 [ 5.416324] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: unknown (0x0) [ 5.416329] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 5.416333] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 [ 5.416336] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 5.416340] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 5.416343] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 [ 73.156519] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 73.156538] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 73.156546] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x0000073A [ 73.156551] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: DCEDMC (0x3) [ 73.156562] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 73.156566] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x5 [ 73.156570] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [ 73.156578] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x1 [ 73.156582] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 uname -a 5.14.21-150500.55.44-default #1 SMP PREEMPT_DYNAMIC Mon Jan 15 10:03:40 UTC 2024 (cc7d8b6) x86_64 x86_64 x86_64 GNU/Linux lspci VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 WKS-XL [Radeon PRO W6600] -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1224383] New: VUL-0: CVE-2024-4068: python-pydata-sphinx-theme: the npm package `micromatch` is vulnerable to Regular Expression Denial of Service (ReDoS)
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224383 Bug ID: 1224383 Summary: VUL-0: CVE-2024-4068: python-pydata-sphinx-theme: the npm package `micromatch` is vulnerable to Regular Expression Denial of Service (ReDoS) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/405384/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: mmachova(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: gabriele.sonnu(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- The NPM package `micromatch` is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in `micromatch.braces()` in `index.js` because the pattern `.*` will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persists. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-4067 https://www.cve.org/CVERecord?id=CVE-2024-4067 https://devhub.checkmarx.com/cve-details/CVE-2024-4067/ https://github.com/micromatch/micromatch/blob/2c56a8604b68c1099e7bc0f807ce0… https://github.com/micromatch/micromatch/issues/243 https://github.com/micromatch/micromatch/pull/247 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1217314] New: [LenovoX13s] Unable to boot from USB
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1217314 Bug ID: 1217314 Summary: [LenovoX13s] Unable to boot from USB Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: chester.lin(a)suse.com Target Milestone: --- Found By: --- Blocker: --- On the Lenovo X13s laptop, we are able to boot DVD ISO from USB and install openSUSE Tumbleweed on a 2nd USB stick, but on reboot, the system hangs after grub loaded kernel+initrd. Live images and JeOS images are not able to boot from USB either. Fedora wiki suggests to blacklist 'modprobe.blacklist=qcom_q6v5_pas' to keep the USB from being reset/renamed. [0] But this does not work in my tests. [0]: https://fedoraproject.org/wiki/Thinkpad_X13s#Rawhide_hacking -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1214969] New: r8169: transmit queue 0 timed out
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1214969 Bug ID: 1214969 Summary: r8169: transmit queue 0 timed out Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jbaier(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I hit a possible regression in kernel 6.4.x, it seems to me that this is a very similar (or same) issue like bsc#1106833 and similar. After some time (depending on the network usage, usually within 24 hours) the kernel panic happens and the network interface becomes unusable (in fact it probably generates some nonsense on the line as it also takes down the whole network segment). This behavior can be observed in 6.4.3-1-default, 6.4.6-1-default, 6.4.9-1-default and now in 6.4.11-1-default. The issue is not happening in 6.3.9-1-default which I am using right now as a workaround. --- zář 04 21:39:12 valiant kernel: ------------[ cut here ]------------ zář 04 21:39:12 valiant kernel: NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out 8160 ms zář 04 21:39:12 valiant kernel: WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: Modules linked in: tun rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device af_packet vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 nls_cp437 vfat fat snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_hda_codec_realtek snd_sof_utils snd_hda_codec_generic mt7921e snd_hda_codec_hdmi snd_soc_core mt7921_common mt76_connac_lib snd_compress intel_rapl_msr btusb mt76 snd_hda_intel snd_pcm_dmaengine intel_rapl_common btrtl snd_intel_dspcfg btbcm snd_intel_sdw_acpi snd_pci_ps btintel edac_mce_amd snd_hda_codec btmtk asus_nb_wmi eeepc_wmi mac80211 asus_wmi snd_rpl_pci_acp6x r8169 snd_hda_core snd_acp_pci battery snd_pci_acp6x kvm_amd snd_hwdep ledtrig_audio bluetooth snd_pcm libarc4 snd_pci_acp5x sparse_keymap realtek kvm joydev ecdh_generic platform_profile snd_rn_pci_acp3x snd_timer snd_acp_config mdio_devres irqbypass wmi_bmof cfg80211 pcspkr snd acpi_cpufreq snd_soc_acpi tiny_power_button efi_pstore soundcore zář 04 21:39:12 valiant kernel: k10temp libphy i2c_piix4 snd_pci_acp3x rfkill serial_multi_instantiate button fuse configfs dmi_sysfs ip_tables x_tables hid_generic usbhid dm_crypt essiv authenc trusted asn1_encoder tee amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 i2c_algo_bit drm_ttm_helper ttm drm_suballoc_helper iommu_v2 drm_buddy xhci_pci xhci_pci_renesas gpu_sched xhci_hcd aesni_intel drm_display_helper nvme crypto_simd ucsi_acpi usbcore cryptd typec_ucsi cec nvme_core roles ccp rc_core sp5100_tco typec video wmi btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg br_netfilter bridge stp llc dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs zář 04 21:39:12 valiant kernel: CPU: 11 PID: 0 Comm: swapper/11 Tainted: G O 6.4.11-1-default #1 openSUSE Tumbleweed b71e9da2e7bdf20ad15c36d48af8b3d0ec2bfcc0 zář 04 21:39:12 valiant kernel: Hardware name: ASUSTeK COMPUTER INC. MINIPC PN52/PN52, BIOS 11800 09/07/2022 zář 04 21:39:12 valiant kernel: RIP: 0010:dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: Code: ff ff ff 48 89 df c6 05 ba 31 5d 01 01 e8 fa 38 fa ff 45 89 f8 44 89 f1 48 89 de 48 89 c2 48 c7 c7 70 16 cb a6 e8 12 d9 5e ff <0f> 0b e9 2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 zář 04 21:39:12 valiant kernel: RSP: 0018:ffffb3a180438ea0 EFLAGS: 00010282 zář 04 21:39:12 valiant kernel: RAX: 0000000000000000 RBX: ffff942ec3f90000 RCX: 0000000000000000 zář 04 21:39:12 valiant kernel: RDX: ffff943af5db4528 RSI: ffff943af5da74c0 RDI: 0000000000000300 zář 04 21:39:12 valiant kernel: RBP: ffff942ec3f904c8 R08: 0000000000000000 R09: ffffb3a180438d48 zář 04 21:39:12 valiant kernel: R10: 0000000000000003 R11: ffff943b2e0fcfe8 R12: ffff942e08ca6000 zář 04 21:39:12 valiant kernel: R13: ffff942ec3f9041c R14: 0000000000000000 R15: 0000000000001fe0 zář 04 21:39:12 valiant kernel: FS: 0000000000000000(0000) GS:ffff943af5d80000(0000) knlGS:0000000000000000 zář 04 21:39:12 valiant kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 zář 04 21:39:12 valiant kernel: CR2: 00007f1ff7fec980 CR3: 00000000bbc36000 CR4: 0000000000750ee0 zář 04 21:39:12 valiant kernel: PKRU: 55555554 zář 04 21:39:12 valiant kernel: Call Trace: zář 04 21:39:12 valiant kernel: <IRQ> zář 04 21:39:12 valiant kernel: ? dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: ? __warn+0x81/0x130 zář 04 21:39:12 valiant kernel: ? dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: ? report_bug+0x171/0x1a0 zář 04 21:39:12 valiant kernel: ? handle_bug+0x3c/0x80 zář 04 21:39:12 valiant kernel: ? exc_invalid_op+0x17/0x70 zář 04 21:39:12 valiant kernel: ? asm_exc_invalid_op+0x1a/0x20 zář 04 21:39:12 valiant kernel: ? dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: ? __pfx_dev_watchdog+0x10/0x10 zář 04 21:39:12 valiant kernel: ? __pfx_dev_watchdog+0x10/0x10 zář 04 21:39:12 valiant kernel: call_timer_fn+0x27/0x130 zář 04 21:39:12 valiant kernel: __run_timers.part.0+0x1d8/0x280 zář 04 21:39:12 valiant kernel: ? __x86_return_thunk+0x9/0x10 zář 04 21:39:12 valiant kernel: ? __x86_return_thunk+0x9/0x10 zář 04 21:39:12 valiant kernel: ? ktime_get+0x3c/0xa0 zář 04 21:39:12 valiant kernel: ? __x86_return_thunk+0x9/0x10 zář 04 21:39:12 valiant kernel: run_timer_softirq+0x2a/0x50 zář 04 21:39:12 valiant kernel: __do_softirq+0xca/0x2a5 zář 04 21:39:12 valiant kernel: __irq_exit_rcu+0xae/0xe0 zář 04 21:39:12 valiant kernel: sysvec_apic_timer_interrupt+0x72/0x90 zář 04 21:39:12 valiant kernel: </IRQ> zář 04 21:39:12 valiant kernel: <TASK> zář 04 21:39:12 valiant kernel: asm_sysvec_apic_timer_interrupt+0x1a/0x20 zář 04 21:39:12 valiant kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x440 zář 04 21:39:12 valiant kernel: Code: 2a ea 47 ff e8 d5 f1 ff ff 8b 53 04 49 89 c5 0f 1f 44 00 00 31 ff e8 b3 f6 46 ff 45 84 ff 0f 85 56 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 85 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d zář 04 21:39:12 valiant kernel: RSP: 0018:ffffb3a1801d7e90 EFLAGS: 00000246 zář 04 21:39:12 valiant kernel: RAX: ffff943af5dba080 RBX: ffff942e08d7bc00 RCX: 000000000000045a zář 04 21:39:12 valiant kernel: RDX: 000000000000000b RSI: 000011088cb991b0 RDI: 0000000000000000 zář 04 21:39:12 valiant kernel: RBP: 0000000000000003 R08: ffffffffffcd2371 R09: 000000002690b399 zář 04 21:39:12 valiant kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffffffffa7632be0 zář 04 21:39:12 valiant kernel: R13: 000011088cb991b0 R14: 0000000000000003 R15: 0000000000000000 zář 04 21:39:12 valiant kernel: cpuidle_enter+0x2d/0x40 zář 04 21:39:12 valiant kernel: do_idle+0x20d/0x270 zář 04 21:39:12 valiant kernel: cpu_startup_entry+0x1d/0x20 zář 04 21:39:12 valiant kernel: start_secondary+0x12e/0x150 zář 04 21:39:12 valiant kernel: secondary_startup_64_no_verify+0x10b/0x10b zář 04 21:39:12 valiant kernel: </TASK> zář 04 21:39:12 valiant kernel: ---[ end trace 0000000000000000 ]--- --- 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) Subsystem: ASUSTeK Computer Inc. Device 87d7 Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 12 I/O ports at f000 [size=256] Memory at fce00000 (64-bit, non-prefetchable) [size=64K] Memory at fce10000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable+ Count=32 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [148] Virtual Channel Capabilities: [168] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [178] Transaction Processing Hints Capabilities: [204] Latency Tolerance Reporting Capabilities: [20c] L1 PM Substates Capabilities: [21c] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?> Kernel driver in use: r8169 Kernel modules: r8169 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215251] New: BTRFS: transaction aborted, forced readonly
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215251 Bug ID: 1215251 Summary: BTRFS: transaction aborted, forced readonly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My laptop hit this today (latest TW): Sep 12 11:26:53 hermes.in-addr.de kernel: ------------[ cut here ]------------ Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS: Transaction aborted (error -17) Sep 12 11:26:53 hermes.in-addr.de kernel: WARNING: CPU: 3 PID: 1289 at fs/btrfs/delayed-inode.c:1158 __btrfs_run_delayed_items+0x27d/0x290 [btrfs] Sep 12 11:26:53 hermes.in-addr.de kernel: Modules linked in: tun ccm michael_mic snd_seq_dummy snd_hrtimer snd_seq af_packet algif_hash af_alg r8153_ecm cdc_ether usbnet r8152 mii snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device nft_masq nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nf_log_syslog nft_log nft_ct nft_chain_nat iscsi_ibft iscsi_boot_sysfs nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security cdc_acm ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter qrtr_mhi uvcvideo videobuf2_vmalloc uvc videobuf2_memops videobuf2_v4l2 videobuf2_common bnep binfmt_misc snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel Sep 12 11:26:53 hermes.in-addr.de kernel: soundwire_cadence snd_sof_intel_hda_mlink snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda nls_iso8859_1 snd_hda_ext_core snd_soc_acpi_intel_match nls_cp437 snd_soc_acpi soundwire_generic_allocation soundwire_bus vfat xxhash_generic fat snd_soc_core qrtr snd_compress snd_pcm_dmaengine ath11k_pci hid_multitouch ath11k spi_nor snd_hda_intel iTCO_wdt snd_intel_dspcfg snd_intel_sdw_acpi mtd x86_pkg_temp_thermal intel_pmc_bxt intel_powerclamp iTCO_vendor_support qmi_helpers mei_pxp snd_hda_codec dell_laptop coretemp pmt_telemetry mei_hdcp kvm_intel snd_hda_core intel_rapl_msr pmt_class dell_smm_hwmon snd_hwdep hci_uart mac80211 btqca dell_wmi snd_pcm kvm btrtl btbcm snd_timer dell_smbios pcspkr efi_pstore btintel irqbypass dcdbas libarc4 dell_wmi_ddv cfg80211 bluetooth dell_wmi_sysman ledtrig_audio dell_wmi_descriptor firmware_attributes_class wmi_bmof snd processor_thermal_device_pci_legacy i2c_i801 spi_intel_pci processor_thermal_device hid_sensor_als spi_intel Sep 12 11:26:53 hermes.in-addr.de kernel: i2c_smbus mhi soundcore hid_sensor_trigger tiny_power_button processor_thermal_rfim mei_me hid_sensor_iio_common processor_thermal_mbox industrialio_triggered_buffer processor_thermal_rapl kfifo_buf thunderbolt mei intel_rapl_common industrialio intel_lpss_pci ecdh_generic intel_vsec intel_lpss intel_soc_dts_iosf igen6_edac idma64 int3403_thermal button rfkill int340x_thermal_zone intel_skl_int3472_tps68470 intel_hid tps68470_regulator intel_skl_int3472_discrete int3400_thermal sparse_keymap acpi_thermal_rel intel_pmc_core acpi_tad ac acpi_pad joydev nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse configfs dmi_sysfs ip_tables x_tables dm_crypt essiv authenc trusted asn1_encoder tee uas usb_storage hid_logitech_hidpp hid_logitech_dj typec_displayport usbhid hid_sensor_hub hid_generic intel_ishtp_hid nvme nvme_core i915 crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 i2c_algo_bit drm_buddy drm_display_helper rtsx_pci_sdmmc xhci_pci xhci_pci_renesas Sep 12 11:26:53 hermes.in-addr.de kernel: mmc_core cec xhci_hcd rc_core aesni_intel ucsi_acpi typec_ucsi intel_ish_ipc crypto_simd cryptd usbcore roles rtsx_pci intel_ishtp vmd ttm typec video battery i2c_hid_acpi i2c_hid wmi pinctrl_tigerlake serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq dm_mirror dm_region_hash dm_log v4l2loopback(O) videodev mc sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua br_netfilter bridge stp llc msr efivarfs Sep 12 11:26:53 hermes.in-addr.de kernel: Unloaded tainted modules: bbswitch(O):2 Sep 12 11:26:53 hermes.in-addr.de kernel: CPU: 3 PID: 1289 Comm: btrfs-transacti Tainted: G O 6.4.12-1-default #1 openSUSE Tumbleweed 90d5a85b7d5cd5540ea49c35d1d7246e55e75794 Sep 12 11:26:53 hermes.in-addr.de kernel: Hardware name: Dell Inc. XPS 13 9310/0F7M4C, BIOS 3.17.0 07/12/2023 Sep 12 11:26:53 hermes.in-addr.de kernel: RIP: 0010:__btrfs_run_delayed_items+0x27d/0x290 [btrfs] Sep 12 11:26:53 hermes.in-addr.de kernel: Code: e9 49 fe ff ff 49 8b 7c 24 50 44 89 fa 48 c7 c6 50 f7 7a c0 e8 c4 73 04 00 eb ac 44 89 fe 48 c7 c7 20 f7 7a c0 e8 73 64 ff f9 <0f> 0b eb 99 41 bf f4 ff ff ff e9 f0 fe ff ff 0f 1f 40 00 90 90 90 Sep 12 11:26:53 hermes.in-addr.de kernel: RSP: 0018:ffffbbb60212be18 EFLAGS: 00010286 Sep 12 11:26:53 hermes.in-addr.de kernel: RAX: 0000000000000000 RBX: ffff95de205f2918 RCX: 0000000000000027 Sep 12 11:26:53 hermes.in-addr.de kernel: RDX: ffff95e32f5a74c8 RSI: 0000000000000001 RDI: ffff95e32f5a74c0 Sep 12 11:26:53 hermes.in-addr.de kernel: RBP: ffff95de205f28c0 R08: 0000000000000000 R09: ffffbbb60212bcc0 Sep 12 11:26:53 hermes.in-addr.de kernel: R10: 0000000000000003 R11: ffff95e34f7401e8 R12: ffff95dbf8902a90 Sep 12 11:26:53 hermes.in-addr.de kernel: R13: ffff95de778c1850 R14: ffff95dc00467800 R15: 00000000ffffffef Sep 12 11:26:53 hermes.in-addr.de kernel: FS: 0000000000000000(0000) GS:ffff95e32f580000(0000) knlGS:0000000000000000 Sep 12 11:26:53 hermes.in-addr.de kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 12 11:26:53 hermes.in-addr.de kernel: CR2: 00007f3e63a04960 CR3: 00000001796c4001 CR4: 0000000000f70ee0 Sep 12 11:26:53 hermes.in-addr.de kernel: PKRU: 55555554 Sep 12 11:26:53 hermes.in-addr.de kernel: Call Trace: Sep 12 11:26:53 hermes.in-addr.de kernel: <TASK> Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? __warn+0x81/0x130 Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? report_bug+0x171/0x1a0 Sep 12 11:26:53 hermes.in-addr.de kernel: ? handle_bug+0x3c/0x80 Sep 12 11:26:53 hermes.in-addr.de kernel: ? exc_invalid_op+0x17/0x70 Sep 12 11:26:53 hermes.in-addr.de kernel: ? asm_exc_invalid_op+0x1a/0x20 Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: btrfs_commit_transaction+0x15f/0xe90 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? start_transaction+0xc5/0x5d0 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: transaction_kthread+0x141/0x1b0 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? __pfx_transaction_kthread+0x10/0x10 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: kthread+0xe5/0x120 Sep 12 11:26:53 hermes.in-addr.de kernel: ? __pfx_kthread+0x10/0x10 Sep 12 11:26:53 hermes.in-addr.de kernel: ret_from_fork+0x29/0x50 Sep 12 11:26:53 hermes.in-addr.de kernel: </TASK> Sep 12 11:26:53 hermes.in-addr.de kernel: ---[ end trace 0000000000000000 ]--- Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS: error (device dm-4: state A) in __btrfs_run_delayed_items:1158: errno=-17 Object already exists Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS info (device dm-4: state EA): forced readonly Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS warning (device dm-4: state EA): Skipping commit of aborted transaction. Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS: error (device dm-4: state EA) in cleanup_transaction:1984: errno=-17 Object already exists Sep 12 11:27:03 hermes.in-addr.de wireplumber[18046]: could not save restore-stream: Failed to create file “/home/lmb/.local/state/wireplumber/restore-stream.EN8MB2”: Read-only file system After a subsequent reboot, btrfs check did not find any errors on the file system, and the system has been up and running since. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215665] New: Lenovo ThinkPad T14s Gen 2a intermittent freezing / "your system is too slow"
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215665 Bug ID: 1215665 Summary: Lenovo ThinkPad T14s Gen 2a intermittent freezing / "your system is too slow" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, said machine will randomly freeze for a marginal period of time (1-5 seconds). This is particularly noticeable while performing touch-typing, where the short freezes result in irregular text input (missing, duplicate, or infinite characters). I attempted booting with `amd_pstate=active` with no change in behavior. My desktop environment is openSUSEway (Sway/Wayland). This problem started occurring some Tumbleweed snapshots ago, though I don't recall exactly - there were other freezing issues with this hardware model before, though not in the current form where it happens consistently for short periods throughout the day. There's nothing printed in the kernel log when this happens, but the system journal is spammed with the following: ``` Sep 25 13:09:44 dreamland sway[2704]: 25:10:18.402 [ERROR] [wlr] [libinput] event5 - Microsoft Microsoft Ergonomic Mouse: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages. Sep 25 13:10:03 dreamland sway[2704]: 25:10:36.590 [ERROR] [wlr] [libinput] event6 - Logitech K350: client bug: event processing lagging behind by 26ms, your system is too slow ``` Currently I am running: ``` $ grep ^VERSION /etc/os-release ; uname -r ; cpupower frequency-info --driver VERSION_ID="20230921" 6.5.4-1-default analyzing CPU 15: driver: amd-pstate-epp ``` Note that the behavior happens both under load and when idle, directly after rebooting. Happy to test any other constellations or provide more information as needed. I entered this in the Kernel component as there seem to have been other kernel issues with this machine in the past, however feel free to route elsewhere should this not apply here. Would appreciate any help, Georg -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1225574] New: AUDIT-FIND: apache2-mod_mono: configuration defaults to predictable socket path in /tmp
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1225574 Bug ID: 1225574 Summary: AUDIT-FIND: apache2-mod_mono: configuration defaults to predictable socket path in /tmp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- apache2-mod_mono, by default, creates a socket `/tmp/mod_mono_server_global`, allowing unprivileged users to break the module by creating an identically named file in that location. However a) this behavior is documented b) it is mitigated by a systemd hardening in the apache2 package: > [Unit] > Description=The Apache Webserver > After=network.target nss-lookup.target time-sync.target remote-fs.target > Before=getty(a)tty1.service plymouth-quit.service xdm.service > PartOf=apache2.target > [Service] > Type=notify > PrivateTmp=true -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1219943] New: Certificate error while fetching from https://debuginfod.opensuse.org
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1219943 Bug ID: 1219943 Summary: Certificate error while fetching from https://debuginfod.opensuse.org Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: jimis(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Certificate error while fetching from https://debuginfod.opensuse.org Sorry about setting the component to "other" but I couldn't find a suitable one, I was searching for something like "infrastructure" or "administration". -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1223434] New: /etc/fonts/conf.d/21-emoji-rendering.conf makes emoji rendering in Firefox worse
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1223434 Bug ID: 1223434 Summary: /etc/fonts/conf.d/21-emoji-rendering.conf makes emoji rendering in Firefox worse Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: gerald_chen(a)foxmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874523 --> https://bugzilla.suse.com/attachment.cgi?id=874523&action=edit With 21.conf vs without 21.conf I've noticed that emoji look weird in Firefox, as shown in the upper side of the attachment (look at those spooky triangle eyes!). After deleting /etc/fonts/conf.d/21-emoji-rendering.conf, emoji got rendered properly, as shown in the lower side of the attachment. Other applications, such as Konsole and Chromium, don't have this problem. /etc/fonts/conf.d/21-emoji-rendering.conf says that emoji fonts don't need hinting. It seems not to be the case. My fontconfig file in home directory hasn't specified hinting or hintstyle. System info: Operating System: openSUSE Tumbleweed 20240423 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: Wayland Other files in /etc/fonts/conf.d: 09-autohint-if-no-hinting.conf 10-hinting-slight.conf 10-rendering-options.conf 10-scale-bitmap-fonts.conf 10-sub-pixel-none.conf 10-yes-antialias.conf 11-base-rendering.conf 11-lcdfilter-default.conf 12-tt-monospace-rendering.conf 13-selective-rendering.conf 13-selective-rendering-ipa.conf 20-unhint-small-vera.conf 22-noto-cjk-rendering.conf 30-metric-aliases.conf 31-metric-aliases-bw.conf 32-emoji-reject.conf 32-symbol-substitution.conf 40-nonlatin.conf 45-generic.conf 45-latin.conf 48-spacing.conf 49-family-default.conf 49-family-default-emoji.conf 49-sansserif.conf 55-local.conf 56-user.conf 58-family-prefer-local.conf 59-family-prefer-lang-specific-cjk.conf 59-family-prefer-lang-specific.conf 59-family-prefer-lang-specific-noto.conf 60-family-prefer.conf 60-generic.conf 61-latin.conf 61-stix.conf 61-wine-aliases.conf 65-fonts-persian.conf 65-nonlatin.conf 69-unifont.conf 70-reject.conf 80-delicious.conf 90-synthetic.conf README -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213879] New: Could not allocate memory for RTAS
by bugzilla_noreply＠suse.com 28 Nov '24

28 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213879 Bug ID: 1213879 Summary: Could not allocate memory for RTAS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: PowerPC OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: dmitriy.markov(a)mezame.ru QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: Good afternoon. While booting from iso for further installation of the system, I encountered the error "Could not allocate memory for RTAS". The problem is only present in the openSUSE Leap 15.5 ppc64le distribution. OpenSUSE Leap 15.4 ppc64le does not have this problem. Of course, on the Internet there was a solution from the equipment manufacturer. (https://www.ibm.com/support/pages/could-not-allocate-memory-rtas-grub-or-ya…) But it does not help and the error remains. My opinion is that this is a bug in the distribution, if it is not, please let me know about it. Reproducible: Always Steps to Reproduce: 1.Booting LPAR from CD/DVD openSUSE-Leap-15.5-DVD-ppc64le-Media.iso 2.In the bootloader, select "install operating system" 3.We get an error Actual Results: We get an error Welcome to GRUB! search prep from disk `ieee1275//vdevice/v-s csi@3000000b/disk@8100000000000000' error: ../../grub-core/commands/prep_loadenv.c:179:no prep partition. earlycfg: root=memdisk prefix=(memdisk)/ bdev=ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000 bpart=,1 bpath=/boot/ppc64le/grub2-ieee1275 Reading vars from (ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000) error: ../../grub-core/commands/prep_loadenv.c:179:no prep partition. ENV_HINT= ENV_GRUB_DIR= ENV_FS_UUID= searching for /boot/ppc64le/grub2-ieee1275/grub.cfg /boot/ppc64le/grub2-ieee1275/grub.cfg is on ieee1275//vdevice/v-scsi@3000000b/disk@81000 00000000000,1 prefix=(ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000,1)/boot/ppc64le /grub2-ieee1275 root=ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000,1 Loading kernel ... Loading initial ramdisk ... OF stdout device is: /vdevice/vty@30000000 Preparing to boot Linux version 5.14.21-150500.53-default (geeko@buildhost) (gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binut ils; SUSE Linux Enterprise 15) 2.39.0.20220810-150100.7.40) #1 SMP Wed May 10 07:56:26 UTC 2023 (b630043) Detected machine type: 0000000000000101 command line: BOOT_IMAGE=/boot/ppc64le/linux Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 000000001fef0000 alloc_top : 0000000020000000 alloc_top_hi : 0000000020000000 rmo_top : 0000000020000000 ram_top : 0000000020000000 Could not allocate memory for RTAS EXIT called ok 0 > Expected Results: The system installer is loading iso SHA-256 checksum - pass My HW - IBM Power E880 SLES 12SP5 - also not affected by this error. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1215349] New: VUL-0: CVE-2023-4863: dssim: Heap buffer overflow in WebP
by bugzilla_noreply＠suse.com 27 Nov '24

27 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215349 Bug ID: 1215349 Summary: VUL-0: CVE-2023-4863: dssim: Heap buffer overflow in WebP Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/377966/ OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de CC: Andreas.Stieger(a)gmx.de, gianluca.gabrielli(a)suse.com, gmbr3(a)opensuse.org, gnome-bugs(a)suse.de, jengelh(a)inai.de, m.szczepaniak.000(a)gmail.com, martin.sirringhaus(a)suse.com, meissner(a)suse.com, security-team(a)suse.de, wolfgang(a)rosenauer.org, xiaoguang.wang(a)suse.com Depends on: 1215231 Blocks: 1215347 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1215231 +++ CVE-2023-4863 The Stable and Extended stable channels has been updated to 116.0.5845.187 for Mac and Linux and 116.0.5845.187/.188 for Windows, which will roll out over the coming days/weeks. A full list of changes in this build is available in the log. This update includes 1 security fix. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. CVE-2023-4863: Heap buffer overflow in WebP. Reported by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at The University of Torontoʼs Munk School on 2023-09-06 Google is aware that an exploit for CVE-2023-4863 exists in the wild. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=1479274 References: https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-des… http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 https://bugzilla.redhat.com/show_bug.cgi?id=2238431 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215347] New: VUL-0: CVE-2023-4863: zola: Heap buffer overflow in WebP
by bugzilla_noreply＠suse.com 27 Nov '24

27 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215347 Bug ID: 1215347 Summary: VUL-0: CVE-2023-4863: zola: Heap buffer overflow in WebP Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/377966/ OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Security Assignee: socvirnyl.estela(a)gmail.com Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de CC: Andreas.Stieger(a)gmx.de, gianluca.gabrielli(a)suse.com, gmbr3(a)opensuse.org, gnome-bugs(a)suse.de, jengelh(a)inai.de, m.szczepaniak.000(a)gmail.com, martin.sirringhaus(a)suse.com, meissner(a)suse.com, security-team(a)suse.de, wolfgang(a)rosenauer.org, xiaoguang.wang(a)suse.com Depends on: 1215231 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1215231 +++ CVE-2023-4863 The Stable and Extended stable channels has been updated to 116.0.5845.187 for Mac and Linux and 116.0.5845.187/.188 for Windows, which will roll out over the coming days/weeks. A full list of changes in this build is available in the log. This update includes 1 security fix. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. CVE-2023-4863: Heap buffer overflow in WebP. Reported by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at The University of Torontoʼs Munk School on 2023-09-06 Google is aware that an exploit for CVE-2023-4863 exists in the wild. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=1479274 References: https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-des… http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 https://bugzilla.redhat.com/show_bug.cgi?id=2238431 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1213370] New: tesseract-ocr should not be built with experimantal opencl support
by bugzilla_noreply＠suse.com 25 Nov '24

25 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213370 Bug ID: 1213370 Summary: tesseract-ocr should not be built with experimantal opencl support Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: opensuse(a)titlis.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- opencl in tesseract-ocr is considered experimental, according to this thread (https://groups.google.com/g/tesseract-ocr/c/eIQbsurfSEM/m/mVb_4GF1BgAJ) it is considered just an entry point for possible developers. Their own doucmentantion (https://tesseract-ocr.github.io/tessdoc/TesseractOpenCL.html) states: "Important note: OpenCL support in Tesseract is still considered experimental. There are some major bugs associated with it (see issue 837). Building Tesseract with OpenCL support is not recommended (for any version of Tesseract), unless you are a developer and want to improve the OpenCL code" Please remove the flag "--enable-opencl" from https://build.opensuse.org/package/view_file/openSUSE:Factory/tesseract-ocr… This would also resolve https://bugzilla.opensuse.org/show_bug.cgi?id=1207570 PS: I indeed encounter problems with the opencl code path -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219405] New: older clang package depends on latest libLLVM
by bugzilla_noreply＠suse.com 19 Nov '24

19 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1219405 Bug ID: 1219405 Summary: older clang package depends on latest libLLVM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: shung-hsi.yu(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Trying to install older clang will pull in the latest llvm package (libclang13 and libLLVM17): > $ zypper install clang16 # (latest is clang17 at the moment) > > The following 11 NEW packages are going to be installed: > clang16 libLLVM16 libLLVM17 libclang-cpp16 libclang-cpp17 libclang13 > libedit0 libmpdec3 libpython3_11-1_0 python311-base update-alternatives The problem is likely that c-index-test-16 is incorrectly linked to /lib64/libclang.so.13 that is created from the latest llvm package (llvm17 at the moment), and that ends up making it linked to both the latest llvm shared library (libLLVM.so.17 from llvm17) as well as one in the corresponding package (libLLVM.so.16 from llvm16). > $ ldd /usr/bin/c-index-test-16.0.6 > linux-vdso.so.1 (0x00007ffce2336000) > libclang.so.13 => /lib64/libclang.so.13 (0x00007fb21ca18000) > libclang-cpp.so.16 => /lib64/libclang-cpp.so.16 (0x00007fb218800000) > libxml2.so.2 => /lib64/libxml2.so.2 (0x00007fb218690000) > libLLVM.so.16 => /lib64/libLLVM.so.16 (0x00007fb211200000) > libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fb210e00000) > libc.so.6 => /lib64/libc.so.6 (0x00007fb210a00000) > libclang-cpp.so.17 => /lib64/libclang-cpp.so.17 (0x00007fb20c800000) > libLLVM.so.17 => /lib64/libLLVM.so.17 (0x00007fb205200000) > libm.so.6 => /lib64/libm.so.6 (0x00007fb21c92f000) > /lib64/ld-linux-x86-64.so.2 (0x00007fb21cb11000) > libz.so.1 => /lib64/glibc-hwcaps/x86-64-v3/libz.so.1.3 (0x00007fb218676000) > liblzma.so.5 => /lib64/glibc-hwcaps/x86-64-v3/liblzma.so.5.4.5 (0x00007fb21863d000) > libedit.so.0 => /lib64/libedit.so.0 (0x00007fb218601000) > libtinfo.so.6 => /lib64/libtinfo.so.6 (0x00007fb2111c5000) > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fb2111a0000) c-index-test-16.0.6 thus will segfault when ran > #0 0x00007fccc253d319 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/lib64/libLLVM.so.17+0x3b3d319) > #1 0x00007fccc253aed2 llvm::sys::RunSignalHandlers() (/lib64/libLLVM.so.17+0x3b3aed2) > #2 0x00007fccc253db9b (/lib64/libLLVM.so.17+0x3b3db9b) > #3 0x00007fccca23f190 __restore_rt (/lib64/libc.so.6+0x3f190) > #4 0x00007fccc724587a (/lib64/libclang-cpp.so.17+0x124587a) > #5 0x00007fccca2414e1 __cxa_finalize (/lib64/libc.so.6+0x414e1) > #6 0x00007fccc719c0f7 (/lib64/libclang-cpp.so.17+0x119c0f7) > Segmentation fault (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.

1 6