- openSUSE Bugs

[Bug 1234405] New: devel:microos/libeconf: Bug libeconf 0.7.5 causes systemd/sddm/pam/libc crash and prevents login
by bugzilla_noreply＠suse.com 19 Dec '24

19 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234405 Bug ID: 1234405 Summary: devel:microos/libeconf: Bug libeconf 0.7.5 causes systemd/sddm/pam/libc crash and prevents login Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: rbrown(a)suse.com Reporter: pallaswept(a)proton.me QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 879108 --> https://bugzilla.suse.com/attachment.cgi?id=879108&action=edit output of `journalctl -b -2 |rg dumped -A 40` After today's dup, I rebooted to a desktop with a mouse cursor and otherwise unresponsive. Switching to a TTY showed an error "Unable to start user manager for user 1000". I was unable to login with any account including root. Using the recovery console, I was able to retrieve logs, find this culprit, rollback, and am currently working after locking out the libeconf updates with `sudo zypper al libeconf0 libeconf0-32bit libeconf-devel` Not sure if this is just me, hopefully it is. I did have some custom pam config, which I naturally removed to test, and there was no change, but I did notice that `rpm -qf /etc/pam.d/*` returns several "file foo is not owned by any package", and none of those files are mine. I'm not sure if this is intentional or if it is related. Relevant section of the journal is attached. Please let me know if I can help in any way. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1234703] New: VUL-0: CVE-2024-56128: kafka: SCRAM authentication vulnerable to replay attacks when used without encryption
by bugzilla_noreply＠suse.com 19 Dec '24

19 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234703 Bug ID: 1234703 Summary: VUL-0: CVE-2024-56128: kafka: SCRAM authentication vulnerable to replay attacks when used without encryption Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/433309/ 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: stoyan.manolov(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation. Issue Summary: Apache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1]. Specifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message. However, Kafka's SCRAM implementation did not perform this validation. Impact: This vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly discouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3]. Deployments using SCRAM with TLS are not affected by this issue. How to Detect If You Are Impacted: If your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted. To check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted. Fix Details: The issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802. Affected Versions: Apache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below. Fixed Versions: 3.9.0 3.8.1 3.7.2 Users are advised to upgrade to 3.7.2 or later to mitigate this issue. Recommendations for Mitigation: Users unable to upgrade to the fixed versions can mitigate the issue by: - Using TLS with SCRAM Authentication: Always deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception. - Considering Alternative Authentication Mechanisms: Evaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56128 https://www.cve.org/CVERecord?id=CVE-2024-56128 https://datatracker.ietf.org/doc/html/rfc5802 https://datatracker.ietf.org/doc/html/rfc5802#section-9 https://kafka.apache.org/documentation/#security_sasl_scram_security https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw https://seclists.org/oss-sec/2024/q4/162 http://www.openwall.com/lists/oss-security/2024/12/18/3 https://bugzilla.redhat.com/show_bug.cgi?id=2333013 https://github.com/CVEProject/cvelistV5/blob/main//cves/2024/56xxx/CVE-2024… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1234406] New: bind package root.hints outdated
by bugzilla_noreply＠suse.com 18 Dec '24

18 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234406 Bug ID: 1234406 Summary: bind package root.hints outdated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: patrick.schaaf(a)yalwa.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Package bind-9.20.3-1.1.x86_64, current as of tumbleweed 20241210, contains an outdated root.hints file. Canonical source is https://www.internic.net/domain/named.root and has for b.root-servers.net > ; last update: November 20, 2024 > B.ROOT-SERVERS.NET. 3600000 A 170.247.170.2 > B.ROOT-SERVERS.NET. 3600000 AAAA 2801:1b8:10::b Packaged file has > ; last update: July 28, 2021 > B.ROOT-SERVERS.NET. 3600000 A 199.9.14.201 > B.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:200::b I noticed this because apparently bind has a builtin list, and using that, puts this warning into syslog: Dec 12 08:33:01 track named[616754]: checkhints: b.root-servers.net/A (170.247.170.2) missing from hints Dec 12 08:33:01 track named[616754]: checkhints: b.root-servers.net/A (199.9.14.201) extra record in hints Dec 12 08:33:01 track named[616754]: checkhints: b.root-servers.net/AAAA (2801:1b8:10::b) missing from hints Dec 12 08:33:01 track named[616754]: checkhints: b.root-servers.net/AAAA (2001:500:200::b) extra record in hints -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1234691] Yast2: Add "About" section or button to show program and module versions, show yast version in terminal
by bugzilla_noreply＠suse.com 18 Dec '24

18 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234691 https://bugzilla.suse.com/show_bug.cgi?id=1234691#c1 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #1 from Stefan Hundhammer <shundhammer(a)suse.com> --- That information is easily obtainable from /var/log/YaST/y2log (the UI versions) or from rpm -qa "libyui*" rpm -qa "yast2*" There is no need to clutter the UI with it, even less so since YaST consists of several dozen packages; and it's of very limited use to almost all users. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226207] New: breeze-dark (kf6-breeze-icons) symbolic icons aren't recolored and dark though should be light
by bugzilla_noreply＠suse.com 18 Dec '24

18 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1226207 Bug ID: 1226207 Summary: breeze-dark (kf6-breeze-icons) symbolic icons aren't recolored and dark though should be light 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: w01dnick(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- kf6-breeze-icons generate identical icons for both breeze & breeze-dark. While this is not an issue for KF6 apps, that use run-time recoloring, in KF5 apps, like Krusader, when dark color theme is used and icons are breeze-dark symbolic icons are dark on dark background and almost invisible. The reason is this build option: `-DWITH_ICON_GENERATION:BOOL=FALSE` I've tried to make my custom build [1] switching it to TRUE and breeze-dark icons are fine with Krusader now. But I don't know the reasoning behind switching it to FALSE. There is comment: ``` saves ~30MB and installs dangling symlinks ``` Less size is true, though IMHO it's not a good solution to break KF5 apps to save some space. But I can't see any dangling symlinks: ``` find /usr/share/icons/breeze{,-dark} -xtype l ``` doesn't find anything. Any other reason or should I cleanup [1] and make a submit request? [1] https://build.opensuse.org/package/show/home:NickLion:branches:KDE:Framewor… -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1230643] [SELinux] semodule removal issues
by bugzilla_noreply＠suse.com 18 Dec '24

18 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1230643 https://bugzilla.suse.com/show_bug.cgi?id=1230643#c11 Cathy Hu <cathy.hu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #11 from Cathy Hu <cathy.hu(a)suse.com> --- probably would make sense to also reinstall selinux-policy and selinux-policy-targeted as well. but let me know if anything along the way does not work as i assumed :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230643] [SELinux] semodule removal issues
by bugzilla_noreply＠suse.com 18 Dec '24

18 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1230643 https://bugzilla.suse.com/show_bug.cgi?id=1230643#c10 Cathy Hu <cathy.hu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #10 from Cathy Hu <cathy.hu(a)suse.com> --- okay my guess is that if you delete all these empty directories (check if they are empty before!) and then run `semodule -l`, it should work again without the error: /var/lib/selinux/targeted/active/modules/100/ajaxterm/ /var/lib/selinux/targeted/active/modules/100/authconfig /var/lib/selinux/targeted/active/modules/100/bumblebee /var/lib/selinux/targeted/active/modules/100/dirsrv-admin /var/lib/selinux/targeted/active/modules/100/mip6d /var/lib/selinux/targeted/active/modules/100/piranha /var/lib/selinux/targeted/active/modules/100/sge /var/lib/selinux/targeted/active/modules/100/smsd /var/lib/selinux/targeted/active/modules/100/mirrormanager /var/lib/selinux/targeted/active/modules/100/kmscon /var/lib/selinux/targeted/active/modules/100/naemon /var/lib/selinux/targeted/active/modules/100/rolekit /var/lib/selinux/targeted/active/modules/100/pkcs11proxyd /var/lib/selinux/targeted/active/modules/100/rkt and then my second guess is that after that if you reinstall container-selinux and passt-selinux, it should install without an error. if so, you can do `touch /etc/selinux/.autorelabel`, reboot and then do `ls -alZ /usr/bin/crun` it should show `container_runtime_exec_t` and the container stuff should work again but these are just assumptions, since i can not reproduce the issue and also dont have access to the system. also i am still pretty unsure what exactly happened there, so please take it with a grain of salt :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233134] New: boot freeze with kernel-default=5.14.21-150500.55.86 and amdgpu
by bugzilla_noreply＠suse.com 18 Dec '24

18 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233134 Bug ID: 1233134 Summary: boot freeze with kernel-default=5.14.21-150500.55.86 and amdgpu Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: heiko.rommel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After having installed version 5.14.21-150500.55.86 of the kernel release candidate for SLE 15 SP5 / openSUSE 15.5 on my desktop, the system hangs in early boot with no video signal. When booting with loglevel=7 and drm.debug=0x1e I see that there are apparently some errors in drm, but they are only displayed for a very short time (< 1 sec) and then the signal to the display is cut off. The GPU is a discrete AMD Radeon RX 7800 XT. What did work: a) booting with nomodeset b) creating an update directory in /lib/modules/ for the new kernel and putting there the amdgpu.ko.zst from the previous kernel, rebuilding the initrd and booting (see https://bugzilla.suse.com/show_bug.cgi?id=1215802#c11) This looks like an re-incarnation of https://bugzilla.suse.com/show_bug.cgi?id=1215802 reported 14 month ago, but maybe with different root problems. Currently, I am trying to get a legible video of the booting. -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 18 Dec '24

18 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c76 --- Comment #76 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2024:4376-1: An update that solves 230 vulnerabilities, contains 10 features and has 33 security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-su-20244376-1 Category: security (important) Bug References: 1082555, 1194869, 1218644, 1220382, 1221309, 1221333, 1222364, 1222590, 1223202, 1223656, 1223848, 1223919, 1223942, 1224518, 1224526, 1224574, 1225725, 1225730, 1225742, 1225764, 1225812, 1226560, 1226592, 1226631, 1226748, 1226872, 1227853, 1228410, 1228430, 1228486, 1228650, 1228857, 1229312, 1229429, 1229585, 1229752, 1229808, 1230055, 1230220, 1230231, 1230270, 1230558, 1230827, 1230918, 1231083, 1231089, 1231098, 1231101, 1231108, 1231111, 1231132, 1231135, 1231138, 1231169, 1231178, 1231180, 1231181, 1231187, 1231202, 1231434, 1231441, 1231452, 1231465, 1231474, 1231481, 1231537, 1231541, 1231646, 1231849, 1231856, 1231858, 1231859, 1231864, 1231904, 1231916, 1231920, 1231923, 1231930, 1231931, 1231947, 1231952, 1231953, 1231959, 1231978, 1232013, 1232015, 1232016, 1232017, 1232027, 1232028, 1232047, 1232048, 1232050, 1232056, 1232076, 1232080, 1232094, 1232096, 1232098, 1232111, 1232126, 1232134, 1232135, 1232141, 1232142, 1232147, 1232152, 1232159, 1232162, 1232165, 1232180, 1232185, 1232187, 1232189, 1232195, 1232198, 1232201, 1232218, 1232224, 1232232, 1232254, 1232255, 1232264, 1232272, 1232279, 1232287, 1232293, 1232312, 1232317, 1232318, 1232333, 1232334, 1232335, 1232339, 1232349, 1232357, 1232359, 1232362, 1232364, 1232370, 1232371, 1232378, 1232385, 1232387, 1232394, 1232413, 1232416, 1232436, 1232483, 1232500, 1232503, 1232504, 1232507, 1232520, 1232552, 1232757, 1232819, 1232860, 1232870, 1232873, 1232877, 1232878, 1232881, 1232884, 1232885, 1232887, 1232888, 1232890, 1232892, 1232896, 1232897, 1232905, 1232907, 1232919, 1232926, 1232928, 1232935, 1233035, 1233049, 1233051, 1233056, 1233057, 1233061, 1233063, 1233065, 1233067, 1233070, 1233073, 1233074, 1233100, 1233103, 1233104, 1233105, 1233106, 1233107, 1233108, 1233110, 1233111, 1233113, 1233114, 1233117, 1233123, 1233125, 1233129, 1233130, 1233134, 1233135, 1233150, 1233189, 1233191, 1233197, 1233205, 1233206, 1233209, 1233210, 1233211, 1233212, 1233214, 1233216, 1233238, 1233241, 1233253, 1233255, 1233293, 1233350, 1233452, 1233453, 1233454, 1233456, 1233457, 1233458, 1233460, 1233462, 1233463, 1233468, 1233471, 1233476, 1233478, 1233479, 1233481, 1233484, 1233487, 1233490, 1233491, 1233528, 1233548, 1233552, 1233553, 1233554, 1233555, 1233557, 1233560, 1233561, 1233570, 1233577, 1233580, 1233977, 1234012, 1234025, 1234085, 1234093, 1234098, 1234108 CVE References: CVE-2021-47594, CVE-2022-48674, CVE-2022-48979, CVE-2022-48982, CVE-2022-48983, CVE-2022-48989, CVE-2022-48990, CVE-2023-52915, CVE-2023-52917, CVE-2023-52918, CVE-2023-52921, CVE-2023-52922, CVE-2024-26782, CVE-2024-26906, CVE-2024-26953, CVE-2024-35888, CVE-2024-35937, CVE-2024-35980, CVE-2024-36484, CVE-2024-36883, CVE-2024-36886, CVE-2024-36905, CVE-2024-36953, CVE-2024-36954, CVE-2024-38577, CVE-2024-38589, CVE-2024-38615, CVE-2024-40997, CVE-2024-41016, CVE-2024-41023, CVE-2024-41049, CVE-2024-42131, CVE-2024-43817, CVE-2024-43897, CVE-2024-44932, CVE-2024-44964, CVE-2024-44995, CVE-2024-46681, CVE-2024-46800, CVE-2024-46802, CVE-2024-46804, CVE-2024-46805, CVE-2024-46807, CVE-2024-46810, CVE-2024-46812, CVE-2024-46819, CVE-2024-46821, CVE-2024-46835, CVE-2024-46842, CVE-2024-46853, CVE-2024-46859, CVE-2024-46864, CVE-2024-46871, CVE-2024-47663, CVE-2024-47665, CVE-2024-47667, CVE-2024-47669, CVE-2024-47670, CVE-2024-47671, CVE-2024-47679, CVE-2024-47682, CVE-2024-47693, CVE-2024-47695, CVE-2024-47696, CVE-2024-47697, CVE-2024-47698, CVE-2024-47699, CVE-2024-47701, CVE-2024-47709, CVE-2024-47712, CVE-2024-47713, CVE-2024-47718, CVE-2024-47723, CVE-2024-47728, CVE-2024-47735, CVE-2024-47737, CVE-2024-47742, CVE-2024-47745, CVE-2024-47749, CVE-2024-47756, CVE-2024-47757, CVE-2024-49850, CVE-2024-49851, CVE-2024-49852, CVE-2024-49855, CVE-2024-49861, CVE-2024-49863, CVE-2024-49868, CVE-2024-49870, CVE-2024-49871, CVE-2024-49875, CVE-2024-49877, CVE-2024-49879, CVE-2024-49884, CVE-2024-49891, CVE-2024-49900, CVE-2024-49902, CVE-2024-49903, CVE-2024-49905, CVE-2024-49907, CVE-2024-49908, CVE-2024-49921, CVE-2024-49924, CVE-2024-49925, CVE-2024-49934, CVE-2024-49935, CVE-2024-49938, CVE-2024-49945, CVE-2024-49947, CVE-2024-49950, CVE-2024-49957, CVE-2024-49963, CVE-2024-49965, CVE-2024-49966, CVE-2024-49968, CVE-2024-49981, CVE-2024-49983, CVE-2024-49985, CVE-2024-49989, CVE-2024-50003, CVE-2024-50007, CVE-2024-50008, CVE-2024-50009, CVE-2024-50013, CVE-2024-50017, CVE-2024-50025, CVE-2024-50026, CVE-2024-50031, CVE-2024-50044, CVE-2024-50062, CVE-2024-50067, CVE-2024-50073, CVE-2024-50074, CVE-2024-50077, CVE-2024-50078, CVE-2024-50082, CVE-2024-50089, CVE-2024-50093, CVE-2024-50095, CVE-2024-50096, CVE-2024-50098, CVE-2024-50099, CVE-2024-50103, CVE-2024-50108, CVE-2024-50110, CVE-2024-50115, CVE-2024-50116, CVE-2024-50117, CVE-2024-50124, CVE-2024-50125, CVE-2024-50127, CVE-2024-50128, CVE-2024-50131, CVE-2024-50134, CVE-2024-50135, CVE-2024-50138, CVE-2024-50141, CVE-2024-50146, CVE-2024-50147, CVE-2024-50148, CVE-2024-50150, CVE-2024-50153, CVE-2024-50154, CVE-2024-50155, CVE-2024-50156, CVE-2024-50160, CVE-2024-50167, CVE-2024-50171, CVE-2024-50179, CVE-2024-50180, CVE-2024-50182, CVE-2024-50183, CVE-2024-50184, CVE-2024-50186, CVE-2024-50187, CVE-2024-50188, CVE-2024-50189, CVE-2024-50192, CVE-2024-50194, CVE-2024-50195, CVE-2024-50196, CVE-2024-50198, CVE-2024-50201, CVE-2024-50205, CVE-2024-50208, CVE-2024-50209, CVE-2024-50215, CVE-2024-50218, CVE-2024-50229, CVE-2024-50230, CVE-2024-50232, CVE-2024-50233, CVE-2024-50234, CVE-2024-50236, CVE-2024-50237, CVE-2024-50249, CVE-2024-50255, CVE-2024-50259, CVE-2024-50261, CVE-2024-50264, CVE-2024-50265, CVE-2024-50267, CVE-2024-50268, CVE-2024-50269, CVE-2024-50271, CVE-2024-50273, CVE-2024-50274, CVE-2024-50279, CVE-2024-50282, CVE-2024-50287, CVE-2024-50289, CVE-2024-50290, CVE-2024-50292, CVE-2024-50295, CVE-2024-50298, CVE-2024-50301, CVE-2024-50302, CVE-2024-53052, CVE-2024-53058, CVE-2024-53059, CVE-2024-53060, CVE-2024-53061, CVE-2024-53063, CVE-2024-53066, CVE-2024-53068, CVE-2024-53079, CVE-2024-53085, CVE-2024-53088, CVE-2024-53104, CVE-2024-53110 Jira References: PED-1166, PED-1168, PED-1170, PED-1218, PED-1220, PED-1222, PED-1223, PED-1225, PED-2849, SES-1880 Maintenance Incident: [SUSE:Maintenance:36744](https://smelt.suse.de/incident/36744/) Sources used: openSUSE Leap 15.5 (src): kernel-source-azure-5.14.21-150500.33.75.1, kernel-syms-azure-5.14.21-150500.33.75.1 Public Cloud Module 15-SP5 (src): kernel-source-azure-5.14.21-150500.33.75.1, kernel-syms-azure-5.14.21-150500.33.75.1 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 on the CC list for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 18 Dec '24

18 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c75 --- Comment #75 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2024:4376-1: An update that solves 230 vulnerabilities, contains 10 features and has 33 security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-su-20244376-1 Category: security (important) Bug References: 1082555, 1194869, 1218644, 1220382, 1221309, 1221333, 1222364, 1222590, 1223202, 1223656, 1223848, 1223919, 1223942, 1224518, 1224526, 1224574, 1225725, 1225730, 1225742, 1225764, 1225812, 1226560, 1226592, 1226631, 1226748, 1226872, 1227853, 1228410, 1228430, 1228486, 1228650, 1228857, 1229312, 1229429, 1229585, 1229752, 1229808, 1230055, 1230220, 1230231, 1230270, 1230558, 1230827, 1230918, 1231083, 1231089, 1231098, 1231101, 1231108, 1231111, 1231132, 1231135, 1231138, 1231169, 1231178, 1231180, 1231181, 1231187, 1231202, 1231434, 1231441, 1231452, 1231465, 1231474, 1231481, 1231537, 1231541, 1231646, 1231849, 1231856, 1231858, 1231859, 1231864, 1231904, 1231916, 1231920, 1231923, 1231930, 1231931, 1231947, 1231952, 1231953, 1231959, 1231978, 1232013, 1232015, 1232016, 1232017, 1232027, 1232028, 1232047, 1232048, 1232050, 1232056, 1232076, 1232080, 1232094, 1232096, 1232098, 1232111, 1232126, 1232134, 1232135, 1232141, 1232142, 1232147, 1232152, 1232159, 1232162, 1232165, 1232180, 1232185, 1232187, 1232189, 1232195, 1232198, 1232201, 1232218, 1232224, 1232232, 1232254, 1232255, 1232264, 1232272, 1232279, 1232287, 1232293, 1232312, 1232317, 1232318, 1232333, 1232334, 1232335, 1232339, 1232349, 1232357, 1232359, 1232362, 1232364, 1232370, 1232371, 1232378, 1232385, 1232387, 1232394, 1232413, 1232416, 1232436, 1232483, 1232500, 1232503, 1232504, 1232507, 1232520, 1232552, 1232757, 1232819, 1232860, 1232870, 1232873, 1232877, 1232878, 1232881, 1232884, 1232885, 1232887, 1232888, 1232890, 1232892, 1232896, 1232897, 1232905, 1232907, 1232919, 1232926, 1232928, 1232935, 1233035, 1233049, 1233051, 1233056, 1233057, 1233061, 1233063, 1233065, 1233067, 1233070, 1233073, 1233074, 1233100, 1233103, 1233104, 1233105, 1233106, 1233107, 1233108, 1233110, 1233111, 1233113, 1233114, 1233117, 1233123, 1233125, 1233129, 1233130, 1233134, 1233135, 1233150, 1233189, 1233191, 1233197, 1233205, 1233206, 1233209, 1233210, 1233211, 1233212, 1233214, 1233216, 1233238, 1233241, 1233253, 1233255, 1233293, 1233350, 1233452, 1233453, 1233454, 1233456, 1233457, 1233458, 1233460, 1233462, 1233463, 1233468, 1233471, 1233476, 1233478, 1233479, 1233481, 1233484, 1233487, 1233490, 1233491, 1233528, 1233548, 1233552, 1233553, 1233554, 1233555, 1233557, 1233560, 1233561, 1233570, 1233577, 1233580, 1233977, 1234012, 1234025, 1234085, 1234093, 1234098, 1234108 CVE References: CVE-2021-47594, CVE-2022-48674, CVE-2022-48979, CVE-2022-48982, CVE-2022-48983, CVE-2022-48989, CVE-2022-48990, CVE-2023-52915, CVE-2023-52917, CVE-2023-52918, CVE-2023-52921, CVE-2023-52922, CVE-2024-26782, CVE-2024-26906, CVE-2024-26953, CVE-2024-35888, CVE-2024-35937, CVE-2024-35980, CVE-2024-36484, CVE-2024-36883, CVE-2024-36886, CVE-2024-36905, CVE-2024-36953, CVE-2024-36954, CVE-2024-38577, CVE-2024-38589, CVE-2024-38615, CVE-2024-40997, CVE-2024-41016, CVE-2024-41023, CVE-2024-41049, CVE-2024-42131, CVE-2024-43817, CVE-2024-43897, CVE-2024-44932, CVE-2024-44964, CVE-2024-44995, CVE-2024-46681, CVE-2024-46800, CVE-2024-46802, CVE-2024-46804, CVE-2024-46805, CVE-2024-46807, CVE-2024-46810, CVE-2024-46812, CVE-2024-46819, CVE-2024-46821, CVE-2024-46835, CVE-2024-46842, CVE-2024-46853, CVE-2024-46859, CVE-2024-46864, CVE-2024-46871, CVE-2024-47663, CVE-2024-47665, CVE-2024-47667, CVE-2024-47669, CVE-2024-47670, CVE-2024-47671, CVE-2024-47679, CVE-2024-47682, CVE-2024-47693, CVE-2024-47695, CVE-2024-47696, CVE-2024-47697, CVE-2024-47698, CVE-2024-47699, CVE-2024-47701, CVE-2024-47709, CVE-2024-47712, CVE-2024-47713, CVE-2024-47718, CVE-2024-47723, CVE-2024-47728, CVE-2024-47735, CVE-2024-47737, CVE-2024-47742, CVE-2024-47745, CVE-2024-47749, CVE-2024-47756, CVE-2024-47757, CVE-2024-49850, CVE-2024-49851, CVE-2024-49852, CVE-2024-49855, CVE-2024-49861, CVE-2024-49863, CVE-2024-49868, CVE-2024-49870, CVE-2024-49871, CVE-2024-49875, CVE-2024-49877, CVE-2024-49879, CVE-2024-49884, CVE-2024-49891, CVE-2024-49900, CVE-2024-49902, CVE-2024-49903, CVE-2024-49905, CVE-2024-49907, CVE-2024-49908, CVE-2024-49921, CVE-2024-49924, CVE-2024-49925, CVE-2024-49934, CVE-2024-49935, CVE-2024-49938, CVE-2024-49945, CVE-2024-49947, CVE-2024-49950, CVE-2024-49957, CVE-2024-49963, CVE-2024-49965, CVE-2024-49966, CVE-2024-49968, CVE-2024-49981, CVE-2024-49983, CVE-2024-49985, CVE-2024-49989, CVE-2024-50003, CVE-2024-50007, CVE-2024-50008, CVE-2024-50009, CVE-2024-50013, CVE-2024-50017, CVE-2024-50025, CVE-2024-50026, CVE-2024-50031, CVE-2024-50044, CVE-2024-50062, CVE-2024-50067, CVE-2024-50073, CVE-2024-50074, CVE-2024-50077, CVE-2024-50078, CVE-2024-50082, CVE-2024-50089, CVE-2024-50093, CVE-2024-50095, CVE-2024-50096, CVE-2024-50098, CVE-2024-50099, CVE-2024-50103, CVE-2024-50108, CVE-2024-50110, CVE-2024-50115, CVE-2024-50116, CVE-2024-50117, CVE-2024-50124, CVE-2024-50125, CVE-2024-50127, CVE-2024-50128, CVE-2024-50131, CVE-2024-50134, CVE-2024-50135, CVE-2024-50138, CVE-2024-50141, CVE-2024-50146, CVE-2024-50147, CVE-2024-50148, CVE-2024-50150, CVE-2024-50153, CVE-2024-50154, CVE-2024-50155, CVE-2024-50156, CVE-2024-50160, CVE-2024-50167, CVE-2024-50171, CVE-2024-50179, CVE-2024-50180, CVE-2024-50182, CVE-2024-50183, CVE-2024-50184, CVE-2024-50186, CVE-2024-50187, CVE-2024-50188, CVE-2024-50189, CVE-2024-50192, CVE-2024-50194, CVE-2024-50195, CVE-2024-50196, CVE-2024-50198, CVE-2024-50201, CVE-2024-50205, CVE-2024-50208, CVE-2024-50209, CVE-2024-50215, CVE-2024-50218, CVE-2024-50229, CVE-2024-50230, CVE-2024-50232, CVE-2024-50233, CVE-2024-50234, CVE-2024-50236, CVE-2024-50237, CVE-2024-50249, CVE-2024-50255, CVE-2024-50259, CVE-2024-50261, CVE-2024-50264, CVE-2024-50265, CVE-2024-50267, CVE-2024-50268, CVE-2024-50269, CVE-2024-50271, CVE-2024-50273, CVE-2024-50274, CVE-2024-50279, CVE-2024-50282, CVE-2024-50287, CVE-2024-50289, CVE-2024-50290, CVE-2024-50292, CVE-2024-50295, CVE-2024-50298, CVE-2024-50301, CVE-2024-50302, CVE-2024-53052, CVE-2024-53058, CVE-2024-53059, CVE-2024-53060, CVE-2024-53061, CVE-2024-53063, CVE-2024-53066, CVE-2024-53068, CVE-2024-53079, CVE-2024-53085, CVE-2024-53088, CVE-2024-53104, CVE-2024-53110 Jira References: PED-1166, PED-1168, PED-1170, PED-1218, PED-1220, PED-1222, PED-1223, PED-1225, PED-2849, SES-1880 Maintenance Incident: [SUSE:Maintenance:36744](https://smelt.suse.de/incident/36744/) Sources used: openSUSE Leap 15.5 (src): kernel-syms-azure-5.14.21-150500.33.75.1, kernel-source-azure-5.14.21-150500.33.75.1 Public Cloud Module 15-SP5 (src): kernel-syms-azure-5.14.21-150500.33.75.1, kernel-source-azure-5.14.21-150500.33.75.1 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 on the CC list for the bug.

1 0