September 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1230373] New: No USB Support after booting on a VisionFive2 8GB system.
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1230373 Bug ID: 1230373 Summary: No USB Support after booting on a VisionFive2 8GB system. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: malcolmlewis(a)linuxmail.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 Build Identifier: USB devices present in u-boot, not visible after booting Tumbleweed. It seems this patch set should fix the issue; riscv: jh7110: Fix configuration for on-chip USB 2.0 support; <https://lore.kernel.org/all/20240815-endless-credible-324438d164f4@spud/T/> Can this be backported to the current kernel? Reproducible: Always Steps to Reproduce: Using the latest Tumbleweed RISC-V image or the one from Factory, attaching a USB device and booting device is not present. Actual Results: Booting from minicom and checking with u-boot, device is present; ```bash U-Boot SPL 2024.07 (Sep 04 2024 - 13:57:12 +0000) DDR version: dc2e84f0. Trying to boot from MMC2 U-Boot 2024.07 (Sep 04 2024 - 13:57:12 +0000) CPU: sifive,u74-mc Model: StarFive VisionFive 2 v1.3B DRAM: 8 GiB Core: 136 devices, 26 uclasses, devicetree: board WDT: Not starting watchdog@13070000 MMC: mmc@16010000: 0, mmc@16020000: 1 Loading Environment from SPIFlash... SF: Detected gd25lq128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB OK StarFive EEPROM format v2 --------EEPROM INFO-------- Vendor : StarFive Technology Co., Ltd. Product full SN: VF7110B1-2253-D008E000-00003370 data version: 0x2 PCB revision: 0xb2 BOM revision: A Ethernet MAC0 address: 6c:cf:39:00:3d:b0 Ethernet MAC1 address: 6c:cf:39:00:3d:b1 --------EEPROM INFO-------- starfive_7110_pcie pcie@2b000000: Starfive PCIe bus probed. starfive_7110_pcie pcie@2c000000: Starfive PCIe bus probed. In: serial@10000000 Out: serial@10000000 Err: serial@10000000 Net: eth0: ethernet@16030000, eth1: ethernet@16040000 starting USB... Bus xhci_pci: Register 5000420 NbrPorts 5 Starting the controller USB XHCI 1.00 scanning bus xhci_pci for devices... 4 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Working FDT set to ff72e9b0 Hit any key to stop autoboot: 0 StarFive # usb tree USB device tree: 1 Hub (5 Gb/s, 0mA) | U-Boot XHCI Host Controller | +-2 Hub (480 Mb/s, 100mA) | USB2.0 Hub | +-3 Human Interface (1.5 Mb/s, 100mA) | YSPRINGTECH USB OPTICAL MOUSE | +-4 Human Interface (1.5 Mb/s, 100mA) YSPRINGTECH USB OPTICAL MOUSE ``` Boot system, device disappears; ```bash Loading Linux 6.11.0-rc6-100-default ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Using DTB from configuration table <== USB disappears her EFI stub: Exiting boot services... usb-devices find: ‘/sys/bus/usb/devices’: No such file or directory ``` Expected Results: Any attached USB device is present in the output from lsusb or usb-devices. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1222914] Upgrade from kernel 5.14.21-150500.55.39-default to kernel 5.14.21-150500.55.44-default broke on my laptop
by bugzilla_noreply＠suse.com 28 Sep '24

28 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222914 https://bugzilla.suse.com/show_bug.cgi?id=1222914#c13 --- Comment #13 from Marc Chamberlin <marc(a)marcchamberlin.com> --- Thanks Takashi Iwai for your suggestions, and joy! It works. I installed kernel-default-5.14.21-150500.342.1.g644bf81.x86_64.rpm My questions now become: 1. Will this newer version of the kernel be part of an upcoming update? 2. Do I need to do anything to keep this and/or other software working? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231050] What does this error mean: xs_tcp_setup_socket...unhandled error -107
by bugzilla_noreply＠suse.com 28 Sep '24

28 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1231050 https://bugzilla.suse.com/show_bug.cgi?id=1231050#c3 --- Comment #3 from Anthony Iliopoulos <ailiopoulos(a)suse.com> --- (In reply to James Moe from comment #2) > > Are you using this system as a nfs client? > Yes. > > > What is the kernel release precisely (uname -a)? > $ uname -a > Linux sma-station14l 6.11.0-1-default #1 SMP PREEMPT_DYNAMIC Wed Sep 25 > 07:09:20 UTC 2024 (b87e886) x86_64 x86_64 x86_64 GNU/Linux > > > Apparently this is a rare and intermittent issue. I restarted the host after > a system update and there is none of these error messages. was there a kernel update? which kernel was exhibiting the issue before the restart? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222914] Upgrade from kernel 5.14.21-150500.55.39-default to kernel 5.14.21-150500.55.44-default broke on my laptop
by bugzilla_noreply＠suse.com 28 Sep '24

28 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222914 https://bugzilla.suse.com/show_bug.cgi?id=1222914#c12 --- Comment #12 from Marc Chamberlin <marc(a)marcchamberlin.com> --- Oh sorry, belay that last comment and send it to the bit bucked if you can. That was meant for a different problem I am having and I got my wires crossed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222914] Upgrade from kernel 5.14.21-150500.55.39-default to kernel 5.14.21-150500.55.44-default broke on my laptop
by bugzilla_noreply＠suse.com 28 Sep '24

28 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222914 https://bugzilla.suse.com/show_bug.cgi?id=1222914#c11 --- Comment #11 from Marc Chamberlin <marc(a)marcchamberlin.com> --- Thanks Takashi Iwai for your suggestions, but no joy! I installed kernel-default-5.14.21-150500.342.1.g644bf81.x86_64.rpm from the repository you suggested but it still does not allow me to bring up the X11 desktop, just Wayland. Setting the nomodeset flag makes no difference either. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231050] What does this error mean: xs_tcp_setup_socket...unhandled error -107
by bugzilla_noreply＠suse.com 28 Sep '24

28 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1231050 https://bugzilla.suse.com/show_bug.cgi?id=1231050#c2 --- Comment #2 from James Moe <jimoe(a)sma-inc.us> --- > Are you using this system as a nfs client? Yes. > What is the kernel release precisely (uname -a)? $ uname -a Linux sma-station14l 6.11.0-1-default #1 SMP PREEMPT_DYNAMIC Wed Sep 25 07:09:20 UTC 2024 (b87e886) x86_64 x86_64 x86_64 GNU/Linux Apparently this is a rare and intermittent issue. I restarted the host after a system update and there is none of these error messages. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231042] New: [Build 20240926] openQA test fails in insmod01_sh
by bugzilla_noreply＠suse.com 28 Sep '24

28 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1231042 Bug ID: 1231042 Summary: [Build 20240926] openQA test fails in insmod01_sh Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/4516395/modules/insm od01_sh/steps/6 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 Target Milestone: --- Found By: openQA Blocker: Yes Created attachment 877620 --> https://bugzilla.suse.com/attachment.cgi?id=877620&action=edit log ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-ltp-commands@aarch64-HD20G fails in [insmod01_sh](https://openqa.opensuse.org/tests/4516395/modules/insmod01_sh/… ## Test suite description backup: LTP_COMMAND_EXCLUDE=tar01_sh|logrotate_sh|unzip01_sh|df01_.*_sh|sysctl01_sh|mkfs01.*_sh|which01_sh|insmod01_sh LTP_TAINT_EXPECTED=0x8001b801 ## Reproducible Fails since (at least) Build [20240925](https://openqa.opensuse.org/tests/4513137) ## Expected result Last good: [20240924](https://openqa.opensuse.org/tests/4507219) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1231050] What does this error mean: xs_tcp_setup_socket...unhandled error -107
by bugzilla_noreply＠suse.com 27 Sep '24

27 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1231050 https://bugzilla.suse.com/show_bug.cgi?id=1231050#c1 Anthony Iliopoulos <ailiopoulos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ailiopoulos(a)suse.com --- Comment #1 from Anthony Iliopoulos <ailiopoulos(a)suse.com> --- This is a nfs-related rpc message. Are you using this system as a nfs client? What is the kernel release precisely (uname -a)? Error -107 is -ENOTCONN which implies that the tcp socket is not connected. Since you mention this happens periodically, is there any packet filtering between the client and server that could be affecting the state of the connections? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231050] New: What does this error mean: xs_tcp_setup_socket...unhandled error -107
by bugzilla_noreply＠suse.com 27 Sep '24

27 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1231050 Bug ID: 1231050 Summary: What does this error mean: xs_tcp_setup_socket...unhandled error -107 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jimoe(a)sma-inc.us QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There have been a lot of these log entries recently. They occur in groups of three about every 13-14 minutes. Web searches returned results showing this issue for years. If anyone had ever responded to those issues, it is hidden behind an account requirement. I had posted this question in Opensuse's user forum myself a year ago; no response. 2024-09-27T11:03:03-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 2024-09-27T11:03:03-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 2024-09-27T11:03:03-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 2024-09-27T11:05:17-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 2024-09-27T11:05:17-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 2024-09-27T11:05:17-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 2024-09-27T11:07:30-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 2024-09-27T11:07:30-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 2024-09-27T11:09:43-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 2024-09-27T11:09:43-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 2024-09-27T11:09:43-07:00 sma-station14l kernel: xs_tcp_setup_socket: connect returned unhandled error -107 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1229054] Error probing device: Error sending ATA command IDENTIFY DEVICE to...
by bugzilla_noreply＠suse.com 27 Sep '24

27 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1229054 https://bugzilla.suse.com/show_bug.cgi?id=1229054#c45 --- Comment #45 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2024:3483-1: An update that solves 296 vulnerabilities, contains two features and has 42 security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-su-20243483-1 Category: security (important) Bug References: 1193629, 1194111, 1194765, 1194869, 1196261, 1196516, 1196894, 1198017, 1203329, 1203330, 1203360, 1205462, 1206006, 1206258, 1206843, 1207158, 1208783, 1210644, 1213580, 1213632, 1214285, 1216834, 1220428, 1220877, 1220962, 1221269, 1221326, 1221630, 1221645, 1222335, 1222350, 1222372, 1222387, 1222634, 1222808, 1222967, 1223074, 1223191, 1223508, 1223720, 1223742, 1223777, 1223803, 1223807, 1224105, 1224415, 1224496, 1224510, 1224542, 1224578, 1224639, 1225162, 1225352, 1225428, 1225524, 1225578, 1225582, 1225773, 1225814, 1225827, 1225832, 1225903, 1226168, 1226530, 1226613, 1226742, 1226765, 1226798, 1226801, 1226874, 1226885, 1227079, 1227623, 1227761, 1227830, 1227863, 1227867, 1227929, 1227937, 1227958, 1228020, 1228065, 1228114, 1228410, 1228426, 1228427, 1228429, 1228446, 1228447, 1228449, 1228450, 1228452, 1228456, 1228463, 1228466, 1228467, 1228469, 1228480, 1228481, 1228482, 1228483, 1228484, 1228485, 1228487, 1228489, 1228491, 1228493, 1228494, 1228495, 1228496, 1228501, 1228503, 1228509, 1228513, 1228515, 1228516, 1228526, 1228531, 1228563, 1228564, 1228567, 1228576, 1228579, 1228584, 1228588, 1228590, 1228615, 1228616, 1228635, 1228636, 1228654, 1228656, 1228658, 1228660, 1228662, 1228667, 1228673, 1228677, 1228687, 1228706, 1228708, 1228710, 1228718, 1228720, 1228721, 1228722, 1228724, 1228726, 1228727, 1228733, 1228748, 1228766, 1228779, 1228801, 1228850, 1228857, 1228959, 1228964, 1228966, 1228967, 1228979, 1228988, 1228989, 1228991, 1228992, 1229042, 1229054, 1229086, 1229136, 1229154, 1229187, 1229188, 1229190, 1229287, 1229290, 1229292, 1229296, 1229297, 1229301, 1229303, 1229304, 1229305, 1229307, 1229309, 1229312, 1229314, 1229315, 1229317, 1229318, 1229319, 1229327, 1229341, 1229345, 1229346, 1229347, 1229349, 1229350, 1229351, 1229354, 1229356, 1229357, 1229358, 1229359, 1229360, 1229366, 1229370, 1229373, 1229374, 1229381, 1229382, 1229383, 1229386, 1229388, 1229391, 1229392, 1229395, 1229398, 1229399, 1229400, 1229407, 1229409, 1229410, 1229411, 1229413, 1229414, 1229417, 1229418, 1229444, 1229453, 1229454, 1229481, 1229482, 1229488, 1229489, 1229490, 1229493, 1229495, 1229497, 1229500, 1229503, 1229506, 1229507, 1229508, 1229509, 1229510, 1229512, 1229516, 1229521, 1229522, 1229523, 1229524, 1229525, 1229526, 1229527, 1229528, 1229529, 1229531, 1229533, 1229535, 1229536, 1229537, 1229540, 1229544, 1229545, 1229546, 1229547, 1229548, 1229554, 1229557, 1229558, 1229559, 1229560, 1229562, 1229564, 1229565, 1229566, 1229568, 1229569, 1229572, 1229573, 1229576, 1229581, 1229588, 1229598, 1229603, 1229604, 1229605, 1229608, 1229611, 1229612, 1229613, 1229614, 1229615, 1229616, 1229617, 1229620, 1229622, 1229623, 1229624, 1229625, 1229626, 1229628, 1229629, 1229630, 1229631, 1229632, 1229635, 1229636, 1229637, 1229638, 1229639, 1229641, 1229642, 1229643, 1229645, 1229657, 1229658, 1229662, 1229664, 1229707, 1229739, 1229743, 1229746, 1229754, 1229755, 1229756, 1229759, 1229761, 1229767, 1229768, 1229781, 1229784, 1229787, 1229788, 1229789, 1229792, 1229820, 1230413 CVE References: CVE-2021-4204, CVE-2021-4441, CVE-2021-47106, CVE-2021-47517, CVE-2021-47546, CVE-2022-0500, CVE-2022-23222, CVE-2022-38457, CVE-2022-40133, CVE-2022-4382, CVE-2022-48645, CVE-2022-48706, CVE-2022-48808, CVE-2022-48865, CVE-2022-48868, CVE-2022-48869, CVE-2022-48870, CVE-2022-48871, CVE-2022-48872, CVE-2022-48873, CVE-2022-48875, CVE-2022-48878, CVE-2022-48880, CVE-2022-48881, CVE-2022-48882, CVE-2022-48883, CVE-2022-48884, CVE-2022-48885, CVE-2022-48886, CVE-2022-48887, CVE-2022-48888, CVE-2022-48889, CVE-2022-48890, CVE-2022-48891, CVE-2022-48893, CVE-2022-48896, CVE-2022-48898, CVE-2022-48899, CVE-2022-48903, CVE-2022-48904, CVE-2022-48905, CVE-2022-48906, CVE-2022-48907, CVE-2022-48909, CVE-2022-48910, CVE-2022-48912, CVE-2022-48913, CVE-2022-48914, CVE-2022-48915, CVE-2022-48916, CVE-2022-48917, CVE-2022-48918, CVE-2022-48919, CVE-2022-48920, CVE-2022-48921, CVE-2022-48923, CVE-2022-48924, CVE-2022-48925, CVE-2022-48926, CVE-2022-48927, CVE-2022-48928, CVE-2022-48929, CVE-2022-48930, CVE-2022-48931, CVE-2022-48932, CVE-2022-48934, CVE-2022-48937, CVE-2022-48938, CVE-2022-48939, CVE-2022-48940, CVE-2022-48941, CVE-2022-48942, CVE-2022-48943, CVE-2023-3610, CVE-2023-52458, CVE-2023-52489, CVE-2023-52498, CVE-2023-52581, CVE-2023-52859, CVE-2023-52887, CVE-2023-52889, CVE-2023-52893, CVE-2023-52894, CVE-2023-52896, CVE-2023-52898, CVE-2023-52899, CVE-2023-52900, CVE-2023-52901, CVE-2023-52904, CVE-2023-52905, CVE-2023-52906, CVE-2023-52907, CVE-2023-52908, CVE-2023-52909, CVE-2023-52910, CVE-2023-52911, CVE-2023-52912, CVE-2023-52913, CVE-2024-26631, CVE-2024-26668, CVE-2024-26669, CVE-2024-26677, CVE-2024-26735, CVE-2024-26808, CVE-2024-26812, CVE-2024-26835, CVE-2024-26851, CVE-2024-27010, CVE-2024-27011, CVE-2024-27016, CVE-2024-27024, CVE-2024-27079, CVE-2024-27403, CVE-2024-31076, CVE-2024-35897, CVE-2024-35902, CVE-2024-35945, CVE-2024-35971, CVE-2024-36009, CVE-2024-36013, CVE-2024-36270, CVE-2024-36286, CVE-2024-36489, CVE-2024-36929, CVE-2024-36933, CVE-2024-36936, CVE-2024-36962, CVE-2024-38554, CVE-2024-38602, CVE-2024-38662, CVE-2024-39489, CVE-2024-40905, CVE-2024-40978, CVE-2024-40980, CVE-2024-40995, CVE-2024-41000, CVE-2024-41007, CVE-2024-41009, CVE-2024-41011, CVE-2024-41016, CVE-2024-41020, CVE-2024-41022, CVE-2024-41035, CVE-2024-41036, CVE-2024-41038, CVE-2024-41039, CVE-2024-41042, CVE-2024-41045, CVE-2024-41056, CVE-2024-41060, CVE-2024-41062, CVE-2024-41065, CVE-2024-41068, CVE-2024-41073, CVE-2024-41079, CVE-2024-41080, CVE-2024-41087, CVE-2024-41088, CVE-2024-41089, CVE-2024-41092, CVE-2024-41093, CVE-2024-41095, CVE-2024-41097, CVE-2024-41098, CVE-2024-42069, CVE-2024-42074, CVE-2024-42076, CVE-2024-42077, CVE-2024-42080, CVE-2024-42082, CVE-2024-42085, CVE-2024-42086, CVE-2024-42087, CVE-2024-42089, CVE-2024-42090, CVE-2024-42092, CVE-2024-42095, CVE-2024-42097, CVE-2024-42098, CVE-2024-42101, CVE-2024-42104, CVE-2024-42106, CVE-2024-42107, CVE-2024-42110, CVE-2024-42114, CVE-2024-42115, CVE-2024-42119, CVE-2024-42120, CVE-2024-42121, CVE-2024-42126, CVE-2024-42127, CVE-2024-42130, CVE-2024-42137, CVE-2024-42139, CVE-2024-42142, CVE-2024-42143, CVE-2024-42148, CVE-2024-42152, CVE-2024-42155, CVE-2024-42156, CVE-2024-42157, CVE-2024-42158, CVE-2024-42162, CVE-2024-42223, CVE-2024-42225, CVE-2024-42228, CVE-2024-42229, CVE-2024-42230, CVE-2024-42232, CVE-2024-42236, CVE-2024-42237, CVE-2024-42238, CVE-2024-42239, CVE-2024-42240, CVE-2024-42244, CVE-2024-42246, CVE-2024-42247, CVE-2024-42268, CVE-2024-42271, CVE-2024-42274, CVE-2024-42276, CVE-2024-42277, CVE-2024-42280, CVE-2024-42281, CVE-2024-42283, CVE-2024-42284, CVE-2024-42285, CVE-2024-42286, CVE-2024-42287, CVE-2024-42288, CVE-2024-42289, CVE-2024-42291, CVE-2024-42292, CVE-2024-42295, CVE-2024-42301, CVE-2024-42302, CVE-2024-42308, CVE-2024-42309, CVE-2024-42310, CVE-2024-42311, CVE-2024-42312, CVE-2024-42313, CVE-2024-42315, CVE-2024-42318, CVE-2024-42319, CVE-2024-42320, CVE-2024-42322, CVE-2024-43816, CVE-2024-43818, CVE-2024-43819, CVE-2024-43821, CVE-2024-43823, CVE-2024-43829, CVE-2024-43830, CVE-2024-43831, CVE-2024-43834, CVE-2024-43837, CVE-2024-43839, CVE-2024-43841, CVE-2024-43842, CVE-2024-43846, CVE-2024-43849, CVE-2024-43853, CVE-2024-43854, CVE-2024-43856, CVE-2024-43858, CVE-2024-43860, CVE-2024-43861, CVE-2024-43863, CVE-2024-43866, CVE-2024-43867, CVE-2024-43871, CVE-2024-43872, CVE-2024-43873, CVE-2024-43879, CVE-2024-43880, CVE-2024-43882, CVE-2024-43883, CVE-2024-43884, CVE-2024-43889, CVE-2024-43892, CVE-2024-43893, CVE-2024-43894, CVE-2024-43895, CVE-2024-43899, CVE-2024-43900, CVE-2024-43902, CVE-2024-43903, CVE-2024-43904, CVE-2024-43905, CVE-2024-43907, CVE-2024-43908, CVE-2024-43909, CVE-2024-44938, CVE-2024-44939, CVE-2024-44947 Jira References: PED-8491, PED-8779 Maintenance Incident: [SUSE:Maintenance:35521](https://smelt.suse.de/incident/35521/) Sources used: openSUSE Leap 15.5 (src): kernel-obs-build-5.14.21-150500.55.80.1, kernel-syms-5.14.21-150500.55.80.1, kernel-source-5.14.21-150500.55.80.2, kernel-livepatch-SLE15-SP5_Update_19-1-150500.11.3.2, kernel-obs-qa-5.14.21-150500.55.80.1, kernel-default-base-5.14.21-150500.55.80.2.150500.6.35.6 openSUSE Leap Micro 5.5 (src): kernel-default-base-5.14.21-150500.55.80.2.150500.6.35.6 SUSE Linux Enterprise Micro 5.5 (src): kernel-default-base-5.14.21-150500.55.80.2.150500.6.35.6 Basesystem Module 15-SP5 (src): kernel-source-5.14.21-150500.55.80.2, kernel-default-base-5.14.21-150500.55.80.2.150500.6.35.6 Development Tools Module 15-SP5 (src): kernel-obs-build-5.14.21-150500.55.80.1, kernel-syms-5.14.21-150500.55.80.1, kernel-source-5.14.21-150500.55.80.2 SUSE Linux Enterprise Live Patching 15-SP5 (src): kernel-livepatch-SLE15-SP5_Update_19-1-150500.11.3.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0