Security update for the Linux Kernel SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2025:1194-1 Final 1 1 2025-04-10T13:46:40Z current 2025-04-10T13:46:40Z 2025-04-10T13:46:40Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for the Linux Kernel The SUSE Linux Enterprise 15 SP3 RT kernel was updated to receive various security bugfixes. The following security bugs were fixed: - CVE-2021-47248: udp: fix race between close() and udp_abort() (bsc#1224867). - CVE-2022-49051: net: usb: aqc111: Fix out-of-bounds accesses in RX fixup (bsc#1237903). - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918). - CVE-2022-49275: can: m_can: m_can_tx_handler(): fix use after free of skb (bsc#1238719). - CVE-2022-49413: bfq: Update cgroup information before merging bio (bsc#1238710). - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919). - CVE-2022-49545: ALSA: usb-audio: Cancel pending work at closing a MIDI substream (bsc#1238729). - CVE-2022-49563: crypto: qat - add param check for RSA (bsc#1238787). - CVE-2022-49564: crypto: qat - add param check for DH (bsc#1238789). - CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207). - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276). - CVE-2024-56642: tipc: Fix use-after-free of kernel socket in cleanup_bearer() (bsc#1235433). - CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528). - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076). - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109). - CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911). - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115). The following non-security bugs were fixed: - ACPI: processor: idle: Return an error if both P_LVL{2,3} idle states are invalid (bsc#1237530). - btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1239969). - btrfs: send: fix invalid clone operation for file that got its size decreased (bsc#1239969). - btrfs: send: use btrfs_file_extent_end() in send_write_or_clone() (bsc#1239969). The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-2025-1194,SUSE-SUSE-MicroOS-5.1-2025-1194,SUSE-SUSE-MicroOS-5.2-2025-1194 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ Link for SUSE-SU-2025:1194-1 https://lists.suse.com/pipermail/sle-security-updates/2025-April/020681.html E-Mail link for SUSE-SU-2025:1194-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1065729 SUSE Bug 1065729 https://bugzilla.suse.com/1179878 SUSE Bug 1179878 https://bugzilla.suse.com/1180814 SUSE Bug 1180814 https://bugzilla.suse.com/1185762 SUSE Bug 1185762 https://bugzilla.suse.com/1195823 SUSE Bug 1195823 https://bugzilla.suse.com/1196444 SUSE Bug 1196444 https://bugzilla.suse.com/1197158 SUSE Bug 1197158 https://bugzilla.suse.com/1197227 SUSE Bug 1197227 https://bugzilla.suse.com/1197302 SUSE Bug 1197302 https://bugzilla.suse.com/1197331 SUSE Bug 1197331 https://bugzilla.suse.com/1197472 SUSE Bug 1197472 https://bugzilla.suse.com/1197661 SUSE Bug 1197661 https://bugzilla.suse.com/1197926 SUSE Bug 1197926 https://bugzilla.suse.com/1198577 SUSE Bug 1198577 https://bugzilla.suse.com/1198660 SUSE Bug 1198660 https://bugzilla.suse.com/1199657 SUSE Bug 1199657 https://bugzilla.suse.com/1200045 SUSE Bug 1200045 https://bugzilla.suse.com/1200217 SUSE Bug 1200217 https://bugzilla.suse.com/1200571 SUSE Bug 1200571 https://bugzilla.suse.com/1200807 SUSE Bug 1200807 https://bugzilla.suse.com/1200809 SUSE Bug 1200809 https://bugzilla.suse.com/1200825 SUSE Bug 1200825 https://bugzilla.suse.com/1200871 SUSE Bug 1200871 https://bugzilla.suse.com/1200872 SUSE Bug 1200872 https://bugzilla.suse.com/1201193 SUSE Bug 1201193 https://bugzilla.suse.com/1201381 SUSE Bug 1201381 https://bugzilla.suse.com/1201610 SUSE Bug 1201610 https://bugzilla.suse.com/1202672 SUSE Bug 1202672 https://bugzilla.suse.com/1202711 SUSE Bug 1202711 https://bugzilla.suse.com/1203769 SUSE Bug 1203769 https://bugzilla.suse.com/1207186 SUSE Bug 1207186 https://bugzilla.suse.com/1209547 SUSE Bug 1209547 https://bugzilla.suse.com/1210647 SUSE Bug 1210647 https://bugzilla.suse.com/1213167 SUSE Bug 1213167 https://bugzilla.suse.com/1224867 SUSE Bug 1224867 https://bugzilla.suse.com/1225742 SUSE Bug 1225742 https://bugzilla.suse.com/1230326 SUSE Bug 1230326 https://bugzilla.suse.com/1231375 SUSE Bug 1231375 https://bugzilla.suse.com/1233479 SUSE Bug 1233479 https://bugzilla.suse.com/1233557 SUSE Bug 1233557 https://bugzilla.suse.com/1235433 SUSE Bug 1235433 https://bugzilla.suse.com/1235528 SUSE Bug 1235528 https://bugzilla.suse.com/1237530 SUSE Bug 1237530 https://bugzilla.suse.com/1237718 SUSE Bug 1237718 https://bugzilla.suse.com/1237721 SUSE Bug 1237721 https://bugzilla.suse.com/1237723 SUSE Bug 1237723 https://bugzilla.suse.com/1237726 SUSE Bug 1237726 https://bugzilla.suse.com/1237734 SUSE Bug 1237734 https://bugzilla.suse.com/1237735 SUSE Bug 1237735 https://bugzilla.suse.com/1237736 SUSE Bug 1237736 https://bugzilla.suse.com/1237738 SUSE Bug 1237738 https://bugzilla.suse.com/1237739 SUSE Bug 1237739 https://bugzilla.suse.com/1237740 SUSE Bug 1237740 https://bugzilla.suse.com/1237742 SUSE Bug 1237742 https://bugzilla.suse.com/1237746 SUSE Bug 1237746 https://bugzilla.suse.com/1237748 SUSE Bug 1237748 https://bugzilla.suse.com/1237752 SUSE Bug 1237752 https://bugzilla.suse.com/1237778 SUSE Bug 1237778 https://bugzilla.suse.com/1237782 SUSE Bug 1237782 https://bugzilla.suse.com/1237783 SUSE Bug 1237783 https://bugzilla.suse.com/1237784 SUSE Bug 1237784 https://bugzilla.suse.com/1237788 SUSE Bug 1237788 https://bugzilla.suse.com/1237798 SUSE Bug 1237798 https://bugzilla.suse.com/1237810 SUSE Bug 1237810 https://bugzilla.suse.com/1237813 SUSE Bug 1237813 https://bugzilla.suse.com/1237814 SUSE Bug 1237814 https://bugzilla.suse.com/1237815 SUSE Bug 1237815 https://bugzilla.suse.com/1237823 SUSE Bug 1237823 https://bugzilla.suse.com/1237829 SUSE Bug 1237829 https://bugzilla.suse.com/1237831 SUSE Bug 1237831 https://bugzilla.suse.com/1237839 SUSE Bug 1237839 https://bugzilla.suse.com/1237840 SUSE Bug 1237840 https://bugzilla.suse.com/1237846 SUSE Bug 1237846 https://bugzilla.suse.com/1237868 SUSE Bug 1237868 https://bugzilla.suse.com/1237872 SUSE Bug 1237872 https://bugzilla.suse.com/1237903 SUSE Bug 1237903 https://bugzilla.suse.com/1237916 SUSE Bug 1237916 https://bugzilla.suse.com/1237918 SUSE Bug 1237918 https://bugzilla.suse.com/1237932 SUSE Bug 1237932 https://bugzilla.suse.com/1237940 SUSE Bug 1237940 https://bugzilla.suse.com/1237941 SUSE Bug 1237941 https://bugzilla.suse.com/1237951 SUSE Bug 1237951 https://bugzilla.suse.com/1237954 SUSE Bug 1237954 https://bugzilla.suse.com/1237958 SUSE Bug 1237958 https://bugzilla.suse.com/1237963 SUSE Bug 1237963 https://bugzilla.suse.com/1237983 SUSE Bug 1237983 https://bugzilla.suse.com/1237984 SUSE Bug 1237984 https://bugzilla.suse.com/1237996 SUSE Bug 1237996 https://bugzilla.suse.com/1237997 SUSE Bug 1237997 https://bugzilla.suse.com/1237998 SUSE Bug 1237998 https://bugzilla.suse.com/1238000 SUSE Bug 1238000 https://bugzilla.suse.com/1238007 SUSE Bug 1238007 https://bugzilla.suse.com/1238013 SUSE Bug 1238013 https://bugzilla.suse.com/1238022 SUSE Bug 1238022 https://bugzilla.suse.com/1238030 SUSE Bug 1238030 https://bugzilla.suse.com/1238036 SUSE Bug 1238036 https://bugzilla.suse.com/1238046 SUSE Bug 1238046 https://bugzilla.suse.com/1238071 SUSE Bug 1238071 https://bugzilla.suse.com/1238079 SUSE Bug 1238079 https://bugzilla.suse.com/1238096 SUSE Bug 1238096 https://bugzilla.suse.com/1238099 SUSE Bug 1238099 https://bugzilla.suse.com/1238103 SUSE Bug 1238103 https://bugzilla.suse.com/1238108 SUSE Bug 1238108 https://bugzilla.suse.com/1238111 SUSE Bug 1238111 https://bugzilla.suse.com/1238123 SUSE Bug 1238123 https://bugzilla.suse.com/1238126 SUSE Bug 1238126 https://bugzilla.suse.com/1238131 SUSE Bug 1238131 https://bugzilla.suse.com/1238135 SUSE Bug 1238135 https://bugzilla.suse.com/1238139 SUSE Bug 1238139 https://bugzilla.suse.com/1238146 SUSE Bug 1238146 https://bugzilla.suse.com/1238149 SUSE Bug 1238149 https://bugzilla.suse.com/1238150 SUSE Bug 1238150 https://bugzilla.suse.com/1238155 SUSE Bug 1238155 https://bugzilla.suse.com/1238156 SUSE Bug 1238156 https://bugzilla.suse.com/1238158 SUSE Bug 1238158 https://bugzilla.suse.com/1238162 SUSE Bug 1238162 https://bugzilla.suse.com/1238166 SUSE Bug 1238166 https://bugzilla.suse.com/1238168 SUSE Bug 1238168 https://bugzilla.suse.com/1238169 SUSE Bug 1238169 https://bugzilla.suse.com/1238170 SUSE Bug 1238170 https://bugzilla.suse.com/1238171 SUSE Bug 1238171 https://bugzilla.suse.com/1238172 SUSE Bug 1238172 https://bugzilla.suse.com/1238175 SUSE Bug 1238175 https://bugzilla.suse.com/1238177 SUSE Bug 1238177 https://bugzilla.suse.com/1238181 SUSE Bug 1238181 https://bugzilla.suse.com/1238183 SUSE Bug 1238183 https://bugzilla.suse.com/1238184 SUSE Bug 1238184 https://bugzilla.suse.com/1238228 SUSE Bug 1238228 https://bugzilla.suse.com/1238229 SUSE Bug 1238229 https://bugzilla.suse.com/1238231 SUSE Bug 1238231 https://bugzilla.suse.com/1238235 SUSE Bug 1238235 https://bugzilla.suse.com/1238236 SUSE Bug 1238236 https://bugzilla.suse.com/1238239 SUSE Bug 1238239 https://bugzilla.suse.com/1238241 SUSE Bug 1238241 https://bugzilla.suse.com/1238242 SUSE Bug 1238242 https://bugzilla.suse.com/1238243 SUSE Bug 1238243 https://bugzilla.suse.com/1238244 SUSE Bug 1238244 https://bugzilla.suse.com/1238249 SUSE Bug 1238249 https://bugzilla.suse.com/1238255 SUSE Bug 1238255 https://bugzilla.suse.com/1238256 SUSE Bug 1238256 https://bugzilla.suse.com/1238257 SUSE Bug 1238257 https://bugzilla.suse.com/1238263 SUSE Bug 1238263 https://bugzilla.suse.com/1238264 SUSE Bug 1238264 https://bugzilla.suse.com/1238266 SUSE Bug 1238266 https://bugzilla.suse.com/1238267 SUSE Bug 1238267 https://bugzilla.suse.com/1238269 SUSE Bug 1238269 https://bugzilla.suse.com/1238271 SUSE Bug 1238271 https://bugzilla.suse.com/1238272 SUSE Bug 1238272 https://bugzilla.suse.com/1238274 SUSE Bug 1238274 https://bugzilla.suse.com/1238275 SUSE Bug 1238275 https://bugzilla.suse.com/1238276 SUSE Bug 1238276 https://bugzilla.suse.com/1238278 SUSE Bug 1238278 https://bugzilla.suse.com/1238279 SUSE Bug 1238279 https://bugzilla.suse.com/1238281 SUSE Bug 1238281 https://bugzilla.suse.com/1238284 SUSE Bug 1238284 https://bugzilla.suse.com/1238289 SUSE Bug 1238289 https://bugzilla.suse.com/1238293 SUSE Bug 1238293 https://bugzilla.suse.com/1238306 SUSE Bug 1238306 https://bugzilla.suse.com/1238307 SUSE Bug 1238307 https://bugzilla.suse.com/1238313 SUSE Bug 1238313 https://bugzilla.suse.com/1238327 SUSE Bug 1238327 https://bugzilla.suse.com/1238331 SUSE Bug 1238331 https://bugzilla.suse.com/1238333 SUSE Bug 1238333 https://bugzilla.suse.com/1238334 SUSE Bug 1238334 https://bugzilla.suse.com/1238336 SUSE Bug 1238336 https://bugzilla.suse.com/1238337 SUSE Bug 1238337 https://bugzilla.suse.com/1238338 SUSE Bug 1238338 https://bugzilla.suse.com/1238343 SUSE Bug 1238343 https://bugzilla.suse.com/1238372 SUSE Bug 1238372 https://bugzilla.suse.com/1238373 SUSE Bug 1238373 https://bugzilla.suse.com/1238377 SUSE Bug 1238377 https://bugzilla.suse.com/1238382 SUSE Bug 1238382 https://bugzilla.suse.com/1238386 SUSE Bug 1238386 https://bugzilla.suse.com/1238393 SUSE Bug 1238393 https://bugzilla.suse.com/1238394 SUSE Bug 1238394 https://bugzilla.suse.com/1238395 SUSE Bug 1238395 https://bugzilla.suse.com/1238413 SUSE Bug 1238413 https://bugzilla.suse.com/1238416 SUSE Bug 1238416 https://bugzilla.suse.com/1238417 SUSE Bug 1238417 https://bugzilla.suse.com/1238419 SUSE Bug 1238419 https://bugzilla.suse.com/1238420 SUSE Bug 1238420 https://bugzilla.suse.com/1238429 SUSE Bug 1238429 https://bugzilla.suse.com/1238430 SUSE Bug 1238430 https://bugzilla.suse.com/1238435 SUSE Bug 1238435 https://bugzilla.suse.com/1238441 SUSE Bug 1238441 https://bugzilla.suse.com/1238443 SUSE Bug 1238443 https://bugzilla.suse.com/1238454 SUSE Bug 1238454 https://bugzilla.suse.com/1238462 SUSE Bug 1238462 https://bugzilla.suse.com/1238467 SUSE Bug 1238467 https://bugzilla.suse.com/1238469 SUSE Bug 1238469 https://bugzilla.suse.com/1238539 SUSE Bug 1238539 https://bugzilla.suse.com/1238543 SUSE Bug 1238543 https://bugzilla.suse.com/1238546 SUSE Bug 1238546 https://bugzilla.suse.com/1238599 SUSE Bug 1238599 https://bugzilla.suse.com/1238600 SUSE Bug 1238600 https://bugzilla.suse.com/1238612 SUSE Bug 1238612 https://bugzilla.suse.com/1238615 SUSE Bug 1238615 https://bugzilla.suse.com/1238617 SUSE Bug 1238617 https://bugzilla.suse.com/1238618 SUSE Bug 1238618 https://bugzilla.suse.com/1238621 SUSE Bug 1238621 https://bugzilla.suse.com/1238623 SUSE Bug 1238623 https://bugzilla.suse.com/1238625 SUSE Bug 1238625 https://bugzilla.suse.com/1238626 SUSE Bug 1238626 https://bugzilla.suse.com/1238630 SUSE Bug 1238630 https://bugzilla.suse.com/1238631 SUSE Bug 1238631 https://bugzilla.suse.com/1238633 SUSE Bug 1238633 https://bugzilla.suse.com/1238635 SUSE Bug 1238635 https://bugzilla.suse.com/1238638 SUSE Bug 1238638 https://bugzilla.suse.com/1238639 SUSE Bug 1238639 https://bugzilla.suse.com/1238641 SUSE Bug 1238641 https://bugzilla.suse.com/1238643 SUSE Bug 1238643 https://bugzilla.suse.com/1238645 SUSE Bug 1238645 https://bugzilla.suse.com/1238646 SUSE Bug 1238646 https://bugzilla.suse.com/1238653 SUSE Bug 1238653 https://bugzilla.suse.com/1238655 SUSE Bug 1238655 https://bugzilla.suse.com/1238663 SUSE Bug 1238663 https://bugzilla.suse.com/1238705 SUSE Bug 1238705 https://bugzilla.suse.com/1238707 SUSE Bug 1238707 https://bugzilla.suse.com/1238710 SUSE Bug 1238710 https://bugzilla.suse.com/1238712 SUSE Bug 1238712 https://bugzilla.suse.com/1238718 SUSE Bug 1238718 https://bugzilla.suse.com/1238719 SUSE Bug 1238719 https://bugzilla.suse.com/1238721 SUSE Bug 1238721 https://bugzilla.suse.com/1238722 SUSE Bug 1238722 https://bugzilla.suse.com/1238727 SUSE Bug 1238727 https://bugzilla.suse.com/1238729 SUSE Bug 1238729 https://bugzilla.suse.com/1238750 SUSE Bug 1238750 https://bugzilla.suse.com/1238787 SUSE Bug 1238787 https://bugzilla.suse.com/1238789 SUSE Bug 1238789 https://bugzilla.suse.com/1238805 SUSE Bug 1238805 https://bugzilla.suse.com/1238809 SUSE Bug 1238809 https://bugzilla.suse.com/1238814 SUSE Bug 1238814 https://bugzilla.suse.com/1238815 SUSE Bug 1238815 https://bugzilla.suse.com/1238819 SUSE Bug 1238819 https://bugzilla.suse.com/1238821 SUSE Bug 1238821 https://bugzilla.suse.com/1238822 SUSE Bug 1238822 https://bugzilla.suse.com/1238823 SUSE Bug 1238823 https://bugzilla.suse.com/1238825 SUSE Bug 1238825 https://bugzilla.suse.com/1238835 SUSE Bug 1238835 https://bugzilla.suse.com/1238838 SUSE Bug 1238838 https://bugzilla.suse.com/1238868 SUSE Bug 1238868 https://bugzilla.suse.com/1238869 SUSE Bug 1238869 https://bugzilla.suse.com/1238871 SUSE Bug 1238871 https://bugzilla.suse.com/1238892 SUSE Bug 1238892 https://bugzilla.suse.com/1238893 SUSE Bug 1238893 https://bugzilla.suse.com/1238911 SUSE Bug 1238911 https://bugzilla.suse.com/1238919 SUSE Bug 1238919 https://bugzilla.suse.com/1238925 SUSE Bug 1238925 https://bugzilla.suse.com/1238930 SUSE Bug 1238930 https://bugzilla.suse.com/1238933 SUSE Bug 1238933 https://bugzilla.suse.com/1238937 SUSE Bug 1238937 https://bugzilla.suse.com/1238938 SUSE Bug 1238938 https://bugzilla.suse.com/1238939 SUSE Bug 1238939 https://bugzilla.suse.com/1238948 SUSE Bug 1238948 https://bugzilla.suse.com/1238949 SUSE Bug 1238949 https://bugzilla.suse.com/1238952 SUSE Bug 1238952 https://bugzilla.suse.com/1239001 SUSE Bug 1239001 https://bugzilla.suse.com/1239035 SUSE Bug 1239035 https://bugzilla.suse.com/1239040 SUSE Bug 1239040 https://bugzilla.suse.com/1239041 SUSE Bug 1239041 https://bugzilla.suse.com/1239060 SUSE Bug 1239060 https://bugzilla.suse.com/1239070 SUSE Bug 1239070 https://bugzilla.suse.com/1239071 SUSE Bug 1239071 https://bugzilla.suse.com/1239076 SUSE Bug 1239076 https://bugzilla.suse.com/1239109 SUSE Bug 1239109 https://bugzilla.suse.com/1239115 SUSE Bug 1239115 https://bugzilla.suse.com/1239454 SUSE Bug 1239454 https://bugzilla.suse.com/1239969 SUSE Bug 1239969 https://bugzilla.suse.com/1240207 SUSE Bug 1240207 https://bugzilla.suse.com/1240213 SUSE Bug 1240213 https://bugzilla.suse.com/1240218 SUSE Bug 1240218 https://bugzilla.suse.com/1240227 SUSE Bug 1240227 https://bugzilla.suse.com/1240272 SUSE Bug 1240272 https://bugzilla.suse.com/1240276 SUSE Bug 1240276 https://bugzilla.suse.com/1240288 SUSE Bug 1240288 https://www.suse.com/security/cve/CVE-2017-5753/ SUSE CVE CVE-2017-5753 page https://www.suse.com/security/cve/CVE-2020-27835/ SUSE CVE CVE-2020-27835 page https://www.suse.com/security/cve/CVE-2021-47248/ SUSE CVE CVE-2021-47248 page https://www.suse.com/security/cve/CVE-2021-47631/ SUSE CVE CVE-2021-47631 page https://www.suse.com/security/cve/CVE-2021-47641/ SUSE CVE CVE-2021-47641 page https://www.suse.com/security/cve/CVE-2021-47642/ SUSE CVE CVE-2021-47642 page https://www.suse.com/security/cve/CVE-2021-47650/ SUSE CVE CVE-2021-47650 page https://www.suse.com/security/cve/CVE-2021-47651/ SUSE CVE CVE-2021-47651 page https://www.suse.com/security/cve/CVE-2021-47652/ SUSE CVE CVE-2021-47652 page https://www.suse.com/security/cve/CVE-2021-47653/ SUSE CVE CVE-2021-47653 page https://www.suse.com/security/cve/CVE-2021-47659/ SUSE CVE CVE-2021-47659 page https://www.suse.com/security/cve/CVE-2022-0168/ SUSE CVE CVE-2022-0168 page https://www.suse.com/security/cve/CVE-2022-1016/ SUSE CVE CVE-2022-1016 page https://www.suse.com/security/cve/CVE-2022-1048/ SUSE CVE CVE-2022-1048 page https://www.suse.com/security/cve/CVE-2022-1184/ SUSE CVE CVE-2022-1184 page https://www.suse.com/security/cve/CVE-2022-2977/ SUSE CVE CVE-2022-2977 page https://www.suse.com/security/cve/CVE-2022-29900/ SUSE CVE CVE-2022-29900 page https://www.suse.com/security/cve/CVE-2022-29901/ SUSE CVE CVE-2022-29901 page https://www.suse.com/security/cve/CVE-2022-3303/ SUSE CVE CVE-2022-3303 page https://www.suse.com/security/cve/CVE-2022-49044/ SUSE CVE CVE-2022-49044 page https://www.suse.com/security/cve/CVE-2022-49051/ SUSE CVE CVE-2022-49051 page https://www.suse.com/security/cve/CVE-2022-49053/ SUSE CVE CVE-2022-49053 page https://www.suse.com/security/cve/CVE-2022-49055/ SUSE CVE CVE-2022-49055 page https://www.suse.com/security/cve/CVE-2022-49058/ SUSE CVE CVE-2022-49058 page https://www.suse.com/security/cve/CVE-2022-49059/ SUSE CVE CVE-2022-49059 page https://www.suse.com/security/cve/CVE-2022-49063/ SUSE CVE CVE-2022-49063 page https://www.suse.com/security/cve/CVE-2022-49065/ SUSE CVE CVE-2022-49065 page https://www.suse.com/security/cve/CVE-2022-49073/ SUSE CVE CVE-2022-49073 page https://www.suse.com/security/cve/CVE-2022-49076/ SUSE CVE CVE-2022-49076 page https://www.suse.com/security/cve/CVE-2022-49078/ SUSE CVE CVE-2022-49078 page https://www.suse.com/security/cve/CVE-2022-49082/ SUSE CVE CVE-2022-49082 page https://www.suse.com/security/cve/CVE-2022-49083/ SUSE CVE CVE-2022-49083 page https://www.suse.com/security/cve/CVE-2022-49085/ SUSE CVE CVE-2022-49085 page https://www.suse.com/security/cve/CVE-2022-49091/ SUSE CVE CVE-2022-49091 page https://www.suse.com/security/cve/CVE-2022-49095/ SUSE CVE CVE-2022-49095 page https://www.suse.com/security/cve/CVE-2022-49098/ SUSE CVE CVE-2022-49098 page https://www.suse.com/security/cve/CVE-2022-49100/ SUSE CVE CVE-2022-49100 page https://www.suse.com/security/cve/CVE-2022-49111/ SUSE CVE CVE-2022-49111 page https://www.suse.com/security/cve/CVE-2022-49114/ SUSE CVE CVE-2022-49114 page https://www.suse.com/security/cve/CVE-2022-49122/ SUSE CVE CVE-2022-49122 page https://www.suse.com/security/cve/CVE-2022-49137/ SUSE CVE CVE-2022-49137 page https://www.suse.com/security/cve/CVE-2022-49145/ SUSE CVE CVE-2022-49145 page https://www.suse.com/security/cve/CVE-2022-49151/ SUSE CVE CVE-2022-49151 page https://www.suse.com/security/cve/CVE-2022-49153/ SUSE CVE CVE-2022-49153 page https://www.suse.com/security/cve/CVE-2022-49155/ SUSE CVE CVE-2022-49155 page https://www.suse.com/security/cve/CVE-2022-49156/ SUSE CVE CVE-2022-49156 page https://www.suse.com/security/cve/CVE-2022-49157/ SUSE CVE CVE-2022-49157 page https://www.suse.com/security/cve/CVE-2022-49158/ SUSE CVE CVE-2022-49158 page https://www.suse.com/security/cve/CVE-2022-49159/ SUSE CVE CVE-2022-49159 page https://www.suse.com/security/cve/CVE-2022-49160/ SUSE CVE CVE-2022-49160 page https://www.suse.com/security/cve/CVE-2022-49162/ SUSE CVE CVE-2022-49162 page https://www.suse.com/security/cve/CVE-2022-49164/ SUSE CVE CVE-2022-49164 page https://www.suse.com/security/cve/CVE-2022-49175/ SUSE CVE CVE-2022-49175 page https://www.suse.com/security/cve/CVE-2022-49185/ SUSE CVE CVE-2022-49185 page https://www.suse.com/security/cve/CVE-2022-49189/ SUSE CVE CVE-2022-49189 page https://www.suse.com/security/cve/CVE-2022-49196/ SUSE CVE CVE-2022-49196 page https://www.suse.com/security/cve/CVE-2022-49200/ SUSE CVE CVE-2022-49200 page https://www.suse.com/security/cve/CVE-2022-49201/ SUSE CVE CVE-2022-49201 page https://www.suse.com/security/cve/CVE-2022-49206/ SUSE CVE CVE-2022-49206 page https://www.suse.com/security/cve/CVE-2022-49212/ SUSE CVE CVE-2022-49212 page https://www.suse.com/security/cve/CVE-2022-49213/ SUSE CVE CVE-2022-49213 page https://www.suse.com/security/cve/CVE-2022-49216/ SUSE CVE CVE-2022-49216 page https://www.suse.com/security/cve/CVE-2022-49217/ SUSE CVE CVE-2022-49217 page https://www.suse.com/security/cve/CVE-2022-49224/ SUSE CVE CVE-2022-49224 page https://www.suse.com/security/cve/CVE-2022-49226/ SUSE CVE CVE-2022-49226 page https://www.suse.com/security/cve/CVE-2022-49232/ SUSE CVE CVE-2022-49232 page https://www.suse.com/security/cve/CVE-2022-49235/ SUSE CVE CVE-2022-49235 page https://www.suse.com/security/cve/CVE-2022-49239/ SUSE CVE CVE-2022-49239 page https://www.suse.com/security/cve/CVE-2022-49242/ SUSE CVE CVE-2022-49242 page https://www.suse.com/security/cve/CVE-2022-49243/ SUSE CVE CVE-2022-49243 page https://www.suse.com/security/cve/CVE-2022-49247/ SUSE CVE CVE-2022-49247 page https://www.suse.com/security/cve/CVE-2022-49248/ SUSE CVE CVE-2022-49248 page https://www.suse.com/security/cve/CVE-2022-49253/ SUSE CVE CVE-2022-49253 page https://www.suse.com/security/cve/CVE-2022-49259/ SUSE CVE CVE-2022-49259 page https://www.suse.com/security/cve/CVE-2022-49261/ SUSE CVE CVE-2022-49261 page https://www.suse.com/security/cve/CVE-2022-49263/ SUSE CVE CVE-2022-49263 page https://www.suse.com/security/cve/CVE-2022-49264/ SUSE CVE CVE-2022-49264 page https://www.suse.com/security/cve/CVE-2022-49271/ SUSE CVE CVE-2022-49271 page https://www.suse.com/security/cve/CVE-2022-49272/ SUSE CVE CVE-2022-49272 page https://www.suse.com/security/cve/CVE-2022-49275/ SUSE CVE CVE-2022-49275 page https://www.suse.com/security/cve/CVE-2022-49279/ SUSE CVE CVE-2022-49279 page https://www.suse.com/security/cve/CVE-2022-49280/ SUSE CVE CVE-2022-49280 page https://www.suse.com/security/cve/CVE-2022-49281/ SUSE CVE CVE-2022-49281 page https://www.suse.com/security/cve/CVE-2022-49285/ SUSE CVE CVE-2022-49285 page https://www.suse.com/security/cve/CVE-2022-49287/ SUSE CVE CVE-2022-49287 page https://www.suse.com/security/cve/CVE-2022-49288/ SUSE CVE CVE-2022-49288 page https://www.suse.com/security/cve/CVE-2022-49290/ SUSE CVE CVE-2022-49290 page https://www.suse.com/security/cve/CVE-2022-49291/ SUSE CVE CVE-2022-49291 page https://www.suse.com/security/cve/CVE-2022-49292/ SUSE CVE CVE-2022-49292 page https://www.suse.com/security/cve/CVE-2022-49293/ SUSE CVE CVE-2022-49293 page https://www.suse.com/security/cve/CVE-2022-49295/ SUSE CVE CVE-2022-49295 page https://www.suse.com/security/cve/CVE-2022-49297/ SUSE CVE CVE-2022-49297 page https://www.suse.com/security/cve/CVE-2022-49298/ SUSE CVE CVE-2022-49298 page https://www.suse.com/security/cve/CVE-2022-49299/ SUSE CVE CVE-2022-49299 page https://www.suse.com/security/cve/CVE-2022-49300/ SUSE CVE CVE-2022-49300 page https://www.suse.com/security/cve/CVE-2022-49301/ SUSE CVE CVE-2022-49301 page https://www.suse.com/security/cve/CVE-2022-49302/ SUSE CVE CVE-2022-49302 page https://www.suse.com/security/cve/CVE-2022-49304/ SUSE CVE CVE-2022-49304 page https://www.suse.com/security/cve/CVE-2022-49305/ SUSE CVE CVE-2022-49305 page https://www.suse.com/security/cve/CVE-2022-49307/ SUSE CVE CVE-2022-49307 page https://www.suse.com/security/cve/CVE-2022-49313/ SUSE CVE CVE-2022-49313 page https://www.suse.com/security/cve/CVE-2022-49314/ SUSE CVE CVE-2022-49314 page https://www.suse.com/security/cve/CVE-2022-49315/ SUSE CVE CVE-2022-49315 page https://www.suse.com/security/cve/CVE-2022-49316/ SUSE CVE CVE-2022-49316 page https://www.suse.com/security/cve/CVE-2022-49320/ SUSE CVE CVE-2022-49320 page https://www.suse.com/security/cve/CVE-2022-49321/ SUSE CVE CVE-2022-49321 page https://www.suse.com/security/cve/CVE-2022-49326/ SUSE CVE CVE-2022-49326 page https://www.suse.com/security/cve/CVE-2022-49327/ SUSE CVE CVE-2022-49327 page https://www.suse.com/security/cve/CVE-2022-49331/ SUSE CVE CVE-2022-49331 page https://www.suse.com/security/cve/CVE-2022-49332/ SUSE CVE CVE-2022-49332 page https://www.suse.com/security/cve/CVE-2022-49335/ SUSE CVE CVE-2022-49335 page https://www.suse.com/security/cve/CVE-2022-49343/ SUSE CVE CVE-2022-49343 page https://www.suse.com/security/cve/CVE-2022-49347/ SUSE CVE CVE-2022-49347 page https://www.suse.com/security/cve/CVE-2022-49349/ SUSE CVE CVE-2022-49349 page https://www.suse.com/security/cve/CVE-2022-49352/ SUSE CVE CVE-2022-49352 page https://www.suse.com/security/cve/CVE-2022-49357/ SUSE CVE CVE-2022-49357 page https://www.suse.com/security/cve/CVE-2022-49370/ SUSE CVE CVE-2022-49370 page https://www.suse.com/security/cve/CVE-2022-49371/ SUSE CVE CVE-2022-49371 page https://www.suse.com/security/cve/CVE-2022-49373/ SUSE CVE CVE-2022-49373 page https://www.suse.com/security/cve/CVE-2022-49375/ SUSE CVE CVE-2022-49375 page https://www.suse.com/security/cve/CVE-2022-49376/ SUSE CVE CVE-2022-49376 page https://www.suse.com/security/cve/CVE-2022-49382/ SUSE CVE CVE-2022-49382 page https://www.suse.com/security/cve/CVE-2022-49385/ SUSE CVE CVE-2022-49385 page https://www.suse.com/security/cve/CVE-2022-49389/ SUSE CVE CVE-2022-49389 page https://www.suse.com/security/cve/CVE-2022-49394/ SUSE CVE CVE-2022-49394 page https://www.suse.com/security/cve/CVE-2022-49396/ SUSE CVE CVE-2022-49396 page https://www.suse.com/security/cve/CVE-2022-49397/ SUSE CVE CVE-2022-49397 page https://www.suse.com/security/cve/CVE-2022-49398/ SUSE CVE CVE-2022-49398 page https://www.suse.com/security/cve/CVE-2022-49399/ SUSE CVE CVE-2022-49399 page https://www.suse.com/security/cve/CVE-2022-49402/ SUSE CVE CVE-2022-49402 page https://www.suse.com/security/cve/CVE-2022-49404/ SUSE CVE CVE-2022-49404 page https://www.suse.com/security/cve/CVE-2022-49409/ SUSE CVE CVE-2022-49409 page https://www.suse.com/security/cve/CVE-2022-49410/ SUSE CVE CVE-2022-49410 page https://www.suse.com/security/cve/CVE-2022-49411/ SUSE CVE CVE-2022-49411 page https://www.suse.com/security/cve/CVE-2022-49413/ SUSE CVE CVE-2022-49413 page https://www.suse.com/security/cve/CVE-2022-49414/ SUSE CVE CVE-2022-49414 page https://www.suse.com/security/cve/CVE-2022-49416/ SUSE CVE CVE-2022-49416 page https://www.suse.com/security/cve/CVE-2022-49421/ SUSE CVE CVE-2022-49421 page https://www.suse.com/security/cve/CVE-2022-49422/ SUSE CVE CVE-2022-49422 page https://www.suse.com/security/cve/CVE-2022-49437/ SUSE CVE CVE-2022-49437 page https://www.suse.com/security/cve/CVE-2022-49438/ SUSE CVE CVE-2022-49438 page https://www.suse.com/security/cve/CVE-2022-49441/ SUSE CVE CVE-2022-49441 page https://www.suse.com/security/cve/CVE-2022-49442/ SUSE CVE CVE-2022-49442 page https://www.suse.com/security/cve/CVE-2022-49446/ SUSE CVE CVE-2022-49446 page https://www.suse.com/security/cve/CVE-2022-49451/ SUSE CVE CVE-2022-49451 page https://www.suse.com/security/cve/CVE-2022-49455/ SUSE CVE CVE-2022-49455 page https://www.suse.com/security/cve/CVE-2022-49459/ SUSE CVE CVE-2022-49459 page https://www.suse.com/security/cve/CVE-2022-49460/ SUSE CVE CVE-2022-49460 page https://www.suse.com/security/cve/CVE-2022-49462/ SUSE CVE CVE-2022-49462 page https://www.suse.com/security/cve/CVE-2022-49465/ SUSE CVE CVE-2022-49465 page https://www.suse.com/security/cve/CVE-2022-49467/ SUSE CVE CVE-2022-49467 page https://www.suse.com/security/cve/CVE-2022-49473/ SUSE CVE CVE-2022-49473 page https://www.suse.com/security/cve/CVE-2022-49474/ SUSE CVE CVE-2022-49474 page https://www.suse.com/security/cve/CVE-2022-49475/ SUSE CVE CVE-2022-49475 page https://www.suse.com/security/cve/CVE-2022-49478/ SUSE CVE CVE-2022-49478 page https://www.suse.com/security/cve/CVE-2022-49481/ SUSE CVE CVE-2022-49481 page https://www.suse.com/security/cve/CVE-2022-49482/ SUSE CVE CVE-2022-49482 page https://www.suse.com/security/cve/CVE-2022-49488/ SUSE CVE CVE-2022-49488 page https://www.suse.com/security/cve/CVE-2022-49489/ SUSE CVE CVE-2022-49489 page https://www.suse.com/security/cve/CVE-2022-49490/ SUSE CVE CVE-2022-49490 page https://www.suse.com/security/cve/CVE-2022-49491/ SUSE CVE CVE-2022-49491 page https://www.suse.com/security/cve/CVE-2022-49493/ SUSE CVE CVE-2022-49493 page https://www.suse.com/security/cve/CVE-2022-49495/ SUSE CVE CVE-2022-49495 page https://www.suse.com/security/cve/CVE-2022-49498/ SUSE CVE CVE-2022-49498 page https://www.suse.com/security/cve/CVE-2022-49503/ SUSE CVE CVE-2022-49503 page https://www.suse.com/security/cve/CVE-2022-49504/ SUSE CVE CVE-2022-49504 page https://www.suse.com/security/cve/CVE-2022-49505/ SUSE CVE CVE-2022-49505 page https://www.suse.com/security/cve/CVE-2022-49508/ SUSE CVE CVE-2022-49508 page https://www.suse.com/security/cve/CVE-2022-49514/ SUSE CVE CVE-2022-49514 page https://www.suse.com/security/cve/CVE-2022-49517/ SUSE CVE CVE-2022-49517 page https://www.suse.com/security/cve/CVE-2022-49521/ SUSE CVE CVE-2022-49521 page https://www.suse.com/security/cve/CVE-2022-49522/ SUSE CVE CVE-2022-49522 page https://www.suse.com/security/cve/CVE-2022-49524/ SUSE CVE CVE-2022-49524 page https://www.suse.com/security/cve/CVE-2022-49525/ SUSE CVE CVE-2022-49525 page https://www.suse.com/security/cve/CVE-2022-49526/ SUSE CVE CVE-2022-49526 page https://www.suse.com/security/cve/CVE-2022-49527/ SUSE CVE CVE-2022-49527 page https://www.suse.com/security/cve/CVE-2022-49532/ SUSE CVE CVE-2022-49532 page https://www.suse.com/security/cve/CVE-2022-49534/ SUSE CVE CVE-2022-49534 page https://www.suse.com/security/cve/CVE-2022-49535/ SUSE CVE CVE-2022-49535 page https://www.suse.com/security/cve/CVE-2022-49536/ SUSE CVE CVE-2022-49536 page https://www.suse.com/security/cve/CVE-2022-49537/ SUSE CVE CVE-2022-49537 page https://www.suse.com/security/cve/CVE-2022-49541/ SUSE CVE CVE-2022-49541 page https://www.suse.com/security/cve/CVE-2022-49542/ SUSE CVE CVE-2022-49542 page https://www.suse.com/security/cve/CVE-2022-49544/ SUSE CVE CVE-2022-49544 page https://www.suse.com/security/cve/CVE-2022-49545/ SUSE CVE CVE-2022-49545 page https://www.suse.com/security/cve/CVE-2022-49546/ SUSE CVE CVE-2022-49546 page https://www.suse.com/security/cve/CVE-2022-49555/ SUSE CVE CVE-2022-49555 page https://www.suse.com/security/cve/CVE-2022-49563/ SUSE CVE CVE-2022-49563 page https://www.suse.com/security/cve/CVE-2022-49564/ SUSE CVE CVE-2022-49564 page https://www.suse.com/security/cve/CVE-2022-49566/ SUSE CVE CVE-2022-49566 page https://www.suse.com/security/cve/CVE-2022-49609/ SUSE CVE CVE-2022-49609 page https://www.suse.com/security/cve/CVE-2022-49610/ SUSE CVE CVE-2022-49610 page https://www.suse.com/security/cve/CVE-2022-49611/ SUSE CVE CVE-2022-49611 page https://www.suse.com/security/cve/CVE-2022-49623/ SUSE CVE CVE-2022-49623 page https://www.suse.com/security/cve/CVE-2022-49627/ SUSE CVE CVE-2022-49627 page https://www.suse.com/security/cve/CVE-2022-49631/ SUSE CVE CVE-2022-49631 page https://www.suse.com/security/cve/CVE-2022-49640/ SUSE CVE CVE-2022-49640 page https://www.suse.com/security/cve/CVE-2022-49641/ SUSE CVE CVE-2022-49641 page https://www.suse.com/security/cve/CVE-2022-49643/ SUSE CVE CVE-2022-49643 page https://www.suse.com/security/cve/CVE-2022-49644/ SUSE CVE CVE-2022-49644 page https://www.suse.com/security/cve/CVE-2022-49645/ SUSE CVE CVE-2022-49645 page https://www.suse.com/security/cve/CVE-2022-49646/ SUSE CVE CVE-2022-49646 page https://www.suse.com/security/cve/CVE-2022-49647/ SUSE CVE CVE-2022-49647 page https://www.suse.com/security/cve/CVE-2022-49648/ SUSE CVE CVE-2022-49648 page https://www.suse.com/security/cve/CVE-2022-49649/ SUSE CVE CVE-2022-49649 page https://www.suse.com/security/cve/CVE-2022-49652/ SUSE CVE CVE-2022-49652 page https://www.suse.com/security/cve/CVE-2022-49657/ SUSE CVE CVE-2022-49657 page https://www.suse.com/security/cve/CVE-2022-49661/ SUSE CVE CVE-2022-49661 page https://www.suse.com/security/cve/CVE-2022-49670/ SUSE CVE CVE-2022-49670 page https://www.suse.com/security/cve/CVE-2022-49671/ SUSE CVE CVE-2022-49671 page https://www.suse.com/security/cve/CVE-2022-49673/ SUSE CVE CVE-2022-49673 page https://www.suse.com/security/cve/CVE-2022-49674/ SUSE CVE CVE-2022-49674 page https://www.suse.com/security/cve/CVE-2022-49678/ SUSE CVE CVE-2022-49678 page https://www.suse.com/security/cve/CVE-2022-49685/ SUSE CVE CVE-2022-49685 page https://www.suse.com/security/cve/CVE-2022-49687/ SUSE CVE CVE-2022-49687 page https://www.suse.com/security/cve/CVE-2022-49693/ SUSE CVE CVE-2022-49693 page https://www.suse.com/security/cve/CVE-2022-49700/ SUSE CVE CVE-2022-49700 page https://www.suse.com/security/cve/CVE-2022-49701/ SUSE CVE CVE-2022-49701 page https://www.suse.com/security/cve/CVE-2022-49703/ SUSE CVE CVE-2022-49703 page https://www.suse.com/security/cve/CVE-2022-49707/ SUSE CVE CVE-2022-49707 page https://www.suse.com/security/cve/CVE-2022-49708/ SUSE CVE CVE-2022-49708 page https://www.suse.com/security/cve/CVE-2022-49710/ SUSE CVE CVE-2022-49710 page https://www.suse.com/security/cve/CVE-2022-49711/ SUSE CVE CVE-2022-49711 page https://www.suse.com/security/cve/CVE-2022-49712/ SUSE CVE CVE-2022-49712 page https://www.suse.com/security/cve/CVE-2022-49713/ SUSE CVE CVE-2022-49713 page https://www.suse.com/security/cve/CVE-2022-49720/ SUSE CVE CVE-2022-49720 page https://www.suse.com/security/cve/CVE-2022-49723/ SUSE CVE CVE-2022-49723 page https://www.suse.com/security/cve/CVE-2022-49724/ SUSE CVE CVE-2022-49724 page https://www.suse.com/security/cve/CVE-2022-49729/ SUSE CVE CVE-2022-49729 page https://www.suse.com/security/cve/CVE-2022-49730/ SUSE CVE CVE-2022-49730 page https://www.suse.com/security/cve/CVE-2022-49731/ SUSE CVE CVE-2022-49731 page https://www.suse.com/security/cve/CVE-2022-49733/ SUSE CVE CVE-2022-49733 page https://www.suse.com/security/cve/CVE-2022-49739/ SUSE CVE CVE-2022-49739 page https://www.suse.com/security/cve/CVE-2023-2162/ SUSE CVE CVE-2023-2162 page https://www.suse.com/security/cve/CVE-2023-3567/ SUSE CVE CVE-2023-3567 page https://www.suse.com/security/cve/CVE-2023-52935/ SUSE CVE CVE-2023-52935 page https://www.suse.com/security/cve/CVE-2023-52973/ SUSE CVE CVE-2023-52973 page https://www.suse.com/security/cve/CVE-2023-52974/ SUSE CVE CVE-2023-52974 page https://www.suse.com/security/cve/CVE-2023-53000/ SUSE CVE CVE-2023-53000 page https://www.suse.com/security/cve/CVE-2023-53015/ SUSE CVE CVE-2023-53015 page https://www.suse.com/security/cve/CVE-2023-53024/ SUSE CVE CVE-2023-53024 page https://www.suse.com/security/cve/CVE-2024-50290/ SUSE CVE CVE-2024-50290 page https://www.suse.com/security/cve/CVE-2024-53063/ SUSE CVE CVE-2024-53063 page https://www.suse.com/security/cve/CVE-2024-56642/ SUSE CVE CVE-2024-56642 page https://www.suse.com/security/cve/CVE-2024-56651/ SUSE CVE CVE-2024-56651 page https://www.suse.com/security/cve/CVE-2024-57996/ SUSE CVE CVE-2024-57996 page https://www.suse.com/security/cve/CVE-2024-58014/ SUSE CVE CVE-2024-58014 page https://www.suse.com/security/cve/CVE-2025-21772/ SUSE CVE CVE-2025-21772 page https://www.suse.com/security/cve/CVE-2025-21780/ SUSE CVE CVE-2025-21780 page SUSE Linux Enterprise Micro 5.1 SUSE Linux Enterprise Micro 5.2 cluster-md-kmp-rt-5.3.18-150300.205.1 cluster-md-kmp-rt_debug-5.3.18-150300.205.1 dlm-kmp-rt-5.3.18-150300.205.1 dlm-kmp-rt_debug-5.3.18-150300.205.1 gfs2-kmp-rt-5.3.18-150300.205.1 gfs2-kmp-rt_debug-5.3.18-150300.205.1 kernel-devel-rt-5.3.18-150300.205.1 kernel-rt-5.3.18-150300.205.1 kernel-rt-devel-5.3.18-150300.205.1 kernel-rt-extra-5.3.18-150300.205.1 kernel-rt-livepatch-devel-5.3.18-150300.205.1 kernel-rt-optional-5.3.18-150300.205.1 kernel-rt_debug-5.3.18-150300.205.1 kernel-rt_debug-devel-5.3.18-150300.205.1 kernel-rt_debug-extra-5.3.18-150300.205.1 kernel-rt_debug-livepatch-devel-5.3.18-150300.205.1 kernel-rt_debug-optional-5.3.18-150300.205.1 kernel-source-rt-5.3.18-150300.205.1 kernel-syms-rt-5.3.18-150300.205.1 kselftests-kmp-rt-5.3.18-150300.205.1 kselftests-kmp-rt_debug-5.3.18-150300.205.1 ocfs2-kmp-rt-5.3.18-150300.205.1 ocfs2-kmp-rt_debug-5.3.18-150300.205.1 reiserfs-kmp-rt-5.3.18-150300.205.1 reiserfs-kmp-rt_debug-5.3.18-150300.205.1 kernel-rt-5.3.18-150300.205.1 as a component of SUSE Linux Enterprise Micro 5.1 kernel-source-rt-5.3.18-150300.205.1 as a component of SUSE Linux Enterprise Micro 5.1 kernel-rt-5.3.18-150300.205.1 as a component of SUSE Linux Enterprise Micro 5.2 kernel-source-rt-5.3.18-150300.205.1 as a component of SUSE Linux Enterprise Micro 5.2 Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis. CVE-2017-5753 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important 4.9 AV:L/AC:L/Au:N/C:C/I:N/A:N 4.7 AV:L/AC:M/Au:N/C:C/I:N/A:N To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2017-5753.html CVE-2017-5753 https://bugzilla.suse.com/1068032 SUSE Bug 1068032 https://bugzilla.suse.com/1074562 SUSE Bug 1074562 https://bugzilla.suse.com/1074578 SUSE Bug 1074578 https://bugzilla.suse.com/1074701 SUSE Bug 1074701 https://bugzilla.suse.com/1075006 SUSE Bug 1075006 https://bugzilla.suse.com/1075419 SUSE Bug 1075419 https://bugzilla.suse.com/1075748 SUSE Bug 1075748 https://bugzilla.suse.com/1080039 SUSE Bug 1080039 https://bugzilla.suse.com/1087084 SUSE Bug 1087084 https://bugzilla.suse.com/1087939 SUSE Bug 1087939 https://bugzilla.suse.com/1089055 SUSE Bug 1089055 https://bugzilla.suse.com/1136865 SUSE Bug 1136865 https://bugzilla.suse.com/1178658 SUSE Bug 1178658 https://bugzilla.suse.com/1201877 SUSE Bug 1201877 https://bugzilla.suse.com/1209547 SUSE Bug 1209547 A use after free in the Linux kernel infiniband hfi1 driver in versions prior to 5.10-rc6 was found in the way user calls Ioctl after open dev file and fork. A local user could use this flaw to crash the system. CVE-2020-27835 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important 4.9 AV:L/AC:L/Au:N/C:N/I:N/A:C To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2020-27835.html CVE-2020-27835 https://bugzilla.suse.com/1179878 SUSE Bug 1179878 In the Linux kernel, the following vulnerability has been resolved: udp: fix race between close() and udp_abort() Kaustubh reported and diagnosed a panic in udp_lib_lookup(). The root cause is udp_abort() racing with close(). Both racing functions acquire the socket lock, but udp{v6}_destroy_sock() release it before performing destructive actions. We can't easily extend the socket lock scope to avoid the race, instead use the SOCK_DEAD flag to prevent udp_abort from doing any action when the critical race happens. Diagnosed-and-tested-by: Kaustubh Pandey <kapandey@codeaurora.org> CVE-2021-47248 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2021-47248.html CVE-2021-47248 https://bugzilla.suse.com/1224867 SUSE Bug 1224867 In the Linux kernel, the following vulnerability has been resolved: ARM: davinci: da850-evm: Avoid NULL pointer dereference With newer versions of GCC, there is a panic in da850_evm_config_emac() when booting multi_v5_defconfig in QEMU under the palmetto-bmc machine: Unable to handle kernel NULL pointer dereference at virtual address 00000020 pgd = (ptrval) [00000020] *pgd=00000000 Internal error: Oops: 5 [#1] PREEMPT ARM Modules linked in: CPU: 0 PID: 1 Comm: swapper Not tainted 5.15.0 #1 Hardware name: Generic DT based system PC is at da850_evm_config_emac+0x1c/0x120 LR is at do_one_initcall+0x50/0x1e0 The emac_pdata pointer in soc_info is NULL because davinci_soc_info only gets populated on davinci machines but da850_evm_config_emac() is called on all machines via device_initcall(). Move the rmii_en assignment below the machine check so that it is only dereferenced when running on a supported SoC. CVE-2021-47631 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2021-47631.html CVE-2021-47631 https://bugzilla.suse.com/1237718 SUSE Bug 1237718 In the Linux kernel, the following vulnerability has been resolved: video: fbdev: cirrusfb: check pixclock to avoid divide by zero Do a sanity check on pixclock value to avoid divide by zero. If the pixclock value is zero, the cirrusfb driver will round up pixclock to get the derived frequency as close to maxclock as possible. Syzkaller reported a divide error in cirrusfb_check_pixclock. divide error: 0000 [#1] SMP KASAN PTI CPU: 0 PID: 14938 Comm: cirrusfb_test Not tainted 5.15.0-rc6 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-2 RIP: 0010:cirrusfb_check_var+0x6f1/0x1260 Call Trace: fb_set_var+0x398/0xf90 do_fb_ioctl+0x4b8/0x6f0 fb_ioctl+0xeb/0x130 __x64_sys_ioctl+0x19d/0x220 do_syscall_64+0x3a/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae CVE-2021-47641 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2021-47641.html CVE-2021-47641 https://bugzilla.suse.com/1237734 SUSE Bug 1237734 In the Linux kernel, the following vulnerability has been resolved: video: fbdev: nvidiafb: Use strscpy() to prevent buffer overflow Coverity complains of a possible buffer overflow. However, given the 'static' scope of nvidia_setup_i2c_bus() it looks like that can't happen after examiniing the call sites. CID 19036 (#1 of 1): Copy into fixed size buffer (STRING_OVERFLOW) 1. fixed_size_dest: You might overrun the 48-character fixed-size string chan->adapter.name by copying name without checking the length. 2. parameter_as_source: Note: This defect has an elevated risk because the source argument is a parameter of the current function. 89 strcpy(chan->adapter.name, name); Fix this warning by using strscpy() which will silence the warning and prevent any future buffer overflows should the names used to identify the channel become much longer. CVE-2021-47642 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2021-47642.html CVE-2021-47642 https://bugzilla.suse.com/1237916 SUSE Bug 1237916 In the Linux kernel, the following vulnerability has been resolved: ASoC: soc-compress: prevent the potentially use of null pointer There is one call trace that snd_soc_register_card() ->snd_soc_bind_card()->soc_init_pcm_runtime() ->snd_soc_dai_compress_new()->snd_soc_new_compress(). In the trace the 'codec_dai' transfers from card->dai_link, and we can see from the snd_soc_add_pcm_runtime() in snd_soc_bind_card() that, if value of card->dai_link->num_codecs is 0, then 'codec_dai' could be null pointer caused by index out of bound in 'asoc_rtd_to_codec(rtd, 0)'. And snd_soc_register_card() is called by various platforms. Therefore, it is better to add the check in the case of misusing. And because 'cpu_dai' has already checked in soc_init_pcm_runtime(), there is no need to check again. Adding the check as follow, then if 'codec_dai' is null, snd_soc_new_compress() will not pass through the check 'if (playback + capture != 1)', avoiding the leftover use of 'codec_dai'. CVE-2021-47650 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2021-47650.html CVE-2021-47650 https://bugzilla.suse.com/1237742 SUSE Bug 1237742 In the Linux kernel, the following vulnerability has been resolved: soc: qcom: rpmpd: Check for null return of devm_kcalloc Because of the possible failure of the allocation, data->domains might be NULL pointer and will cause the dereference of the NULL pointer later. Therefore, it might be better to check it and directly return -ENOMEM without releasing data manually if fails, because the comment of the devm_kmalloc() says "Memory allocated with this function is automatically freed on driver detach.". CVE-2021-47651 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2021-47651.html CVE-2021-47651 https://bugzilla.suse.com/1237872 SUSE Bug 1237872 In the Linux kernel, the following vulnerability has been resolved: video: fbdev: smscufx: Fix null-ptr-deref in ufx_usb_probe() I got a null-ptr-deref report: BUG: kernel NULL pointer dereference, address: 0000000000000000 ... RIP: 0010:fb_destroy_modelist+0x38/0x100 ... Call Trace: ufx_usb_probe.cold+0x2b5/0xac1 [smscufx] usb_probe_interface+0x1aa/0x3c0 [usbcore] really_probe+0x167/0x460 ... ret_from_fork+0x1f/0x30 If fb_alloc_cmap() fails in ufx_usb_probe(), fb_destroy_modelist() will be called to destroy modelist in the error handling path. But modelist has not been initialized yet, so it will result in null-ptr-deref. Initialize modelist before calling fb_alloc_cmap() to fix this bug. CVE-2021-47652 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2021-47652.html CVE-2021-47652 https://bugzilla.suse.com/1237721 SUSE Bug 1237721 In the Linux kernel, the following vulnerability has been resolved: media: davinci: vpif: fix use-after-free on driver unbind The driver allocates and registers two platform device structures during probe, but the devices were never deregistered on driver unbind. This results in a use-after-free on driver unbind as the device structures were allocated using devres and would be freed by driver core when remove() returns. Fix this by adding the missing deregistration calls to the remove() callback and failing probe on registration errors. Note that the platform device structures must be freed using a proper release callback to avoid leaking associated resources like device names. CVE-2021-47653 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2021-47653.html CVE-2021-47653 https://bugzilla.suse.com/1237748 SUSE Bug 1237748 In the Linux kernel, the following vulnerability has been resolved: drm/plane: Move range check for format_count earlier While the check for format_count > 64 in __drm_universal_plane_init() shouldn't be hit (it's a WARN_ON), in its current position it will then leak the plane->format_types array and fail to call drm_mode_object_unregister() leaking the modeset identifier. Move it to the start of the function to avoid allocating those resources in the first place. CVE-2021-47659 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2021-47659.html CVE-2021-47659 https://bugzilla.suse.com/1237839 SUSE Bug 1237839 A denial of service (DOS) issue was found in the Linux kernel's smb2_ioctl_query_info function in the fs/cifs/smb2ops.c Common Internet File System (CIFS) due to an incorrect return from the memdup_user function. This flaw allows a local, privileged (CAP_SYS_ADMIN) attacker to crash the system. CVE-2022-0168 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-0168.html CVE-2022-0168 https://bugzilla.suse.com/1197472 SUSE Bug 1197472 A flaw was found in the Linux kernel in net/netfilter/nf_tables_core.c:nft_do_chain, which can cause a use-after-free. This issue needs to handle 'return' with proper preconditions, as it can lead to a kernel information leak problem caused by a local, unprivileged attacker. CVE-2022-1016 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-1016.html CVE-2022-1016 https://bugzilla.suse.com/1197335 SUSE Bug 1197335 A use-after-free flaw was found in the Linux kernel's sound subsystem in the way a user triggers concurrent calls of PCM hw_params. The hw_free ioctls or similar race condition happens inside ALSA PCM for other ioctls. This flaw allows a local user to crash or potentially escalate their privileges on the system. CVE-2022-1048 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important 6.9 AV:L/AC:M/Au:N/C:C/I:C/A:C To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-1048.html CVE-2022-1048 https://bugzilla.suse.com/1197331 SUSE Bug 1197331 https://bugzilla.suse.com/1197597 SUSE Bug 1197597 https://bugzilla.suse.com/1200041 SUSE Bug 1200041 https://bugzilla.suse.com/1204132 SUSE Bug 1204132 https://bugzilla.suse.com/1212325 SUSE Bug 1212325 A use-after-free flaw was found in fs/ext4/namei.c:dx_insert_block() in the Linux kernel's filesystem sub-component. This flaw allows a local attacker with a user privilege to cause a denial of service. CVE-2022-1184 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-1184.html CVE-2022-1184 https://bugzilla.suse.com/1198577 SUSE Bug 1198577 https://bugzilla.suse.com/1210859 SUSE Bug 1210859 A flaw was found in the Linux kernel implementation of proxied virtualized TPM devices. On a system where virtualized TPM devices are configured (this is not the default) a local attacker can create a use-after-free and create a situation where it may be possible to escalate privileges on the system. CVE-2022-2977 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-2977.html CVE-2022-2977 https://bugzilla.suse.com/1202672 SUSE Bug 1202672 Mis-trained branch predictions for return instructions may allow arbitrary speculative code execution under certain microarchitecture-dependent conditions. CVE-2022-29900 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-29900.html CVE-2022-29900 https://bugzilla.suse.com/1199657 SUSE Bug 1199657 https://bugzilla.suse.com/1201469 SUSE Bug 1201469 https://bugzilla.suse.com/1207894 SUSE Bug 1207894 Intel microprocessor generations 6 to 8 are affected by a new Spectre variant that is able to bypass their retpoline mitigation in the kernel to leak arbitrary data. An attacker with unprivileged user access can hijack return instructions to achieve arbitrary speculative code execution under certain microarchitecture-dependent conditions. CVE-2022-29901 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-29901.html CVE-2022-29901 https://bugzilla.suse.com/1201469 SUSE Bug 1201469 https://bugzilla.suse.com/1207894 SUSE Bug 1207894 A race condition flaw was found in the Linux kernel sound subsystem due to improper locking. It could lead to a NULL pointer dereference while handling the SNDCTL_DSP_SYNC ioctl. A privileged local user (root or member of the audio group) could use this flaw to crash the system, resulting in a denial of service condition CVE-2022-3303 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-3303.html CVE-2022-3303 https://bugzilla.suse.com/1203769 SUSE Bug 1203769 https://bugzilla.suse.com/1212304 SUSE Bug 1212304 In the Linux kernel, the following vulnerability has been resolved: dm integrity: fix memory corruption when tag_size is less than digest size It is possible to set up dm-integrity in such a way that the "tag_size" parameter is less than the actual digest size. In this situation, a part of the digest beyond tag_size is ignored. In this case, dm-integrity would write beyond the end of the ic->recalc_tags array and corrupt memory. The corruption happened in integrity_recalc->integrity_sector_checksum->crypto_shash_final. Fix this corruption by increasing the tags array so that it has enough padding at the end to accomodate the loop in integrity_recalc() being able to write a full digest size for the last member of the tags array. CVE-2022-49044 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49044.html CVE-2022-49044 https://bugzilla.suse.com/1237840 SUSE Bug 1237840 In the Linux kernel, the following vulnerability has been resolved: net: usb: aqc111: Fix out-of-bounds accesses in RX fixup aqc111_rx_fixup() contains several out-of-bounds accesses that can be triggered by a malicious (or defective) USB device, in particular: - The metadata array (desc_offset..desc_offset+2*pkt_count) can be out of bounds, causing OOB reads and (on big-endian systems) OOB endianness flips. - A packet can overlap the metadata array, causing a later OOB endianness flip to corrupt data used by a cloned SKB that has already been handed off into the network stack. - A packet SKB can be constructed whose tail is far beyond its end, causing out-of-bounds heap data to be considered part of the SKB's data. Found doing variant analysis. Tested it with another driver (ax88179_178a), since I don't have a aqc111 device to test it, but the code looks very similar. CVE-2022-49051 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49051.html CVE-2022-49051 https://bugzilla.suse.com/1237903 SUSE Bug 1237903 In the Linux kernel, the following vulnerability has been resolved: scsi: target: tcmu: Fix possible page UAF tcmu_try_get_data_page() looks up pages under cmdr_lock, but it does not take refcount properly and just returns page pointer. When tcmu_try_get_data_page() returns, the returned page may have been freed by tcmu_blocks_release(). We need to get_page() under cmdr_lock to avoid concurrent tcmu_blocks_release(). CVE-2022-49053 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49053.html CVE-2022-49053 https://bugzilla.suse.com/1237918 SUSE Bug 1237918 https://bugzilla.suse.com/1237930 SUSE Bug 1237930 In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check for potential null return of kmalloc_array() As the kmalloc_array() may return null, the 'event_waiters[i].wait' would lead to null-pointer dereference. Therefore, it is better to check the return value of kmalloc_array() to avoid this confusion. CVE-2022-49055 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49055.html CVE-2022-49055 https://bugzilla.suse.com/1237868 SUSE Bug 1237868 In the Linux kernel, the following vulnerability has been resolved: cifs: potential buffer overflow in handling symlinks Smatch printed a warning: arch/x86/crypto/poly1305_glue.c:198 poly1305_update_arch() error: __memcpy() 'dctx->buf' too small (16 vs u32max) It's caused because Smatch marks 'link_len' as untrusted since it comes from sscanf(). Add a check to ensure that 'link_len' is not larger than the size of the 'link_str' buffer. CVE-2022-49058 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49058.html CVE-2022-49058 https://bugzilla.suse.com/1237814 SUSE Bug 1237814 In the Linux kernel, the following vulnerability has been resolved: nfc: nci: add flush_workqueue to prevent uaf Our detector found a concurrent use-after-free bug when detaching an NCI device. The main reason for this bug is the unexpected scheduling between the used delayed mechanism (timer and workqueue). The race can be demonstrated below: Thread-1 Thread-2 | nci_dev_up() | nci_open_device() | __nci_request(nci_reset_req) | nci_send_cmd | queue_work(cmd_work) nci_unregister_device() | nci_close_device() | ... del_timer_sync(cmd_timer)[1] | ... | Worker nci_free_device() | nci_cmd_work() kfree(ndev)[3] | mod_timer(cmd_timer)[2] In short, the cleanup routine thought that the cmd_timer has already been detached by [1] but the mod_timer can re-attach the timer [2], even it is already released [3], resulting in UAF. This UAF is easy to trigger, crash trace by POC is like below [ 66.703713] ================================================================== [ 66.703974] BUG: KASAN: use-after-free in enqueue_timer+0x448/0x490 [ 66.703974] Write of size 8 at addr ffff888009fb7058 by task kworker/u4:1/33 [ 66.703974] [ 66.703974] CPU: 1 PID: 33 Comm: kworker/u4:1 Not tainted 5.18.0-rc2 #5 [ 66.703974] Workqueue: nfc2_nci_cmd_wq nci_cmd_work [ 66.703974] Call Trace: [ 66.703974] <TASK> [ 66.703974] dump_stack_lvl+0x57/0x7d [ 66.703974] print_report.cold+0x5e/0x5db [ 66.703974] ? enqueue_timer+0x448/0x490 [ 66.703974] kasan_report+0xbe/0x1c0 [ 66.703974] ? enqueue_timer+0x448/0x490 [ 66.703974] enqueue_timer+0x448/0x490 [ 66.703974] __mod_timer+0x5e6/0xb80 [ 66.703974] ? mark_held_locks+0x9e/0xe0 [ 66.703974] ? try_to_del_timer_sync+0xf0/0xf0 [ 66.703974] ? lockdep_hardirqs_on_prepare+0x17b/0x410 [ 66.703974] ? queue_work_on+0x61/0x80 [ 66.703974] ? lockdep_hardirqs_on+0xbf/0x130 [ 66.703974] process_one_work+0x8bb/0x1510 [ 66.703974] ? lockdep_hardirqs_on_prepare+0x410/0x410 [ 66.703974] ? pwq_dec_nr_in_flight+0x230/0x230 [ 66.703974] ? rwlock_bug.part.0+0x90/0x90 [ 66.703974] ? _raw_spin_lock_irq+0x41/0x50 [ 66.703974] worker_thread+0x575/0x1190 [ 66.703974] ? process_one_work+0x1510/0x1510 [ 66.703974] kthread+0x2a0/0x340 [ 66.703974] ? kthread_complete_and_exit+0x20/0x20 [ 66.703974] ret_from_fork+0x22/0x30 [ 66.703974] </TASK> [ 66.703974] [ 66.703974] Allocated by task 267: [ 66.703974] kasan_save_stack+0x1e/0x40 [ 66.703974] __kasan_kmalloc+0x81/0xa0 [ 66.703974] nci_allocate_device+0xd3/0x390 [ 66.703974] nfcmrvl_nci_register_dev+0x183/0x2c0 [ 66.703974] nfcmrvl_nci_uart_open+0xf2/0x1dd [ 66.703974] nci_uart_tty_ioctl+0x2c3/0x4a0 [ 66.703974] tty_ioctl+0x764/0x1310 [ 66.703974] __x64_sys_ioctl+0x122/0x190 [ 66.703974] do_syscall_64+0x3b/0x90 [ 66.703974] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 66.703974] [ 66.703974] Freed by task 406: [ 66.703974] kasan_save_stack+0x1e/0x40 [ 66.703974] kasan_set_track+0x21/0x30 [ 66.703974] kasan_set_free_info+0x20/0x30 [ 66.703974] __kasan_slab_free+0x108/0x170 [ 66.703974] kfree+0xb0/0x330 [ 66.703974] nfcmrvl_nci_unregister_dev+0x90/0xd0 [ 66.703974] nci_uart_tty_close+0xdf/0x180 [ 66.703974] tty_ldisc_kill+0x73/0x110 [ 66.703974] tty_ldisc_hangup+0x281/0x5b0 [ 66.703974] __tty_hangup.part.0+0x431/0x890 [ 66.703974] tty_release+0x3a8/0xc80 [ 66.703974] __fput+0x1f0/0x8c0 [ 66.703974] task_work_run+0xc9/0x170 [ 66.703974] exit_to_user_mode_prepare+0x194/0x1a0 [ 66.703974] syscall_exit_to_user_mode+0x19/0x50 [ 66.703974] do_syscall_64+0x48/0x90 [ 66.703974] entry_SYSCALL_64_after_hwframe+0x44/0x ---truncated--- CVE-2022-49059 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49059.html CVE-2022-49059 https://bugzilla.suse.com/1238007 SUSE Bug 1238007 In the Linux kernel, the following vulnerability has been resolved: ice: arfs: fix use-after-free when freeing @rx_cpu_rmap The CI testing bots triggered the following splat: [ 718.203054] BUG: KASAN: use-after-free in free_irq_cpu_rmap+0x53/0x80 [ 718.206349] Read of size 4 at addr ffff8881bd127e00 by task sh/20834 [ 718.212852] CPU: 28 PID: 20834 Comm: sh Kdump: loaded Tainted: G S W IOE 5.17.0-rc8_nextqueue-devqueue-02643-g23f3121aca93 #1 [ 718.219695] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0012.070720200218 07/07/2020 [ 718.223418] Call Trace: [ 718.227139] [ 718.230783] dump_stack_lvl+0x33/0x42 [ 718.234431] print_address_description.constprop.9+0x21/0x170 [ 718.238177] ? free_irq_cpu_rmap+0x53/0x80 [ 718.241885] ? free_irq_cpu_rmap+0x53/0x80 [ 718.245539] kasan_report.cold.18+0x7f/0x11b [ 718.249197] ? free_irq_cpu_rmap+0x53/0x80 [ 718.252852] free_irq_cpu_rmap+0x53/0x80 [ 718.256471] ice_free_cpu_rx_rmap.part.11+0x37/0x50 [ice] [ 718.260174] ice_remove_arfs+0x5f/0x70 [ice] [ 718.263810] ice_rebuild_arfs+0x3b/0x70 [ice] [ 718.267419] ice_rebuild+0x39c/0xb60 [ice] [ 718.270974] ? asm_sysvec_apic_timer_interrupt+0x12/0x20 [ 718.274472] ? ice_init_phy_user_cfg+0x360/0x360 [ice] [ 718.278033] ? delay_tsc+0x4a/0xb0 [ 718.281513] ? preempt_count_sub+0x14/0xc0 [ 718.284984] ? delay_tsc+0x8f/0xb0 [ 718.288463] ice_do_reset+0x92/0xf0 [ice] [ 718.292014] ice_pci_err_resume+0x91/0xf0 [ice] [ 718.295561] pci_reset_function+0x53/0x80 <...> [ 718.393035] Allocated by task 690: [ 718.433497] Freed by task 20834: [ 718.495688] Last potentially related work creation: [ 718.568966] The buggy address belongs to the object at ffff8881bd127e00 which belongs to the cache kmalloc-96 of size 96 [ 718.574085] The buggy address is located 0 bytes inside of 96-byte region [ffff8881bd127e00, ffff8881bd127e60) [ 718.579265] The buggy address belongs to the page: [ 718.598905] Memory state around the buggy address: [ 718.601809] ffff8881bd127d00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc [ 718.604796] ffff8881bd127d80: 00 00 00 00 00 00 00 00 00 00 fc fc fc fc fc fc [ 718.607794] >ffff8881bd127e00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc [ 718.610811] ^ [ 718.613819] ffff8881bd127e80: 00 00 00 00 00 00 00 00 00 00 00 00 fc fc fc fc [ 718.617107] ffff8881bd127f00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc This is due to that free_irq_cpu_rmap() is always being called *after* (devm_)free_irq() and thus it tries to work with IRQ descs already freed. For example, on device reset the driver frees the rmap right before allocating a new one (the splat above). Make rmap creation and freeing function symmetrical with {request,free}_irq() calls i.e. do that on ifup/ifdown instead of device probe/remove/resume. These operations can be performed independently from the actual device aRFS configuration. Also, make sure ice_vsi_free_irq() clears IRQ affinity notifiers only when aRFS is disabled -- otherwise, CPU rmap sets and clears its own and they must not be touched manually. CVE-2022-49063 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49063.html CVE-2022-49063 https://bugzilla.suse.com/1237846 SUSE Bug 1237846 In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix the svc_deferred_event trace class Fix a NULL deref crash that occurs when an svc_rqst is deferred while the sunrpc tracing subsystem is enabled. svc_revisit() sets dr->xprt to NULL, so it can't be relied upon in the tracepoint to provide the remote's address. Unfortunately we can't revert the "svc_deferred_class" hunk in commit ece200ddd54b ("sunrpc: Save remote presentation address in svc_xprt for trace events") because there is now a specific check of event format specifiers for unsafe dereferences. The warning that check emits is: event svc_defer_recv has unsafe dereference of argument 1 A "%pISpc" format specifier with a "struct sockaddr *" is indeed flagged by this check. Instead, take the brute-force approach used by the svcrdma_qp_error tracepoint. Convert the dr::addr field into a presentation address in the TP_fast_assign() arm of the trace event, and store that as a string. This fix can be backported to -stable kernels. In the meantime, commit c6ced22997ad ("tracing: Update print fmt check to handle new __get_sockaddr() macro") is now in v5.18, so this wonky fix can be replaced with __sockaddr() and friends properly during the v5.19 merge window. CVE-2022-49065 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49065.html CVE-2022-49065 https://bugzilla.suse.com/1237739 SUSE Bug 1237739 In the Linux kernel, the following vulnerability has been resolved: ata: sata_dwc_460ex: Fix crash due to OOB write the driver uses libata's "tag" values from in various arrays. Since the mentioned patch bumped the ATA_TAG_INTERNAL to 32, the value of the SATA_DWC_QCMD_MAX needs to account for that. Otherwise ATA_TAG_INTERNAL usage cause similar crashes like this as reported by Tice Rex on the OpenWrt Forum and reproduced (with symbols) here: | BUG: Kernel NULL pointer dereference at 0x00000000 | Faulting instruction address: 0xc03ed4b8 | Oops: Kernel access of bad area, sig: 11 [#1] | BE PAGE_SIZE=4K PowerPC 44x Platform | CPU: 0 PID: 362 Comm: scsi_eh_1 Not tainted 5.4.163 #0 | NIP: c03ed4b8 LR: c03d27e8 CTR: c03ed36c | REGS: cfa59950 TRAP: 0300 Not tainted (5.4.163) | MSR: 00021000 <CE,ME> CR: 42000222 XER: 00000000 | DEAR: 00000000 ESR: 00000000 | GPR00: c03d27e8 cfa59a08 cfa55fe0 00000000 0fa46bc0 [...] | [..] | NIP [c03ed4b8] sata_dwc_qc_issue+0x14c/0x254 | LR [c03d27e8] ata_qc_issue+0x1c8/0x2dc | Call Trace: | [cfa59a08] [c003f4e0] __cancel_work_timer+0x124/0x194 (unreliable) | [cfa59a78] [c03d27e8] ata_qc_issue+0x1c8/0x2dc | [cfa59a98] [c03d2b3c] ata_exec_internal_sg+0x240/0x524 | [cfa59b08] [c03d2e98] ata_exec_internal+0x78/0xe0 | [cfa59b58] [c03d30fc] ata_read_log_page.part.38+0x1dc/0x204 | [cfa59bc8] [c03d324c] ata_identify_page_supported+0x68/0x130 | [...] This is because sata_dwc_dma_xfer_complete() NULLs the dma_pending's next neighbour "chan" (a *dma_chan struct) in this '32' case right here (line ~735): > hsdevp->dma_pending[tag] = SATA_DWC_DMA_PENDING_NONE; Then the next time, a dma gets issued; dma_dwc_xfer_setup() passes the NULL'd hsdevp->chan to the dmaengine_slave_config() which then causes the crash. With this patch, SATA_DWC_QCMD_MAX is now set to ATA_MAX_QUEUE + 1. This avoids the OOB. But please note, there was a worthwhile discussion on what ATA_TAG_INTERNAL and ATA_MAX_QUEUE is. And why there should not be a "fake" 33 command-long queue size. Ideally, the dw driver should account for the ATA_TAG_INTERNAL. In Damien Le Moal's words: "... having looked at the driver, it is a bigger change than just faking a 33rd "tag" that is in fact not a command tag at all." BugLink: https://github.com/openwrt/openwrt/issues/9505 CVE-2022-49073 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49073.html CVE-2022-49073 https://bugzilla.suse.com/1237746 SUSE Bug 1237746 In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Fix use-after-free bug for mm struct Under certain conditions, such as MPI_Abort, the hfi1 cleanup code may represent the last reference held on the task mm. hfi1_mmu_rb_unregister() then drops the last reference and the mm is freed before the final use in hfi1_release_user_pages(). A new task may allocate the mm structure while it is still being used, resulting in problems. One manifestation is corruption of the mmap_sem counter leading to a hang in down_write(). Another is corruption of an mm struct that is in use by another task. CVE-2022-49076 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49076.html CVE-2022-49076 https://bugzilla.suse.com/1237738 SUSE Bug 1237738 In the Linux kernel, the following vulnerability has been resolved: lz4: fix LZ4_decompress_safe_partial read out of bound When partialDecoding, it is EOF if we've either filled the output buffer or can't proceed with reading an offset for following match. In some extreme corner cases when compressed data is suitably corrupted, UAF will occur. As reported by KASAN [1], LZ4_decompress_safe_partial may lead to read out of bound problem during decoding. lz4 upstream has fixed it [2] and this issue has been disscussed here [3] before. current decompression routine was ported from lz4 v1.8.3, bumping lib/lz4 to v1.9.+ is certainly a huge work to be done later, so, we'd better fix it first. [1] https://lore.kernel.org/all/000000000000830d1205cf7f0477@google.com/ [2] https://github.com/lz4/lz4/commit/c5d6f8a8be3927c0bec91bcc58667a6cfad244ad# [3] https://lore.kernel.org/all/CC666AE8-4CA4-4951-B6FB-A2EFDE3AC03B@fb.com/ CVE-2022-49078 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49078.html CVE-2022-49078 https://bugzilla.suse.com/1237736 SUSE Bug 1237736 In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Fix use after free in _scsih_expander_node_remove() The function mpt3sas_transport_port_remove() called in _scsih_expander_node_remove() frees the port field of the sas_expander structure, leading to the following use-after-free splat from KASAN when the ioc_info() call following that function is executed (e.g. when doing rmmod of the driver module): [ 3479.371167] ================================================================== [ 3479.378496] BUG: KASAN: use-after-free in _scsih_expander_node_remove+0x710/0x750 [mpt3sas] [ 3479.386936] Read of size 1 at addr ffff8881c037691c by task rmmod/1531 [ 3479.393524] [ 3479.395035] CPU: 18 PID: 1531 Comm: rmmod Not tainted 5.17.0-rc8+ #1436 [ 3479.401712] Hardware name: Supermicro Super Server/H12SSL-NT, BIOS 2.1 06/02/2021 [ 3479.409263] Call Trace: [ 3479.411743] <TASK> [ 3479.413875] dump_stack_lvl+0x45/0x59 [ 3479.417582] print_address_description.constprop.0+0x1f/0x120 [ 3479.423389] ? _scsih_expander_node_remove+0x710/0x750 [mpt3sas] [ 3479.429469] kasan_report.cold+0x83/0xdf [ 3479.433438] ? _scsih_expander_node_remove+0x710/0x750 [mpt3sas] [ 3479.439514] _scsih_expander_node_remove+0x710/0x750 [mpt3sas] [ 3479.445411] ? _raw_spin_unlock_irqrestore+0x2d/0x40 [ 3479.452032] scsih_remove+0x525/0xc90 [mpt3sas] [ 3479.458212] ? mpt3sas_expander_remove+0x1d0/0x1d0 [mpt3sas] [ 3479.465529] ? down_write+0xde/0x150 [ 3479.470746] ? up_write+0x14d/0x460 [ 3479.475840] ? kernfs_find_ns+0x137/0x310 [ 3479.481438] pci_device_remove+0x65/0x110 [ 3479.487013] __device_release_driver+0x316/0x680 [ 3479.493180] driver_detach+0x1ec/0x2d0 [ 3479.498499] bus_remove_driver+0xe7/0x2d0 [ 3479.504081] pci_unregister_driver+0x26/0x250 [ 3479.510033] _mpt3sas_exit+0x2b/0x6cf [mpt3sas] [ 3479.516144] __x64_sys_delete_module+0x2fd/0x510 [ 3479.522315] ? free_module+0xaa0/0xaa0 [ 3479.527593] ? __cond_resched+0x1c/0x90 [ 3479.532951] ? lockdep_hardirqs_on_prepare+0x273/0x3e0 [ 3479.539607] ? syscall_enter_from_user_mode+0x21/0x70 [ 3479.546161] ? trace_hardirqs_on+0x1c/0x110 [ 3479.551828] do_syscall_64+0x35/0x80 [ 3479.556884] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 3479.563402] RIP: 0033:0x7f1fc482483b ... [ 3479.943087] ================================================================== Fix this by introducing the local variable port_id to store the port ID value before executing mpt3sas_transport_port_remove(). This local variable is then used in the call to ioc_info() instead of dereferencing the freed port structure. CVE-2022-49082 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49082.html CVE-2022-49082 https://bugzilla.suse.com/1237740 SUSE Bug 1237740 In the Linux kernel, the following vulnerability has been resolved: iommu/omap: Fix regression in probe for NULL pointer dereference Commit 3f6634d997db ("iommu: Use right way to retrieve iommu_ops") started triggering a NULL pointer dereference for some omap variants: __iommu_probe_device from probe_iommu_group+0x2c/0x38 probe_iommu_group from bus_for_each_dev+0x74/0xbc bus_for_each_dev from bus_iommu_probe+0x34/0x2e8 bus_iommu_probe from bus_set_iommu+0x80/0xc8 bus_set_iommu from omap_iommu_init+0x88/0xcc omap_iommu_init from do_one_initcall+0x44/0x24 This is caused by omap iommu probe returning 0 instead of ERR_PTR(-ENODEV) as noted by Jason Gunthorpe <jgg@ziepe.ca>. Looks like the regression already happened with an earlier commit 6785eb9105e3 ("iommu/omap: Convert to probe/release_device() call-backs") that changed the function return type and missed converting one place. CVE-2022-49083 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49083.html CVE-2022-49083 https://bugzilla.suse.com/1237723 SUSE Bug 1237723 In the Linux kernel, the following vulnerability has been resolved: drbd: Fix five use after free bugs in get_initial_state In get_initial_state, it calls notify_initial_state_done(skb,..) if cb->args[5]==1. If genlmsg_put() failed in notify_initial_state_done(), the skb will be freed by nlmsg_free(skb). Then get_initial_state will goto out and the freed skb will be used by return value skb->len, which is a uaf bug. What's worse, the same problem goes even further: skb can also be freed in the notify_*_state_change -> notify_*_state calls below. Thus 4 additional uaf bugs happened. My patch lets the problem callee functions: notify_initial_state_done and notify_*_state_change return an error code if errors happen. So that the error codes could be propagated and the uaf bugs can be avoid. v2 reports a compilation warning. This v3 fixed this warning and built successfully in my local environment with no additional warnings. v2: https://lore.kernel.org/patchwork/patch/1435218/ CVE-2022-49085 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49085.html CVE-2022-49085 https://bugzilla.suse.com/1238036 SUSE Bug 1238036 In the Linux kernel, the following vulnerability has been resolved: drm/imx: Fix memory leak in imx_pd_connector_get_modes Avoid leaking the display mode variable if of_get_drm_display_mode fails. Addresses-Coverity-ID: 1443943 ("Resource leak") CVE-2022-49091 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49091.html CVE-2022-49091 https://bugzilla.suse.com/1237726 SUSE Bug 1237726 In the Linux kernel, the following vulnerability has been resolved: scsi: zorro7xx: Fix a resource leak in zorro7xx_remove_one() The error handling path of the probe releases a resource that is not freed in the remove function. In some cases, a ioremap() must be undone. Add the missing iounmap() call in the remove function. CVE-2022-49095 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49095.html CVE-2022-49095 https://bugzilla.suse.com/1237752 SUSE Bug 1237752 In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Fix potential crash on module unload The vmbus driver relies on the panic notifier infrastructure to perform some operations when a panic event is detected. Since vmbus can be built as module, it is required that the driver handles both registering and unregistering such panic notifier callback. After commit 74347a99e73a ("x86/Hyper-V: Unload vmbus channel in hv panic callback") though, the panic notifier registration is done unconditionally in the module initialization routine whereas the unregistering procedure is conditionally guarded and executes only if HV_FEATURE_GUEST_CRASH_MSR_AVAILABLE capability is set. This patch fixes that by unconditionally unregistering the panic notifier in the module's exit routine as well. CVE-2022-49098 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49098.html CVE-2022-49098 https://bugzilla.suse.com/1238079 SUSE Bug 1238079 In the Linux kernel, the following vulnerability has been resolved: virtio_console: eliminate anonymous module_init & module_exit Eliminate anonymous module_init() and module_exit(), which can lead to confusion or ambiguity when reading System.map, crashes/oops/bugs, or an initcall_debug log. Give each of these init and exit functions unique driver-specific names to eliminate the anonymous names. Example 1: (System.map) ffffffff832fc78c t init ffffffff832fc79e t init ffffffff832fc8f8 t init Example 2: (initcall_debug log) calling init+0x0/0x12 @ 1 initcall init+0x0/0x12 returned 0 after 15 usecs calling init+0x0/0x60 @ 1 initcall init+0x0/0x60 returned 0 after 2 usecs calling init+0x0/0x9a @ 1 initcall init+0x0/0x9a returned 0 after 74 usecs CVE-2022-49100 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49100.html CVE-2022-49100 https://bugzilla.suse.com/1237735 SUSE Bug 1237735 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49111 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49111.html CVE-2022-49111 https://bugzilla.suse.com/1237984 SUSE Bug 1237984 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49114 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49114.html CVE-2022-49114 https://bugzilla.suse.com/1238146 SUSE Bug 1238146 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49122 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49122.html CVE-2022-49122 https://bugzilla.suse.com/1237983 SUSE Bug 1237983 In the Linux kernel, the following vulnerability has been resolved: drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj This issue takes place in an error path in amdgpu_cs_fence_to_handle_ioctl(). When `info->in.what` falls into default case, the function simply returns -EINVAL, forgetting to decrement the reference count of a dma_fence obj, which is bumped earlier by amdgpu_cs_get_fence(). This may result in reference count leaks. Fix it by decreasing the refcount of specific object before returning the error code. CVE-2022-49137 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49137.html CVE-2022-49137 https://bugzilla.suse.com/1238155 SUSE Bug 1238155 In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Avoid out of bounds access when parsing _CPC data If the NumEntries field in the _CPC return package is less than 2, do not attempt to access the "Revision" element of that package, because it may not be present then. BugLink: https://lore.kernel.org/lkml/20220322143534.GC32582@xsang-OptiPlex-9020/ CVE-2022-49145 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49145.html CVE-2022-49145 https://bugzilla.suse.com/1238162 SUSE Bug 1238162 In the Linux kernel, the following vulnerability has been resolved: can: mcba_usb: properly check endpoint type Syzbot reported warning in usb_submit_urb() which is caused by wrong endpoint type. We should check that in endpoint is actually present to prevent this warning. Found pipes are now saved to struct mcba_priv and code uses them directly instead of making pipes in place. Fail log: | usb 5-1: BOGUS urb xfer, pipe 3 != type 1 | WARNING: CPU: 1 PID: 49 at drivers/usb/core/urb.c:502 usb_submit_urb+0xed2/0x18a0 drivers/usb/core/urb.c:502 | Modules linked in: | CPU: 1 PID: 49 Comm: kworker/1:2 Not tainted 5.17.0-rc6-syzkaller-00184-g38f80f42147f #0 | Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 | Workqueue: usb_hub_wq hub_event | RIP: 0010:usb_submit_urb+0xed2/0x18a0 drivers/usb/core/urb.c:502 | ... | Call Trace: | <TASK> | mcba_usb_start drivers/net/can/usb/mcba_usb.c:662 [inline] | mcba_usb_probe+0x8a3/0xc50 drivers/net/can/usb/mcba_usb.c:858 | usb_probe_interface+0x315/0x7f0 drivers/usb/core/driver.c:396 | call_driver_probe drivers/base/dd.c:517 [inline] CVE-2022-49151 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49151.html CVE-2022-49151 https://bugzilla.suse.com/1237778 SUSE Bug 1237778 In the Linux kernel, the following vulnerability has been resolved: wireguard: socket: free skb in send6 when ipv6 is disabled I got a memory leak report: unreferenced object 0xffff8881191fc040 (size 232): comm "kworker/u17:0", pid 23193, jiffies 4295238848 (age 3464.870s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff814c3ef4>] slab_post_alloc_hook+0x84/0x3b0 [<ffffffff814c8977>] kmem_cache_alloc_node+0x167/0x340 [<ffffffff832974fb>] __alloc_skb+0x1db/0x200 [<ffffffff82612b5d>] wg_socket_send_buffer_to_peer+0x3d/0xc0 [<ffffffff8260e94a>] wg_packet_send_handshake_initiation+0xfa/0x110 [<ffffffff8260ec81>] wg_packet_handshake_send_worker+0x21/0x30 [<ffffffff8119c558>] process_one_work+0x2e8/0x770 [<ffffffff8119ca2a>] worker_thread+0x4a/0x4b0 [<ffffffff811a88e0>] kthread+0x120/0x160 [<ffffffff8100242f>] ret_from_fork+0x1f/0x30 In function wg_socket_send_buffer_as_reply_to_skb() or wg_socket_send_ buffer_to_peer(), the semantics of send6() is required to free skb. But when CONFIG_IPV6 is disable, kfree_skb() is missing. This patch adds it to fix this bug. CVE-2022-49153 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49153.html CVE-2022-49153 https://bugzilla.suse.com/1238166 SUSE Bug 1238166 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Suppress a kernel complaint in qla_create_qpair() [ 12.323788] BUG: using smp_processor_id() in preemptible [00000000] code: systemd-udevd/1020 [ 12.332297] caller is qla2xxx_create_qpair+0x32a/0x5d0 [qla2xxx] [ 12.338417] CPU: 7 PID: 1020 Comm: systemd-udevd Tainted: G I --------- --- 5.14.0-29.el9.x86_64 #1 [ 12.348827] Hardware name: Dell Inc. PowerEdge R610/0F0XJ6, BIOS 6.6.0 05/22/2018 [ 12.356356] Call Trace: [ 12.358821] dump_stack_lvl+0x34/0x44 [ 12.362514] check_preemption_disabled+0xd9/0xe0 [ 12.367164] qla2xxx_create_qpair+0x32a/0x5d0 [qla2xxx] [ 12.372481] qla2x00_probe_one+0xa3a/0x1b80 [qla2xxx] [ 12.377617] ? _raw_spin_lock_irqsave+0x19/0x40 [ 12.384284] local_pci_probe+0x42/0x80 [ 12.390162] ? pci_match_device+0xd7/0x110 [ 12.396366] pci_device_probe+0xfd/0x1b0 [ 12.402372] really_probe+0x1e7/0x3e0 [ 12.408114] __driver_probe_device+0xfe/0x180 [ 12.414544] driver_probe_device+0x1e/0x90 [ 12.420685] __driver_attach+0xc0/0x1c0 [ 12.426536] ? __device_attach_driver+0xe0/0xe0 [ 12.433061] ? __device_attach_driver+0xe0/0xe0 [ 12.439538] bus_for_each_dev+0x78/0xc0 [ 12.445294] bus_add_driver+0x12b/0x1e0 [ 12.451021] driver_register+0x8f/0xe0 [ 12.456631] ? 0xffffffffc07bc000 [ 12.461773] qla2x00_module_init+0x1be/0x229 [qla2xxx] [ 12.468776] do_one_initcall+0x44/0x200 [ 12.474401] ? load_module+0xad3/0xba0 [ 12.479908] ? kmem_cache_alloc_trace+0x45/0x410 [ 12.486268] do_init_module+0x5c/0x280 [ 12.491730] __do_sys_init_module+0x12e/0x1b0 [ 12.497785] do_syscall_64+0x3b/0x90 [ 12.503029] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.509764] RIP: 0033:0x7f554f73ab2e CVE-2022-49155 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49155.html CVE-2022-49155 https://bugzilla.suse.com/1237941 SUSE Bug 1237941 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix scheduling while atomic The driver makes a call into midlayer (fc_remote_port_delete) which can put the thread to sleep. The thread that originates the call is in interrupt context. The combination of the two trigger a crash. Schedule the call in non-interrupt context where it is more safe. kernel: BUG: scheduling while atomic: swapper/7/0/0x00010000 kernel: Call Trace: kernel: <IRQ> kernel: dump_stack+0x66/0x81 kernel: __schedule_bug.cold.90+0x5/0x1d kernel: __schedule+0x7af/0x960 kernel: schedule+0x28/0x80 kernel: schedule_timeout+0x26d/0x3b0 kernel: wait_for_completion+0xb4/0x140 kernel: ? wake_up_q+0x70/0x70 kernel: __wait_rcu_gp+0x12c/0x160 kernel: ? sdev_evt_alloc+0xc0/0x180 [scsi_mod] kernel: synchronize_sched+0x6c/0x80 kernel: ? call_rcu_bh+0x20/0x20 kernel: ? __bpf_trace_rcu_invoke_callback+0x10/0x10 kernel: sdev_evt_alloc+0xfd/0x180 [scsi_mod] kernel: starget_for_each_device+0x85/0xb0 [scsi_mod] kernel: ? scsi_init_io+0x360/0x3d0 [scsi_mod] kernel: scsi_init_io+0x388/0x3d0 [scsi_mod] kernel: device_for_each_child+0x54/0x90 kernel: fc_remote_port_delete+0x70/0xe0 [scsi_transport_fc] kernel: qla2x00_schedule_rport_del+0x62/0xf0 [qla2xxx] kernel: qla2x00_mark_device_lost+0x9c/0xd0 [qla2xxx] kernel: qla24xx_handle_plogi_done_event+0x55f/0x570 [qla2xxx] kernel: qla2x00_async_login_sp_done+0xd2/0x100 [qla2xxx] kernel: qla24xx_logio_entry+0x13a/0x3c0 [qla2xxx] kernel: qla24xx_process_response_queue+0x306/0x400 [qla2xxx] kernel: qla24xx_msix_rsp_q+0x3f/0xb0 [qla2xxx] kernel: __handle_irq_event_percpu+0x40/0x180 kernel: handle_irq_event_percpu+0x30/0x80 kernel: handle_irq_event+0x36/0x60 CVE-2022-49156 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49156.html CVE-2022-49156 https://bugzilla.suse.com/1238168 SUSE Bug 1238168 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix premature hw access after PCI error After a recoverable PCI error has been detected and recovered, qla driver needs to check to see if the error condition still persist and/or wait for the OS to give the resume signal. Sep 8 22:26:03 localhost kernel: WARNING: CPU: 9 PID: 124606 at qla_tmpl.c:440 qla27xx_fwdt_entry_t266+0x55/0x60 [qla2xxx] Sep 8 22:26:03 localhost kernel: RIP: 0010:qla27xx_fwdt_entry_t266+0x55/0x60 [qla2xxx] Sep 8 22:26:03 localhost kernel: Call Trace: Sep 8 22:26:03 localhost kernel: ? qla27xx_walk_template+0xb1/0x1b0 [qla2xxx] Sep 8 22:26:03 localhost kernel: ? qla27xx_execute_fwdt_template+0x12a/0x160 [qla2xxx] Sep 8 22:26:03 localhost kernel: ? qla27xx_fwdump+0xa0/0x1c0 [qla2xxx] Sep 8 22:26:03 localhost kernel: ? qla2xxx_pci_mmio_enabled+0xfb/0x120 [qla2xxx] Sep 8 22:26:03 localhost kernel: ? report_mmio_enabled+0x44/0x80 Sep 8 22:26:03 localhost kernel: ? report_slot_reset+0x80/0x80 Sep 8 22:26:03 localhost kernel: ? pci_walk_bus+0x70/0x90 Sep 8 22:26:03 localhost kernel: ? aer_dev_correctable_show+0xc0/0xc0 Sep 8 22:26:03 localhost kernel: ? pcie_do_recovery+0x1bb/0x240 Sep 8 22:26:03 localhost kernel: ? aer_recover_work_func+0xaa/0xd0 Sep 8 22:26:03 localhost kernel: ? process_one_work+0x1a7/0x360 .. Sep 8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-8041:22: detected PCI disconnect. Sep 8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-107ff:22: qla27xx_fwdt_entry_t262: dump ram MB failed. Area 5h start 198013h end 198013h Sep 8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-107ff:22: Unable to capture FW dump Sep 8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-1015:22: cmd=0x0, waited 5221 msecs Sep 8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-680d:22: mmio enabled returning. Sep 8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-d04c:22: MBX Command timeout for cmd 0, iocontrol=ffffffff jiffies=10140f2e5 mb[0-3]=[0xffff 0xffff 0xffff 0xffff] CVE-2022-49157 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49157.html CVE-2022-49157 https://bugzilla.suse.com/1238169 SUSE Bug 1238169 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix warning message due to adisc being flushed Fix warning message due to adisc being flushed. Linux kernel triggered a warning message where a different error code type is not matching up with the expected type. Add additional translation of one error code type to another. WARNING: CPU: 2 PID: 1131623 at drivers/scsi/qla2xxx/qla_init.c:498 qla2x00_async_adisc_sp_done+0x294/0x2b0 [qla2xxx] CPU: 2 PID: 1131623 Comm: drmgr Not tainted 5.13.0-rc1-autotest #1 .. GPR28: c000000aaa9c8890 c0080000079ab678 c00000140a104800 c00000002bd19000 NIP [c00800000790857c] qla2x00_async_adisc_sp_done+0x294/0x2b0 [qla2xxx] LR [c008000007908578] qla2x00_async_adisc_sp_done+0x290/0x2b0 [qla2xxx] Call Trace: [c00000001cdc3620] [c008000007908578] qla2x00_async_adisc_sp_done+0x290/0x2b0 [qla2xxx] (unreliable) [c00000001cdc3710] [c0080000078f3080] __qla2x00_abort_all_cmds+0x1b8/0x580 [qla2xxx] [c00000001cdc3840] [c0080000078f589c] qla2x00_abort_all_cmds+0x34/0xd0 [qla2xxx] [c00000001cdc3880] [c0080000079153d8] qla2x00_abort_isp_cleanup+0x3f0/0x570 [qla2xxx] [c00000001cdc3920] [c0080000078fb7e8] qla2x00_remove_one+0x3d0/0x480 [qla2xxx] [c00000001cdc39b0] [c00000000071c274] pci_device_remove+0x64/0x120 [c00000001cdc39f0] [c0000000007fb818] device_release_driver_internal+0x168/0x2a0 [c00000001cdc3a30] [c00000000070e304] pci_stop_bus_device+0xb4/0x100 [c00000001cdc3a70] [c00000000070e4f0] pci_stop_and_remove_bus_device+0x20/0x40 [c00000001cdc3aa0] [c000000000073940] pci_hp_remove_devices+0x90/0x130 [c00000001cdc3b30] [c0080000070704d0] disable_slot+0x38/0x90 [rpaphp] [ c00000001cdc3b60] [c00000000073eb4c] power_write_file+0xcc/0x180 [c00000001cdc3be0] [c0000000007354bc] pci_slot_attr_store+0x3c/0x60 [c00000001cdc3c00] [c00000000055f820] sysfs_kf_write+0x60/0x80 [c00000001cdc3c20] [c00000000055df10] kernfs_fop_write_iter+0x1a0/0x290 [c00000001cdc3c70] [c000000000447c4c] new_sync_write+0x14c/0x1d0 [c00000001cdc3d10] [c00000000044b134] vfs_write+0x224/0x330 [c00000001cdc3d60] [c00000000044b3f4] ksys_write+0x74/0x130 [c00000001cdc3db0] [c00000000002df70] system_call_exception+0x150/0x2d0 [c00000001cdc3e10] [c00000000000d45c] system_call_common+0xec/0x278 CVE-2022-49158 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49158.html CVE-2022-49158 https://bugzilla.suse.com/1238170 SUSE Bug 1238170 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Implement ref count for SRB The timeout handler and the done function are racing. When qla2x00_async_iocb_timeout() starts to run it can be preempted by the normal response path (via the firmware?). qla24xx_async_gpsc_sp_done() releases the SRB unconditionally. When scheduling back to qla2x00_async_iocb_timeout() qla24xx_async_abort_cmd() will access an freed sp->qpair pointer: qla2xxx [0000:83:00.0]-2871:0: Async-gpsc timeout - hdl=63d portid=234500 50:06:0e:80:08:77:b6:21. qla2xxx [0000:83:00.0]-2853:0: Async done-gpsc res 0, WWPN 50:06:0e:80:08:77:b6:21 qla2xxx [0000:83:00.0]-2854:0: Async-gpsc OUT WWPN 20:45:00:27:f8:75:33:00 speeds=2c00 speed=0400. qla2xxx [0000:83:00.0]-28d8:0: qla24xx_handle_gpsc_event 50:06:0e:80:08:77:b6:21 DS 7 LS 6 rc 0 login 1|1 rscn 1|0 lid 5 BUG: unable to handle kernel NULL pointer dereference at 0000000000000004 IP: qla24xx_async_abort_cmd+0x1b/0x1c0 [qla2xxx] Obvious solution to this is to introduce a reference counter. One reference is taken for the normal code path (the 'good' case) and one for the timeout path. As we always race between the normal good case and the timeout/abort handler we need to serialize it. Also we cannot assume any order between the handlers. Since this is slow path we can use proper synchronization via locks. When we are able to cancel a timer (del_timer returns 1) we know there can't be any error handling in progress because the timeout handler hasn't expired yet, thus we can safely decrement the refcounter by one. If we are not able to cancel the timer, we know an abort handler is running. We have to make sure we call sp->done() in the abort handlers before calling kref_put(). CVE-2022-49159 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49159.html CVE-2022-49159 https://bugzilla.suse.com/1238171 SUSE Bug 1238171 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix crash during module load unload test During purex packet handling the driver was incorrectly freeing a pre-allocated structure. Fix this by skipping that entry. System crashed with the following stack during a module unload test. Call Trace: sbitmap_init_node+0x7f/0x1e0 sbitmap_queue_init_node+0x24/0x150 blk_mq_init_bitmaps+0x3d/0xa0 blk_mq_init_tags+0x68/0x90 blk_mq_alloc_map_and_rqs+0x44/0x120 blk_mq_alloc_set_map_and_rqs+0x63/0x150 blk_mq_alloc_tag_set+0x11b/0x230 scsi_add_host_with_dma.cold+0x3f/0x245 qla2x00_probe_one+0xd5a/0x1b80 [qla2xxx] Call Trace with slub_debug and debug kernel: kasan_report_invalid_free+0x50/0x80 __kasan_slab_free+0x137/0x150 slab_free_freelist_hook+0xc6/0x190 kfree+0xe8/0x2e0 qla2x00_free_device+0x3bb/0x5d0 [qla2xxx] qla2x00_remove_one+0x668/0xcf0 [qla2xxx] CVE-2022-49160 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49160.html CVE-2022-49160 https://bugzilla.suse.com/1238172 SUSE Bug 1238172 In the Linux kernel, the following vulnerability has been resolved: video: fbdev: sm712fb: Fix crash in smtcfb_write() When the sm712fb driver writes three bytes to the framebuffer, the driver will crash: BUG: unable to handle page fault for address: ffffc90001ffffff RIP: 0010:smtcfb_write+0x454/0x5b0 Call Trace: vfs_write+0x291/0xd60 ? do_sys_openat2+0x27d/0x350 ? __fget_light+0x54/0x340 ksys_write+0xce/0x190 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae Fix it by removing the open-coded endianness fixup-code. CVE-2022-49162 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49162.html CVE-2022-49162 https://bugzilla.suse.com/1238096 SUSE Bug 1238096 In the Linux kernel, the following vulnerability has been resolved: powerpc/tm: Fix more userspace r13 corruption Commit cf13435b730a ("powerpc/tm: Fix userspace r13 corruption") fixes a problem in treclaim where a SLB miss can occur on the thread_struct->ckpt_regs while SCRATCH0 is live with the saved user r13 value, clobbering it with the kernel r13 and ultimately resulting in kernel r13 being stored in ckpt_regs. There is an equivalent problem in trechkpt where the user r13 value is loaded into r13 from chkpt_regs to be recheckpointed, but a SLB miss could occur on ckpt_regs accesses after that, which will result in r13 being clobbered with a kernel value and that will get recheckpointed and then restored to user registers. The same memory page is accessed right before this critical window where a SLB miss could cause corruption, so hitting the bug requires the SLB entry be removed within a small window of instructions, which is possible if a SLB related MCE hits there. PAPR also permits the hypervisor to discard this SLB entry (because slb_shadow->persistent is only set to SLB_NUM_BOLTED) although it's not known whether any implementations would do this (KVM does not). So this is an extremely unlikely bug, only found by inspection. Fix this by also storing user r13 in a temporary location on the kernel stack and don't change the r13 register from kernel r13 until the RI=0 critical section that does not fault. The SCRATCH0 change is not strictly part of the fix, it's only used in the RI=0 section so it does not have the same problem as the previous SCRATCH0 bug. CVE-2022-49164 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49164.html CVE-2022-49164 https://bugzilla.suse.com/1238108 SUSE Bug 1238108 In the Linux kernel, the following vulnerability has been resolved: PM: core: keep irq flags in device_pm_check_callbacks() The function device_pm_check_callbacks() can be called under the spin lock (in the reported case it happens from genpd_add_device() -> dev_pm_domain_set(), when the genpd uses spinlocks rather than mutexes. However this function uncoditionally uses spin_lock_irq() / spin_unlock_irq(), thus not preserving the CPU flags. Use the irqsave/irqrestore instead. The backtrace for the reference: [ 2.752010] ------------[ cut here ]------------ [ 2.756769] raw_local_irq_restore() called with IRQs enabled [ 2.762596] WARNING: CPU: 4 PID: 1 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x34/0x50 [ 2.772338] Modules linked in: [ 2.775487] CPU: 4 PID: 1 Comm: swapper/0 Tainted: G S 5.17.0-rc6-00384-ge330d0d82eff-dirty #684 [ 2.781384] Freeing initrd memory: 46024K [ 2.785839] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2.785841] pc : warn_bogus_irq_restore+0x34/0x50 [ 2.785844] lr : warn_bogus_irq_restore+0x34/0x50 [ 2.785846] sp : ffff80000805b7d0 [ 2.785847] x29: ffff80000805b7d0 x28: 0000000000000000 x27: 0000000000000002 [ 2.785850] x26: ffffd40e80930b18 x25: ffff7ee2329192b8 x24: ffff7edfc9f60800 [ 2.785853] x23: ffffd40e80930b18 x22: ffffd40e80930d30 x21: ffff7edfc0dffa00 [ 2.785856] x20: ffff7edfc09e3768 x19: 0000000000000000 x18: ffffffffffffffff [ 2.845775] x17: 6572206f74206465 x16: 6c696166203a3030 x15: ffff80008805b4f7 [ 2.853108] x14: 0000000000000000 x13: ffffd40e809550b0 x12: 00000000000003d8 [ 2.860441] x11: 0000000000000148 x10: ffffd40e809550b0 x9 : ffffd40e809550b0 [ 2.867774] x8 : 00000000ffffefff x7 : ffffd40e809ad0b0 x6 : ffffd40e809ad0b0 [ 2.875107] x5 : 000000000000bff4 x4 : 0000000000000000 x3 : 0000000000000000 [ 2.882440] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff7edfc03a8000 [ 2.889774] Call trace: [ 2.892290] warn_bogus_irq_restore+0x34/0x50 [ 2.896770] _raw_spin_unlock_irqrestore+0x94/0xa0 [ 2.901690] genpd_unlock_spin+0x20/0x30 [ 2.905724] genpd_add_device+0x100/0x2d0 [ 2.909850] __genpd_dev_pm_attach+0xa8/0x23c [ 2.914329] genpd_dev_pm_attach_by_id+0xc4/0x190 [ 2.919167] genpd_dev_pm_attach_by_name+0x3c/0xd0 [ 2.924086] dev_pm_domain_attach_by_name+0x24/0x30 [ 2.929102] psci_dt_attach_cpu+0x24/0x90 [ 2.933230] psci_cpuidle_probe+0x2d4/0x46c [ 2.937534] platform_probe+0x68/0xe0 [ 2.941304] really_probe.part.0+0x9c/0x2fc [ 2.945605] __driver_probe_device+0x98/0x144 [ 2.950085] driver_probe_device+0x44/0x15c [ 2.954385] __device_attach_driver+0xb8/0x120 [ 2.958950] bus_for_each_drv+0x78/0xd0 [ 2.962896] __device_attach+0xd8/0x180 [ 2.966843] device_initial_probe+0x14/0x20 [ 2.971144] bus_probe_device+0x9c/0xa4 [ 2.975092] device_add+0x380/0x88c [ 2.978679] platform_device_add+0x114/0x234 [ 2.983067] platform_device_register_full+0x100/0x190 [ 2.988344] psci_idle_init+0x6c/0xb0 [ 2.992113] do_one_initcall+0x74/0x3a0 [ 2.996060] kernel_init_freeable+0x2fc/0x384 [ 3.000543] kernel_init+0x28/0x130 [ 3.004132] ret_from_fork+0x10/0x20 [ 3.007817] irq event stamp: 319826 [ 3.011404] hardirqs last enabled at (319825): [<ffffd40e7eda0268>] __up_console_sem+0x78/0x84 [ 3.020332] hardirqs last disabled at (319826): [<ffffd40e7fd6d9d8>] el1_dbg+0x24/0x8c [ 3.028458] softirqs last enabled at (318312): [<ffffd40e7ec90410>] _stext+0x410/0x588 [ 3.036678] softirqs last disabled at (318299): [<ffffd40e7ed1bf68>] __irq_exit_rcu+0x158/0x174 [ 3.045607] ---[ end trace 0000000000000000 ]--- CVE-2022-49175 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49175.html CVE-2022-49175 https://bugzilla.suse.com/1238099 SUSE Bug 1238099 In the Linux kernel, the following vulnerability has been resolved: pinctrl: nomadik: Add missing of_node_put() in nmk_pinctrl_probe This node pointer is returned by of_parse_phandle() with refcount incremented in this function. Calling of_node_put() to avoid the refcount leak. CVE-2022-49185 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49185.html CVE-2022-49185 https://bugzilla.suse.com/1238111 SUSE Bug 1238111 In the Linux kernel, the following vulnerability has been resolved: clk: qcom: clk-rcg2: Update logic to calculate D value for RCG The display pixel clock has a requirement on certain newer platforms to support M/N as (2/3) and the final D value calculated results in underflow errors. As the current implementation does not check for D value is within the accepted range for a given M & N value. Update the logic to calculate the final D value based on the range. CVE-2022-49189 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49189.html CVE-2022-49189 https://bugzilla.suse.com/1238150 SUSE Bug 1238150 In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries: Fix use after free in remove_phb_dynamic() In remove_phb_dynamic() we use &phb->io_resource, after we've called device_unregister(&host_bridge->dev). But the unregister may have freed phb, because pcibios_free_controller_deferred() is the release function for the host_bridge. If there are no outstanding references when we call device_unregister() then phb will be freed out from under us. This has gone mainly unnoticed, but with slub_debug and page_poison enabled it can lead to a crash: PID: 7574 TASK: c0000000d492cb80 CPU: 13 COMMAND: "drmgr" #0 [c0000000e4f075a0] crash_kexec at c00000000027d7dc #1 [c0000000e4f075d0] oops_end at c000000000029608 #2 [c0000000e4f07650] __bad_page_fault at c0000000000904b4 #3 [c0000000e4f076c0] do_bad_slb_fault at c00000000009a5a8 #4 [c0000000e4f076f0] data_access_slb_common_virt at c000000000008b30 Data SLB Access [380] exception frame: R0: c000000000167250 R1: c0000000e4f07a00 R2: c000000002a46100 R3: c000000002b39ce8 R4: 00000000000000c0 R5: 00000000000000a9 R6: 3894674d000000c0 R7: 0000000000000000 R8: 00000000000000ff R9: 0000000000000100 R10: 6b6b6b6b6b6b6b6b R11: 0000000000008000 R12: c00000000023da80 R13: c0000009ffd38b00 R14: 0000000000000000 R15: 000000011c87f0f0 R16: 0000000000000006 R17: 0000000000000003 R18: 0000000000000002 R19: 0000000000000004 R20: 0000000000000005 R21: 000000011c87ede8 R22: 000000011c87c5a8 R23: 000000011c87d3a0 R24: 0000000000000000 R25: 0000000000000001 R26: c0000000e4f07cc8 R27: c00000004d1cc400 R28: c0080000031d00e8 R29: c00000004d23d800 R30: c00000004d1d2400 R31: c00000004d1d2540 NIP: c000000000167258 MSR: 8000000000009033 OR3: c000000000e9f474 CTR: 0000000000000000 LR: c000000000167250 XER: 0000000020040003 CCR: 0000000024088420 MQ: 0000000000000000 DAR: 6b6b6b6b6b6b6ba3 DSISR: c0000000e4f07920 Syscall Result: fffffffffffffff2 [NIP : release_resource+56] [LR : release_resource+48] #5 [c0000000e4f07a00] release_resource at c000000000167258 (unreliable) #6 [c0000000e4f07a30] remove_phb_dynamic at c000000000105648 #7 [c0000000e4f07ab0] dlpar_remove_slot at c0080000031a09e8 [rpadlpar_io] #8 [c0000000e4f07b50] remove_slot_store at c0080000031a0b9c [rpadlpar_io] #9 [c0000000e4f07be0] kobj_attr_store at c000000000817d8c #10 [c0000000e4f07c00] sysfs_kf_write at c00000000063e504 #11 [c0000000e4f07c20] kernfs_fop_write_iter at c00000000063d868 #12 [c0000000e4f07c70] new_sync_write at c00000000054339c #13 [c0000000e4f07d10] vfs_write at c000000000546624 #14 [c0000000e4f07d60] ksys_write at c0000000005469f4 #15 [c0000000e4f07db0] system_call_exception at c000000000030840 #16 [c0000000e4f07e10] system_call_vectored_common at c00000000000c168 To avoid it, we can take a reference to the host_bridge->dev until we're done using phb. Then when we drop the reference the phb will be freed. CVE-2022-49196 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49196.html CVE-2022-49196 https://bugzilla.suse.com/1238274 SUSE Bug 1238274 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtksdio: Fix kernel oops in btmtksdio_interrupt Fix the following kernel oops in btmtksdio_interrrupt [ 14.339134] btmtksdio_interrupt+0x28/0x54 [ 14.339139] process_sdio_pending_irqs+0x68/0x1a0 [ 14.339144] sdio_irq_work+0x40/0x70 [ 14.339154] process_one_work+0x184/0x39c [ 14.339160] worker_thread+0x228/0x3e8 [ 14.339168] kthread+0x148/0x3ac [ 14.339176] ret_from_fork+0x10/0x30 That happened because hdev->power_on is already called before sdio_set_drvdata which btmtksdio_interrupt handler relies on is not properly set up. The details are shown as the below: hci_register_dev would run queue_work(hdev->req_workqueue, &hdev->power_on) as WQ_HIGHPRI workqueue_struct to complete the power-on sequeunce and thus hci_power_on may run before sdio_set_drvdata is done in btmtksdio_probe. The hci_dev_do_open in hci_power_on would initialize the device and enable the interrupt and thus it is possible that btmtksdio_interrupt is being called right before sdio_set_drvdata is filled out. When btmtksdio_interrupt is being called and sdio_set_drvdata is not filled , the kernel oops is going to happen because btmtksdio_interrupt access an uninitialized pointer. CVE-2022-49200 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49200.html CVE-2022-49200 https://bugzilla.suse.com/1237958 SUSE Bug 1237958 In the Linux kernel, the following vulnerability has been resolved: ibmvnic: fix race between xmit and reset There is a race between reset and the transmit paths that can lead to ibmvnic_xmit() accessing an scrq after it has been freed in the reset path. It can result in a crash like: Kernel attempted to read user page (0) - exploit attempt? (uid: 0) BUG: Kernel NULL pointer dereference on read at 0x00000000 Faulting instruction address: 0xc0080000016189f8 Oops: Kernel access of bad area, sig: 11 [#1] ... NIP [c0080000016189f8] ibmvnic_xmit+0x60/0xb60 [ibmvnic] LR [c000000000c0046c] dev_hard_start_xmit+0x11c/0x280 Call Trace: [c008000001618f08] ibmvnic_xmit+0x570/0xb60 [ibmvnic] (unreliable) [c000000000c0046c] dev_hard_start_xmit+0x11c/0x280 [c000000000c9cfcc] sch_direct_xmit+0xec/0x330 [c000000000bfe640] __dev_xmit_skb+0x3a0/0x9d0 [c000000000c00ad4] __dev_queue_xmit+0x394/0x730 [c008000002db813c] __bond_start_xmit+0x254/0x450 [bonding] [c008000002db8378] bond_start_xmit+0x40/0xc0 [bonding] [c000000000c0046c] dev_hard_start_xmit+0x11c/0x280 [c000000000c00ca4] __dev_queue_xmit+0x564/0x730 [c000000000cf97e0] neigh_hh_output+0xd0/0x180 [c000000000cfa69c] ip_finish_output2+0x31c/0x5c0 [c000000000cfd244] __ip_queue_xmit+0x194/0x4f0 [c000000000d2a3c4] __tcp_transmit_skb+0x434/0x9b0 [c000000000d2d1e0] __tcp_retransmit_skb+0x1d0/0x6a0 [c000000000d2d984] tcp_retransmit_skb+0x34/0x130 [c000000000d310e8] tcp_retransmit_timer+0x388/0x6d0 [c000000000d315ec] tcp_write_timer_handler+0x1bc/0x330 [c000000000d317bc] tcp_write_timer+0x5c/0x200 [c000000000243270] call_timer_fn+0x50/0x1c0 [c000000000243704] __run_timers.part.0+0x324/0x460 [c000000000243894] run_timer_softirq+0x54/0xa0 [c000000000ea713c] __do_softirq+0x15c/0x3e0 [c000000000166258] __irq_exit_rcu+0x158/0x190 [c000000000166420] irq_exit+0x20/0x40 [c00000000002853c] timer_interrupt+0x14c/0x2b0 [c000000000009a00] decrementer_common_virt+0x210/0x220 --- interrupt: 900 at plpar_hcall_norets_notrace+0x18/0x2c The immediate cause of the crash is the access of tx_scrq in the following snippet during a reset, where the tx_scrq can be either NULL or an address that will soon be invalid: ibmvnic_xmit() { ... tx_scrq = adapter->tx_scrq[queue_num]; txq = netdev_get_tx_queue(netdev, queue_num); ind_bufp = &tx_scrq->ind_buf; if (test_bit(0, &adapter->resetting)) { ... } But beyond that, the call to ibmvnic_xmit() itself is not safe during a reset and the reset path attempts to avoid this by stopping the queue in ibmvnic_cleanup(). However just after the queue was stopped, an in-flight ibmvnic_complete_tx() could have restarted the queue even as the reset is progressing. Since the queue was restarted we could get a call to ibmvnic_xmit() which can then access the bad tx_scrq (or other fields). We cannot however simply have ibmvnic_complete_tx() check the ->resetting bit and skip starting the queue. This can race at the "back-end" of a good reset which just restarted the queue but has not cleared the ->resetting bit yet. If we skip restarting the queue due to ->resetting being true, the queue would remain stopped indefinitely potentially leading to transmit timeouts. IOW ->resetting is too broad for this purpose. Instead use a new flag that indicates whether or not the queues are active. Only the open/ reset paths control when the queues are active. ibmvnic_complete_tx() and others wake up the queue only if the queue is marked active. So we will have: A. reset/open thread in ibmvnic_cleanup() and __ibmvnic_open() ->resetting = true ->tx_queues_active = false disable tx queues ... ->tx_queues_active = true start tx queues B. Tx interrupt in ibmvnic_complete_tx(): if (->tx_queues_active) netif_wake_subqueue(); To ensure that ->tx_queues_active and state of the queues are consistent, we need a lock which: - must also be taken in the interrupt path (ibmvnic_complete_tx()) - shared across the multiple ---truncated--- CVE-2022-49201 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49201.html CVE-2022-49201 https://bugzilla.suse.com/1238256 SUSE Bug 1238256 In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix memory leak in error flow for subscribe event routine In case the second xa_insert() fails, the obj_event is not released. Fix the error unwind flow to free that memory to avoid a memory leak. CVE-2022-49206 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49206.html CVE-2022-49206 https://bugzilla.suse.com/1238343 SUSE Bug 1238343 In the Linux kernel, the following vulnerability has been resolved: mtd: rawnand: atmel: fix refcount issue in atmel_nand_controller_init The reference counting issue happens in several error handling paths on a refcounted object "nc->dmac". In these paths, the function simply returns the error code, forgetting to balance the reference count of "nc->dmac", increased earlier by dma_request_channel(), which may cause refcount leaks. Fix it by decrementing the refcount of specific object in those error paths. CVE-2022-49212 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49212.html CVE-2022-49212 https://bugzilla.suse.com/1238331 SUSE Bug 1238331 In the Linux kernel, the following vulnerability has been resolved: ath10k: Fix error handling in ath10k_setup_msa_resources The device_node pointer is returned by of_parse_phandle() with refcount incremented. We should use of_node_put() on it when done. This function only calls of_node_put() in the regular path. And it will cause refcount leak in error path. CVE-2022-49213 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49213.html CVE-2022-49213 https://bugzilla.suse.com/1238327 SUSE Bug 1238327 In the Linux kernel, the following vulnerability has been resolved: drm/tegra: Fix reference leak in tegra_dsi_ganged_probe The reference taken by 'of_find_device_by_node()' must be released when not needed anymore. Add put_device() call to fix this. CVE-2022-49216 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49216.html CVE-2022-49216 https://bugzilla.suse.com/1238338 SUSE Bug 1238338 In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix abort all task initialization In pm80xx_send_abort_all(), the n_elem field of the ccb used is not initialized to 0. This missing initialization sometimes lead to the task completion path seeing the ccb with a non-zero n_elem resulting in the execution of invalid dma_unmap_sg() calls in pm8001_ccb_task_free(), causing a crash such as: [ 197.676341] RIP: 0010:iommu_dma_unmap_sg+0x6d/0x280 [ 197.700204] RSP: 0018:ffff889bbcf89c88 EFLAGS: 00010012 [ 197.705485] RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff83d0bda0 [ 197.712687] RDX: 0000000000000002 RSI: 0000000000000000 RDI: ffff88810dffc0d0 [ 197.719887] RBP: 0000000000000000 R08: 0000000000000000 R09: ffff8881c790098b [ 197.727089] R10: ffffed1038f20131 R11: 0000000000000001 R12: 0000000000000000 [ 197.734296] R13: ffff88810dffc0d0 R14: 0000000000000010 R15: 0000000000000000 [ 197.741493] FS: 0000000000000000(0000) GS:ffff889bbcf80000(0000) knlGS:0000000000000000 [ 197.749659] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 197.755459] CR2: 00007f16c1b42734 CR3: 0000000004814000 CR4: 0000000000350ee0 [ 197.762656] Call Trace: [ 197.765127] <IRQ> [ 197.767162] pm8001_ccb_task_free+0x5f1/0x820 [pm80xx] [ 197.772364] ? do_raw_spin_unlock+0x54/0x220 [ 197.776680] pm8001_mpi_task_abort_resp+0x2ce/0x4f0 [pm80xx] [ 197.782406] process_oq+0xe85/0x7890 [pm80xx] [ 197.786817] ? lock_acquire+0x194/0x490 [ 197.790697] ? handle_irq_event+0x10e/0x1b0 [ 197.794920] ? mpi_sata_completion+0x2d70/0x2d70 [pm80xx] [ 197.800378] ? __wake_up_bit+0x100/0x100 [ 197.804340] ? lock_is_held_type+0x98/0x110 [ 197.808565] pm80xx_chip_isr+0x94/0x130 [pm80xx] [ 197.813243] tasklet_action_common.constprop.0+0x24b/0x2f0 [ 197.818785] __do_softirq+0x1b5/0x82d [ 197.822485] ? do_raw_spin_unlock+0x54/0x220 [ 197.826799] __irq_exit_rcu+0x17e/0x1e0 [ 197.830678] irq_exit_rcu+0xa/0x20 [ 197.834114] common_interrupt+0x78/0x90 [ 197.840051] </IRQ> [ 197.844236] <TASK> [ 197.848397] asm_common_interrupt+0x1e/0x40 Avoid this issue by always initializing the ccb n_elem field to 0 in pm8001_send_abort_all(), pm8001_send_read_log() and pm80xx_send_abort_all(). CVE-2022-49217 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49217.html CVE-2022-49217 https://bugzilla.suse.com/1238313 SUSE Bug 1238313 In the Linux kernel, the following vulnerability has been resolved: power: supply: ab8500: Fix memory leak in ab8500_fg_sysfs_init kobject_init_and_add() takes reference even when it fails. According to the doc of kobject_init_and_add(): If this function returns an error, kobject_put() must be called to properly clean up the memory associated with the object. Fix memory leak by calling kobject_put(). CVE-2022-49224 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49224.html CVE-2022-49224 https://bugzilla.suse.com/1237998 SUSE Bug 1237998 In the Linux kernel, the following vulnerability has been resolved: net: asix: add proper error handling of usb read errors Syzbot once again hit uninit value in asix driver. The problem still the same -- asix_read_cmd() reads less bytes, than was requested by caller. Since all read requests are performed via asix_read_cmd() let's catch usb related error there and add __must_check notation to be sure all callers actually check return value. So, this patch adds sanity check inside asix_read_cmd(), that simply checks if bytes read are not less, than was requested and adds missing error handling of asix_read_cmd() all across the driver code. CVE-2022-49226 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49226.html CVE-2022-49226 https://bugzilla.suse.com/1238336 SUSE Bug 1238336 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix a NULL pointer dereference in amdgpu_dm_connector_add_common_modes() In amdgpu_dm_connector_add_common_modes(), amdgpu_dm_create_common_mode() is assigned to mode and is passed to drm_mode_probed_add() directly after that. drm_mode_probed_add() passes &mode->head to list_add_tail(), and there is a dereference of it in list_add_tail() without recoveries, which could lead to NULL pointer dereference on failure of amdgpu_dm_create_common_mode(). Fix this by adding a NULL check of mode. This bug was found by a static analyzer. Builds with 'make allyesconfig' show no new warnings, and our static analyzer no longer warns about this code. CVE-2022-49232 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49232.html CVE-2022-49232 https://bugzilla.suse.com/1238139 SUSE Bug 1238139 In the Linux kernel, the following vulnerability has been resolved: ath9k_htc: fix uninit value bugs Syzbot reported 2 KMSAN bugs in ath9k. All of them are caused by missing field initialization. In htc_connect_service() svc_meta_len and pad are not initialized. Based on code it looks like in current skb there is no service data, so simply initialize svc_meta_len to 0. htc_issue_send() does not initialize htc_frame_hdr::control array. Based on firmware code, it will initialize it by itself, so simply zero whole array to make KMSAN happy Fail logs: BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x6c1/0x2aa0 drivers/usb/core/urb.c:430 usb_submit_urb+0x6c1/0x2aa0 drivers/usb/core/urb.c:430 hif_usb_send_regout drivers/net/wireless/ath/ath9k/hif_usb.c:127 [inline] hif_usb_send+0x5f0/0x16f0 drivers/net/wireless/ath/ath9k/hif_usb.c:479 htc_issue_send drivers/net/wireless/ath/ath9k/htc_hst.c:34 [inline] htc_connect_service+0x143e/0x1960 drivers/net/wireless/ath/ath9k/htc_hst.c:275 ... Uninit was created at: slab_post_alloc_hook mm/slab.h:524 [inline] slab_alloc_node mm/slub.c:3251 [inline] __kmalloc_node_track_caller+0xe0c/0x1510 mm/slub.c:4974 kmalloc_reserve net/core/skbuff.c:354 [inline] __alloc_skb+0x545/0xf90 net/core/skbuff.c:426 alloc_skb include/linux/skbuff.h:1126 [inline] htc_connect_service+0x1029/0x1960 drivers/net/wireless/ath/ath9k/htc_hst.c:258 ... Bytes 4-7 of 18 are uninitialized Memory access of size 18 starts at ffff888027377e00 BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x6c1/0x2aa0 drivers/usb/core/urb.c:430 usb_submit_urb+0x6c1/0x2aa0 drivers/usb/core/urb.c:430 hif_usb_send_regout drivers/net/wireless/ath/ath9k/hif_usb.c:127 [inline] hif_usb_send+0x5f0/0x16f0 drivers/net/wireless/ath/ath9k/hif_usb.c:479 htc_issue_send drivers/net/wireless/ath/ath9k/htc_hst.c:34 [inline] htc_connect_service+0x143e/0x1960 drivers/net/wireless/ath/ath9k/htc_hst.c:275 ... Uninit was created at: slab_post_alloc_hook mm/slab.h:524 [inline] slab_alloc_node mm/slub.c:3251 [inline] __kmalloc_node_track_caller+0xe0c/0x1510 mm/slub.c:4974 kmalloc_reserve net/core/skbuff.c:354 [inline] __alloc_skb+0x545/0xf90 net/core/skbuff.c:426 alloc_skb include/linux/skbuff.h:1126 [inline] htc_connect_service+0x1029/0x1960 drivers/net/wireless/ath/ath9k/htc_hst.c:258 ... Bytes 16-17 of 18 are uninitialized Memory access of size 18 starts at ffff888027377e00 CVE-2022-49235 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49235.html CVE-2022-49235 https://bugzilla.suse.com/1238333 SUSE Bug 1238333 In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd934x: Add missing of_node_put() in wcd934x_codec_parse_data The device_node pointer is returned by of_parse_phandle() with refcount incremented. We should use of_node_put() on it when done. This is similar to commit 64b92de9603f ("ASoC: wcd9335: fix a leaked reference by adding missing of_node_put") CVE-2022-49239 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49239.html CVE-2022-49239 https://bugzilla.suse.com/1238334 SUSE Bug 1238334 In the Linux kernel, the following vulnerability has been resolved: ASoC: mxs: Fix error handling in mxs_sgtl5000_probe This function only calls of_node_put() in the regular path. And it will cause refcount leak in error paths. For example, when codec_np is NULL, saif_np[0] and saif_np[1] are not NULL, it will cause leaks. of_node_put() will check if the node pointer is NULL, so we can call it directly to release the refcount of regular pointers. CVE-2022-49242 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49242.html CVE-2022-49242 https://bugzilla.suse.com/1238126 SUSE Bug 1238126 In the Linux kernel, the following vulnerability has been resolved: ASoC: atmel: Add missing of_node_put() in at91sam9g20ek_audio_probe This node pointer is returned by of_parse_phandle() with refcount incremented in this function. Calling of_node_put() to avoid the refcount leak. CVE-2022-49243 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49243.html CVE-2022-49243 https://bugzilla.suse.com/1238337 SUSE Bug 1238337 In the Linux kernel, the following vulnerability has been resolved: media: stk1160: If start stream fails, return buffers with VB2_BUF_STATE_QUEUED If the callback 'start_streaming' fails, then all queued buffers in the driver should be returned with state 'VB2_BUF_STATE_QUEUED'. Currently, they are returned with 'VB2_BUF_STATE_ERROR' which is wrong. Fix this. This also fixes the warning: [ 65.583633] WARNING: CPU: 5 PID: 593 at drivers/media/common/videobuf2/videobuf2-core.c:1612 vb2_start_streaming+0xd4/0x160 [videobuf2_common] [ 65.585027] Modules linked in: snd_usb_audio snd_hwdep snd_usbmidi_lib snd_rawmidi snd_soc_hdmi_codec dw_hdmi_i2s_audio saa7115 stk1160 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc crct10dif_ce panfrost snd_soc_simple_card snd_soc_audio_graph_card snd_soc_spdif_tx snd_soc_simple_card_utils gpu_sched phy_rockchip_pcie snd_soc_rockchip_i2s rockchipdrm analogix_dp dw_mipi_dsi dw_hdmi cec drm_kms_helper drm rtc_rk808 rockchip_saradc industrialio_triggered_buffer kfifo_buf rockchip_thermal pcie_rockchip_host ip_tables x_tables ipv6 [ 65.589383] CPU: 5 PID: 593 Comm: v4l2src0:src Tainted: G W 5.16.0-rc4-62408-g32447129cb30-dirty #14 [ 65.590293] Hardware name: Radxa ROCK Pi 4B (DT) [ 65.590696] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 65.591304] pc : vb2_start_streaming+0xd4/0x160 [videobuf2_common] [ 65.591850] lr : vb2_start_streaming+0x6c/0x160 [videobuf2_common] [ 65.592395] sp : ffff800012bc3ad0 [ 65.592685] x29: ffff800012bc3ad0 x28: 0000000000000000 x27: ffff800012bc3cd8 [ 65.593312] x26: 0000000000000000 x25: ffff00000d8a7800 x24: 0000000040045612 [ 65.593938] x23: ffff800011323000 x22: ffff800012bc3cd8 x21: ffff00000908a8b0 [ 65.594562] x20: ffff00000908a8c8 x19: 00000000fffffff4 x18: ffffffffffffffff [ 65.595188] x17: 000000040044ffff x16: 00400034b5503510 x15: ffff800011323f78 [ 65.595813] x14: ffff000013163886 x13: ffff000013163885 x12: 00000000000002ce [ 65.596439] x11: 0000000000000028 x10: 0000000000000001 x9 : 0000000000000228 [ 65.597064] x8 : 0101010101010101 x7 : 7f7f7f7f7f7f7f7f x6 : fefefeff726c5e78 [ 65.597690] x5 : ffff800012bc3990 x4 : 0000000000000000 x3 : ffff000009a34880 [ 65.598315] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000007cd99f0 [ 65.598940] Call trace: [ 65.599155] vb2_start_streaming+0xd4/0x160 [videobuf2_common] [ 65.599672] vb2_core_streamon+0x17c/0x1a8 [videobuf2_common] [ 65.600179] vb2_streamon+0x54/0x88 [videobuf2_v4l2] [ 65.600619] vb2_ioctl_streamon+0x54/0x60 [videobuf2_v4l2] [ 65.601103] v4l_streamon+0x3c/0x50 [videodev] [ 65.601521] __video_do_ioctl+0x1a4/0x428 [videodev] [ 65.601977] video_usercopy+0x320/0x828 [videodev] [ 65.602419] video_ioctl2+0x3c/0x58 [videodev] [ 65.602830] v4l2_ioctl+0x60/0x90 [videodev] [ 65.603227] __arm64_sys_ioctl+0xa8/0xe0 [ 65.603576] invoke_syscall+0x54/0x118 [ 65.603911] el0_svc_common.constprop.3+0x84/0x100 [ 65.604332] do_el0_svc+0x34/0xa0 [ 65.604625] el0_svc+0x1c/0x50 [ 65.604897] el0t_64_sync_handler+0x88/0xb0 [ 65.605264] el0t_64_sync+0x16c/0x170 [ 65.605587] ---[ end trace 578e0ba07742170d ]--- CVE-2022-49247 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49247.html CVE-2022-49247 https://bugzilla.suse.com/1237783 SUSE Bug 1237783 In the Linux kernel, the following vulnerability has been resolved: ALSA: firewire-lib: fix uninitialized flag for AV/C deferred transaction AV/C deferred transaction was supported at a commit 00a7bb81c20f ("ALSA: firewire-lib: Add support for deferred transaction") while 'deferrable' flag can be uninitialized for non-control/notify AV/C transactions. UBSAN reports it: kernel: ================================================================================ kernel: UBSAN: invalid-load in /build/linux-aa0B4d/linux-5.15.0/sound/firewire/fcp.c:363:9 kernel: load of value 158 is not a valid value for type '_Bool' kernel: CPU: 3 PID: 182227 Comm: irq/35-firewire Tainted: P OE 5.15.0-18-generic #18-Ubuntu kernel: Hardware name: Gigabyte Technology Co., Ltd. AX370-Gaming 5/AX370-Gaming 5, BIOS F42b 08/01/2019 kernel: Call Trace: kernel: <IRQ> kernel: show_stack+0x52/0x58 kernel: dump_stack_lvl+0x4a/0x5f kernel: dump_stack+0x10/0x12 kernel: ubsan_epilogue+0x9/0x45 kernel: __ubsan_handle_load_invalid_value.cold+0x44/0x49 kernel: fcp_response.part.0.cold+0x1a/0x2b [snd_firewire_lib] kernel: fcp_response+0x28/0x30 [snd_firewire_lib] kernel: fw_core_handle_request+0x230/0x3d0 [firewire_core] kernel: handle_ar_packet+0x1d9/0x200 [firewire_ohci] kernel: ? handle_ar_packet+0x1d9/0x200 [firewire_ohci] kernel: ? transmit_complete_callback+0x9f/0x120 [firewire_core] kernel: ar_context_tasklet+0xa8/0x2e0 [firewire_ohci] kernel: tasklet_action_common.constprop.0+0xea/0xf0 kernel: tasklet_action+0x22/0x30 kernel: __do_softirq+0xd9/0x2e3 kernel: ? irq_finalize_oneshot.part.0+0xf0/0xf0 kernel: do_softirq+0x75/0xa0 kernel: </IRQ> kernel: <TASK> kernel: __local_bh_enable_ip+0x50/0x60 kernel: irq_forced_thread_fn+0x7e/0x90 kernel: irq_thread+0xba/0x190 kernel: ? irq_thread_fn+0x60/0x60 kernel: kthread+0x11e/0x140 kernel: ? irq_thread_check_affinity+0xf0/0xf0 kernel: ? set_kthread_struct+0x50/0x50 kernel: ret_from_fork+0x22/0x30 kernel: </TASK> kernel: ================================================================================ This commit fixes the bug. The bug has no disadvantage for the non- control/notify AV/C transactions since the flag has an effect for AV/C response with INTERIM (0x0f) status which is not used for the transactions in AV/C general specification. CVE-2022-49248 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49248.html CVE-2022-49248 https://bugzilla.suse.com/1238284 SUSE Bug 1238284 In the Linux kernel, the following vulnerability has been resolved: media: usb: go7007: s2250-board: fix leak in probe() Call i2c_unregister_device(audio) on this error path. CVE-2022-49253 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49253.html CVE-2022-49253 https://bugzilla.suse.com/1238420 SUSE Bug 1238420 In the Linux kernel, the following vulnerability has been resolved: block: don't delete queue kobject before its children kobjects aren't supposed to be deleted before their child kobjects are deleted. Apparently this is usually benign; however, a WARN will be triggered if one of the child kobjects has a named attribute group: sysfs group 'modes' not found for kobject 'crypto' WARNING: CPU: 0 PID: 1 at fs/sysfs/group.c:278 sysfs_remove_group+0x72/0x80 ... Call Trace: sysfs_remove_groups+0x29/0x40 fs/sysfs/group.c:312 __kobject_del+0x20/0x80 lib/kobject.c:611 kobject_cleanup+0xa4/0x140 lib/kobject.c:696 kobject_release lib/kobject.c:736 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x53/0x70 lib/kobject.c:753 blk_crypto_sysfs_unregister+0x10/0x20 block/blk-crypto-sysfs.c:159 blk_unregister_queue+0xb0/0x110 block/blk-sysfs.c:962 del_gendisk+0x117/0x250 block/genhd.c:610 Fix this by moving the kobject_del() and the corresponding kobject_uevent() to the correct place. CVE-2022-49259 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49259.html CVE-2022-49259 https://bugzilla.suse.com/1238413 SUSE Bug 1238413 In the Linux kernel, the following vulnerability has been resolved: drm/i915/gem: add missing boundary check in vm_access A missing bounds check in vm_access() can lead to an out-of-bounds read or write in the adjacent memory area, since the len attribute is not validated before the memcpy later in the function, potentially hitting: [ 183.637831] BUG: unable to handle page fault for address: ffffc90000c86000 [ 183.637934] #PF: supervisor read access in kernel mode [ 183.637997] #PF: error_code(0x0000) - not-present page [ 183.638059] PGD 100000067 P4D 100000067 PUD 100258067 PMD 106341067 PTE 0 [ 183.638144] Oops: 0000 [#2] PREEMPT SMP NOPTI [ 183.638201] CPU: 3 PID: 1790 Comm: poc Tainted: G D 5.17.0-rc6-ci-drm-11296+ #1 [ 183.638298] Hardware name: Intel Corporation CoffeeLake Client Platform/CoffeeLake H DDR4 RVP, BIOS CNLSFWR1.R00.X208.B00.1905301319 05/30/2019 [ 183.638430] RIP: 0010:memcpy_erms+0x6/0x10 [ 183.640213] RSP: 0018:ffffc90001763d48 EFLAGS: 00010246 [ 183.641117] RAX: ffff888109c14000 RBX: ffff888111bece40 RCX: 0000000000000ffc [ 183.642029] RDX: 0000000000001000 RSI: ffffc90000c86000 RDI: ffff888109c14004 [ 183.642946] RBP: 0000000000000ffc R08: 800000000000016b R09: 0000000000000000 [ 183.643848] R10: ffffc90000c85000 R11: 0000000000000048 R12: 0000000000001000 [ 183.644742] R13: ffff888111bed190 R14: ffff888109c14000 R15: 0000000000001000 [ 183.645653] FS: 00007fe5ef807540(0000) GS:ffff88845b380000(0000) knlGS:0000000000000000 [ 183.646570] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 183.647481] CR2: ffffc90000c86000 CR3: 000000010ff02006 CR4: 00000000003706e0 [ 183.648384] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 183.649271] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 183.650142] Call Trace: [ 183.650988] <TASK> [ 183.651793] vm_access+0x1f0/0x2a0 [i915] [ 183.652726] __access_remote_vm+0x224/0x380 [ 183.653561] mem_rw.isra.0+0xf9/0x190 [ 183.654402] vfs_read+0x9d/0x1b0 [ 183.655238] ksys_read+0x63/0xe0 [ 183.656065] do_syscall_64+0x38/0xc0 [ 183.656882] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 183.657663] RIP: 0033:0x7fe5ef725142 [ 183.659351] RSP: 002b:00007ffe1e81c7e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 [ 183.660227] RAX: ffffffffffffffda RBX: 0000557055dfb780 RCX: 00007fe5ef725142 [ 183.661104] RDX: 0000000000001000 RSI: 00007ffe1e81d880 RDI: 0000000000000005 [ 183.661972] RBP: 00007ffe1e81e890 R08: 0000000000000030 R09: 0000000000000046 [ 183.662832] R10: 0000557055dfc2e0 R11: 0000000000000246 R12: 0000557055dfb1c0 [ 183.663691] R13: 00007ffe1e81e980 R14: 0000000000000000 R15: 0000000000000000 Changes since v1: - Updated if condition with range_overflows_t [Chris Wilson] [mauld: tidy up the commit message and add Cc: stable] (cherry picked from commit 661412e301e2ca86799aa4f400d1cf0bd38c57c6) CVE-2022-49261 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49261.html CVE-2022-49261 https://bugzilla.suse.com/1238462 SUSE Bug 1238462 In the Linux kernel, the following vulnerability has been resolved: brcmfmac: pcie: Release firmwares in the brcmf_pcie_setup error path This avoids leaking memory if brcmf_chip_get_raminfo fails. Note that the CLM blob is released in the device remove path. CVE-2022-49263 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49263.html CVE-2022-49263 https://bugzilla.suse.com/1238267 SUSE Bug 1238267 In the Linux kernel, the following vulnerability has been resolved: exec: Force single empty string when argv is empty Quoting[1] Ariadne Conill: "In several other operating systems, it is a hard requirement that the second argument to execve(2) be the name of a program, thus prohibiting a scenario where argc < 1. POSIX 2017 also recommends this behaviour, but it is not an explicit requirement[2]: The argument arg0 should point to a filename string that is associated with the process being started by one of the exec functions. ... Interestingly, Michael Kerrisk opened an issue about this in 2008[3], but there was no consensus to support fixing this issue then. Hopefully now that CVE-2021-4034 shows practical exploitative use[4] of this bug in a shellcode, we can reconsider. This issue is being tracked in the KSPP issue tracker[5]." While the initial code searches[6][7] turned up what appeared to be mostly corner case tests, trying to that just reject argv == NULL (or an immediately terminated pointer list) quickly started tripping[8] existing userspace programs. The next best approach is forcing a single empty string into argv and adjusting argc to match. The number of programs depending on argc == 0 seems a smaller set than those calling execve with a NULL argv. Account for the additional stack space in bprm_stack_limits(). Inject an empty string when argc == 0 (and set argc = 1). Warn about the case so userspace has some notice about the change: process './argc0' launched './argc0' with NULL argv: empty string added Additionally WARN() and reject NULL argv usage for kernel threads. [1] https://lore.kernel.org/lkml/20220127000724.15106-1-ariadne@dereferenced.org/ [2] https://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html [3] https://bugzilla.kernel.org/show_bug.cgi?id=8408 [4] https://www.qualys.com/2022/01/25/cve-2021-4034/pwnkit.txt [5] https://github.com/KSPP/linux/issues/176 [6] https://codesearch.debian.net/search?q=execve%5C+*%5C%28%5B%5E%2C%5D%2B%2C+*NULL&literal=0 [7] https://codesearch.debian.net/search?q=execlp%3F%5Cs*%5C%28%5B%5E%2C%5D%2B%2C%5Cs*NULL&literal=0 [8] https://lore.kernel.org/lkml/20220131144352.GE16385@xsang-OptiPlex-9020/ CVE-2022-49264 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49264.html CVE-2022-49264 https://bugzilla.suse.com/1237815 SUSE Bug 1237815 In the Linux kernel, the following vulnerability has been resolved: cifs: prevent bad output lengths in smb2_ioctl_query_info() When calling smb2_ioctl_query_info() with smb_query_info::flags=PASSTHRU_FSCTL and smb_query_info::output_buffer_length=0, the following would return 0x10 buffer = memdup_user(arg + sizeof(struct smb_query_info), qi.output_buffer_length); if (IS_ERR(buffer)) { kfree(vars); return PTR_ERR(buffer); } rather than a valid pointer thus making IS_ERR() check fail. This would then cause a NULL ptr deference in @buffer when accessing it later in smb2_ioctl_query_ioctl(). While at it, prevent having a @buffer smaller than 8 bytes to correctly handle SMB2_SET_INFO FileEndOfFileInformation requests when smb_query_info::flags=PASSTHRU_SET_INFO. Here is a small C reproducer which triggers a NULL ptr in @buffer when passing an invalid smb_query_info::flags #include <stdio.h> #include <stdlib.h> #include <stdint.h> #include <unistd.h> #include <fcntl.h> #include <sys/ioctl.h> #define die(s) perror(s), exit(1) #define QUERY_INFO 0xc018cf07 int main(int argc, char *argv[]) { int fd; if (argc < 2) exit(1); fd = open(argv[1], O_RDONLY); if (fd == -1) die("open"); if (ioctl(fd, QUERY_INFO, (uint32_t[]) { 0, 0, 0, 4, 0, 0}) == -1) die("ioctl"); close(fd); return 0; } mount.cifs //srv/share /mnt -o ... gcc repro.c && ./a.out /mnt/f0 [ 114.138620] general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI [ 114.139310] KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] [ 114.139775] CPU: 2 PID: 995 Comm: a.out Not tainted 5.17.0-rc8 #1 [ 114.140148] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.15.0-0-g2dd4b9b-rebuilt.opensuse.org 04/01/2014 [ 114.140818] RIP: 0010:smb2_ioctl_query_info+0x206/0x410 [cifs] [ 114.141221] Code: 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 c8 01 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 7b 28 4c 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 9c 01 00 00 49 8b 3f e8 58 02 fb ff 48 8b 14 24 [ 114.142348] RSP: 0018:ffffc90000b47b00 EFLAGS: 00010256 [ 114.142692] RAX: dffffc0000000000 RBX: ffff888115503200 RCX: ffffffffa020580d [ 114.143119] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffffa043a380 [ 114.143544] RBP: ffff888115503278 R08: 0000000000000001 R09: 0000000000000003 [ 114.143983] R10: fffffbfff4087470 R11: 0000000000000001 R12: ffff888115503288 [ 114.144424] R13: 00000000ffffffea R14: ffff888115503228 R15: 0000000000000000 [ 114.144852] FS: 00007f7aeabdf740(0000) GS:ffff888151600000(0000) knlGS:0000000000000000 [ 114.145338] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 114.145692] CR2: 00007f7aeacfdf5e CR3: 000000012000e000 CR4: 0000000000350ee0 [ 114.146131] Call Trace: [ 114.146291] <TASK> [ 114.146432] ? smb2_query_reparse_tag+0x890/0x890 [cifs] [ 114.146800] ? cifs_mapchar+0x460/0x460 [cifs] [ 114.147121] ? rcu_read_lock_sched_held+0x3f/0x70 [ 114.147412] ? cifs_strndup_to_utf16+0x15b/0x250 [cifs] [ 114.147775] ? dentry_path_raw+0xa6/0xf0 [ 114.148024] ? cifs_convert_path_to_utf16+0x198/0x220 [cifs] [ 114.148413] ? smb2_check_message+0x1080/0x1080 [cifs] [ 114.148766] ? rcu_read_lock_sched_held+0x3f/0x70 [ 114.149065] cifs_ioctl+0x1577/0x3320 [cifs] [ 114.149371] ? lock_downgrade+0x6f0/0x6f0 [ 114.149631] ? cifs_readdir+0x2e60/0x2e60 [cifs] [ 114.149956] ? rcu_read_lock_sched_held+0x3f/0x70 [ 114.150250] ? __rseq_handle_notify_resume+0x80b/0xbe0 [ 114.150562] ? __up_read+0x192/0x710 [ 114.150791] ? __ia32_sys_rseq+0xf0/0xf0 [ 114.151025] ? __x64_sys_openat+0x11f/0x1d0 [ 114.151296] __x64_sys_ioctl+0x127/0x190 [ 114.151549] do_syscall_64+0x3b/0x90 [ 114.151768] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 114.152079] RIP: 0033:0x7f7aead043df [ 114.152306] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 ---truncated--- CVE-2022-49271 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49271.html CVE-2022-49271 https://bugzilla.suse.com/1238626 SUSE Bug 1238626 In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix potential AB/BA lock with buffer_mutex and mmap_lock syzbot caught a potential deadlock between the PCM runtime->buffer_mutex and the mm->mmap_lock. It was brought by the recent fix to cover the racy read/write and other ioctls, and in that commit, I overlooked a (hopefully only) corner case that may take the revert lock, namely, the OSS mmap. The OSS mmap operation exceptionally allows to re-configure the parameters inside the OSS mmap syscall, where mm->mmap_mutex is already held. Meanwhile, the copy_from/to_user calls at read/write operations also take the mm->mmap_lock internally, hence it may lead to a AB/BA deadlock. A similar problem was already seen in the past and we fixed it with a refcount (in commit b248371628aa). The former fix covered only the call paths with OSS read/write and OSS ioctls, while we need to cover the concurrent access via both ALSA and OSS APIs now. This patch addresses the problem above by replacing the buffer_mutex lock in the read/write operations with a refcount similar as we've used for OSS. The new field, runtime->buffer_accessing, keeps the number of concurrent read/write operations. Unlike the former buffer_mutex protection, this protects only around the copy_from/to_user() calls; the other codes are basically protected by the PCM stream lock. The refcount can be a negative, meaning blocked by the ioctls. If a negative value is seen, the read/write aborts with -EBUSY. In the ioctl side, OTOH, they check this refcount, too, and set to a negative value for blocking unless it's already being accessed. CVE-2022-49272 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49272.html CVE-2022-49272 https://bugzilla.suse.com/1238272 SUSE Bug 1238272 In the Linux kernel, the following vulnerability has been resolved: can: m_can: m_can_tx_handler(): fix use after free of skb can_put_echo_skb() will clone skb then free the skb. Move the can_put_echo_skb() for the m_can version 3.0.x directly before the start of the xmit in hardware, similar to the 3.1.x branch. CVE-2022-49275 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49275.html CVE-2022-49275 https://bugzilla.suse.com/1238719 SUSE Bug 1238719 https://bugzilla.suse.com/1238720 SUSE Bug 1238720 In the Linux kernel, the following vulnerability has been resolved: NFSD: prevent integer overflow on 32 bit systems On a 32 bit system, the "len * sizeof(*p)" operation can have an integer overflow. CVE-2022-49279 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49279.html CVE-2022-49279 https://bugzilla.suse.com/1238655 SUSE Bug 1238655 In the Linux kernel, the following vulnerability has been resolved: NFSD: prevent underflow in nfssvc_decode_writeargs() Smatch complains: fs/nfsd/nfsxdr.c:341 nfssvc_decode_writeargs() warn: no lower bound on 'args->len' Change the type to unsigned to prevent this issue. CVE-2022-49280 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49280.html CVE-2022-49280 https://bugzilla.suse.com/1238630 SUSE Bug 1238630 In the Linux kernel, the following vulnerability has been resolved: cifs: fix handlecache and multiuser In multiuser each individual user has their own tcon structure for the share and thus their own handle for a cached directory. When we umount such a share we much make sure to release the pinned down dentry for each such tcon and not just the master tcon. Otherwise we will get nasty warnings on umount that dentries are still in use: [ 3459.590047] BUG: Dentry 00000000115c6f41{i=12000000019d95,n=/} still in use\ (2) [unmount of cifs cifs] ... [ 3459.590492] Call Trace: [ 3459.590500] d_walk+0x61/0x2a0 [ 3459.590518] ? shrink_lock_dentry.part.0+0xe0/0xe0 [ 3459.590526] shrink_dcache_for_umount+0x49/0x110 [ 3459.590535] generic_shutdown_super+0x1a/0x110 [ 3459.590542] kill_anon_super+0x14/0x30 [ 3459.590549] cifs_kill_sb+0xf5/0x104 [cifs] [ 3459.590773] deactivate_locked_super+0x36/0xa0 [ 3459.590782] cleanup_mnt+0x131/0x190 [ 3459.590789] task_work_run+0x5c/0x90 [ 3459.590798] exit_to_user_mode_loop+0x151/0x160 [ 3459.590809] exit_to_user_mode_prepare+0x83/0xd0 [ 3459.590818] syscall_exit_to_user_mode+0x12/0x30 [ 3459.590828] do_syscall_64+0x48/0x90 [ 3459.590833] entry_SYSCALL_64_after_hwframe+0x44/0xae CVE-2022-49281 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49281.html CVE-2022-49281 https://bugzilla.suse.com/1238635 SUSE Bug 1238635 In the Linux kernel, the following vulnerability has been resolved: iio: accel: mma8452: use the correct logic to get mma8452_data The original logic to get mma8452_data is wrong, the *dev point to the device belong to iio_dev. we can't use this dev to find the correct i2c_client. The original logic happen to work because it finally use dev->driver_data to get iio_dev. Here use the API to_i2c_client() is wrong and make reader confuse. To correct the logic, it should be like this struct mma8452_data *data = iio_priv(dev_get_drvdata(dev)); But after commit 8b7651f25962 ("iio: iio_device_alloc(): Remove unnecessary self drvdata"), the upper logic also can't work. When try to show the avialable scale in userspace, will meet kernel dump, kernel handle NULL pointer dereference. So use dev_to_iio_dev() to correct the logic. Dual fixes tags as the second reflects when the bug was exposed, whilst the first reflects when the original bug was introduced. CVE-2022-49285 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49285.html CVE-2022-49285 https://bugzilla.suse.com/1238641 SUSE Bug 1238641 In the Linux kernel, the following vulnerability has been resolved: tpm: fix reference counting for struct tpm_chip The following sequence of operations results in a refcount warning: 1. Open device /dev/tpmrm. 2. Remove module tpm_tis_spi. 3. Write a TPM command to the file descriptor opened at step 1. ------------[ cut here ]------------ WARNING: CPU: 3 PID: 1161 at lib/refcount.c:25 kobject_get+0xa0/0xa4 refcount_t: addition on 0; use-after-free. Modules linked in: tpm_tis_spi tpm_tis_core tpm mdio_bcm_unimac brcmfmac sha256_generic libsha256 sha256_arm hci_uart btbcm bluetooth cfg80211 vc4 brcmutil ecdh_generic ecc snd_soc_core crc32_arm_ce libaes raspberrypi_hwmon ac97_bus snd_pcm_dmaengine bcm2711_thermal snd_pcm snd_timer genet snd phy_generic soundcore [last unloaded: spi_bcm2835] CPU: 3 PID: 1161 Comm: hold_open Not tainted 5.10.0ls-main-dirty #2 Hardware name: BCM2711 [<c0410c3c>] (unwind_backtrace) from [<c040b580>] (show_stack+0x10/0x14) [<c040b580>] (show_stack) from [<c1092174>] (dump_stack+0xc4/0xd8) [<c1092174>] (dump_stack) from [<c0445a30>] (__warn+0x104/0x108) [<c0445a30>] (__warn) from [<c0445aa8>] (warn_slowpath_fmt+0x74/0xb8) [<c0445aa8>] (warn_slowpath_fmt) from [<c08435d0>] (kobject_get+0xa0/0xa4) [<c08435d0>] (kobject_get) from [<bf0a715c>] (tpm_try_get_ops+0x14/0x54 [tpm]) [<bf0a715c>] (tpm_try_get_ops [tpm]) from [<bf0a7d6c>] (tpm_common_write+0x38/0x60 [tpm]) [<bf0a7d6c>] (tpm_common_write [tpm]) from [<c05a7ac0>] (vfs_write+0xc4/0x3c0) [<c05a7ac0>] (vfs_write) from [<c05a7ee4>] (ksys_write+0x58/0xcc) [<c05a7ee4>] (ksys_write) from [<c04001a0>] (ret_fast_syscall+0x0/0x4c) Exception stack(0xc226bfa8 to 0xc226bff0) bfa0: 00000000 000105b4 00000003 beafe664 00000014 00000000 bfc0: 00000000 000105b4 000103f8 00000004 00000000 00000000 b6f9c000 beafe684 bfe0: 0000006c beafe648 0001056c b6eb6944 ---[ end trace d4b8409def9b8b1f ]--- The reason for this warning is the attempt to get the chip->dev reference in tpm_common_write() although the reference counter is already zero. Since commit 8979b02aaf1d ("tpm: Fix reference count to main device") the extra reference used to prevent a premature zero counter is never taken, because the required TPM_CHIP_FLAG_TPM2 flag is never set. Fix this by moving the TPM 2 character device handling from tpm_chip_alloc() to tpm_add_char_device() which is called at a later point in time when the flag has been set in case of TPM2. Commit fdc915f7f719 ("tpm: expose spaces via a device link /dev/tpmrm<n>") already introduced function tpm_devs_release() to release the extra reference but did not implement the required put on chip->devs that results in the call of this function. Fix this by putting chip->devs in tpm_chip_unregister(). Finally move the new implementation for the TPM 2 handling into a new function to avoid multiple checks for the TPM_CHIP_FLAG_TPM2 flag in the good case and error cases. CVE-2022-49287 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49287.html CVE-2022-49287 https://bugzilla.suse.com/1238276 SUSE Bug 1238276 In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix races among concurrent prealloc proc writes We have no protection against concurrent PCM buffer preallocation changes via proc files, and it may potentially lead to UAF or some weird problem. This patch applies the PCM open_mutex to the proc write operation for avoiding the racy proc writes and the PCM stream open (and further operations). CVE-2022-49288 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49288.html CVE-2022-49288 https://bugzilla.suse.com/1238271 SUSE Bug 1238271 In the Linux kernel, the following vulnerability has been resolved: mac80211: fix potential double free on mesh join While commit 6a01afcf8468 ("mac80211: mesh: Free ie data when leaving mesh") fixed a memory leak on mesh leave / teardown it introduced a potential memory corruption caused by a double free when rejoining the mesh: ieee80211_leave_mesh() -> kfree(sdata->u.mesh.ie); ... ieee80211_join_mesh() -> copy_mesh_setup() -> old_ie = ifmsh->ie; -> kfree(old_ie); This double free / kernel panics can be reproduced by using wpa_supplicant with an encrypted mesh (if set up without encryption via "iw" then ifmsh->ie is always NULL, which avoids this issue). And then calling: $ iw dev mesh0 mesh leave $ iw dev mesh0 mesh join my-mesh Note that typically these commands are not used / working when using wpa_supplicant. And it seems that wpa_supplicant or wpa_cli are going through a NETDEV_DOWN/NETDEV_UP cycle between a mesh leave and mesh join where the NETDEV_UP resets the mesh.ie to NULL via a memcpy of default_mesh_setup in cfg80211_netdev_notifier_call, which then avoids the memory corruption, too. The issue was first observed in an application which was not using wpa_supplicant but "Senf" instead, which implements its own calls to nl80211. Fixing the issue by removing the kfree()'ing of the mesh IE in the mesh join function and leaving it solely up to the mesh leave to free the mesh IE. CVE-2022-49290 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49290.html CVE-2022-49290 https://bugzilla.suse.com/1238156 SUSE Bug 1238156 In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix races among concurrent hw_params and hw_free calls Currently we have neither proper check nor protection against the concurrent calls of PCM hw_params and hw_free ioctls, which may result in a UAF. Since the existing PCM stream lock can't be used for protecting the whole ioctl operations, we need a new mutex to protect those racy calls. This patch introduced a new mutex, runtime->buffer_mutex, and applies it to both hw_params and hw_free ioctl code paths. Along with it, the both functions are slightly modified (the mmap_count check is moved into the state-check block) for code simplicity. CVE-2022-49291 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49291.html CVE-2022-49291 https://bugzilla.suse.com/1238705 SUSE Bug 1238705 https://bugzilla.suse.com/1238706 SUSE Bug 1238706 In the Linux kernel, the following vulnerability has been resolved: ALSA: oss: Fix PCM OSS buffer allocation overflow We've got syzbot reports hitting INT_MAX overflow at vmalloc() allocation that is called from snd_pcm_plug_alloc(). Although we apply the restrictions to input parameters, it's based only on the hw_params of the underlying PCM device. Since the PCM OSS layer allocates a temporary buffer for the data conversion, the size may become unexpectedly large when more channels or higher rates is given; in the reported case, it went over INT_MAX, hence it hits WARN_ON(). This patch is an attempt to avoid such an overflow and an allocation for too large buffers. First off, it adds the limit of 1MB as the upper bound for period bytes. This must be large enough for all use cases, and we really don't want to handle a larger temporary buffer than this size. The size check is performed at two places, where the original period bytes is calculated and where the plugin buffer size is calculated. In addition, the driver uses array_size() and array3_size() for multiplications to catch overflows for the converted period size and buffer bytes. CVE-2022-49292 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49292.html CVE-2022-49292 https://bugzilla.suse.com/1238625 SUSE Bug 1238625 In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: initialize registers in nft_do_chain() Initialize registers to avoid stack leak into userspace. CVE-2022-49293 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49293.html CVE-2022-49293 https://bugzilla.suse.com/1239454 SUSE Bug 1239454 In the Linux kernel, the following vulnerability has been resolved: nbd: call genl_unregister_family() first in nbd_cleanup() Otherwise there may be race between module removal and the handling of netlink command, which can lead to the oops as shown below: BUG: kernel NULL pointer dereference, address: 0000000000000098 Oops: 0002 [#1] SMP PTI CPU: 1 PID: 31299 Comm: nbd-client Tainted: G E 5.14.0-rc4 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) RIP: 0010:down_write+0x1a/0x50 Call Trace: start_creating+0x89/0x130 debugfs_create_dir+0x1b/0x130 nbd_start_device+0x13d/0x390 [nbd] nbd_genl_connect+0x42f/0x748 [nbd] genl_family_rcv_msg_doit.isra.0+0xec/0x150 genl_rcv_msg+0xe5/0x1e0 netlink_rcv_skb+0x55/0x100 genl_rcv+0x29/0x40 netlink_unicast+0x1a8/0x250 netlink_sendmsg+0x21b/0x430 ____sys_sendmsg+0x2a4/0x2d0 ___sys_sendmsg+0x81/0xc0 __sys_sendmsg+0x62/0xb0 __x64_sys_sendmsg+0x1f/0x30 do_syscall_64+0x3b/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae Modules linked in: nbd(E-) CVE-2022-49295 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49295.html CVE-2022-49295 https://bugzilla.suse.com/1238707 SUSE Bug 1238707 In the Linux kernel, the following vulnerability has been resolved: nbd: fix io hung while disconnecting device In our tests, "qemu-nbd" triggers a io hung: INFO: task qemu-nbd:11445 blocked for more than 368 seconds. Not tainted 5.18.0-rc3-next-20220422-00003-g2176915513ca #884 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:qemu-nbd state:D stack: 0 pid:11445 ppid: 1 flags:0x00000000 Call Trace: <TASK> __schedule+0x480/0x1050 ? _raw_spin_lock_irqsave+0x3e/0xb0 schedule+0x9c/0x1b0 blk_mq_freeze_queue_wait+0x9d/0xf0 ? ipi_rseq+0x70/0x70 blk_mq_freeze_queue+0x2b/0x40 nbd_add_socket+0x6b/0x270 [nbd] nbd_ioctl+0x383/0x510 [nbd] blkdev_ioctl+0x18e/0x3e0 __x64_sys_ioctl+0xac/0x120 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7fd8ff706577 RSP: 002b:00007fd8fcdfebf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000040000000 RCX: 00007fd8ff706577 RDX: 000000000000000d RSI: 000000000000ab00 RDI: 000000000000000f RBP: 000000000000000f R08: 000000000000fbe8 R09: 000055fe497c62b0 R10: 00000002aff20000 R11: 0000000000000246 R12: 000000000000006d R13: 0000000000000000 R14: 00007ffe82dc5e70 R15: 00007fd8fcdff9c0 "qemu-ndb -d" will call ioctl 'NBD_DISCONNECT' first, however, following message was found: block nbd0: Send disconnect failed -32 Which indicate that something is wrong with the server. Then, "qemu-nbd -d" will call ioctl 'NBD_CLEAR_SOCK', however ioctl can't clear requests after commit 2516ab1543fd("nbd: only clear the queue on device teardown"). And in the meantime, request can't complete through timeout because nbd_xmit_timeout() will always return 'BLK_EH_RESET_TIMER', which means such request will never be completed in this situation. Now that the flag 'NBD_CMD_INFLIGHT' can make sure requests won't complete multiple times, switch back to call nbd_clear_sock() in nbd_clear_sock_ioctl(), so that inflight requests can be cleared. CVE-2022-49297 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49297.html CVE-2022-49297 https://bugzilla.suse.com/1238469 SUSE Bug 1238469 In the Linux kernel, the following vulnerability has been resolved: staging: rtl8712: fix uninit-value in r871xu_drv_init() When 'tmpU1b' returns from r8712_read8(padapter, EE_9346CR) is 0, 'mac[6]' will not be initialized. BUG: KMSAN: uninit-value in r871xu_drv_init+0x2d54/0x3070 drivers/staging/rtl8712/usb_intf.c:541 r871xu_drv_init+0x2d54/0x3070 drivers/staging/rtl8712/usb_intf.c:541 usb_probe_interface+0xf19/0x1600 drivers/usb/core/driver.c:396 really_probe+0x653/0x14b0 drivers/base/dd.c:596 __driver_probe_device+0x3e9/0x530 drivers/base/dd.c:752 driver_probe_device drivers/base/dd.c:782 [inline] __device_attach_driver+0x79f/0x1120 drivers/base/dd.c:899 bus_for_each_drv+0x2d6/0x3f0 drivers/base/bus.c:427 __device_attach+0x593/0x8e0 drivers/base/dd.c:970 device_initial_probe+0x4a/0x60 drivers/base/dd.c:1017 bus_probe_device+0x17b/0x3e0 drivers/base/bus.c:487 device_add+0x1fff/0x26e0 drivers/base/core.c:3405 usb_set_configuration+0x37e9/0x3ed0 drivers/usb/core/message.c:2170 usb_generic_driver_probe+0x13c/0x300 drivers/usb/core/generic.c:238 usb_probe_device+0x309/0x570 drivers/usb/core/driver.c:293 really_probe+0x653/0x14b0 drivers/base/dd.c:596 __driver_probe_device+0x3e9/0x530 drivers/base/dd.c:752 driver_probe_device drivers/base/dd.c:782 [inline] __device_attach_driver+0x79f/0x1120 drivers/base/dd.c:899 bus_for_each_drv+0x2d6/0x3f0 drivers/base/bus.c:427 __device_attach+0x593/0x8e0 drivers/base/dd.c:970 device_initial_probe+0x4a/0x60 drivers/base/dd.c:1017 bus_probe_device+0x17b/0x3e0 drivers/base/bus.c:487 device_add+0x1fff/0x26e0 drivers/base/core.c:3405 usb_new_device+0x1b8e/0x2950 drivers/usb/core/hub.c:2566 hub_port_connect drivers/usb/core/hub.c:5358 [inline] hub_port_connect_change drivers/usb/core/hub.c:5502 [inline] port_event drivers/usb/core/hub.c:5660 [inline] hub_event+0x58e3/0x89e0 drivers/usb/core/hub.c:5742 process_one_work+0xdb6/0x1820 kernel/workqueue.c:2307 worker_thread+0x10b3/0x21e0 kernel/workqueue.c:2454 kthread+0x3c7/0x500 kernel/kthread.c:377 ret_from_fork+0x1f/0x30 Local variable mac created at: r871xu_drv_init+0x1771/0x3070 drivers/staging/rtl8712/usb_intf.c:394 usb_probe_interface+0xf19/0x1600 drivers/usb/core/driver.c:396 KMSAN: uninit-value in r871xu_drv_init https://syzkaller.appspot.com/bug?id=3cd92b1d85428b128503bfa7a250294c9ae00bd8 CVE-2022-49298 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49298.html CVE-2022-49298 https://bugzilla.suse.com/1238718 SUSE Bug 1238718 In the Linux kernel, the following vulnerability has been resolved: usb: dwc2: gadget: don't reset gadget's driver->bus UDC driver should not touch gadget's driver internals, especially it should not reset driver->bus. This wasn't harmful so far, but since commit fc274c1e9973 ("USB: gadget: Add a new bus for gadgets") gadget subsystem got it's own bus and messing with ->bus triggers the following NULL pointer dereference: dwc2 12480000.hsotg: bound driver g_ether 8<--- cut here --- Unable to handle kernel NULL pointer dereference at virtual address 00000000 [00000000] *pgd=00000000 Internal error: Oops: 5 [#1] SMP ARM Modules linked in: ... CPU: 0 PID: 620 Comm: modprobe Not tainted 5.18.0-rc5-next-20220504 #11862 Hardware name: Samsung Exynos (Flattened Device Tree) PC is at module_add_driver+0x44/0xe8 LR is at sysfs_do_create_link_sd+0x84/0xe0 ... Process modprobe (pid: 620, stack limit = 0x(ptrval)) ... module_add_driver from bus_add_driver+0xf4/0x1e4 bus_add_driver from driver_register+0x78/0x10c driver_register from usb_gadget_register_driver_owner+0x40/0xb4 usb_gadget_register_driver_owner from do_one_initcall+0x44/0x1e0 do_one_initcall from do_init_module+0x44/0x1c8 do_init_module from load_module+0x19b8/0x1b9c load_module from sys_finit_module+0xdc/0xfc sys_finit_module from ret_fast_syscall+0x0/0x54 Exception stack(0xf1771fa8 to 0xf1771ff0) ... dwc2 12480000.hsotg: new device is high-speed ---[ end trace 0000000000000000 ]--- Fix this by removing driver->bus entry reset. CVE-2022-49299 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49299.html CVE-2022-49299 https://bugzilla.suse.com/1238184 SUSE Bug 1238184 In the Linux kernel, the following vulnerability has been resolved: nbd: fix race between nbd_alloc_config() and module removal When nbd module is being removing, nbd_alloc_config() may be called concurrently by nbd_genl_connect(), although try_module_get() will return false, but nbd_alloc_config() doesn't handle it. The race may lead to the leak of nbd_config and its related resources (e.g, recv_workq) and oops in nbd_read_stat() due to the unload of nbd module as shown below: BUG: kernel NULL pointer dereference, address: 0000000000000040 Oops: 0000 [#1] SMP PTI CPU: 5 PID: 13840 Comm: kworker/u17:33 Not tainted 5.14.0+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: knbd16-recv recv_work [nbd] RIP: 0010:nbd_read_stat.cold+0x130/0x1a4 [nbd] Call Trace: recv_work+0x3b/0xb0 [nbd] process_one_work+0x1ed/0x390 worker_thread+0x4a/0x3d0 kthread+0x12a/0x150 ret_from_fork+0x22/0x30 Fixing it by checking the return value of try_module_get() in nbd_alloc_config(). As nbd_alloc_config() may return ERR_PTR(-ENODEV), assign nbd->config only when nbd_alloc_config() succeeds to ensure the value of nbd->config is binary (valid or NULL). Also adding a debug message to check the reference counter of nbd_config during module removal. CVE-2022-49300 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49300.html CVE-2022-49300 https://bugzilla.suse.com/1238183 SUSE Bug 1238183 In the Linux kernel, the following vulnerability has been resolved: staging: rtl8712: fix uninit-value in usb_read8() and friends When r8712_usbctrl_vendorreq() returns negative, 'data' in usb_read{8,16,32} will not be initialized. BUG: KMSAN: uninit-value in string_nocheck lib/vsprintf.c:643 [inline] BUG: KMSAN: uninit-value in string+0x4ec/0x6f0 lib/vsprintf.c:725 string_nocheck lib/vsprintf.c:643 [inline] string+0x4ec/0x6f0 lib/vsprintf.c:725 vsnprintf+0x2222/0x3650 lib/vsprintf.c:2806 va_format lib/vsprintf.c:1704 [inline] pointer+0x18e6/0x1f70 lib/vsprintf.c:2443 vsnprintf+0x1a9b/0x3650 lib/vsprintf.c:2810 vprintk_store+0x537/0x2150 kernel/printk/printk.c:2158 vprintk_emit+0x28b/0xab0 kernel/printk/printk.c:2256 dev_vprintk_emit+0x5ef/0x6d0 drivers/base/core.c:4604 dev_printk_emit+0x1dd/0x21f drivers/base/core.c:4615 __dev_printk+0x3be/0x440 drivers/base/core.c:4627 _dev_info+0x1ea/0x22f drivers/base/core.c:4673 r871xu_drv_init+0x1929/0x3070 drivers/staging/rtl8712/usb_intf.c:401 usb_probe_interface+0xf19/0x1600 drivers/usb/core/driver.c:396 really_probe+0x6c7/0x1350 drivers/base/dd.c:621 __driver_probe_device+0x3e9/0x530 drivers/base/dd.c:752 driver_probe_device drivers/base/dd.c:782 [inline] __device_attach_driver+0x79f/0x1120 drivers/base/dd.c:899 bus_for_each_drv+0x2d6/0x3f0 drivers/base/bus.c:427 __device_attach+0x593/0x8e0 drivers/base/dd.c:970 device_initial_probe+0x4a/0x60 drivers/base/dd.c:1017 bus_probe_device+0x17b/0x3e0 drivers/base/bus.c:487 device_add+0x1fff/0x26e0 drivers/base/core.c:3405 usb_set_configuration+0x37e9/0x3ed0 drivers/usb/core/message.c:2170 usb_generic_driver_probe+0x13c/0x300 drivers/usb/core/generic.c:238 usb_probe_device+0x309/0x570 drivers/usb/core/driver.c:293 really_probe+0x6c7/0x1350 drivers/base/dd.c:621 __driver_probe_device+0x3e9/0x530 drivers/base/dd.c:752 driver_probe_device drivers/base/dd.c:782 [inline] __device_attach_driver+0x79f/0x1120 drivers/base/dd.c:899 bus_for_each_drv+0x2d6/0x3f0 drivers/base/bus.c:427 __device_attach+0x593/0x8e0 drivers/base/dd.c:970 device_initial_probe+0x4a/0x60 drivers/base/dd.c:1017 bus_probe_device+0x17b/0x3e0 drivers/base/bus.c:487 device_add+0x1fff/0x26e0 drivers/base/core.c:3405 usb_new_device+0x1b91/0x2950 drivers/usb/core/hub.c:2566 hub_port_connect drivers/usb/core/hub.c:5363 [inline] hub_port_connect_change drivers/usb/core/hub.c:5507 [inline] port_event drivers/usb/core/hub.c:5665 [inline] hub_event+0x58e3/0x89e0 drivers/usb/core/hub.c:5747 process_one_work+0xdb6/0x1820 kernel/workqueue.c:2289 worker_thread+0x10d0/0x2240 kernel/workqueue.c:2436 kthread+0x3c7/0x500 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 Local variable data created at: usb_read8+0x5d/0x130 drivers/staging/rtl8712/usb_ops.c:33 r8712_read8+0xa5/0xd0 drivers/staging/rtl8712/rtl8712_io.c:29 KMSAN: uninit-value in r871xu_drv_init https://syzkaller.appspot.com/bug?id=3cd92b1d85428b128503bfa7a250294c9ae00bd8 CVE-2022-49301 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49301.html CVE-2022-49301 https://bugzilla.suse.com/1238643 SUSE Bug 1238643 In the Linux kernel, the following vulnerability has been resolved: USB: host: isp116x: check return value after calling platform_get_resource() It will cause null-ptr-deref if platform_get_resource() returns NULL, we need check the return value. CVE-2022-49302 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49302.html CVE-2022-49302 https://bugzilla.suse.com/1238653 SUSE Bug 1238653 In the Linux kernel, the following vulnerability has been resolved: drivers: tty: serial: Fix deadlock in sa1100_set_termios() There is a deadlock in sa1100_set_termios(), which is shown below: (Thread 1) | (Thread 2) | sa1100_enable_ms() sa1100_set_termios() | mod_timer() spin_lock_irqsave() //(1) | (wait a time) ... | sa1100_timeout() del_timer_sync() | spin_lock_irqsave() //(2) (wait timer to stop) | ... We hold sport->port.lock in position (1) of thread 1 and use del_timer_sync() to wait timer to stop, but timer handler also need sport->port.lock in position (2) of thread 2. As a result, sa1100_set_termios() will block forever. This patch moves del_timer_sync() before spin_lock_irqsave() in order to prevent the deadlock. CVE-2022-49304 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49304.html CVE-2022-49304 https://bugzilla.suse.com/1238639 SUSE Bug 1238639 In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8192u: Fix deadlock in ieee80211_beacons_stop() There is a deadlock in ieee80211_beacons_stop(), which is shown below: (Thread 1) | (Thread 2) | ieee80211_send_beacon() ieee80211_beacons_stop() | mod_timer() spin_lock_irqsave() //(1) | (wait a time) ... | ieee80211_send_beacon_cb() del_timer_sync() | spin_lock_irqsave() //(2) (wait timer to stop) | ... We hold ieee->beacon_lock in position (1) of thread 1 and use del_timer_sync() to wait timer to stop, but timer handler also need ieee->beacon_lock in position (2) of thread 2. As a result, ieee80211_beacons_stop() will block forever. This patch extracts del_timer_sync() from the protection of spin_lock_irqsave(), which could let timer handler to obtain the needed lock. CVE-2022-49305 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49305.html CVE-2022-49305 https://bugzilla.suse.com/1238645 SUSE Bug 1238645 In the Linux kernel, the following vulnerability has been resolved: tty: synclink_gt: Fix null-pointer-dereference in slgt_clean() When the driver fails at alloc_hdlcdev(), and then we remove the driver module, we will get the following splat: [ 25.065966] general protection fault, probably for non-canonical address 0xdffffc0000000182: 0000 [#1] PREEMPT SMP KASAN PTI [ 25.066914] KASAN: null-ptr-deref in range [0x0000000000000c10-0x0000000000000c17] [ 25.069262] RIP: 0010:detach_hdlc_protocol+0x2a/0x3e0 [ 25.077709] Call Trace: [ 25.077924] <TASK> [ 25.078108] unregister_hdlc_device+0x16/0x30 [ 25.078481] slgt_cleanup+0x157/0x9f0 [synclink_gt] Fix this by checking whether the 'info->netdev' is a null pointer first. CVE-2022-49307 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49307.html CVE-2022-49307 https://bugzilla.suse.com/1238149 SUSE Bug 1238149 In the Linux kernel, the following vulnerability has been resolved: drivers: usb: host: Fix deadlock in oxu_bus_suspend() There is a deadlock in oxu_bus_suspend(), which is shown below: (Thread 1) | (Thread 2) | timer_action() oxu_bus_suspend() | mod_timer() spin_lock_irq() //(1) | (wait a time) ... | oxu_watchdog() del_timer_sync() | spin_lock_irq() //(2) (wait timer to stop) | ... We hold oxu->lock in position (1) of thread 1, and use del_timer_sync() to wait timer to stop, but timer handler also need oxu->lock in position (2) of thread 2. As a result, oxu_bus_suspend() will block forever. This patch extracts del_timer_sync() from the protection of spin_lock_irq(), which could let timer handler to obtain the needed lock. CVE-2022-49313 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49313.html CVE-2022-49313 https://bugzilla.suse.com/1238633 SUSE Bug 1238633 In the Linux kernel, the following vulnerability has been resolved: tty: Fix a possible resource leak in icom_probe When pci_read_config_dword failed, call pci_release_regions() and pci_disable_device() to recycle the resource previously allocated. CVE-2022-49314 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49314.html CVE-2022-49314 https://bugzilla.suse.com/1238158 SUSE Bug 1238158 In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8192e: Fix deadlock in rtllib_beacons_stop() There is a deadlock in rtllib_beacons_stop(), which is shown below: (Thread 1) | (Thread 2) | rtllib_send_beacon() rtllib_beacons_stop() | mod_timer() spin_lock_irqsave() //(1) | (wait a time) ... | rtllib_send_beacon_cb() del_timer_sync() | spin_lock_irqsave() //(2) (wait timer to stop) | ... We hold ieee->beacon_lock in position (1) of thread 1 and use del_timer_sync() to wait timer to stop, but timer handler also need ieee->beacon_lock in position (2) of thread 2. As a result, rtllib_beacons_stop() will block forever. This patch extracts del_timer_sync() from the protection of spin_lock_irqsave(), which could let timer handler to obtain the needed lock. CVE-2022-49315 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49315.html CVE-2022-49315 https://bugzilla.suse.com/1238638 SUSE Bug 1238638 In the Linux kernel, the following vulnerability has been resolved: NFSv4: Don't hold the layoutget locks across multiple RPC calls When doing layoutget as part of the open() compound, we have to be careful to release the layout locks before we can call any further RPC calls, such as setattr(). The reason is that those calls could trigger a recall, which could deadlock. CVE-2022-49316 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49316.html CVE-2022-49316 https://bugzilla.suse.com/1238386 SUSE Bug 1238386 In the Linux kernel, the following vulnerability has been resolved: dmaengine: zynqmp_dma: In struct zynqmp_dma_chan fix desc_size data type In zynqmp_dma_alloc/free_chan_resources functions there is a potential overflow in the below expressions. dma_alloc_coherent(chan->dev, (2 * chan->desc_size * ZYNQMP_DMA_NUM_DESCS), &chan->desc_pool_p, GFP_KERNEL); dma_free_coherent(chan->dev,(2 * ZYNQMP_DMA_DESC_SIZE(chan) * ZYNQMP_DMA_NUM_DESCS), chan->desc_pool_v, chan->desc_pool_p); The arguments desc_size and ZYNQMP_DMA_NUM_DESCS were 32 bit. Though this overflow condition is not observed but it is a potential problem in the case of 32-bit multiplication. Hence fix it by changing the desc_size data type to size_t. In addition to coverity fix it also reuse ZYNQMP_DMA_DESC_SIZE macro in dma_alloc_coherent API argument. Addresses-Coverity: Event overflow_before_widen. CVE-2022-49320 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49320.html CVE-2022-49320 https://bugzilla.suse.com/1238394 SUSE Bug 1238394 In the Linux kernel, the following vulnerability has been resolved: xprtrdma: treat all calls not a bcall when bc_serv is NULL When a rdma server returns a fault format reply, nfs v3 client may treats it as a bcall when bc service is not exist. The debug message at rpcrdma_bc_receive_call are, [56579.837169] RPC: rpcrdma_bc_receive_call: callback XID 00000001, length=20 [56579.837174] RPC: rpcrdma_bc_receive_call: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 After that, rpcrdma_bc_receive_call will meets NULL pointer as, [ 226.057890] BUG: unable to handle kernel NULL pointer dereference at 00000000000000c8 ... [ 226.058704] RIP: 0010:_raw_spin_lock+0xc/0x20 ... [ 226.059732] Call Trace: [ 226.059878] rpcrdma_bc_receive_call+0x138/0x327 [rpcrdma] [ 226.060011] __ib_process_cq+0x89/0x170 [ib_core] [ 226.060092] ib_cq_poll_work+0x26/0x80 [ib_core] [ 226.060257] process_one_work+0x1a7/0x360 [ 226.060367] ? create_worker+0x1a0/0x1a0 [ 226.060440] worker_thread+0x30/0x390 [ 226.060500] ? create_worker+0x1a0/0x1a0 [ 226.060574] kthread+0x116/0x130 [ 226.060661] ? kthread_flush_work_fn+0x10/0x10 [ 226.060724] ret_from_fork+0x35/0x40 ... CVE-2022-49321 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49321.html CVE-2022-49321 https://bugzilla.suse.com/1238373 SUSE Bug 1238373 In the Linux kernel, the following vulnerability has been resolved: rtl818x: Prevent using not initialized queues Using not existing queues can panic the kernel with rtl8180/rtl8185 cards. Ignore the skb priority for those cards, they only have one tx queue. Pierre Asselin (pa@panix.com) reported the kernel crash in the Gentoo forum: https://forums.gentoo.org/viewtopic-t-1147832-postdays-0-postorder-asc-start-25.html He also confirmed that this patch fixes the issue. In summary this happened: After updating wpa_supplicant from 2.9 to 2.10 the kernel crashed with a "divide error: 0000" when connecting to an AP. Control port tx now tries to use IEEE80211_AC_VO for the priority, which wpa_supplicants starts to use in 2.10. Since only the rtl8187se part of the driver supports QoS, the priority of the skb is set to IEEE80211_AC_BE (2) by mac80211 for rtl8180/rtl8185 cards. rtl8180 is then unconditionally reading out the priority and finally crashes on drivers/net/wireless/realtek/rtl818x/rtl8180/dev.c line 544 without this patch: idx = (ring->idx + skb_queue_len(&ring->queue)) % ring->entries "ring->entries" is zero for rtl8180/rtl8185 cards, tx_ring[2] never got initialized. CVE-2022-49326 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49326.html CVE-2022-49326 https://bugzilla.suse.com/1238646 SUSE Bug 1238646 In the Linux kernel, the following vulnerability has been resolved: bcache: avoid journal no-space deadlock by reserving 1 journal bucket The journal no-space deadlock was reported time to time. Such deadlock can happen in the following situation. When all journal buckets are fully filled by active jset with heavy write I/O load, the cache set registration (after a reboot) will load all active jsets and inserting them into the btree again (which is called journal replay). If a journaled bkey is inserted into a btree node and results btree node split, new journal request might be triggered. For example, the btree grows one more level after the node split, then the root node record in cache device super block will be upgrade by bch_journal_meta() from bch_btree_set_root(). But there is no space in journal buckets, the journal replay has to wait for new journal bucket to be reclaimed after at least one journal bucket replayed. This is one example that how the journal no-space deadlock happens. The solution to avoid the deadlock is to reserve 1 journal bucket in run time, and only permit the reserved journal bucket to be used during cache set registration procedure for things like journal replay. Then the journal space will never be fully filled, there is no chance for journal no-space deadlock to happen anymore. This patch adds a new member "bool do_reserve" in struct journal, it is inititalized to 0 (false) when struct journal is allocated, and set to 1 (true) by bch_journal_space_reserve() when all initialization done in run_cache_set(). In the run time when journal_reclaim() tries to allocate a new journal bucket, free_journal_buckets() is called to check whether there are enough free journal buckets to use. If there is only 1 free journal bucket and journal->do_reserve is 1 (true), the last bucket is reserved and free_journal_buckets() will return 0 to indicate no free journal bucket. Then journal_reclaim() will give up, and try next time to see whetheer there is free journal bucket to allocate. By this method, there is always 1 jouranl bucket reserved in run time. During the cache set registration, journal->do_reserve is 0 (false), so the reserved journal bucket can be used to avoid the no-space deadlock. CVE-2022-49327 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49327.html CVE-2022-49327 https://bugzilla.suse.com/1238662 SUSE Bug 1238662 In the Linux kernel, the following vulnerability has been resolved: nfc: st21nfca: fix memory leaks in EVT_TRANSACTION handling Error paths do not free previously allocated memory. Add devm_kfree() to those failure paths. CVE-2022-49331 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49331.html CVE-2022-49331 https://bugzilla.suse.com/1237813 SUSE Bug 1237813 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Address NULL pointer dereference after starget_to_rport() Calls to starget_to_rport() may return NULL. Add check for NULL rport before dereference. CVE-2022-49332 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49332.html CVE-2022-49332 https://bugzilla.suse.com/1238236 SUSE Bug 1238236 In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/cs: make commands with 0 chunks illegal behaviour. Submitting a cs with 0 chunks, causes an oops later, found trying to execute the wrong userspace driver. MESA_LOADER_DRIVER_OVERRIDE=v3d glxinfo [172536.665184] BUG: kernel NULL pointer dereference, address: 00000000000001d8 [172536.665188] #PF: supervisor read access in kernel mode [172536.665189] #PF: error_code(0x0000) - not-present page [172536.665191] PGD 6712a0067 P4D 6712a0067 PUD 5af9ff067 PMD 0 [172536.665195] Oops: 0000 [#1] SMP NOPTI [172536.665197] CPU: 7 PID: 2769838 Comm: glxinfo Tainted: P O 5.10.81 #1-NixOS [172536.665199] Hardware name: To be filled by O.E.M. To be filled by O.E.M./CROSSHAIR V FORMULA-Z, BIOS 2201 03/23/2015 [172536.665272] RIP: 0010:amdgpu_cs_ioctl+0x96/0x1ce0 [amdgpu] [172536.665274] Code: 75 18 00 00 4c 8b b2 88 00 00 00 8b 46 08 48 89 54 24 68 49 89 f7 4c 89 5c 24 60 31 d2 4c 89 74 24 30 85 c0 0f 85 c0 01 00 00 <48> 83 ba d8 01 00 00 00 48 8b b4 24 90 00 00 00 74 16 48 8b 46 10 [172536.665276] RSP: 0018:ffffb47c0e81bbe0 EFLAGS: 00010246 [172536.665277] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 [172536.665278] RDX: 0000000000000000 RSI: ffffb47c0e81be28 RDI: ffffb47c0e81bd68 [172536.665279] RBP: ffff936524080010 R08: 0000000000000000 R09: ffffb47c0e81be38 [172536.665281] R10: ffff936524080010 R11: ffff936524080000 R12: ffffb47c0e81bc40 [172536.665282] R13: ffffb47c0e81be28 R14: ffff9367bc410000 R15: ffffb47c0e81be28 [172536.665283] FS: 00007fe35e05d740(0000) GS:ffff936c1edc0000(0000) knlGS:0000000000000000 [172536.665284] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [172536.665286] CR2: 00000000000001d8 CR3: 0000000532e46000 CR4: 00000000000406e0 [172536.665287] Call Trace: [172536.665322] ? amdgpu_cs_find_mapping+0x110/0x110 [amdgpu] [172536.665332] drm_ioctl_kernel+0xaa/0xf0 [drm] [172536.665338] drm_ioctl+0x201/0x3b0 [drm] [172536.665369] ? amdgpu_cs_find_mapping+0x110/0x110 [amdgpu] [172536.665372] ? selinux_file_ioctl+0x135/0x230 [172536.665399] amdgpu_drm_ioctl+0x49/0x80 [amdgpu] [172536.665403] __x64_sys_ioctl+0x83/0xb0 [172536.665406] do_syscall_64+0x33/0x40 [172536.665409] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/2018 CVE-2022-49335 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49335.html CVE-2022-49335 https://bugzilla.suse.com/1238377 SUSE Bug 1238377 In the Linux kernel, the following vulnerability has been resolved: ext4: avoid cycles in directory h-tree A maliciously corrupted filesystem can contain cycles in the h-tree stored inside a directory. That can easily lead to the kernel corrupting tree nodes that were already verified under its hands while doing a node split and consequently accessing unallocated memory. Fix the problem by verifying traversed block numbers are unique. CVE-2022-49343 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49343.html CVE-2022-49343 https://bugzilla.suse.com/1238382 SUSE Bug 1238382 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49347 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49347.html CVE-2022-49347 https://bugzilla.suse.com/1238393 SUSE Bug 1238393 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49349 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49349.html CVE-2022-49349 https://bugzilla.suse.com/1238372 SUSE Bug 1238372 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49352 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49352.html CVE-2022-49352 https://bugzilla.suse.com/1238395 SUSE Bug 1238395 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49357 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49357.html CVE-2022-49357 https://bugzilla.suse.com/1238631 SUSE Bug 1238631 In the Linux kernel, the following vulnerability has been resolved: firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle kobject_init_and_add() takes reference even when it fails. According to the doc of kobject_init_and_add() If this function returns an error, kobject_put() must be called to properly clean up the memory associated with the object. Fix this issue by calling kobject_put(). CVE-2022-49370 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49370.html CVE-2022-49370 https://bugzilla.suse.com/1238467 SUSE Bug 1238467 In the Linux kernel, the following vulnerability has been resolved: driver core: fix deadlock in __device_attach In __device_attach function, The lock holding logic is as follows: ... __device_attach device_lock(dev) // get lock dev async_schedule_dev(__device_attach_async_helper, dev); // func async_schedule_node async_schedule_node_domain(func) entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC); /* when fail or work limit, sync to execute func, but __device_attach_async_helper will get lock dev as well, which will lead to A-A deadlock. */ if (!entry || atomic_read(&entry_count) > MAX_WORK) { func; else queue_work_node(node, system_unbound_wq, &entry->work) device_unlock(dev) As shown above, when it is allowed to do async probes, because of out of memory or work limit, async work is not allowed, to do sync execute instead. it will lead to A-A deadlock because of __device_attach_async_helper getting lock dev. To fix the deadlock, move the async_schedule_dev outside device_lock, as we can see, in async_schedule_node_domain, the parameter of queue_work_node is system_unbound_wq, so it can accept concurrent operations. which will also not change the code logic, and will not lead to deadlock. CVE-2022-49371 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49371.html CVE-2022-49371 https://bugzilla.suse.com/1238546 SUSE Bug 1238546 In the Linux kernel, the following vulnerability has been resolved: watchdog: ts4800_wdt: Fix refcount leak in ts4800_wdt_probe of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() in some error paths. CVE-2022-49373 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49373.html CVE-2022-49373 https://bugzilla.suse.com/1238175 SUSE Bug 1238175 In the Linux kernel, the following vulnerability has been resolved: rtc: mt6397: check return value after calling platform_get_resource() It will cause null-ptr-deref if platform_get_resource() returns NULL, we need check the return value. CVE-2022-49375 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49375.html CVE-2022-49375 https://bugzilla.suse.com/1238228 SUSE Bug 1238228 In the Linux kernel, the following vulnerability has been resolved: scsi: sd: Fix potential NULL pointer dereference If sd_probe() sees an early error before sdkp->device is initialized, sd_zbc_release_disk() is called. This causes a NULL pointer dereference when sd_is_zoned() is called inside that function. Avoid this by removing the call to sd_zbc_release_disk() in sd_probe() error path. This change is safe and does not result in zone information memory leakage because the zone information for a zoned disk is allocated only when sd_revalidate_disk() is called, at which point sdkp->disk_dev is fully set, resulting in sd_disk_release() being called when needed to cleanup a disk zone information using sd_zbc_release_disk(). CVE-2022-49376 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49376.html CVE-2022-49376 https://bugzilla.suse.com/1238103 SUSE Bug 1238103 In the Linux kernel, the following vulnerability has been resolved: soc: rockchip: Fix refcount leak in rockchip_grf_init of_find_matching_node_and_match returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak. CVE-2022-49382 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49382.html CVE-2022-49382 https://bugzilla.suse.com/1238306 SUSE Bug 1238306 In the Linux kernel, the following vulnerability has been resolved: driver: base: fix UAF when driver_attach failed When driver_attach(drv); failed, the driver_private will be freed. But it has been added to the bus, which caused a UAF. To fix it, we need to delete it from the bus when failed. CVE-2022-49385 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49385.html CVE-2022-49385 https://bugzilla.suse.com/1237951 SUSE Bug 1237951 In the Linux kernel, the following vulnerability has been resolved: usb: usbip: fix a refcount leak in stub_probe() usb_get_dev() is called in stub_device_alloc(). When stub_probe() fails after that, usb_put_dev() needs to be called to release the reference. Fix this by moving usb_put_dev() to sdev_free error path handling. Find this by code review. CVE-2022-49389 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49389.html CVE-2022-49389 https://bugzilla.suse.com/1238257 SUSE Bug 1238257 In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix inflight count imbalances and IO hangs on offline iolatency needs to track the number of inflight IOs per cgroup. As this tracking can be expensive, it is disabled when no cgroup has iolatency configured for the device. To ensure that the inflight counters stay balanced, iolatency_set_limit() freezes the request_queue while manipulating the enabled counter, which ensures that no IO is in flight and thus all counters are zero. Unfortunately, iolatency_set_limit() isn't the only place where the enabled counter is manipulated. iolatency_pd_offline() can also dec the counter and trigger disabling. As this disabling happens without freezing the q, this can easily happen while some IOs are in flight and thus leak the counts. This can be easily demonstrated by turning on iolatency on an one empty cgroup while IOs are in flight in other cgroups and then removing the cgroup. Note that iolatency shouldn't have been enabled elsewhere in the system to ensure that removing the cgroup disables iolatency for the whole device. The following keeps flipping on and off iolatency on sda: echo +io > /sys/fs/cgroup/cgroup.subtree_control while true; do mkdir -p /sys/fs/cgroup/test echo '8:0 target=100000' > /sys/fs/cgroup/test/io.latency sleep 1 rmdir /sys/fs/cgroup/test sleep 1 done and there's concurrent fio generating direct rand reads: fio --name test --filename=/dev/sda --direct=1 --rw=randread \ --runtime=600 --time_based --iodepth=256 --numjobs=4 --bs=4k while monitoring with the following drgn script: while True: for css in css_for_each_descendant_pre(prog['blkcg_root'].css.address_of_()): for pos in hlist_for_each(container_of(css, 'struct blkcg', 'css').blkg_list): blkg = container_of(pos, 'struct blkcg_gq', 'blkcg_node') pd = blkg.pd[prog['blkcg_policy_iolatency'].plid] if pd.value_() == 0: continue iolat = container_of(pd, 'struct iolatency_grp', 'pd') inflight = iolat.rq_wait.inflight.counter.value_() if inflight: print(f'inflight={inflight} {disk_name(blkg.q.disk).decode("utf-8")} ' f'{cgroup_path(css.cgroup).decode("utf-8")}') time.sleep(1) The monitoring output looks like the following: inflight=1 sda /user.slice inflight=1 sda /user.slice ... inflight=14 sda /user.slice inflight=13 sda /user.slice inflight=17 sda /user.slice inflight=15 sda /user.slice inflight=18 sda /user.slice inflight=17 sda /user.slice inflight=20 sda /user.slice inflight=19 sda /user.slice <- fio stopped, inflight stuck at 19 inflight=19 sda /user.slice inflight=19 sda /user.slice If a cgroup with stuck inflight ends up getting throttled, the throttled IOs will never get issued as there's no completion event to wake it up leading to an indefinite hang. This patch fixes the bug by unifying enable handling into a work item which is automatically kicked off from iolatency_set_min_lat_nsec() which is called from both iolatency_set_limit() and iolatency_pd_offline() paths. Punting to a work item is necessary as iolatency_pd_offline() is called under spinlocks while freezing a request_queue requires a sleepable context. This also simplifies the code reducing LOC sans the comments and avoids the unnecessary freezes which were happening whenever a cgroup's latency target is newly set or cleared. CVE-2022-49394 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49394.html CVE-2022-49394 https://bugzilla.suse.com/1238712 SUSE Bug 1238712 In the Linux kernel, the following vulnerability has been resolved: phy: qcom-qmp: fix reset-controller leak on probe errors Make sure to release the lane reset controller in case of a late probe error (e.g. probe deferral). Note that due to the reset controller being defined in devicetree in "lane" child nodes, devm_reset_control_get_exclusive() cannot be used directly. CVE-2022-49396 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49396.html CVE-2022-49396 https://bugzilla.suse.com/1238289 SUSE Bug 1238289 In the Linux kernel, the following vulnerability has been resolved: phy: qcom-qmp: fix struct clk leak on probe errors Make sure to release the pipe clock reference in case of a late probe error (e.g. probe deferral). CVE-2022-49397 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49397.html CVE-2022-49397 https://bugzilla.suse.com/1237823 SUSE Bug 1237823 In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: gadget: Replace list_for_each_entry_safe() if using giveback The list_for_each_entry_safe() macro saves the current item (n) and the item after (n+1), so that n can be safely removed without corrupting the list. However, when traversing the list and removing items using gadget giveback, the DWC3 lock is briefly released, allowing other routines to execute. There is a situation where, while items are being removed from the cancelled_list using dwc3_gadget_ep_cleanup_cancelled_requests(), the pullup disable routine is running in parallel (due to UDC unbind). As the cleanup routine removes n, and the pullup disable removes n+1, once the cleanup retakes the DWC3 lock, it references a request who was already removed/handled. With list debug enabled, this leads to a panic. Ensure all instances of the macro are replaced where gadget giveback is used. Example call stack: Thread#1: __dwc3_gadget_ep_set_halt() - CLEAR HALT -> dwc3_gadget_ep_cleanup_cancelled_requests() ->list_for_each_entry_safe() ->dwc3_gadget_giveback(n) ->dwc3_gadget_del_and_unmap_request()- n deleted[cancelled_list] ->spin_unlock ->Thread#2 executes ... ->dwc3_gadget_giveback(n+1) ->Already removed! Thread#2: dwc3_gadget_pullup() ->waiting for dwc3 spin_lock ... ->Thread#1 released lock ->dwc3_stop_active_transfers() ->dwc3_remove_requests() ->fetches n+1 item from cancelled_list (n removed by Thread#1) ->dwc3_gadget_giveback() ->dwc3_gadget_del_and_unmap_request()- n+1 deleted[cancelled_list] ->spin_unlock CVE-2022-49398 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49398.html CVE-2022-49398 https://bugzilla.suse.com/1238621 SUSE Bug 1238621 In the Linux kernel, the following vulnerability has been resolved: tty: goldfish: Use tty_port_destroy() to destroy port In goldfish_tty_probe(), the port initialized through tty_port_init() should be destroyed in error paths.In goldfish_tty_remove(), qtty->port also should be destroyed or else might leak resources. Fix the above by calling tty_port_destroy(). CVE-2022-49399 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49399.html CVE-2022-49399 https://bugzilla.suse.com/1237829 SUSE Bug 1237829 In the Linux kernel, the following vulnerability has been resolved: ftrace: Clean up hash direct_functions on register failures We see the following GPF when register_ftrace_direct fails: [ ] general protection fault, probably for non-canonical address \ 0x200000000000010: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC PTI [...] [ ] RIP: 0010:ftrace_find_rec_direct+0x53/0x70 [ ] Code: 48 c1 e0 03 48 03 42 08 48 8b 10 31 c0 48 85 d2 74 [...] [ ] RSP: 0018:ffffc9000138bc10 EFLAGS: 00010206 [ ] RAX: 0000000000000000 RBX: ffffffff813e0df0 RCX: 000000000000003b [ ] RDX: 0200000000000000 RSI: 000000000000000c RDI: ffffffff813e0df0 [ ] RBP: ffffffffa00a3000 R08: ffffffff81180ce0 R09: 0000000000000001 [ ] R10: ffffc9000138bc18 R11: 0000000000000001 R12: ffffffff813e0df0 [ ] R13: ffffffff813e0df0 R14: ffff888171b56400 R15: 0000000000000000 [ ] FS: 00007fa9420c7780(0000) GS:ffff888ff6a00000(0000) knlGS:000000000 [ ] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ ] CR2: 000000000770d000 CR3: 0000000107d50003 CR4: 0000000000370ee0 [ ] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ ] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ ] Call Trace: [ ] <TASK> [ ] register_ftrace_direct+0x54/0x290 [ ] ? render_sigset_t+0xa0/0xa0 [ ] bpf_trampoline_update+0x3f5/0x4a0 [ ] ? 0xffffffffa00a3000 [ ] bpf_trampoline_link_prog+0xa9/0x140 [ ] bpf_tracing_prog_attach+0x1dc/0x450 [ ] bpf_raw_tracepoint_open+0x9a/0x1e0 [ ] ? find_held_lock+0x2d/0x90 [ ] ? lock_release+0x150/0x430 [ ] __sys_bpf+0xbd6/0x2700 [ ] ? lock_is_held_type+0xd8/0x130 [ ] __x64_sys_bpf+0x1c/0x20 [ ] do_syscall_64+0x3a/0x80 [ ] entry_SYSCALL_64_after_hwframe+0x44/0xae [ ] RIP: 0033:0x7fa9421defa9 [ ] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 9 f8 [...] [ ] RSP: 002b:00007ffed743bd78 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 [ ] RAX: ffffffffffffffda RBX: 00000000069d2480 RCX: 00007fa9421defa9 [ ] RDX: 0000000000000078 RSI: 00007ffed743bd80 RDI: 0000000000000011 [ ] RBP: 00007ffed743be00 R08: 0000000000bb7270 R09: 0000000000000000 [ ] R10: 00000000069da210 R11: 0000000000000246 R12: 0000000000000001 [ ] R13: 00007ffed743c4b0 R14: 00000000069d2480 R15: 0000000000000001 [ ] </TASK> [ ] Modules linked in: klp_vm(OK) [ ] ---[ end trace 0000000000000000 ]--- One way to trigger this is: 1. load a livepatch that patches kernel function xxx; 2. run bpftrace -e 'kfunc:xxx {}', this will fail (expected for now); 3. repeat #2 => gpf. This is because the entry is added to direct_functions, but not removed. Fix this by remove the entry from direct_functions when register_ftrace_direct fails. Also remove the last trailing space from ftrace.c, so we don't have to worry about it anymore. CVE-2022-49402 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49402.html CVE-2022-49402 https://bugzilla.suse.com/1238255 SUSE Bug 1238255 In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Fix potential integer multiplication overflow errors When multiplying of different types, an overflow is possible even when storing the result in a larger type. This is because the conversion is done after the multiplication. So arithmetic overflow and thus in incorrect value is possible. Correct an instance of this in the inter packet delay calculation. Fix by ensuring one of the operands is u64 which will promote the other to u64 as well ensuring no overflow. CVE-2022-49404 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49404.html CVE-2022-49404 https://bugzilla.suse.com/1238430 SUSE Bug 1238430 In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug_on in __es_tree_search Hulk Robot reported a BUG_ON: ================================================================== kernel BUG at fs/ext4/extents_status.c:199! [...] RIP: 0010:ext4_es_end fs/ext4/extents_status.c:199 [inline] RIP: 0010:__es_tree_search+0x1e0/0x260 fs/ext4/extents_status.c:217 [...] Call Trace: ext4_es_cache_extent+0x109/0x340 fs/ext4/extents_status.c:766 ext4_cache_extents+0x239/0x2e0 fs/ext4/extents.c:561 ext4_find_extent+0x6b7/0xa20 fs/ext4/extents.c:964 ext4_ext_map_blocks+0x16b/0x4b70 fs/ext4/extents.c:4384 ext4_map_blocks+0xe26/0x19f0 fs/ext4/inode.c:567 ext4_getblk+0x320/0x4c0 fs/ext4/inode.c:980 ext4_bread+0x2d/0x170 fs/ext4/inode.c:1031 ext4_quota_read+0x248/0x320 fs/ext4/super.c:6257 v2_read_header+0x78/0x110 fs/quota/quota_v2.c:63 v2_check_quota_file+0x76/0x230 fs/quota/quota_v2.c:82 vfs_load_quota_inode+0x5d1/0x1530 fs/quota/dquot.c:2368 dquot_enable+0x28a/0x330 fs/quota/dquot.c:2490 ext4_quota_enable fs/ext4/super.c:6137 [inline] ext4_enable_quotas+0x5d7/0x960 fs/ext4/super.c:6163 ext4_fill_super+0xa7c9/0xdc00 fs/ext4/super.c:4754 mount_bdev+0x2e9/0x3b0 fs/super.c:1158 mount_fs+0x4b/0x1e4 fs/super.c:1261 [...] ================================================================== Above issue may happen as follows: ------------------------------------- ext4_fill_super ext4_enable_quotas ext4_quota_enable ext4_iget __ext4_iget ext4_ext_check_inode ext4_ext_check __ext4_ext_check ext4_valid_extent_entries Check for overlapping extents does't take effect dquot_enable vfs_load_quota_inode v2_check_quota_file v2_read_header ext4_quota_read ext4_bread ext4_getblk ext4_map_blocks ext4_ext_map_blocks ext4_find_extent ext4_cache_extents ext4_es_cache_extent ext4_es_cache_extent __es_tree_search ext4_es_end BUG_ON(es->es_lblk + es->es_len < es->es_lblk) The error ext4 extents is as follows: 0af3 0300 0400 0000 00000000 extent_header 00000000 0100 0000 12000000 extent1 00000000 0100 0000 18000000 extent2 02000000 0400 0000 14000000 extent3 In the ext4_valid_extent_entries function, if prev is 0, no error is returned even if lblock<=prev. This was intended to skip the check on the first extent, but in the error image above, prev=0+1-1=0 when checking the second extent, so even though lblock<=prev, the function does not return an error. As a result, bug_ON occurs in __es_tree_search and the system panics. To solve this problem, we only need to check that: 1. The lblock of the first extent is not less than 0. 2. The lblock of the next extent is not less than the next block of the previous extent. The same applies to extent_idx. CVE-2022-49409 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49409.html CVE-2022-49409 https://bugzilla.suse.com/1238279 SUSE Bug 1238279 In the Linux kernel, the following vulnerability has been resolved: tracing: Fix potential double free in create_var_ref() In create_var_ref(), init_var_ref() is called to initialize the fields of variable ref_field, which is allocated in the previous function call to create_hist_field(). Function init_var_ref() allocates the corresponding fields such as ref_field->system, but frees these fields when the function encounters an error. The caller later calls destroy_hist_field() to conduct error handling, which frees the fields and the variable itself. This results in double free of the fields which are already freed in the previous function. Fix this by storing NULL to the corresponding fields when they are freed in init_var_ref(). CVE-2022-49410 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49410.html CVE-2022-49410 https://bugzilla.suse.com/1238441 SUSE Bug 1238441 In the Linux kernel, the following vulnerability has been resolved: bfq: Make sure bfqg for which we are queueing requests is online Bios queued into BFQ IO scheduler can be associated with a cgroup that was already offlined. This may then cause insertion of this bfq_group into a service tree. But this bfq_group will get freed as soon as last bio associated with it is completed leading to use after free issues for service tree users. Fix the problem by making sure we always operate on online bfq_group. If the bfq_group associated with the bio is not online, we pick the first online parent. CVE-2022-49411 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49411.html CVE-2022-49411 https://bugzilla.suse.com/1238307 SUSE Bug 1238307 In the Linux kernel, the following vulnerability has been resolved: bfq: Update cgroup information before merging bio When the process is migrated to a different cgroup (or in case of writeback just starts submitting bios associated with a different cgroup) bfq_merge_bio() can operate with stale cgroup information in bic. Thus the bio can be merged to a request from a different cgroup or it can result in merging of bfqqs for different cgroups or bfqqs of already dead cgroups and causing possible use-after-free issues. Fix the problem by updating cgroup information in bfq_merge_bio(). CVE-2022-49413 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49413.html CVE-2022-49413 https://bugzilla.suse.com/1238710 SUSE Bug 1238710 https://bugzilla.suse.com/1238711 SUSE Bug 1238711 In the Linux kernel, the following vulnerability has been resolved: ext4: fix race condition between ext4_write and ext4_convert_inline_data Hulk Robot reported a BUG_ON: ================================================================== EXT4-fs error (device loop3): ext4_mb_generate_buddy:805: group 0, block bitmap and bg descriptor inconsistent: 25 vs 31513 free clusters kernel BUG at fs/ext4/ext4_jbd2.c:53! invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 0 PID: 25371 Comm: syz-executor.3 Not tainted 5.10.0+ #1 RIP: 0010:ext4_put_nojournal fs/ext4/ext4_jbd2.c:53 [inline] RIP: 0010:__ext4_journal_stop+0x10e/0x110 fs/ext4/ext4_jbd2.c:116 [...] Call Trace: ext4_write_inline_data_end+0x59a/0x730 fs/ext4/inline.c:795 generic_perform_write+0x279/0x3c0 mm/filemap.c:3344 ext4_buffered_write_iter+0x2e3/0x3d0 fs/ext4/file.c:270 ext4_file_write_iter+0x30a/0x11c0 fs/ext4/file.c:520 do_iter_readv_writev+0x339/0x3c0 fs/read_write.c:732 do_iter_write+0x107/0x430 fs/read_write.c:861 vfs_writev fs/read_write.c:934 [inline] do_pwritev+0x1e5/0x380 fs/read_write.c:1031 [...] ================================================================== Above issue may happen as follows: cpu1 cpu2 __________________________|__________________________ do_pwritev vfs_writev do_iter_write ext4_file_write_iter ext4_buffered_write_iter generic_perform_write ext4_da_write_begin vfs_fallocate ext4_fallocate ext4_convert_inline_data ext4_convert_inline_data_nolock ext4_destroy_inline_data_nolock clear EXT4_STATE_MAY_INLINE_DATA ext4_map_blocks ext4_ext_map_blocks ext4_mb_new_blocks ext4_mb_regular_allocator ext4_mb_good_group_nolock ext4_mb_init_group ext4_mb_init_cache ext4_mb_generate_buddy --> error ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA) ext4_restore_inline_data set EXT4_STATE_MAY_INLINE_DATA ext4_block_write_begin ext4_da_write_end ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA) ext4_write_inline_data_end handle=NULL ext4_journal_stop(handle) __ext4_journal_stop ext4_put_nojournal(handle) ref_cnt = (unsigned long)handle BUG_ON(ref_cnt == 0) ---> BUG_ON The lock held by ext4_convert_inline_data is xattr_sem, but the lock held by generic_perform_write is i_rwsem. Therefore, the two locks can be concurrent. To solve above issue, we add inode_lock() for ext4_convert_inline_data(). At the same time, move ext4_convert_inline_data() in front of ext4_punch_hole(), remove similar handling from ext4_punch_hole(). CVE-2022-49414 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49414.html CVE-2022-49414 https://bugzilla.suse.com/1238623 SUSE Bug 1238623 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix use-after-free in chanctx code In ieee80211_vif_use_reserved_context(), when we have an old context and the new context's replace_state is set to IEEE80211_CHANCTX_REPLACE_NONE, we free the old context in ieee80211_vif_use_reserved_reassign(). Therefore, we cannot check the old_ctx anymore, so we should set it to NULL after this point. However, since the new_ctx replace state is clearly not IEEE80211_CHANCTX_REPLACES_OTHER, we're not going to do anything else in this function and can just return to avoid accessing the freed old_ctx. CVE-2022-49416 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49416.html CVE-2022-49416 https://bugzilla.suse.com/1238293 SUSE Bug 1238293 In the Linux kernel, the following vulnerability has been resolved: video: fbdev: clcdfb: Fix refcount leak in clcdfb_of_vram_setup of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. CVE-2022-49421 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49421.html CVE-2022-49421 https://bugzilla.suse.com/1238819 SUSE Bug 1238819 In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix the error handling path in idxd_cdev_register() If a call to alloc_chrdev_region() fails, the already allocated resources are leaking. Add the needed error handling path to fix the leak. CVE-2022-49422 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49422.html CVE-2022-49422 https://bugzilla.suse.com/1237784 SUSE Bug 1237784 In the Linux kernel, the following vulnerability has been resolved: powerpc/xive: Fix refcount leak in xive_spapr_init of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak. CVE-2022-49437 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49437.html CVE-2022-49437 https://bugzilla.suse.com/1238443 SUSE Bug 1238443 In the Linux kernel, the following vulnerability has been resolved: Input: sparcspkr - fix refcount leak in bbc_beep_probe of_find_node_by_path() calls of_find_node_opts_by_path(), which returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak. CVE-2022-49438 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49438.html CVE-2022-49438 https://bugzilla.suse.com/1238242 SUSE Bug 1238242 In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print failure message. This can cause a deadlock in the scenario reported by syz-bot below: CPU0 CPU1 CPU2 ---- ---- ---- lock(console_owner); lock(&port_lock_key); lock(&port->lock); lock(&port_lock_key); lock(&port->lock); lock(console_owner); As commit dbdda842fe96 ("printk: Add console owner and waiter logic to load balance console writes") said, such deadlock can be prevented by using printk_deferred() in kmalloc() (which is invoked in the section guarded by the port->lock). But there are too many printk() on the kmalloc() path, and kmalloc() can be called from anywhere, so changing printk() to printk_deferred() is too complicated and inelegant. Therefore, this patch chooses to specify __GFP_NOWARN to kmalloc(), so that printk() will not be called, and this deadlock problem can be avoided. Syzbot reported the following lockdep error: ====================================================== WARNING: possible circular locking dependency detected 5.4.143-00237-g08ccc19a-dirty #10 Not tainted ------------------------------------------------------ syz-executor.4/29420 is trying to acquire lock: ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1752 [inline] ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: vprintk_emit+0x2ca/0x470 kernel/printk/printk.c:2023 but task is already holding lock: ffff8880119c9158 (&port->lock){-.-.}-{2:2}, at: pty_write+0xf4/0x1f0 drivers/tty/pty.c:120 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&port->lock){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159 tty_port_tty_get drivers/tty/tty_port.c:288 [inline] <-- lock(&port->lock); tty_port_default_wakeup+0x1d/0xb0 drivers/tty/tty_port.c:47 serial8250_tx_chars+0x530/0xa80 drivers/tty/serial/8250/8250_port.c:1767 serial8250_handle_irq.part.0+0x31f/0x3d0 drivers/tty/serial/8250/8250_port.c:1854 serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1827 [inline] <-- lock(&port_lock_key); serial8250_default_handle_irq+0xb2/0x220 drivers/tty/serial/8250/8250_port.c:1870 serial8250_interrupt+0xfd/0x200 drivers/tty/serial/8250/8250_core.c:126 __handle_irq_event_percpu+0x109/0xa50 kernel/irq/handle.c:156 [...] -> #1 (&port_lock_key){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159 serial8250_console_write+0x184/0xa40 drivers/tty/serial/8250/8250_port.c:3198 <-- lock(&port_lock_key); call_console_drivers kernel/printk/printk.c:1819 [inline] console_unlock+0x8cb/0xd00 kernel/printk/printk.c:2504 vprintk_emit+0x1b5/0x470 kernel/printk/printk.c:2024 <-- lock(console_owner); vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 printk+0xba/0xed kernel/printk/printk.c:2084 register_console+0x8b3/0xc10 kernel/printk/printk.c:2829 univ8250_console_init+0x3a/0x46 drivers/tty/serial/8250/8250_core.c:681 console_init+0x49d/0x6d3 kernel/printk/printk.c:2915 start_kernel+0x5e9/0x879 init/main.c:713 secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:241 -> #0 (console_owner){....}-{0:0}: [...] lock_acquire+0x127/0x340 kernel/locking/lockdep.c:4734 console_trylock_spinning kernel/printk/printk.c:1773 ---truncated--- CVE-2022-49441 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49441.html CVE-2022-49441 https://bugzilla.suse.com/1238263 SUSE Bug 1238263 In the Linux kernel, the following vulnerability has been resolved: drivers/base/node.c: fix compaction sysfs file leak Compaction sysfs file is created via compaction_register_node in register_node. But we forgot to remove it in unregister_node. Thus compaction sysfs file is leaked. Using compaction_unregister_node to fix this issue. CVE-2022-49442 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49442.html CVE-2022-49442 https://bugzilla.suse.com/1238243 SUSE Bug 1238243 In the Linux kernel, the following vulnerability has been resolved: nvdimm: Fix firmware activation deadlock scenarios Lockdep reports the following deadlock scenarios for CXL root device power-management, device_prepare(), operations, and device_shutdown() operations for 'nd_region' devices: Chain exists of: &nvdimm_region_key --> &nvdimm_bus->reconfig_mutex --> system_transition_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(system_transition_mutex); lock(&nvdimm_bus->reconfig_mutex); lock(system_transition_mutex); lock(&nvdimm_region_key); Chain exists of: &cxl_nvdimm_bridge_key --> acpi_scan_lock --> &cxl_root_key Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&cxl_root_key); lock(acpi_scan_lock); lock(&cxl_root_key); lock(&cxl_nvdimm_bridge_key); These stem from holding nvdimm_bus_lock() over hibernate_quiet_exec() which walks the entire system device topology taking device_lock() along the way. The nvdimm_bus_lock() is protecting against unregistration, multiple simultaneous ops callers, and preventing activate_show() from racing activate_store(). For the first 2, the lock is redundant. Unregistration already flushes all ops users, and sysfs already prevents multiple threads to be active in an ops handler at the same time. For the last userspace should already be waiting for its last activate_store() to complete, and does not need activate_show() to flush the write side, so this lock usage can be deleted in these attributes. CVE-2022-49446 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49446.html CVE-2022-49446 https://bugzilla.suse.com/1238822 SUSE Bug 1238822 In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Fix list protocols enumeration in the base protocol While enumerating protocols implemented by the SCMI platform using BASE_DISCOVER_LIST_PROTOCOLS, the number of returned protocols is currently validated in an improper way since the check employs a sum between unsigned integers that could overflow and cause the check itself to be silently bypassed if the returned value 'loop_num_ret' is big enough. Fix the validation avoiding the addition. CVE-2022-49451 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49451.html CVE-2022-49451 https://bugzilla.suse.com/1238177 SUSE Bug 1238177 In the Linux kernel, the following vulnerability has been resolved: misc: ocxl: fix possible double free in ocxl_file_register_afu info_release() will be called in device_unregister() when info->dev's reference count is 0. So there is no need to call ocxl_afu_put() and kfree() again. Fix this by adding free_minor() and return to err_unregister error path. CVE-2022-49455 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49455.html CVE-2022-49455 https://bugzilla.suse.com/1238229 SUSE Bug 1238229 In the Linux kernel, the following vulnerability has been resolved: thermal/drivers/broadcom: Fix potential NULL dereference in sr_thermal_probe platform_get_resource() may return NULL, add proper check to avoid potential NULL dereferencing. CVE-2022-49459 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49459.html CVE-2022-49459 https://bugzilla.suse.com/1238046 SUSE Bug 1238046 In the Linux kernel, the following vulnerability has been resolved: PM / devfreq: rk3399_dmc: Disable edev on remove() Otherwise we hit an unablanced enable-count when unbinding the DFI device: [ 1279.659119] ------------[ cut here ]------------ [ 1279.659179] WARNING: CPU: 2 PID: 5638 at drivers/devfreq/devfreq-event.c:360 devfreq_event_remove_edev+0x84/0x8c ... [ 1279.659352] Hardware name: Google Kevin (DT) [ 1279.659363] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO BTYPE=--) [ 1279.659371] pc : devfreq_event_remove_edev+0x84/0x8c [ 1279.659380] lr : devm_devfreq_event_release+0x1c/0x28 ... [ 1279.659571] Call trace: [ 1279.659582] devfreq_event_remove_edev+0x84/0x8c [ 1279.659590] devm_devfreq_event_release+0x1c/0x28 [ 1279.659602] release_nodes+0x1cc/0x244 [ 1279.659611] devres_release_all+0x44/0x60 [ 1279.659621] device_release_driver_internal+0x11c/0x1ac [ 1279.659629] device_driver_detach+0x20/0x2c [ 1279.659641] unbind_store+0x7c/0xb0 [ 1279.659650] drv_attr_store+0x2c/0x40 [ 1279.659663] sysfs_kf_write+0x44/0x58 [ 1279.659672] kernfs_fop_write_iter+0xf4/0x190 [ 1279.659684] vfs_write+0x2b0/0x2e4 [ 1279.659693] ksys_write+0x80/0xec [ 1279.659701] __arm64_sys_write+0x24/0x30 [ 1279.659714] el0_svc_common+0xf0/0x1d8 [ 1279.659724] do_el0_svc_compat+0x28/0x3c [ 1279.659738] el0_svc_compat+0x10/0x1c [ 1279.659746] el0_sync_compat_handler+0xa8/0xcc [ 1279.659758] el0_sync_compat+0x188/0x1c0 [ 1279.659768] ---[ end trace cec200e5094155b4 ]--- CVE-2022-49460 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49460.html CVE-2022-49460 https://bugzilla.suse.com/1238892 SUSE Bug 1238892 In the Linux kernel, the following vulnerability has been resolved: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. a6xx_gmu_init() passes the node to of_find_device_by_node() and of_dma_configure(), of_find_device_by_node() will takes its reference, of_dma_configure() doesn't need the node after usage. Add missing of_node_put() to avoid refcount leak. CVE-2022-49462 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49462.html CVE-2022-49462 https://bugzilla.suse.com/1238123 SUSE Bug 1238123 In the Linux kernel, the following vulnerability has been resolved: blk-throttle: Set BIO_THROTTLED when bio has been throttled 1.In current process, all bio will set the BIO_THROTTLED flag after __blk_throtl_bio(). 2.If bio needs to be throttled, it will start the timer and stop submit bio directly. Bio will submit in blk_throtl_dispatch_work_fn() when the timer expires.But in the current process, if bio is throttled. The BIO_THROTTLED will be set to bio after timer start. If the bio has been completed, it may cause use-after-free blow. BUG: KASAN: use-after-free in blk_throtl_bio+0x12f0/0x2c70 Read of size 2 at addr ffff88801b8902d4 by task fio/26380 dump_stack+0x9b/0xce print_address_description.constprop.6+0x3e/0x60 kasan_report.cold.9+0x22/0x3a blk_throtl_bio+0x12f0/0x2c70 submit_bio_checks+0x701/0x1550 submit_bio_noacct+0x83/0xc80 submit_bio+0xa7/0x330 mpage_readahead+0x380/0x500 read_pages+0x1c1/0xbf0 page_cache_ra_unbounded+0x471/0x6f0 do_page_cache_ra+0xda/0x110 ondemand_readahead+0x442/0xae0 page_cache_async_ra+0x210/0x300 generic_file_buffered_read+0x4d9/0x2130 generic_file_read_iter+0x315/0x490 blkdev_read_iter+0x113/0x1b0 aio_read+0x2ad/0x450 io_submit_one+0xc8e/0x1d60 __se_sys_io_submit+0x125/0x350 do_syscall_64+0x2d/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Allocated by task 26380: kasan_save_stack+0x19/0x40 __kasan_kmalloc.constprop.2+0xc1/0xd0 kmem_cache_alloc+0x146/0x440 mempool_alloc+0x125/0x2f0 bio_alloc_bioset+0x353/0x590 mpage_alloc+0x3b/0x240 do_mpage_readpage+0xddf/0x1ef0 mpage_readahead+0x264/0x500 read_pages+0x1c1/0xbf0 page_cache_ra_unbounded+0x471/0x6f0 do_page_cache_ra+0xda/0x110 ondemand_readahead+0x442/0xae0 page_cache_async_ra+0x210/0x300 generic_file_buffered_read+0x4d9/0x2130 generic_file_read_iter+0x315/0x490 blkdev_read_iter+0x113/0x1b0 aio_read+0x2ad/0x450 io_submit_one+0xc8e/0x1d60 __se_sys_io_submit+0x125/0x350 do_syscall_64+0x2d/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Freed by task 0: kasan_save_stack+0x19/0x40 kasan_set_track+0x1c/0x30 kasan_set_free_info+0x1b/0x30 __kasan_slab_free+0x111/0x160 kmem_cache_free+0x94/0x460 mempool_free+0xd6/0x320 bio_free+0xe0/0x130 bio_put+0xab/0xe0 bio_endio+0x3a6/0x5d0 blk_update_request+0x590/0x1370 scsi_end_request+0x7d/0x400 scsi_io_completion+0x1aa/0xe50 scsi_softirq_done+0x11b/0x240 blk_mq_complete_request+0xd4/0x120 scsi_mq_done+0xf0/0x200 virtscsi_vq_done+0xbc/0x150 vring_interrupt+0x179/0x390 __handle_irq_event_percpu+0xf7/0x490 handle_irq_event_percpu+0x7b/0x160 handle_irq_event+0xcc/0x170 handle_edge_irq+0x215/0xb20 common_interrupt+0x60/0x120 asm_common_interrupt+0x1e/0x40 Fix this by move BIO_THROTTLED set into the queue_lock. CVE-2022-49465 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49465.html CVE-2022-49465 https://bugzilla.suse.com/1238919 SUSE Bug 1238919 https://bugzilla.suse.com/1238920 SUSE Bug 1238920 In the Linux kernel, the following vulnerability has been resolved: drm: msm: fix possible memory leak in mdp5_crtc_cursor_set() drm_gem_object_lookup will call drm_gem_object_get inside. So cursor_bo needs to be put when msm_gem_get_and_pin_iova fails. CVE-2022-49467 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49467.html CVE-2022-49467 https://bugzilla.suse.com/1238815 SUSE Bug 1238815 In the Linux kernel, the following vulnerability has been resolved: ASoC: ti: j721e-evm: Fix refcount leak in j721e_soc_probe_* of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not needed anymore. Add missing of_node_put() to avoid refcount leak. CVE-2022-49473 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49473.html CVE-2022-49473 https://bugzilla.suse.com/1238135 SUSE Bug 1238135 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout Connecting the same socket twice consecutively in sco_sock_connect() could lead to a race condition where two sco_conn objects are created but only one is associated with the socket. If the socket is closed before the SCO connection is established, the timer associated with the dangling sco_conn object won't be canceled. As the sock object is being freed, the use-after-free problem happens when the timer callback function sco_sock_timeout() accesses the socket. Here's the call trace: dump_stack+0x107/0x163 ? refcount_inc+0x1c/ print_address_description.constprop.0+0x1c/0x47e ? refcount_inc+0x1c/0x7b kasan_report+0x13a/0x173 ? refcount_inc+0x1c/0x7b check_memory_region+0x132/0x139 refcount_inc+0x1c/0x7b sco_sock_timeout+0xb2/0x1ba process_one_work+0x739/0xbd1 ? cancel_delayed_work+0x13f/0x13f ? __raw_spin_lock_init+0xf0/0xf0 ? to_kthread+0x59/0x85 worker_thread+0x593/0x70e kthread+0x346/0x35a ? drain_workqueue+0x31a/0x31a ? kthread_bind+0x4b/0x4b ret_from_fork+0x1f/0x30 CVE-2022-49474 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49474.html CVE-2022-49474 https://bugzilla.suse.com/1238071 SUSE Bug 1238071 In the Linux kernel, the following vulnerability has been resolved: spi: spi-fsl-qspi: check return value after calling platform_get_resource_byname() It will cause null-ptr-deref if platform_get_resource_byname() returns NULL, we need check the return value. CVE-2022-49475 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49475.html CVE-2022-49475 https://bugzilla.suse.com/1238617 SUSE Bug 1238617 In the Linux kernel, the following vulnerability has been resolved: media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init Syzbot reported that -1 is used as array index. The problem was in missing validation check. hdw->unit_number is initialized with -1 and then if init table walk fails this value remains unchanged. Since code blindly uses this member for array indexing adding sanity check is the easiest fix for that. hdw->workpoll initialization moved upper to prevent warning in __flush_work. CVE-2022-49478 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49478.html CVE-2022-49478 https://bugzilla.suse.com/1238000 SUSE Bug 1238000 In the Linux kernel, the following vulnerability has been resolved: regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt of_node_get() returns a node with refcount incremented. Calling of_node_put() to drop the reference when not needed anymore. CVE-2022-49481 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49481.html CVE-2022-49481 https://bugzilla.suse.com/1238264 SUSE Bug 1238264 In the Linux kernel, the following vulnerability has been resolved: ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. CVE-2022-49482 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49482.html CVE-2022-49482 https://bugzilla.suse.com/1238543 SUSE Bug 1238543 In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected There is a possibility for mdp5_get_global_state to return -EDEADLK when acquiring the modeset lock, but currently global_state in mdp5_mixer_release doesn't check for if an error is returned. To avoid a NULL dereference error, let's have mdp5_mixer_release check if an error is returned and propagate that error. Patchwork: https://patchwork.freedesktop.org/patch/485181/ CVE-2022-49488 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49488.html CVE-2022-49488 https://bugzilla.suse.com/1238600 SUSE Bug 1238600 In the Linux kernel, the following vulnerability has been resolved: drm/msm/disp/dpu1: set vbif hw config to NULL to avoid use after memory free during pm runtime resume BUG: Unable to handle kernel paging request at virtual address 006b6b6b6b6b6be3 Call trace: dpu_vbif_init_memtypes+0x40/0xb8 dpu_runtime_resume+0xcc/0x1c0 pm_generic_runtime_resume+0x30/0x44 __genpd_runtime_resume+0x68/0x7c genpd_runtime_resume+0x134/0x258 __rpm_callback+0x98/0x138 rpm_callback+0x30/0x88 rpm_resume+0x36c/0x49c __pm_runtime_resume+0x80/0xb0 dpu_core_irq_uninstall+0x30/0xb0 dpu_irq_uninstall+0x18/0x24 msm_drm_uninit+0xd8/0x16c Patchwork: https://patchwork.freedesktop.org/patch/483255/ [DB: fixed Fixes tag] CVE-2022-49489 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49489.html CVE-2022-49489 https://bugzilla.suse.com/1238244 SUSE Bug 1238244 In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Return error code in mdp5_pipe_release when deadlock is detected mdp5_get_global_state runs the risk of hitting a -EDEADLK when acquiring the modeset lock, but currently mdp5_pipe_release doesn't check for if an error is returned. Because of this, there is a possibility of mdp5_pipe_release hitting a NULL dereference error. To avoid this, let's have mdp5_pipe_release check if mdp5_get_global_state returns an error and propogate that error. Changes since v1: - Separated declaration and initialization of *new_state to avoid compiler warning - Fixed some spelling mistakes in commit message Changes since v2: - Return 0 in case where hwpipe is NULL as this is considered normal behavior - Added 2nd patch in series to fix a similar NULL dereference issue in mdp5_mixer_release Patchwork: https://patchwork.freedesktop.org/patch/485179/ CVE-2022-49490 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49490.html CVE-2022-49490 https://bugzilla.suse.com/1238275 SUSE Bug 1238275 In the Linux kernel, the following vulnerability has been resolved: drm/rockchip: vop: fix possible null-ptr-deref in vop_bind() It will cause null-ptr-deref in resource_size(), if platform_get_resource() returns NULL, move calling resource_size() after devm_ioremap_resource() that will check 'res' to avoid null-ptr-deref. CVE-2022-49491 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49491.html CVE-2022-49491 https://bugzilla.suse.com/1238539 SUSE Bug 1238539 In the Linux kernel, the following vulnerability has been resolved: ASoC: rt5645: Fix errorenous cleanup order There is a logic error when removing rt5645 device as the function rt5645_i2c_remove() first cancel the &rt5645->jack_detect_work and delete the &rt5645->btn_check_timer latter. However, since the timer handler rt5645_btn_check_callback() will re-queue the jack_detect_work, this cleanup order is buggy. That is, once the del_timer_sync in rt5645_i2c_remove is concurrently run with the rt5645_btn_check_callback, the canceled jack_detect_work will be rescheduled again, leading to possible use-after-free. This patch fix the issue by placing the del_timer_sync function before the cancel_delayed_work_sync. CVE-2022-49493 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49493.html CVE-2022-49493 https://bugzilla.suse.com/1238939 SUSE Bug 1238939 In the Linux kernel, the following vulnerability has been resolved: drm/msm/hdmi: check return value after calling platform_get_resource_byname() It will cause null-ptr-deref if platform_get_resource_byname() returns NULL, we need check the return value. Patchwork: https://patchwork.freedesktop.org/patch/482992/ CVE-2022-49495 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49495.html CVE-2022-49495 https://bugzilla.suse.com/1237932 SUSE Bug 1237932 In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Check for null pointer of pointer substream before dereferencing it Pointer substream is being dereferenced on the assignment of pointer card before substream is being null checked with the macro PCM_RUNTIME_CHECK. Although PCM_RUNTIME_CHECK calls BUG_ON, it still is useful to perform the the pointer check before card is assigned. CVE-2022-49498 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49498.html CVE-2022-49498 https://bugzilla.suse.com/1238825 SUSE Bug 1238825 In the Linux kernel, the following vulnerability has been resolved: ath9k_htc: fix potential out of bounds access with invalid rxstatus->rs_keyix The "rxstatus->rs_keyix" eventually gets passed to test_bit() so we need to ensure that it is within the bitmap. drivers/net/wireless/ath/ath9k/common.c:46 ath9k_cmn_rx_accept() error: passing untrusted data 'rx_stats->rs_keyix' to 'test_bit()' CVE-2022-49503 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49503.html CVE-2022-49503 https://bugzilla.suse.com/1238868 SUSE Bug 1238868 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Inhibit aborts if external loopback plug is inserted After running a short external loopback test, when the external loopback is removed and a normal cable inserted that is directly connected to a target device, the system oops in the llpfc_set_rrq_active() routine. When the loopback was inserted an FLOGI was transmit. As we're looped back, we receive the FLOGI request. The FLOGI is ABTS'd as we recognize the same wppn thus understand it's a loopback. However, as the ABTS sends address information the port is not set to (fffffe), the ABTS is dropped on the wire. A short 1 frame loopback test is run and completes before the ABTS times out. The looback is unplugged and the new cable plugged in, and the an FLOGI to the new device occurs and completes. Due to a mixup in ref counting the completion of the new FLOGI releases the fabric ndlp. Then the original ABTS completes and references the released ndlp generating the oops. Correct by no-op'ing the ABTS when in loopback mode (it will be dropped anyway). Added a flag to track the mode to recognize when it should be no-op'd. CVE-2022-49504 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49504.html CVE-2022-49504 https://bugzilla.suse.com/1238835 SUSE Bug 1238835 In the Linux kernel, the following vulnerability has been resolved: NFC: NULL out the dev->rfkill to prevent UAF Commit 3e3b5dfcd16a ("NFC: reorder the logic in nfc_{un,}register_device") assumes the device_is_registered() in function nfc_dev_up() will help to check when the rfkill is unregistered. However, this check only take effect when device_del(&dev->dev) is done in nfc_unregister_device(). Hence, the rfkill object is still possible be dereferenced. The crash trace in latest kernel (5.18-rc2): [ 68.760105] ================================================================== [ 68.760330] BUG: KASAN: use-after-free in __lock_acquire+0x3ec1/0x6750 [ 68.760756] Read of size 8 at addr ffff888009c93018 by task fuzz/313 [ 68.760756] [ 68.760756] CPU: 0 PID: 313 Comm: fuzz Not tainted 5.18.0-rc2 #4 [ 68.760756] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 68.760756] Call Trace: [ 68.760756] <TASK> [ 68.760756] dump_stack_lvl+0x57/0x7d [ 68.760756] print_report.cold+0x5e/0x5db [ 68.760756] ? __lock_acquire+0x3ec1/0x6750 [ 68.760756] kasan_report+0xbe/0x1c0 [ 68.760756] ? __lock_acquire+0x3ec1/0x6750 [ 68.760756] __lock_acquire+0x3ec1/0x6750 [ 68.760756] ? lockdep_hardirqs_on_prepare+0x410/0x410 [ 68.760756] ? register_lock_class+0x18d0/0x18d0 [ 68.760756] lock_acquire+0x1ac/0x4f0 [ 68.760756] ? rfkill_blocked+0xe/0x60 [ 68.760756] ? lockdep_hardirqs_on_prepare+0x410/0x410 [ 68.760756] ? mutex_lock_io_nested+0x12c0/0x12c0 [ 68.760756] ? nla_get_range_signed+0x540/0x540 [ 68.760756] ? _raw_spin_lock_irqsave+0x4e/0x50 [ 68.760756] _raw_spin_lock_irqsave+0x39/0x50 [ 68.760756] ? rfkill_blocked+0xe/0x60 [ 68.760756] rfkill_blocked+0xe/0x60 [ 68.760756] nfc_dev_up+0x84/0x260 [ 68.760756] nfc_genl_dev_up+0x90/0xe0 [ 68.760756] genl_family_rcv_msg_doit+0x1f4/0x2f0 [ 68.760756] ? genl_family_rcv_msg_attrs_parse.constprop.0+0x230/0x230 [ 68.760756] ? security_capable+0x51/0x90 [ 68.760756] genl_rcv_msg+0x280/0x500 [ 68.760756] ? genl_get_cmd+0x3c0/0x3c0 [ 68.760756] ? lock_acquire+0x1ac/0x4f0 [ 68.760756] ? nfc_genl_dev_down+0xe0/0xe0 [ 68.760756] ? lockdep_hardirqs_on_prepare+0x410/0x410 [ 68.760756] netlink_rcv_skb+0x11b/0x340 [ 68.760756] ? genl_get_cmd+0x3c0/0x3c0 [ 68.760756] ? netlink_ack+0x9c0/0x9c0 [ 68.760756] ? netlink_deliver_tap+0x136/0xb00 [ 68.760756] genl_rcv+0x1f/0x30 [ 68.760756] netlink_unicast+0x430/0x710 [ 68.760756] ? memset+0x20/0x40 [ 68.760756] ? netlink_attachskb+0x740/0x740 [ 68.760756] ? __build_skb_around+0x1f4/0x2a0 [ 68.760756] netlink_sendmsg+0x75d/0xc00 [ 68.760756] ? netlink_unicast+0x710/0x710 [ 68.760756] ? netlink_unicast+0x710/0x710 [ 68.760756] sock_sendmsg+0xdf/0x110 [ 68.760756] __sys_sendto+0x19e/0x270 [ 68.760756] ? __ia32_sys_getpeername+0xa0/0xa0 [ 68.760756] ? fd_install+0x178/0x4c0 [ 68.760756] ? fd_install+0x195/0x4c0 [ 68.760756] ? kernel_fpu_begin_mask+0x1c0/0x1c0 [ 68.760756] __x64_sys_sendto+0xd8/0x1b0 [ 68.760756] ? lockdep_hardirqs_on+0xbf/0x130 [ 68.760756] ? syscall_enter_from_user_mode+0x1d/0x50 [ 68.760756] do_syscall_64+0x3b/0x90 [ 68.760756] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 68.760756] RIP: 0033:0x7f67fb50e6b3 ... [ 68.760756] RSP: 002b:00007f67fa91fe90 EFLAGS: 00000293 ORIG_RAX: 000000000000002c [ 68.760756] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f67fb50e6b3 [ 68.760756] RDX: 000000000000001c RSI: 0000559354603090 RDI: 0000000000000003 [ 68.760756] RBP: 00007f67fa91ff00 R08: 00007f67fa91fedc R09: 000000000000000c [ 68.760756] R10: 0000000000000000 R11: 0000000000000293 R12: 00007ffe824d496e [ 68.760756] R13: 00007ffe824d496f R14: 00007f67fa120000 R15: 0000000000000003 [ 68.760756] </TASK> [ 68.760756] [ 68.760756] Allocated by task 279: [ 68.760756] kasan_save_stack+0x1e/0x40 [ ---truncated--- CVE-2022-49505 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49505.html CVE-2022-49505 https://bugzilla.suse.com/1238615 SUSE Bug 1238615 In the Linux kernel, the following vulnerability has been resolved: HID: elan: Fix potential double free in elan_input_configured 'input' is a managed resource allocated with devm_input_allocate_device(), so there is no need to call input_free_device() explicitly or there will be a double free. According to the doc of devm_input_allocate_device(): * Managed input devices do not need to be explicitly unregistered or * freed as it will be done automatically when owner device unbinds from * its driver (or binding fails). CVE-2022-49508 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49508.html CVE-2022-49508 https://bugzilla.suse.com/1237940 SUSE Bug 1237940 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: Fix error handling in mt8173_max98090_dev_probe Call of_node_put(platform_node) to avoid refcount leak in the error path. CVE-2022-49514 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49514.html CVE-2022-49514 https://bugzilla.suse.com/1238429 SUSE Bug 1238429 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: Fix missing of_node_put in mt2701_wm8960_machine_probe This node pointer is returned by of_parse_phandle() with refcount incremented in this function. Calling of_node_put() to avoid the refcount leak. CVE-2022-49517 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49517.html CVE-2022-49517 https://bugzilla.suse.com/1237996 SUSE Bug 1237996 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() If no handler is found in lpfc_complete_unsol_iocb() to match the rctl of a received frame, the frame is dropped and resources are leaked. Fix by returning resources when discarding an unhandled frame type. Update lpfc_fc_frame_check() handling of NOP basic link service. CVE-2022-49521 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49521.html CVE-2022-49521 https://bugzilla.suse.com/1238938 SUSE Bug 1238938 In the Linux kernel, the following vulnerability has been resolved: mmc: jz4740: Apply DMA engine limits to maximum segment size Do what is done in other DMA-enabled MMC host drivers (cf. host/mmci.c) and limit the maximum segment size based on the DMA engine's capabilities. This is needed to avoid warnings like the following with CONFIG_DMA_API_DEBUG=y. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 21 at kernel/dma/debug.c:1162 debug_dma_map_sg+0x2f4/0x39c DMA-API: jz4780-dma 13420000.dma-controller: mapping sg segment longer than device claims to support [len=98304] [max=65536] CPU: 0 PID: 21 Comm: kworker/0:1H Not tainted 5.18.0-rc1 #19 Workqueue: kblockd blk_mq_run_work_fn Stack : 81575aec 00000004 80620000 80620000 80620000 805e7358 00000009 801537ac 814c832c 806276e3 806e34b4 80620000 81575aec 00000001 81575ab8 09291444 00000000 00000000 805e7358 81575958 ffffffea 8157596c 00000000 636f6c62 6220646b 80387a70 0000000f 6d5f6b6c 80620000 00000000 81575ba4 00000009 805e170c 80896640 00000001 00010000 00000000 00000000 00006098 806e0000 ... Call Trace: [<80107670>] show_stack+0x84/0x120 [<80528cd8>] __warn+0xb8/0xec [<80528d78>] warn_slowpath_fmt+0x6c/0xb8 [<8016f1d4>] debug_dma_map_sg+0x2f4/0x39c [<80169d4c>] __dma_map_sg_attrs+0xf0/0x118 [<8016a27c>] dma_map_sg_attrs+0x14/0x28 [<804f66b4>] jz4740_mmc_prepare_dma_data+0x74/0xa4 [<804f6714>] jz4740_mmc_pre_request+0x30/0x54 [<804f4ff4>] mmc_blk_mq_issue_rq+0x6e0/0x7bc [<804f5590>] mmc_mq_queue_rq+0x220/0x2d4 [<8038b2c0>] blk_mq_dispatch_rq_list+0x480/0x664 [<80391040>] blk_mq_do_dispatch_sched+0x2dc/0x370 [<80391468>] __blk_mq_sched_dispatch_requests+0xec/0x164 [<80391540>] blk_mq_sched_dispatch_requests+0x44/0x94 [<80387900>] __blk_mq_run_hw_queue+0xb0/0xcc [<80134c14>] process_one_work+0x1b8/0x264 [<80134ff8>] worker_thread+0x2ec/0x3b8 [<8013b13c>] kthread+0x104/0x10c [<80101dcc>] ret_from_kernel_thread+0x14/0x1c ---[ end trace 0000000000000000 ]--- CVE-2022-49522 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49522.html CVE-2022-49522 https://bugzilla.suse.com/1238948 SUSE Bug 1238948 In the Linux kernel, the following vulnerability has been resolved: media: pci: cx23885: Fix the error handling in cx23885_initdev() When the driver fails to call the dma_set_mask(), the driver will get the following splat: [ 55.853884] BUG: KASAN: use-after-free in __process_removed_driver+0x3c/0x240 [ 55.854486] Read of size 8 at addr ffff88810de60408 by task modprobe/590 [ 55.856822] Call Trace: [ 55.860327] __process_removed_driver+0x3c/0x240 [ 55.861347] bus_for_each_dev+0x102/0x160 [ 55.861681] i2c_del_driver+0x2f/0x50 This is because the driver has initialized the i2c related resources in cx23885_dev_setup() but not released them in error handling, fix this bug by modifying the error path that jumps after failing to call the dma_set_mask(). CVE-2022-49524 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49524.html CVE-2022-49524 https://bugzilla.suse.com/1238949 SUSE Bug 1238949 In the Linux kernel, the following vulnerability has been resolved: media: cx25821: Fix the warning when removing the module When removing the module, we will get the following warning: [ 14.746697] remove_proc_entry: removing non-empty directory 'irq/21', leaking at least 'cx25821[1]' [ 14.747449] WARNING: CPU: 4 PID: 368 at fs/proc/generic.c:717 remove_proc_entry+0x389/0x3f0 [ 14.751611] RIP: 0010:remove_proc_entry+0x389/0x3f0 [ 14.759589] Call Trace: [ 14.759792] <TASK> [ 14.759975] unregister_irq_proc+0x14c/0x170 [ 14.760340] irq_free_descs+0x94/0xe0 [ 14.760640] mp_unmap_irq+0xb6/0x100 [ 14.760937] acpi_unregister_gsi_ioapic+0x27/0x40 [ 14.761334] acpi_pci_irq_disable+0x1d3/0x320 [ 14.761688] pci_disable_device+0x1ad/0x380 [ 14.762027] ? _raw_spin_unlock_irqrestore+0x2d/0x60 [ 14.762442] ? cx25821_shutdown+0x20/0x9f0 [cx25821] [ 14.762848] cx25821_finidev+0x48/0xc0 [cx25821] [ 14.763242] pci_device_remove+0x92/0x240 Fix this by freeing the irq before call pci_disable_device(). CVE-2022-49525 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49525.html CVE-2022-49525 https://bugzilla.suse.com/1238022 SUSE Bug 1238022 In the Linux kernel, the following vulnerability has been resolved: md/bitmap: don't set sb values if can't pass sanity check If bitmap area contains invalid data, kernel will crash then mdadm triggers "Segmentation fault". This is cluster-md speical bug. In non-clustered env, mdadm will handle broken metadata case. In clustered array, only kernel space handles bitmap slot info. But even this bug only happened in clustered env, current sanity check is wrong, the code should be changed. How to trigger: (faulty injection) dd if=/dev/zero bs=1M count=1 oflag=direct of=/dev/sda dd if=/dev/zero bs=1M count=1 oflag=direct of=/dev/sdb mdadm -C /dev/md0 -b clustered -e 1.2 -n 2 -l mirror /dev/sda /dev/sdb mdadm -Ss echo aaa > magic.txt == below modifying slot 2 bitmap data == dd if=magic.txt of=/dev/sda seek=16384 bs=1 count=3 <== destroy magic dd if=/dev/zero of=/dev/sda seek=16436 bs=1 count=4 <== ZERO chunksize mdadm -A /dev/md0 /dev/sda /dev/sdb == kernel crashes. mdadm outputs "Segmentation fault" == Reason of kernel crash: In md_bitmap_read_sb (called by md_bitmap_create), bad bitmap magic didn't block chunksize assignment, and zero value made DIV_ROUND_UP_SECTOR_T() trigger "divide error". Crash log: kernel: md: md0 stopped. kernel: md/raid1:md0: not clean -- starting background reconstruction kernel: md/raid1:md0: active with 2 out of 2 mirrors kernel: dlm: ... ... kernel: md-cluster: Joined cluster 44810aba-38bb-e6b8-daca-bc97a0b254aa slot 1 kernel: md0: invalid bitmap file superblock: bad magic kernel: md_bitmap_copy_from_slot can't get bitmap from slot 2 kernel: md-cluster: Could not gather bitmaps from slot 2 kernel: divide error: 0000 [#1] SMP NOPTI kernel: CPU: 0 PID: 1603 Comm: mdadm Not tainted 5.14.6-1-default kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) kernel: RIP: 0010:md_bitmap_create+0x1d1/0x850 [md_mod] kernel: RSP: 0018:ffffc22ac0843ba0 EFLAGS: 00010246 kernel: ... ... kernel: Call Trace: kernel: ? dlm_lock_sync+0xd0/0xd0 [md_cluster 77fe..7a0] kernel: md_bitmap_copy_from_slot+0x2c/0x290 [md_mod 24ea..d3a] kernel: load_bitmaps+0xec/0x210 [md_cluster 77fe..7a0] kernel: md_bitmap_load+0x81/0x1e0 [md_mod 24ea..d3a] kernel: do_md_run+0x30/0x100 [md_mod 24ea..d3a] kernel: md_ioctl+0x1290/0x15a0 [md_mod 24ea....d3a] kernel: ? mddev_unlock+0xaa/0x130 [md_mod 24ea..d3a] kernel: ? blkdev_ioctl+0xb1/0x2b0 kernel: block_ioctl+0x3b/0x40 kernel: __x64_sys_ioctl+0x7f/0xb0 kernel: do_syscall_64+0x59/0x80 kernel: ? exit_to_user_mode_prepare+0x1ab/0x230 kernel: ? syscall_exit_to_user_mode+0x18/0x40 kernel: ? do_syscall_64+0x69/0x80 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae kernel: RIP: 0033:0x7f4a15fa722b kernel: ... ... kernel: ---[ end trace 8afa7612f559c868 ]--- kernel: RIP: 0010:md_bitmap_create+0x1d1/0x850 [md_mod] CVE-2022-49526 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49526.html CVE-2022-49526 https://bugzilla.suse.com/1238030 SUSE Bug 1238030 In the Linux kernel, the following vulnerability has been resolved: media: venus: hfi: avoid null dereference in deinit If venus_probe fails at pm_runtime_put_sync the error handling first calls hfi_destroy and afterwards hfi_core_deinit. As hfi_destroy sets core->ops to NULL, hfi_core_deinit cannot call the core_deinit function anymore. Avoid this null pointer derefence by skipping the call when necessary. CVE-2022-49527 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49527.html CVE-2022-49527 https://bugzilla.suse.com/1238013 SUSE Bug 1238013 In the Linux kernel, the following vulnerability has been resolved: drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes drm_cvt_mode may return NULL and we should check it. This bug is found by syzkaller: FAULT_INJECTION stacktrace: [ 168.567394] FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 1 [ 168.567403] CPU: 1 PID: 6425 Comm: syz Kdump: loaded Not tainted 4.19.90-vhulk2201.1.0.h1035.kasan.eulerosv2r10.aarch64 #1 [ 168.567406] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 168.567408] Call trace: [ 168.567414] dump_backtrace+0x0/0x310 [ 168.567418] show_stack+0x28/0x38 [ 168.567423] dump_stack+0xec/0x15c [ 168.567427] should_fail+0x3ac/0x3d0 [ 168.567437] __should_failslab+0xb8/0x120 [ 168.567441] should_failslab+0x28/0xc0 [ 168.567445] kmem_cache_alloc_trace+0x50/0x640 [ 168.567454] drm_mode_create+0x40/0x90 [ 168.567458] drm_cvt_mode+0x48/0xc78 [ 168.567477] virtio_gpu_conn_get_modes+0xa8/0x140 [virtio_gpu] [ 168.567485] drm_helper_probe_single_connector_modes+0x3a4/0xd80 [ 168.567492] drm_mode_getconnector+0x2e0/0xa70 [ 168.567496] drm_ioctl_kernel+0x11c/0x1d8 [ 168.567514] drm_ioctl+0x558/0x6d0 [ 168.567522] do_vfs_ioctl+0x160/0xf30 [ 168.567525] ksys_ioctl+0x98/0xd8 [ 168.567530] __arm64_sys_ioctl+0x50/0xc8 [ 168.567536] el0_svc_common+0xc8/0x320 [ 168.567540] el0_svc_handler+0xf8/0x160 [ 168.567544] el0_svc+0x10/0x218 KASAN stacktrace: [ 168.567561] BUG: KASAN: null-ptr-deref in virtio_gpu_conn_get_modes+0xb4/0x140 [virtio_gpu] [ 168.567565] Read of size 4 at addr 0000000000000054 by task syz/6425 [ 168.567566] [ 168.567571] CPU: 1 PID: 6425 Comm: syz Kdump: loaded Not tainted 4.19.90-vhulk2201.1.0.h1035.kasan.eulerosv2r10.aarch64 #1 [ 168.567573] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 168.567575] Call trace: [ 168.567578] dump_backtrace+0x0/0x310 [ 168.567582] show_stack+0x28/0x38 [ 168.567586] dump_stack+0xec/0x15c [ 168.567591] kasan_report+0x244/0x2f0 [ 168.567594] __asan_load4+0x58/0xb0 [ 168.567607] virtio_gpu_conn_get_modes+0xb4/0x140 [virtio_gpu] [ 168.567612] drm_helper_probe_single_connector_modes+0x3a4/0xd80 [ 168.567617] drm_mode_getconnector+0x2e0/0xa70 [ 168.567621] drm_ioctl_kernel+0x11c/0x1d8 [ 168.567624] drm_ioctl+0x558/0x6d0 [ 168.567628] do_vfs_ioctl+0x160/0xf30 [ 168.567632] ksys_ioctl+0x98/0xd8 [ 168.567636] __arm64_sys_ioctl+0x50/0xc8 [ 168.567641] el0_svc_common+0xc8/0x320 [ 168.567645] el0_svc_handler+0xf8/0x160 [ 168.567649] el0_svc+0x10/0x218 CVE-2022-49532 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49532.html CVE-2022-49532 https://bugzilla.suse.com/1238925 SUSE Bug 1238925 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Protect memory leak for NPIV ports sending PLOGI_RJT There is a potential memory leak in lpfc_ignore_els_cmpl() and lpfc_els_rsp_reject() that was allocated from NPIV PLOGI_RJT (lpfc_rcv_plogi()'s login_mbox). Check if cmdiocb->context_un.mbox was allocated in lpfc_ignore_els_cmpl(), and then free it back to phba->mbox_mem_pool along with mbox->ctx_buf for service parameters. For lpfc_els_rsp_reject() failure, free both the ctx_buf for service parameters and the login_mbox. CVE-2022-49534 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49534.html CVE-2022-49534 https://bugzilla.suse.com/1238893 SUSE Bug 1238893 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI If lpfc_issue_els_flogi() fails and returns non-zero status, the node reference count is decremented to trigger the release of the nodelist structure. However, if there is a prior registration or dev-loss-evt work pending, the node may be released prematurely. When dev-loss-evt completes, the released node is referenced causing a use-after-free null pointer dereference. Similarly, when processing non-zero ELS PLOGI completion status in lpfc_cmpl_els_plogi(), the ndlp flags are checked for a transport registration before triggering node removal. If dev-loss-evt work is pending, the node may be released prematurely and a subsequent call to lpfc_dev_loss_tmo_handler() results in a use after free ndlp dereference. Add test for pending dev-loss before decrementing the node reference count for FLOGI, PLOGI, PRLI, and ADISC handling. CVE-2022-49535 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49535.html CVE-2022-49535 https://bugzilla.suse.com/1238937 SUSE Bug 1238937 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock During stress I/O tests with 500+ vports, hard LOCKUP call traces are observed. CPU A: native_queued_spin_lock_slowpath+0x192 _raw_spin_lock_irqsave+0x32 lpfc_handle_fcp_err+0x4c6 lpfc_fcp_io_cmd_wqe_cmpl+0x964 lpfc_sli4_fp_handle_cqe+0x266 __lpfc_sli4_process_cq+0x105 __lpfc_sli4_hba_process_cq+0x3c lpfc_cq_poll_hdler+0x16 irq_poll_softirq+0x76 __softirqentry_text_start+0xe4 irq_exit+0xf7 do_IRQ+0x7f CPU B: native_queued_spin_lock_slowpath+0x5b _raw_spin_lock+0x1c lpfc_abort_handler+0x13e scmd_eh_abort_handler+0x85 process_one_work+0x1a7 worker_thread+0x30 kthread+0x112 ret_from_fork+0x1f Diagram of lockup: CPUA CPUB ---- ---- lpfc_cmd->buf_lock phba->hbalock lpfc_cmd->buf_lock phba->hbalock Fix by reordering the taking of the lpfc_cmd->buf_lock and phba->hbalock in lpfc_abort_handler routine so that it tries to take the lpfc_cmd->buf_lock first before phba->hbalock. CVE-2022-49536 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49536.html CVE-2022-49536 https://bugzilla.suse.com/1238838 SUSE Bug 1238838 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix call trace observed during I/O with CMF enabled The following was seen with CMF enabled: BUG: using smp_processor_id() in preemptible code: systemd-udevd/31711 kernel: caller is lpfc_update_cmf_cmd+0x214/0x420 [lpfc] kernel: CPU: 12 PID: 31711 Comm: systemd-udevd kernel: Call Trace: kernel: <TASK> kernel: dump_stack_lvl+0x44/0x57 kernel: check_preemption_disabled+0xbf/0xe0 kernel: lpfc_update_cmf_cmd+0x214/0x420 [lpfc] kernel: lpfc_nvme_fcp_io_submit+0x23b4/0x4df0 [lpfc] this_cpu_ptr() calls smp_processor_id() in a preemptible context. Fix by using per_cpu_ptr() with raw_smp_processor_id() instead. CVE-2022-49537 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49537.html CVE-2022-49537 https://bugzilla.suse.com/1238930 SUSE Bug 1238930 In the Linux kernel, the following vulnerability has been resolved: cifs: fix potential double free during failed mount RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=2088799 CVE-2022-49541 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49541.html CVE-2022-49541 https://bugzilla.suse.com/1238727 SUSE Bug 1238727 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg() In an attempt to log message 0126 with LOG_TRACE_EVENT, the following hard lockup call trace hangs the system. Call Trace: _raw_spin_lock_irqsave+0x32/0x40 lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] lpfc_do_work+0x1485/0x1d70 [lpfc] kthread+0x112/0x130 ret_from_fork+0x1f/0x40 Kernel panic - not syncing: Hard LOCKUP The same CPU tries to claim the phba->port_list_lock twice. Move the cfg_log_verbose checks as part of the lpfc_printf_vlog() and lpfc_printf_log() macros before calling lpfc_dmp_dbg(). There is no need to take the phba->port_list_lock within lpfc_dmp_dbg(). CVE-2022-49542 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49542.html CVE-2022-49542 https://bugzilla.suse.com/1238722 SUSE Bug 1238722 In the Linux kernel, the following vulnerability has been resolved: ipw2x00: Fix potential NULL dereference in libipw_xmit() crypt and crypt->ops could be null, so we need to checking null before dereference CVE-2022-49544 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49544.html CVE-2022-49544 https://bugzilla.suse.com/1238721 SUSE Bug 1238721 In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Cancel pending work at closing a MIDI substream At closing a USB MIDI output substream, there might be still a pending work, which would eventually access the rawmidi runtime object that is being released. For fixing the race, make sure to cancel the pending work at closing. CVE-2022-49545 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49545.html CVE-2022-49545 https://bugzilla.suse.com/1238729 SUSE Bug 1238729 https://bugzilla.suse.com/1238730 SUSE Bug 1238730 In the Linux kernel, the following vulnerability has been resolved: x86/kexec: fix memory leak of elf header buffer This is reported by kmemleak detector: unreferenced object 0xffffc900002a9000 (size 4096): comm "kexec", pid 14950, jiffies 4295110793 (age 373.951s) hex dump (first 32 bytes): 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 .ELF............ 04 00 3e 00 01 00 00 00 00 00 00 00 00 00 00 00 ..>............. backtrace: [<0000000016a8ef9f>] __vmalloc_node_range+0x101/0x170 [<000000002b66b6c0>] __vmalloc_node+0xb4/0x160 [<00000000ad40107d>] crash_prepare_elf64_headers+0x8e/0xcd0 [<0000000019afff23>] crash_load_segments+0x260/0x470 [<0000000019ebe95c>] bzImage64_load+0x814/0xad0 [<0000000093e16b05>] arch_kexec_kernel_image_load+0x1be/0x2a0 [<000000009ef2fc88>] kimage_file_alloc_init+0x2ec/0x5a0 [<0000000038f5a97a>] __do_sys_kexec_file_load+0x28d/0x530 [<0000000087c19992>] do_syscall_64+0x3b/0x90 [<0000000066e063a4>] entry_SYSCALL_64_after_hwframe+0x44/0xae In crash_prepare_elf64_headers(), a buffer is allocated via vmalloc() to store elf headers. While it's not freed back to system correctly when kdump kernel is reloaded or unloaded. Then memory leak is caused. Fix it by introducing x86 specific function arch_kimage_file_post_load_cleanup(), and freeing the buffer there. And also remove the incorrect elf header buffer freeing code. Before calling arch specific kexec_file loading function, the image instance has been initialized. So 'image->elf_headers' must be NULL. It doesn't make sense to free the elf header buffer in the place. Three different people have reported three bugs about the memory leak on x86_64 inside Redhat. CVE-2022-49546 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49546.html CVE-2022-49546 https://bugzilla.suse.com/1238750 SUSE Bug 1238750 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_qca: Use del_timer_sync() before freeing While looking at a crash report on a timer list being corrupted, which usually happens when a timer is freed while still active. This is commonly triggered by code calling del_timer() instead of del_timer_sync() just before freeing. One possible culprit is the hci_qca driver, which does exactly that. Eric mentioned that wake_retrans_timer could be rearmed via the work queue, so also move the destruction of the work queue before del_timer_sync(). CVE-2022-49555 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49555.html CVE-2022-49555 https://bugzilla.suse.com/1238231 SUSE Bug 1238231 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49563 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49563.html CVE-2022-49563 https://bugzilla.suse.com/1238787 SUSE Bug 1238787 https://bugzilla.suse.com/1238788 SUSE Bug 1238788 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49564 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49564.html CVE-2022-49564 https://bugzilla.suse.com/1238789 SUSE Bug 1238789 https://bugzilla.suse.com/1238790 SUSE Bug 1238790 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49566 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49566.html CVE-2022-49566 https://bugzilla.suse.com/1238266 SUSE Bug 1238266 In the Linux kernel, the following vulnerability has been resolved: power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe of_find_matching_node_and_match() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. CVE-2022-49609 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49609.html CVE-2022-49609 https://bugzilla.suse.com/1238241 SUSE Bug 1238241 In the Linux kernel, the following vulnerability has been resolved: KVM: VMX: Prevent RSB underflow before vmenter On VMX, there are some balanced returns between the time the guest's SPEC_CTRL value is written, and the vmenter. Balanced returns (matched by a preceding call) are usually ok, but it's at least theoretically possible an NMI with a deep call stack could empty the RSB before one of the returns. For maximum paranoia, don't allow *any* returns (balanced or otherwise) between the SPEC_CTRL write and the vmenter. [ bp: Fix 32-bit build. ] CVE-2022-49610 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49610.html CVE-2022-49610 https://bugzilla.suse.com/1238952 SUSE Bug 1238952 In the Linux kernel, the following vulnerability has been resolved: x86/speculation: Fill RSB on vmexit for IBRS Prevent RSB underflow/poisoning attacks with RSB. While at it, add a bunch of comments to attempt to document the current state of tribal knowledge about RSB attacks and what exactly is being mitigated. CVE-2022-49611 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49611.html CVE-2022-49611 https://bugzilla.suse.com/1238618 SUSE Bug 1238618 In the Linux kernel, the following vulnerability has been resolved: powerpc/xive/spapr: correct bitmap allocation size kasan detects access beyond the end of the xibm->bitmap allocation: BUG: KASAN: slab-out-of-bounds in _find_first_zero_bit+0x40/0x140 Read of size 8 at addr c00000001d1d0118 by task swapper/0/1 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.19.0-rc2-00001-g90df023b36dd #28 Call Trace: [c00000001d98f770] [c0000000012baab8] dump_stack_lvl+0xac/0x108 (unreliable) [c00000001d98f7b0] [c00000000068faac] print_report+0x37c/0x710 [c00000001d98f880] [c0000000006902c0] kasan_report+0x110/0x354 [c00000001d98f950] [c000000000692324] __asan_load8+0xa4/0xe0 [c00000001d98f970] [c0000000011c6ed0] _find_first_zero_bit+0x40/0x140 [c00000001d98f9b0] [c0000000000dbfbc] xive_spapr_get_ipi+0xcc/0x260 [c00000001d98fa70] [c0000000000d6d28] xive_setup_cpu_ipi+0x1e8/0x450 [c00000001d98fb30] [c000000004032a20] pSeries_smp_probe+0x5c/0x118 [c00000001d98fb60] [c000000004018b44] smp_prepare_cpus+0x944/0x9ac [c00000001d98fc90] [c000000004009f9c] kernel_init_freeable+0x2d4/0x640 [c00000001d98fd90] [c0000000000131e8] kernel_init+0x28/0x1d0 [c00000001d98fe10] [c00000000000cd54] ret_from_kernel_thread+0x5c/0x64 Allocated by task 0: kasan_save_stack+0x34/0x70 __kasan_kmalloc+0xb4/0xf0 __kmalloc+0x268/0x540 xive_spapr_init+0x4d0/0x77c pseries_init_irq+0x40/0x27c init_IRQ+0x44/0x84 start_kernel+0x2a4/0x538 start_here_common+0x1c/0x20 The buggy address belongs to the object at c00000001d1d0118 which belongs to the cache kmalloc-8 of size 8 The buggy address is located 0 bytes inside of 8-byte region [c00000001d1d0118, c00000001d1d0120) The buggy address belongs to the physical page: page:c00c000000074740 refcount:1 mapcount:0 mapping:0000000000000000 index:0xc00000001d1d0558 pfn:0x1d1d flags: 0x7ffff000000200(slab|node=0|zone=0|lastcpupid=0x7ffff) raw: 007ffff000000200 c00000001d0003c8 c00000001d0003c8 c00000001d010480 raw: c00000001d1d0558 0000000001e1000a 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: c00000001d1d0000: fc 00 fc fc fc fc fc fc fc fc fc fc fc fc fc fc c00000001d1d0080: fc fc 00 fc fc fc fc fc fc fc fc fc fc fc fc fc >c00000001d1d0100: fc fc fc 02 fc fc fc fc fc fc fc fc fc fc fc fc ^ c00000001d1d0180: fc fc fc fc 04 fc fc fc fc fc fc fc fc fc fc fc c00000001d1d0200: fc fc fc fc fc 04 fc fc fc fc fc fc fc fc fc fc This happens because the allocation uses the wrong unit (bits) when it should pass (BITS_TO_LONGS(count) * sizeof(long)) or equivalent. With small numbers of bits, the allocated object can be smaller than sizeof(long), which results in invalid accesses. Use bitmap_zalloc() to allocate and initialize the irq bitmap, paired with bitmap_free() for consistency. CVE-2022-49623 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49623.html CVE-2022-49623 https://bugzilla.suse.com/1239040 SUSE Bug 1239040 In the Linux kernel, the following vulnerability has been resolved: ima: Fix potential memory leak in ima_init_crypto() On failure to allocate the SHA1 tfm, IMA fails to initialize and exits without freeing the ima_algo_array. Add the missing kfree() for ima_algo_array to avoid the potential memory leak. CVE-2022-49627 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49627.html CVE-2022-49627 https://bugzilla.suse.com/1237798 SUSE Bug 1237798 In the Linux kernel, the following vulnerability has been resolved: raw: Fix a data-race around sysctl_raw_l3mdev_accept. While reading sysctl_raw_l3mdev_accept, it can be changed concurrently. Thus, we need to add READ_ONCE() to its reader. CVE-2022-49631 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49631.html CVE-2022-49631 https://bugzilla.suse.com/1238814 SUSE Bug 1238814 In the Linux kernel, the following vulnerability has been resolved: sysctl: Fix data races in proc_douintvec_minmax(). A sysctl variable is accessed concurrently, and there is always a chance of data-race. So, all readers and writers need some basic protection to avoid load/store-tearing. This patch changes proc_douintvec_minmax() to use READ_ONCE() and WRITE_ONCE() internally to fix data-races on the sysctl side. For now, proc_douintvec_minmax() itself is tolerant to a data-race, but we still need to add annotations on the other subsystem's side. CVE-2022-49640 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49640.html CVE-2022-49640 https://bugzilla.suse.com/1237782 SUSE Bug 1237782 In the Linux kernel, the following vulnerability has been resolved: sysctl: Fix data races in proc_douintvec(). A sysctl variable is accessed concurrently, and there is always a chance of data-race. So, all readers and writers need some basic protection to avoid load/store-tearing. This patch changes proc_douintvec() to use READ_ONCE() and WRITE_ONCE() internally to fix data-races on the sysctl side. For now, proc_douintvec() itself is tolerant to a data-race, but we still need to add annotations on the other subsystem's side. CVE-2022-49641 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49641.html CVE-2022-49641 https://bugzilla.suse.com/1237831 SUSE Bug 1237831 In the Linux kernel, the following vulnerability has been resolved: ima: Fix a potential integer overflow in ima_appraise_measurement When the ima-modsig is enabled, the rc passed to evm_verifyxattr() may be negative, which may cause the integer overflow problem. CVE-2022-49643 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49643.html CVE-2022-49643 https://bugzilla.suse.com/1238663 SUSE Bug 1238663 In the Linux kernel, the following vulnerability has been resolved: drm/i915: fix a possible refcount leak in intel_dp_add_mst_connector() If drm_connector_init fails, intel_connector_free will be called to take care of proper free. So it is necessary to drop the refcount of port before intel_connector_free. (cherry picked from commit cea9ed611e85d36a05db52b6457bf584b7d969e2) CVE-2022-49644 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49644.html CVE-2022-49644 https://bugzilla.suse.com/1238235 SUSE Bug 1238235 In the Linux kernel, the following vulnerability has been resolved: drm/panfrost: Fix shrinker list corruption by madvise IOCTL Calling madvise IOCTL twice on BO causes memory shrinker list corruption and crashes kernel because BO is already on the list and it's added to the list again, while BO should be removed from the list before it's re-added. Fix it. CVE-2022-49645 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49645.html CVE-2022-49645 https://bugzilla.suse.com/1238435 SUSE Bug 1238435 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix queue selection for mesh/OCB interfaces When using iTXQ, the code assumes that there is only one vif queue for broadcast packets, using the BE queue. Allowing non-BE queue marking violates that assumption and txq->ac == skb_queue_mapping is no longer guaranteed. This can cause issues with queue handling in the driver and also causes issues with the recent ATF change, resulting in an AQL underflow warning. CVE-2022-49646 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49646.html CVE-2022-49646 https://bugzilla.suse.com/1239001 SUSE Bug 1239001 In the Linux kernel, the following vulnerability has been resolved: cgroup: Use separate src/dst nodes when preloading css_sets for migration Each cset (css_set) is pinned by its tasks. When we're moving tasks around across csets for a migration, we need to hold the source and destination csets to ensure that they don't go away while we're moving tasks about. This is done by linking cset->mg_preload_node on either the mgctx->preloaded_src_csets or mgctx->preloaded_dst_csets list. Using the same cset->mg_preload_node for both the src and dst lists was deemed okay as a cset can't be both the source and destination at the same time. Unfortunately, this overloading becomes problematic when multiple tasks are involved in a migration and some of them are identity noop migrations while others are actually moving across cgroups. For example, this can happen with the following sequence on cgroup1: #1> mkdir -p /sys/fs/cgroup/misc/a/b #2> echo $$ > /sys/fs/cgroup/misc/a/cgroup.procs #3> RUN_A_COMMAND_WHICH_CREATES_MULTIPLE_THREADS & #4> PID=$! #5> echo $PID > /sys/fs/cgroup/misc/a/b/tasks #6> echo $PID > /sys/fs/cgroup/misc/a/cgroup.procs the process including the group leader back into a. In this final migration, non-leader threads would be doing identity migration while the group leader is doing an actual one. After #3, let's say the whole process was in cset A, and that after #4, the leader moves to cset B. Then, during #6, the following happens: 1. cgroup_migrate_add_src() is called on B for the leader. 2. cgroup_migrate_add_src() is called on A for the other threads. 3. cgroup_migrate_prepare_dst() is called. It scans the src list. 4. It notices that B wants to migrate to A, so it tries to A to the dst list but realizes that its ->mg_preload_node is already busy. 5. and then it notices A wants to migrate to A as it's an identity migration, it culls it by list_del_init()'ing its ->mg_preload_node and putting references accordingly. 6. The rest of migration takes place with B on the src list but nothing on the dst list. This means that A isn't held while migration is in progress. If all tasks leave A before the migration finishes and the incoming task pins it, the cset will be destroyed leading to use-after-free. This is caused by overloading cset->mg_preload_node for both src and dst preload lists. We wanted to exclude the cset from the src list but ended up inadvertently excluding it from the dst list too. This patch fixes the issue by separating out cset->mg_preload_node into ->mg_src_preload_node and ->mg_dst_preload_node, so that the src and dst preloadings don't interfere with each other. CVE-2022-49647 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49647.html CVE-2022-49647 https://bugzilla.suse.com/1238805 SUSE Bug 1238805 In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Fix memory leak problem This reverts commit 46bbe5c671e06f070428b9be142cc4ee5cedebac. As commit 46bbe5c671e0 ("tracing: fix double free") said, the "double free" problem reported by clang static analyzer is: > In parse_var_defs() if there is a problem allocating > var_defs.expr, the earlier var_defs.name is freed. > This free is duplicated by free_var_defs() which frees > the rest of the list. However, if there is a problem allocating N-th var_defs.expr: + in parse_var_defs(), the freed 'earlier var_defs.name' is actually the N-th var_defs.name; + then in free_var_defs(), the names from 0th to (N-1)-th are freed; IF ALLOCATING PROBLEM HAPPENED HERE!!! -+ \ | 0th 1th (N-1)-th N-th V +-------------+-------------+-----+-------------+----------- var_defs: | name | expr | name | expr | ... | name | expr | name | /// +-------------+-------------+-----+-------------+----------- These two frees don't act on same name, so there was no "double free" problem before. Conversely, after that commit, we get a "memory leak" problem because the above "N-th var_defs.name" is not freed. If enable CONFIG_DEBUG_KMEMLEAK and inject a fault at where the N-th var_defs.expr allocated, then execute on shell like: $ echo 'hist:key=call_site:val=$v1,$v2:v1=bytes_req,v2=bytes_alloc' > \ /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger Then kmemleak reports: unreferenced object 0xffff8fb100ef3518 (size 8): comm "bash", pid 196, jiffies 4295681690 (age 28.538s) hex dump (first 8 bytes): 76 31 00 00 b1 8f ff ff v1...... backtrace: [<0000000038fe4895>] kstrdup+0x2d/0x60 [<00000000c99c049a>] event_hist_trigger_parse+0x206f/0x20e0 [<00000000ae70d2cc>] trigger_process_regex+0xc0/0x110 [<0000000066737a4c>] event_trigger_write+0x75/0xd0 [<000000007341e40c>] vfs_write+0xbb/0x2a0 [<0000000087fde4c2>] ksys_write+0x59/0xd0 [<00000000581e9cdf>] do_syscall_64+0x3a/0x80 [<00000000cf3b065c>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 CVE-2022-49648 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49648.html CVE-2022-49648 https://bugzilla.suse.com/1238278 SUSE Bug 1238278 In the Linux kernel, the following vulnerability has been resolved: xen/netback: avoid entering xenvif_rx_next_skb() with an empty rx queue xenvif_rx_next_skb() is expecting the rx queue not being empty, but in case the loop in xenvif_rx_action() is doing multiple iterations, the availability of another skb in the rx queue is not being checked. This can lead to crashes: [40072.537261] BUG: unable to handle kernel NULL pointer dereference at 0000000000000080 [40072.537407] IP: xenvif_rx_skb+0x23/0x590 [xen_netback] [40072.537534] PGD 0 P4D 0 [40072.537644] Oops: 0000 [#1] SMP NOPTI [40072.537749] CPU: 0 PID: 12505 Comm: v1-c40247-q2-gu Not tainted 4.12.14-122.121-default #1 SLE12-SP5 [40072.537867] Hardware name: HP ProLiant DL580 Gen9/ProLiant DL580 Gen9, BIOS U17 11/23/2021 [40072.537999] task: ffff880433b38100 task.stack: ffffc90043d40000 [40072.538112] RIP: e030:xenvif_rx_skb+0x23/0x590 [xen_netback] [40072.538217] RSP: e02b:ffffc90043d43de0 EFLAGS: 00010246 [40072.538319] RAX: 0000000000000000 RBX: ffffc90043cd7cd0 RCX: 00000000000000f7 [40072.538430] RDX: 0000000000000000 RSI: 0000000000000006 RDI: ffffc90043d43df8 [40072.538531] RBP: 000000000000003f R08: 000077ff80000000 R09: 0000000000000008 [40072.538644] R10: 0000000000007ff0 R11: 00000000000008f6 R12: ffffc90043ce2708 [40072.538745] R13: 0000000000000000 R14: ffffc90043d43ed0 R15: ffff88043ea748c0 [40072.538861] FS: 0000000000000000(0000) GS:ffff880484600000(0000) knlGS:0000000000000000 [40072.538988] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [40072.539088] CR2: 0000000000000080 CR3: 0000000407ac8000 CR4: 0000000000040660 [40072.539211] Call Trace: [40072.539319] xenvif_rx_action+0x71/0x90 [xen_netback] [40072.539429] xenvif_kthread_guest_rx+0x14a/0x29c [xen_netback] Fix that by stopping the loop in case the rx queue becomes empty. CVE-2022-49649 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49649.html CVE-2022-49649 https://bugzilla.suse.com/1238612 SUSE Bug 1238612 In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: Fix refcount leak in ti_dra7_xbar_route_allocate of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not needed anymore. Add missing of_node_put() in to fix this. CVE-2022-49652 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49652.html CVE-2022-49652 https://bugzilla.suse.com/1238871 SUSE Bug 1238871 In the Linux kernel, the following vulnerability has been resolved: usbnet: fix memory leak in error case usbnet_write_cmd_async() mixed up which buffers need to be freed in which error case. v2: add Fixes tag v3: fix uninitialized buf pointer CVE-2022-49657 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49657.html CVE-2022-49657 https://bugzilla.suse.com/1238269 SUSE Bug 1238269 In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_open/close(): fix memory leak The gs_usb driver appears to suffer from a malady common to many USB CAN adapter drivers in that it performs usb_alloc_coherent() to allocate a number of USB request blocks (URBs) for RX, and then later relies on usb_kill_anchored_urbs() to free them, but this doesn't actually free them. As a result, this may be leaking DMA memory that's been used by the driver. This commit is an adaptation of the techniques found in the esd_usb2 driver where a similar design pattern led to a memory leak. It explicitly frees the RX URBs and their DMA memory via a call to usb_free_coherent(). Since the RX URBs were allocated in the gs_can_open(), we remove them in gs_can_close() rather than in the disconnect function as was done in esd_usb2. For more information, see the 928150fad41b ("can: esd_usb2: fix memory leak"). CVE-2022-49661 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49661.html CVE-2022-49661 https://bugzilla.suse.com/1237788 SUSE Bug 1237788 In the Linux kernel, the following vulnerability has been resolved: linux/dim: Fix divide by 0 in RDMA DIM Fix a divide 0 error in rdma_dim_stats_compare() when prev->cpe_ratio == 0. CallTrace: Hardware name: H3C R4900 G3/RS33M2C9S, BIOS 2.00.37P21 03/12/2020 task: ffff880194b78000 task.stack: ffffc90006714000 RIP: 0010:backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: 0018:ffff880c10e83ec0 EFLAGS: 00010202 RAX: 0000000000002710 RBX: ffff88096cd7f780 RCX: 0000000000000064 RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000001 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 000000001d7c6c09 R13: ffff88096cd7f780 R14: ffff880b174fe800 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff880c10e80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000a0965b00 CR3: 000000000200a003 CR4: 00000000007606e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <IRQ> ib_poll_handler+0x43/0x80 [ib_core] irq_poll_softirq+0xae/0x110 __do_softirq+0xd1/0x28c irq_exit+0xde/0xf0 do_IRQ+0x54/0xe0 common_interrupt+0x8f/0x8f </IRQ> ? cpuidle_enter_state+0xd9/0x2a0 ? cpuidle_enter_state+0xc7/0x2a0 ? do_idle+0x170/0x1d0 ? cpu_startup_entry+0x6f/0x80 ? start_secondary+0x1b9/0x210 ? secondary_startup_64+0xa5/0xb0 Code: 0f 87 e1 00 00 00 8b 4c 24 14 44 8b 43 14 89 c8 4d 63 c8 44 29 c0 99 31 d0 29 d0 31 d2 48 98 48 8d 04 80 48 8d 04 80 48 c1 e0 02 <49> f7 f1 48 83 f8 0a 0f 86 c1 00 00 00 44 39 c1 7f 10 48 89 df RIP: backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: ffff880c10e83ec0 CVE-2022-49670 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49670.html CVE-2022-49670 https://bugzilla.suse.com/1238809 SUSE Bug 1238809 In the Linux kernel, the following vulnerability has been resolved: RDMA/cm: Fix memory leak in ib_cm_insert_listen cm_alloc_id_priv() allocates resource for the cm_id_priv. When cm_init_listen() fails it doesn't free it, leading to memory leak. Add the missing error unwind. CVE-2022-49671 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49671.html CVE-2022-49671 https://bugzilla.suse.com/1238823 SUSE Bug 1238823 In the Linux kernel, the following vulnerability has been resolved: dm raid: fix KASAN warning in raid5_add_disks There's a KASAN warning in raid5_add_disk when running the LVM testsuite. The warning happens in the test lvconvert-raid-reshape-linear_to_raid6-single-type.sh. We fix the warning by verifying that rdev->saved_raid_disk is within limits. CVE-2022-49673 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49673.html CVE-2022-49673 https://bugzilla.suse.com/1238933 SUSE Bug 1238933 In the Linux kernel, the following vulnerability has been resolved: dm raid: fix accesses beyond end of raid member array On dm-raid table load (using raid_ctr), dm-raid allocates an array rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks is defined by the number of raid metadata and image tupples passed into the target's constructor. In the case of RAID layout changes being requested, that number can be different from the current number of members for existing raid sets as defined in their superblocks. Example RAID layout changes include: - raid1 legs being added/removed - raid4/5/6/10 number of stripes changed (stripe reshaping) - takeover to higher raid level (e.g. raid5 -> raid6) When accessing array members, rs->raid_disks must be used in control loops instead of the potentially larger value in rs->md.raid_disks. Otherwise it will cause memory access beyond the end of the rs->devs array. Fix this by changing code that is prone to out-of-bounds access. Also fix validate_raid_redundancy() to validate all devices that are added. Also, use braces to help clean up raid_iterate_devices(). The out-of-bounds memory accesses was discovered using KASAN. This commit was verified to pass all LVM2 RAID tests (with KASAN enabled). CVE-2022-49674 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49674.html CVE-2022-49674 https://bugzilla.suse.com/1239041 SUSE Bug 1239041 In the Linux kernel, the following vulnerability has been resolved: soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. In brcmstb_init_sram, it pass dn to of_address_to_resource(), of_address_to_resource() will call of_find_device_by_node() to take reference, so we should release the reference returned by of_find_matching_node(). CVE-2022-49678 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49678.html CVE-2022-49678 https://bugzilla.suse.com/1238821 SUSE Bug 1238821 In the Linux kernel, the following vulnerability has been resolved: iio: trigger: sysfs: fix use-after-free on remove Ensure that the irq_work has completed before the trigger is freed. ================================================================== BUG: KASAN: use-after-free in irq_work_run_list Read of size 8 at addr 0000000064702248 by task python3/25 Call Trace: irq_work_run_list irq_work_tick update_process_times tick_sched_handle tick_sched_timer __hrtimer_run_queues hrtimer_interrupt Allocated by task 25: kmem_cache_alloc_trace iio_sysfs_trig_add dev_attr_store sysfs_kf_write kernfs_fop_write_iter new_sync_write vfs_write ksys_write sys_write Freed by task 25: kfree iio_sysfs_trig_remove dev_attr_store sysfs_kf_write kernfs_fop_write_iter new_sync_write vfs_write ksys_write sys_write ================================================================== CVE-2022-49685 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49685.html CVE-2022-49685 https://bugzilla.suse.com/1237963 SUSE Bug 1237963 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49687 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49687.html CVE-2022-49687 https://bugzilla.suse.com/1238181 SUSE Bug 1238181 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49693 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49693.html CVE-2022-49693 https://bugzilla.suse.com/1237954 SUSE Bug 1237954 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49700 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49700.html CVE-2022-49700 https://bugzilla.suse.com/1238249 SUSE Bug 1238249 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49701 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49701.html CVE-2022-49701 https://bugzilla.suse.com/1237810 SUSE Bug 1237810 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49703 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49703.html CVE-2022-49703 https://bugzilla.suse.com/1238131 SUSE Bug 1238131 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49707 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49707.html CVE-2022-49707 https://bugzilla.suse.com/1239035 SUSE Bug 1239035 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49708 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49708.html CVE-2022-49708 https://bugzilla.suse.com/1238599 SUSE Bug 1238599 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49710 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49710.html CVE-2022-49710 https://bugzilla.suse.com/1238417 SUSE Bug 1238417 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49711 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49711.html CVE-2022-49711 https://bugzilla.suse.com/1238416 SUSE Bug 1238416 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49712 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49712.html CVE-2022-49712 https://bugzilla.suse.com/1238239 SUSE Bug 1238239 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49713 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49713.html CVE-2022-49713 https://bugzilla.suse.com/1238419 SUSE Bug 1238419 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49720 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49720.html CVE-2022-49720 https://bugzilla.suse.com/1238281 SUSE Bug 1238281 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49723 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49723.html CVE-2022-49723 https://bugzilla.suse.com/1237997 SUSE Bug 1237997 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49724 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49724.html CVE-2022-49724 https://bugzilla.suse.com/1238869 SUSE Bug 1238869 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49729 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49729.html CVE-2022-49729 https://bugzilla.suse.com/1239060 SUSE Bug 1239060 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49730 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49730.html CVE-2022-49730 https://bugzilla.suse.com/1239070 SUSE Bug 1239070 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2022-49731 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49731.html CVE-2022-49731 https://bugzilla.suse.com/1239071 SUSE Bug 1239071 In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix race at SNDCTL_DSP_SYNC There is a small race window at snd_pcm_oss_sync() that is called from OSS PCM SNDCTL_DSP_SYNC ioctl; namely the function calls snd_pcm_oss_make_ready() at first, then takes the params_lock mutex for the rest. When the stream is set up again by another thread between them, it leads to inconsistency, and may result in unexpected results such as NULL dereference of OSS buffer as a fuzzer spotted recently. The fix is simply to cover snd_pcm_oss_make_ready() call into the same params_lock mutex with snd_pcm_oss_make_ready_locked() variant. CVE-2022-49733 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49733.html CVE-2022-49733 https://bugzilla.suse.com/1238454 SUSE Bug 1238454 In the Linux kernel, the following vulnerability has been resolved: gfs2: Always check inode size of inline inodes Check if the inode size of stuffed (inline) inodes is within the allowed range when reading inodes from disk (gfs2_dinode_in()). This prevents us from on-disk corruption. The two checks in stuffed_readpage() and gfs2_unstuffer_page() that just truncate inline data to the maximum allowed size don't actually make sense, and they can be removed now as well. CVE-2022-49739 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2022-49739.html CVE-2022-49739 https://bugzilla.suse.com/1240207 SUSE Bug 1240207 A use-after-free vulnerability was found in iscsi_sw_tcp_session_create in drivers/scsi/iscsi_tcp.c in SCSI sub-component in the Linux Kernel. In this flaw an attacker could leak kernel internal information. CVE-2023-2162 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2023-2162.html CVE-2023-2162 https://bugzilla.suse.com/1210647 SUSE Bug 1210647 https://bugzilla.suse.com/1210662 SUSE Bug 1210662 https://bugzilla.suse.com/1213841 SUSE Bug 1213841 https://bugzilla.suse.com/1213842 SUSE Bug 1213842 https://bugzilla.suse.com/1214128 SUSE Bug 1214128 https://bugzilla.suse.com/1222212 SUSE Bug 1222212 A use-after-free flaw was found in vcs_read in drivers/tty/vt/vc_screen.c in vc_screen in the Linux Kernel. This issue may allow an attacker with local user access to cause a system crash or leak internal kernel information. CVE-2023-3567 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2023-3567.html CVE-2023-3567 https://bugzilla.suse.com/1213167 SUSE Bug 1213167 https://bugzilla.suse.com/1213244 SUSE Bug 1213244 https://bugzilla.suse.com/1213842 SUSE Bug 1213842 https://bugzilla.suse.com/1215674 SUSE Bug 1215674 https://bugzilla.suse.com/1217444 SUSE Bug 1217444 https://bugzilla.suse.com/1217531 SUSE Bug 1217531 In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: fix ->anon_vma race If an ->anon_vma is attached to the VMA, collapse_and_free_pmd() requires it to be locked. Page table traversal is allowed under any one of the mmap lock, the anon_vma lock (if the VMA is associated with an anon_vma), and the mapping lock (if the VMA is associated with a mapping); and so to be able to remove page tables, we must hold all three of them. retract_page_tables() bails out if an ->anon_vma is attached, but does this check before holding the mmap lock (as the comment above the check explains). If we racily merged an existing ->anon_vma (shared with a child process) from a neighboring VMA, subsequent rmap traversals on pages belonging to the child will be able to see the page tables that we are concurrently removing while assuming that nothing else can access them. Repeat the ->anon_vma check once we hold the mmap lock to ensure that there really is no concurrent page table access. Hitting this bug causes a lockdep warning in collapse_and_free_pmd(), in the line "lockdep_assert_held_write(&vma->anon_vma->root->rwsem)". It can also lead to use-after-free access. CVE-2023-52935 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2023-52935.html CVE-2023-52935 https://bugzilla.suse.com/1240276 SUSE Bug 1240276 In the Linux kernel, the following vulnerability has been resolved: vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF After a call to console_unlock() in vcs_read() the vc_data struct can be freed by vc_deallocate(). Because of that, the struct vc_data pointer load must be done at the top of while loop in vcs_read() to avoid a UAF when vcs_size() is called. Syzkaller reported a UAF in vcs_size(). BUG: KASAN: use-after-free in vcs_size (drivers/tty/vt/vc_screen.c:215) Read of size 4 at addr ffff8881137479a8 by task 4a005ed81e27e65/1537 CPU: 0 PID: 1537 Comm: 4a005ed81e27e65 Not tainted 6.2.0-rc5 #1 Hardware name: Red Hat KVM, BIOS 1.15.0-2.module Call Trace: <TASK> __asan_report_load4_noabort (mm/kasan/report_generic.c:350) vcs_size (drivers/tty/vt/vc_screen.c:215) vcs_read (drivers/tty/vt/vc_screen.c:415) vfs_read (fs/read_write.c:468 fs/read_write.c:450) ... </TASK> Allocated by task 1191: ... kmalloc_trace (mm/slab_common.c:1069) vc_allocate (./include/linux/slab.h:580 ./include/linux/slab.h:720 drivers/tty/vt/vt.c:1128 drivers/tty/vt/vt.c:1108) con_install (drivers/tty/vt/vt.c:3383) tty_init_dev (drivers/tty/tty_io.c:1301 drivers/tty/tty_io.c:1413 drivers/tty/tty_io.c:1390) tty_open (drivers/tty/tty_io.c:2080 drivers/tty/tty_io.c:2126) chrdev_open (fs/char_dev.c:415) do_dentry_open (fs/open.c:883) vfs_open (fs/open.c:1014) ... Freed by task 1548: ... kfree (mm/slab_common.c:1021) vc_port_destruct (drivers/tty/vt/vt.c:1094) tty_port_destructor (drivers/tty/tty_port.c:296) tty_port_put (drivers/tty/tty_port.c:312) vt_disallocate_all (drivers/tty/vt/vt_ioctl.c:662 (discriminator 2)) vt_ioctl (drivers/tty/vt/vt_ioctl.c:903) tty_ioctl (drivers/tty/tty_io.c:2776) ... The buggy address belongs to the object at ffff888113747800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 424 bytes inside of 1024-byte region [ffff888113747800, ffff888113747c00) The buggy address belongs to the physical page: page:00000000b3fe6c7c refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x113740 head:00000000b3fe6c7c order:3 compound_mapcount:0 subpages_mapcount:0 compound_pincount:0 anon flags: 0x17ffffc0010200(slab|head|node=0|zone=2|lastcpupid=0x1fffff) raw: 0017ffffc0010200 ffff888100042dc0 0000000000000000 dead000000000001 raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888113747880: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888113747900: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb > ffff888113747980: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888113747a00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888113747a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== Disabling lock debugging due to kernel taint CVE-2023-52973 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2023-52973.html CVE-2023-52973 https://bugzilla.suse.com/1240218 SUSE Bug 1240218 In the Linux kernel, the following vulnerability has been resolved: scsi: iscsi_tcp: Fix UAF during login when accessing the shost ipaddress If during iscsi_sw_tcp_session_create() iscsi_tcp_r2tpool_alloc() fails, userspace could be accessing the host's ipaddress attr. If we then free the session via iscsi_session_teardown() while userspace is still accessing the session we will hit a use after free bug. Set the tcp_sw_host->session after we have completed session creation and can no longer fail. CVE-2023-52974 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2023-52974.html CVE-2023-52974 https://bugzilla.suse.com/1240213 SUSE Bug 1240213 In the Linux kernel, the following vulnerability has been resolved: netlink: prevent potential spectre v1 gadgets Most netlink attributes are parsed and validated from __nla_validate_parse() or validate_nla() u16 type = nla_type(nla); if (type == 0 || type > maxtype) { /* error or continue */ } @type is then used as an array index and can be used as a Spectre v1 gadget. array_index_nospec() can be used to prevent leaking content of kernel memory to malicious users. This should take care of vast majority of netlink uses, but an audit is needed to take care of others where validation is not yet centralized in core netlink functions. CVE-2023-53000 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2023-53000.html CVE-2023-53000 https://bugzilla.suse.com/1240227 SUSE Bug 1240227 In the Linux kernel, the following vulnerability has been resolved: HID: betop: check shape of output reports betopff_init() only checks the total sum of the report counts for each report field to be at least 4, but hid_betopff_play() expects 4 report fields. A device advertising an output report with one field and 4 report counts would pass the check but crash the kernel with a NULL pointer dereference in hid_betopff_play(). CVE-2023-53015 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2023-53015.html CVE-2023-53015 https://bugzilla.suse.com/1240288 SUSE Bug 1240288 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2023-53024 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2023-53024.html CVE-2023-53024 https://bugzilla.suse.com/1240272 SUSE Bug 1240272 In the Linux kernel, the following vulnerability has been resolved: media: cx24116: prevent overflows on SNR calculus as reported by Coverity, if reading SNR registers fail, a negative number will be returned, causing an underflow when reading SNR registers. Prevent that. CVE-2024-50290 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2024-50290.html CVE-2024-50290 https://bugzilla.suse.com/1225742 SUSE Bug 1225742 https://bugzilla.suse.com/1233479 SUSE Bug 1233479 https://bugzilla.suse.com/1233681 SUSE Bug 1233681 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2024-53063 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2024-53063.html CVE-2024-53063 https://bugzilla.suse.com/1225742 SUSE Bug 1225742 https://bugzilla.suse.com/1233557 SUSE Bug 1233557 https://bugzilla.suse.com/1233619 SUSE Bug 1233619 In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free of kernel socket in cleanup_bearer(). syzkaller reported a use-after-free of UDP kernel socket in cleanup_bearer() without repro. [0][1] When bearer_disable() calls tipc_udp_disable(), cleanup of the UDP kernel socket is deferred by work calling cleanup_bearer(). tipc_exit_net() waits for such works to finish by checking tipc_net(net)->wq_count. However, the work decrements the count too early before releasing the kernel socket, unblocking cleanup_net() and resulting in use-after-free. Let's move the decrement after releasing the socket in cleanup_bearer(). [0]: ref_tracker: net notrefcnt@000000009b3d1faf has 1/1 users at sk_alloc+0x438/0x608 inet_create+0x4c8/0xcb0 __sock_create+0x350/0x6b8 sock_create_kern+0x58/0x78 udp_sock_create4+0x68/0x398 udp_sock_create+0x88/0xc8 tipc_udp_enable+0x5e8/0x848 __tipc_nl_bearer_enable+0x84c/0xed8 tipc_nl_bearer_enable+0x38/0x60 genl_family_rcv_msg_doit+0x170/0x248 genl_rcv_msg+0x400/0x5b0 netlink_rcv_skb+0x1dc/0x398 genl_rcv+0x44/0x68 netlink_unicast+0x678/0x8b0 netlink_sendmsg+0x5e4/0x898 ____sys_sendmsg+0x500/0x830 [1]: BUG: KMSAN: use-after-free in udp_hashslot include/net/udp.h:85 [inline] BUG: KMSAN: use-after-free in udp_lib_unhash+0x3b8/0x930 net/ipv4/udp.c:1979 udp_hashslot include/net/udp.h:85 [inline] udp_lib_unhash+0x3b8/0x930 net/ipv4/udp.c:1979 sk_common_release+0xaf/0x3f0 net/core/sock.c:3820 inet_release+0x1e0/0x260 net/ipv4/af_inet.c:437 inet6_release+0x6f/0xd0 net/ipv6/af_inet6.c:489 __sock_release net/socket.c:658 [inline] sock_release+0xa0/0x210 net/socket.c:686 cleanup_bearer+0x42d/0x4c0 net/tipc/udp_media.c:819 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xcaf/0x1c90 kernel/workqueue.c:3310 worker_thread+0xf6c/0x1510 kernel/workqueue.c:3391 kthread+0x531/0x6b0 kernel/kthread.c:389 ret_from_fork+0x60/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244 Uninit was created at: slab_free_hook mm/slub.c:2269 [inline] slab_free mm/slub.c:4580 [inline] kmem_cache_free+0x207/0xc40 mm/slub.c:4682 net_free net/core/net_namespace.c:454 [inline] cleanup_net+0x16f2/0x19d0 net/core/net_namespace.c:647 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xcaf/0x1c90 kernel/workqueue.c:3310 worker_thread+0xf6c/0x1510 kernel/workqueue.c:3391 kthread+0x531/0x6b0 kernel/kthread.c:389 ret_from_fork+0x60/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244 CPU: 0 UID: 0 PID: 54 Comm: kworker/0:2 Not tainted 6.12.0-rc1-00131-gf66ebf37d69c #7 91723d6f74857f70725e1583cba3cf4adc716cfa Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: events cleanup_bearer CVE-2024-56642 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2024-56642.html CVE-2024-56642 https://bugzilla.suse.com/1235433 SUSE Bug 1235433 https://bugzilla.suse.com/1235434 SUSE Bug 1235434 In the Linux kernel, the following vulnerability has been resolved: can: hi311x: hi3110_can_ist(): fix potential use-after-free The commit a22bd630cfff ("can: hi311x: do not report txerr and rxerr during bus-off") removed the reporting of rxerr and txerr even in case of correct operation (i. e. not bus-off). The error count information added to the CAN frame after netif_rx() is a potential use after free, since there is no guarantee that the skb is in the same state. It might be freed or reused. Fix the issue by postponing the netif_rx() call in case of txerr and rxerr reporting. CVE-2024-56651 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2024-56651.html CVE-2024-56651 https://bugzilla.suse.com/1235528 SUSE Bug 1235528 https://bugzilla.suse.com/1236570 SUSE Bug 1236570 In the Linux kernel, the following vulnerability has been resolved: net_sched: sch_sfq: don't allow 1 packet limit The current implementation does not work correctly with a limit of 1. iproute2 actually checks for this and this patch adds the check in kernel as well. This fixes the following syzkaller reported crash: UBSAN: array-index-out-of-bounds in net/sched/sch_sfq.c:210:6 index 65535 is out of range for type 'struct sfq_head[128]' CPU: 0 PID: 2569 Comm: syz-executor101 Not tainted 5.10.0-smp-DEV #1 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x125/0x19f lib/dump_stack.c:120 ubsan_epilogue lib/ubsan.c:148 [inline] __ubsan_handle_out_of_bounds+0xed/0x120 lib/ubsan.c:347 sfq_link net/sched/sch_sfq.c:210 [inline] sfq_dec+0x528/0x600 net/sched/sch_sfq.c:238 sfq_dequeue+0x39b/0x9d0 net/sched/sch_sfq.c:500 sfq_reset+0x13/0x50 net/sched/sch_sfq.c:525 qdisc_reset+0xfe/0x510 net/sched/sch_generic.c:1026 tbf_reset+0x3d/0x100 net/sched/sch_tbf.c:319 qdisc_reset+0xfe/0x510 net/sched/sch_generic.c:1026 dev_reset_queue+0x8c/0x140 net/sched/sch_generic.c:1296 netdev_for_each_tx_queue include/linux/netdevice.h:2350 [inline] dev_deactivate_many+0x6dc/0xc20 net/sched/sch_generic.c:1362 __dev_close_many+0x214/0x350 net/core/dev.c:1468 dev_close_many+0x207/0x510 net/core/dev.c:1506 unregister_netdevice_many+0x40f/0x16b0 net/core/dev.c:10738 unregister_netdevice_queue+0x2be/0x310 net/core/dev.c:10695 unregister_netdevice include/linux/netdevice.h:2893 [inline] __tun_detach+0x6b6/0x1600 drivers/net/tun.c:689 tun_detach drivers/net/tun.c:705 [inline] tun_chr_close+0x104/0x1b0 drivers/net/tun.c:3640 __fput+0x203/0x840 fs/file_table.c:280 task_work_run+0x129/0x1b0 kernel/task_work.c:185 exit_task_work include/linux/task_work.h:33 [inline] do_exit+0x5ce/0x2200 kernel/exit.c:931 do_group_exit+0x144/0x310 kernel/exit.c:1046 __do_sys_exit_group kernel/exit.c:1057 [inline] __se_sys_exit_group kernel/exit.c:1055 [inline] __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1055 do_syscall_64+0x6c/0xd0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7fe5e7b52479 Code: Unable to access opcode bytes at RIP 0x7fe5e7b5244f. RSP: 002b:00007ffd3c800398 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe5e7b52479 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000 RBP: 00007fe5e7bcd2d0 R08: ffffffffffffffb8 R09: 0000000000000014 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fe5e7bcd2d0 R13: 0000000000000000 R14: 00007fe5e7bcdd20 R15: 00007fe5e7b24270 The crash can be also be reproduced with the following (with a tc recompiled to allow for sfq limits of 1): tc qdisc add dev dummy0 handle 1: root tbf rate 1Kbit burst 100b lat 1s ../iproute2-6.9.0/tc/tc qdisc add dev dummy0 handle 2: parent 1:10 sfq limit 1 ifconfig dummy0 up ping -I dummy0 -f -c2 -W0.1 8.8.8.8 sleep 1 Scenario that triggers the crash: * the first packet is sent and queued in TBF and SFQ; qdisc qlen is 1 * TBF dequeues: it peeks from SFQ which moves the packet to the gso_skb list and keeps qdisc qlen set to 1. TBF is out of tokens so it schedules itself for later. * the second packet is sent and TBF tries to queues it to SFQ. qdisc qlen is now 2 and because the SFQ limit is 1 the packet is dropped by SFQ. At this point qlen is 1, and all of the SFQ slots are empty, however q->tail is not NULL. At this point, assuming no more packets are queued, when sch_dequeue runs again it will decrement the qlen for the current empty slot causing an underflow and the subsequent out of bounds access. CVE-2024-57996 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2024-57996.html CVE-2024-57996 https://bugzilla.suse.com/1239076 SUSE Bug 1239076 https://bugzilla.suse.com/1239077 SUSE Bug 1239077 In the Linux kernel, the following vulnerability has been resolved: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() In 'wlc_phy_iqcal_gainparams_nphy()', add gain range check to WARN() instead of possible out-of-bounds 'tbl_iqcal_gainparams_nphy' access. Compile tested only. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2024-58014 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2024-58014.html CVE-2024-58014 https://bugzilla.suse.com/1239109 SUSE Bug 1239109 https://bugzilla.suse.com/1239110 SUSE Bug 1239110 In the Linux kernel, the following vulnerability has been resolved: partitions: mac: fix handling of bogus partition table Fix several issues in partition probing: - The bailout for a bad partoffset must use put_dev_sector(), since the preceding read_part_sector() succeeded. - If the partition table claims a silly sector size like 0xfff bytes (which results in partition table entries straddling sector boundaries), bail out instead of accessing out-of-bounds memory. - We must not assume that the partition table contains proper NUL termination - use strnlen() and strncmp() instead of strlen() and strcmp(). CVE-2025-21772 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2025-21772.html CVE-2025-21772 https://bugzilla.suse.com/1238911 SUSE Bug 1238911 https://bugzilla.suse.com/1238912 SUSE Bug 1238912 In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() It malicious user provides a small pptable through sysfs and then a bigger pptable, it may cause buffer overflow attack in function smu_sys_set_pp_table(). CVE-2025-21780 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.205.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.205.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20251194-1/ https://www.suse.com/security/cve/CVE-2025-21780.html CVE-2025-21780 https://bugzilla.suse.com/1239115 SUSE Bug 1239115 https://bugzilla.suse.com/1239116 SUSE Bug 1239116