Security update for the Linux Kernel SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2024:2381-1 Final 1 1 2024-07-10T06:10:16Z current 2024-07-10T06:10:16Z 2024-07-10T06:10:16Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for the Linux Kernel The SUSE Linux Enterprise 12 SP5 RT kernel was updated to receive various security bugfixes. The following security bugs were fixed: - CVE-2021-47103: net: sock: preserve kabi for sock (bsc#1221010). - CVE-2021-47191: Fix out-of-bound read in resp_readcap16() (bsc#1222866). - CVE-2021-47267: usb: fix various gadget panics on 10gbps cabling (bsc#1224993). - CVE-2021-47270: usb: fix various gadgets null ptr deref on 10gbps cabling (bsc#1224997). - CVE-2021-47293: net/sched: act_skbmod: Skip non-Ethernet packets (bsc#1224978). - CVE-2021-47294: netrom: Decrease sock refcount when sock timers expire (bsc#1224977). - CVE-2021-47297: net: fix uninit-value in caif_seqpkt_sendmsg (bsc#1224976). - CVE-2021-47309: net: validate lwtstate->data before returning from skb_tunnel_info() (bsc#1224967). - CVE-2021-47354: drm/sched: Avoid data corruptions (bsc#1225140) - CVE-2021-47372: net: macb: fix use after free on rmmod (bsc#1225184). - CVE-2021-47379: blk-cgroup: fix UAF by grabbing blkcg lock before destroying blkg pd (bsc#1225203). - CVE-2021-47407: KVM: x86: Handle SRCU initialization failure during page track init (bsc#1225306). - CVE-2021-47418: net_sched: fix NULL deref in fifo_set_limit() (bsc#1225337). - CVE-2021-47434: xhci: Fix commad ring abort, write all 64 bits to CRCR register (bsc#1225232). - CVE-2021-47445: drm/msm: Fix null pointer dereference on pointer edp (bsc#1225261) - CVE-2021-47518: nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done (bsc#1225372). - CVE-2021-47544: tcp: fix page frag corruption on page fault (bsc#1225463). - CVE-2021-47566: Fix clearing user buffer by properly using clear_user() (bsc#1225514). - CVE-2021-47571: staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() (bsc#1225518). - CVE-2021-47587: net: systemport: Add global locking for descriptor lifecycle (bsc#1226567). - CVE-2021-47602: mac80211: track only QoS data frames for admission control (bsc#1226554). - CVE-2021-47609: firmware: arm_scpi: Fix string overflow in SCPI genpd driver (bsc#1226562) - CVE-2022-48732: drm/nouveau: fix off by one in BIOS boundary checking (bsc#1226716) - CVE-2022-48733: btrfs: fix use-after-free after failure to create a snapshot (bsc#1226718). - CVE-2022-48740: selinux: fix double free of cond_list on error paths (bsc#1226699). - CVE-2022-48743: net: amd-xgbe: Fix skb data length underflow (bsc#1226705). - CVE-2022-48756: drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable (bsc#1226698) - CVE-2022-48759: rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev (bsc#1226711). - CVE-2022-48761: usb: xhci-plat: fix crash when suspend if remote wake enable (bsc#1226701). - CVE-2022-48772: media: lgdt3306a: Add a check against null-pointer-def (bsc#1226976). - CVE-2023-24023: Bluetooth: Add more enc key size check (bsc#1218148). - CVE-2023-52622: ext4: avoid online resizing failures due to oversized flex bg (bsc#1222080). - CVE-2023-52675: powerpc/imc-pmu: Add a null pointer check in update_events_in_group() (bsc#1224504). - CVE-2023-52737: btrfs: lock the inode in shared mode before starting fiemap (bsc#1225484). - CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487). - CVE-2023-52754: media: imon: fix access to invalid resource for the second interface (bsc#1225490). - CVE-2023-52757: Fixed potential deadlock when releasing mids (bsc#1225548). - CVE-2023-52762: virtio-blk: fix implicit overflow on virtio_max_dma_size (bsc#1225573). - CVE-2023-52764: media: gspca: cpia1: shift-out-of-bounds in set_flicker (bsc#1225571). - CVE-2023-52784: bonding: stop the device in bond_setup_by_slave() (bsc#1224946). - CVE-2023-52832: wifi: mac80211: do not return unset power in ieee80211_get_tx_power() (bsc#1225577). - CVE-2023-52834: atl1c: Work around the DMA RX overflow issue (bsc#1225599). - CVE-2023-52835: perf/core: Bail out early if the request AUX area is out of bound (bsc#1225602). - CVE-2023-52843: llc: verify mac len before reading mac header (bsc#1224951). - CVE-2023-52845: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (bsc#1225585). - CVE-2023-52855: usb: dwc2: fix possible NULL pointer dereference caused by driver concurrency (bsc#1225583). - CVE-2023-52881: tcp: do not accept ACK of bytes we never sent (bsc#1225611). - CVE-2024-26633: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (bsc#1221647). - CVE-2024-26641: ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() (bsc#1221654). - CVE-2024-26679: Fixed read sk->sk_family once in inet_recv_error() (bsc#1222385). - CVE-2024-26687: Fixed xen/events close evtchn after mapping cleanup (bsc#1222435). - CVE-2024-26720: mm: Avoid overflows in dirty throttling logic (bsc#1222364). - CVE-2024-26813: vfio/platform: Create persistent IRQ handlers (bsc#1222809). - CVE-2024-26863: hsr: Fix uninit-value access in hsr_get_node() (bsc#1223021). - CVE-2024-26894: ACPI: processor_idle: Fix memory leak in acpi_processor_power_exit() (bsc#1223043). - CVE-2024-26928: Fixed potential UAF in cifs_debug_files_proc_show() (bsc#1223532). - CVE-2024-26973: fat: fix uninitialized field in nostale filehandles (bsc#1223641). - CVE-2024-27399: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout (bsc#1224177). - CVE-2024-27410: Reject iftype change with mesh ID change (bsc#1224432). - CVE-2024-35247: fpga: region: add owner module and take its refcount (bsc#1226948). - CVE-2024-35807: ext4: fix corruption during on-line resize (bsc#1224735). - CVE-2024-35822: usb: udc: remove warning when queue disabled ep (bsc#1224739). - CVE-2024-35835: net/mlx5e: fix a double-free in arfs_create_groups (bsc#1224605). - CVE-2024-35862: Fixed potential UAF in smb2_is_network_name_deleted() (bsc#1224764). - CVE-2024-35863: Fixed potential UAF in is_valid_oplock_break() (bsc#1224763). - CVE-2024-35864: Fixed potential UAF in smb2_is_valid_lease_break() (bsc#1224765). - CVE-2024-35865: Fixed potential UAF in smb2_is_valid_oplock_break() (bsc#1224668). - CVE-2024-35867: Fixed potential UAF in cifs_stats_proc_show() (bsc#1224664). - CVE-2024-35868: Fixed potential UAF in cifs_stats_proc_write() (bsc#1224678). - CVE-2024-35870: Fixed UAF in smb2_reconnect_server() (bsc#1224672). - CVE-2024-35886: ipv6: Fix infinite recursion in fib6_dump_done() (bsc#1224670). - CVE-2024-35922: fbmon: prevent division by zero in fb_videomode_from_videomode() (bsc#1224660) - CVE-2024-35925: block: prevent division by zero in blk_rq_stat_sum() (bsc#1224661). - CVE-2024-35930: scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc() (bsc#1224651). - CVE-2024-35950: drm/client: Fully protect modes with dev->mode_config.mutex (bsc#1224703). - CVE-2024-35956: Fixed qgroup prealloc rsv leak in subvolume operations (bsc#1224674) - CVE-2024-35958: net: ena: Fix incorrect descriptor free behavior (bsc#1224677). - CVE-2024-35960: net/mlx5: Properly link new fs rules into the tree (bsc#1224588). - CVE-2024-35976: Validate user input for XDP_{UMEM|COMPLETION}_FILL_RING (bsc#1224575). - CVE-2024-35979: raid1: fix use-after-free for original bio in raid1_write_request() (bsc#1224572). - CVE-2024-35997: Remove I2C_HID_READ_PENDING flag to prevent lock-up (bsc#1224552). - CVE-2024-35998: Fixed lock ordering potential deadlock in cifs_sync_mid_result (bsc#1224549). - CVE-2024-36016: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() (bsc#1225642). - CVE-2024-36017: rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation (bsc#1225681). - CVE-2024-36479: fpga: bridge: add owner module and take its refcount (bsc#1226949). - CVE-2024-36592: scsi: lpfc: Move NPIV's transport unregistration to after resource clean up (bsc#1225898). - CVE-2024-36880: Bluetooth: qca: add missing firmware sanity checks (bsc#1225722). - CVE-2024-36894: usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete (bsc#1225749). - CVE-2024-36915: nfc: llcp: fix nfc_llcp_setsockopt() unsafe copies (bsc#1225758). - CVE-2024-36917: block: fix overflow in blk_ioctl_discard() (bsc#1225770). - CVE-2024-36919: scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload (bsc#1225767). - CVE-2024-36923: fs/9p: fix uninitialized values during inode evict (bsc#1225815). - CVE-2024-36934: bna: ensure the copied buf is NUL terminated (bsc#1225760). - CVE-2024-36938: Fixed NULL pointer dereference in sk_psock_skb_ingress_enqueue (bsc#1225761). - CVE-2024-36940: pinctrl: core: delete incorrect free in pinctrl_enable() (bsc#1225840). - CVE-2024-36949: amd/amdkfd: sync all devices to wait all processes being evicted (bsc#1225872) - CVE-2024-36950: firewire: ohci: mask bus reset interrupts between ISR and bottom half (bsc#1225895). - CVE-2024-36960: drm/vmwgfx: Fix invalid reads in fence signaled events (bsc#1225872) - CVE-2024-36964: fs/9p: only translate RWX permissions for plain 9P2000 (bsc#1225866). - CVE-2024-37021: fpga: manager: add owner module and take its refcount (bsc#1226950). - CVE-2024-37354: btrfs: fix crash on racing fsync and size-extending write into prealloc (bsc#1227101). - CVE-2024-38544: RDMA/rxe: Fix seg fault in rxe_comp_queue_pkt (bsc#1226597) - CVE-2024-38545: RDMA/hns: Fix UAF for cq async event (bsc#1226595). - CVE-2024-38546: drm: vc4: Fix possible null pointer dereference (bsc#1226593). - CVE-2024-38549: drm/mediatek: Add 0 size check to mtk_drm_gem_obj (bsc#1226735) - CVE-2024-38552: drm/amd/display: Fix potential index out of bounds in color (bsc#1226767) - CVE-2024-38553: net: fec: remove .ndo_poll_controller to avoid deadlock (bsc#1226744). - CVE-2024-38565: wifi: ar5523: enable proper endpoint verification (bsc#1226747). - CVE-2024-38567: wifi: carl9170: add a proper sanity check for endpoints (bsc#1226769). - CVE-2024-38578: ecryptfs: Fix buffer size for tag 66 packet (bsc#1226634). - CVE-2024-38579: crypto: bcm - Fix pointer arithmetic (bsc#1226637). - CVE-2024-38580: epoll: be better about file lifetimes (bsc#1226610). - CVE-2024-38597: eth: sungem: remove .ndo_poll_controller to avoid deadlocks (bsc#1226749). - CVE-2024-38608: net/mlx5e: Fix netif state handling (bsc#1226746). - CVE-2024-38618: ALSA: timer: Set lower bound of start tick time (bsc#1226754). - CVE-2024-38621: media: stk1160: fix bounds checking in stk1160_copy_video() (bsc#1226895). - CVE-2024-38627: stm class: Fix a double free in stm_register_device() (bsc#1226857). - CVE-2024-38659: enic: Validate length of nl attributes in enic_set_vf_port (bsc#1226883). - CVE-2024-38661: s390/ap: Fix crash in AP internal function modify_bitmap() (bsc#1226996). - CVE-2024-38780: dma-buf/sw-sync: do not enable IRQ from sync_print_obj() (bsc#1226886). The following non-security bugs were fixed: - Btrfs: bail out on error during replay_dir_deletes (git-fixes) - Btrfs: clean up resources during umount after trans is aborted (git-fixes) - Btrfs: fix NULL pointer dereference in log_dir_items (git-fixes) - Btrfs: fix memory and mount leak in btrfs_ioctl_rm_dev_v2() (git-fixes) - Btrfs: fix unexpected EEXIST from btrfs_get_extent (git-fixes) - Btrfs: send, fix issuing write op when processing hole in no data mode (git-fixes) - Fix compilation - KVM: allow KVM_BUG/KVM_BUG_ON to handle 64-bit cond (git-fixes). - NFSv4: Always clear the pNFS layout when handling ESTALE (bsc#1221791). - NFSv4: nfs_set_open_stateid must not trigger state recovery for closed state (bsc#1221791). - PNFS for stateid errors retry against MDS first (bsc#1221791). - RDMA/mlx5: Add check for srq max_sge attribute (git-fixes) - Revert 'build initrd without systemd' (bsc#1195775) - USB: serial: option: add Foxconn T99W265 with new baseline (git-fixes). - USB: serial: option: add Quectel EG912Y module support (git-fixes). - USB: serial: option: add Quectel RM500Q R13 firmware support (git-fixes). - arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY (git-fixes). - blk-cgroup: Fix NULL deref caused by blkg_policy_data being installed before init (bsc#1216062 bsc#1225203). - blk-cgroup: fix missing pd_online_fn() while activating policy (git-fixes bsc#1225203). - blk-cgroup: support to track if policy is online (bsc#1216062 bsc#1225203). - bpf, scripts: Correct GPL license name (git-fixes). - bsc#1225894: Fix build warning Fix the following build warning. * unused-variable (i) in ../drivers/gpu/drm/amd/amdkfd/kfd_device.c in kgd2kfd_resume ../drivers/gpu/drm/amd/amdkfd/kfd_device.c: In function 'kgd2kfd_resume': ../drivers/gpu/drm/amd/amdkfd/kfd_device.c:621:11: warning: unused variable 'i' [-Wunused-variable] - btrfs: add barriers to btrfs_sync_log before log_commit_wait wakeups (git-fixes) - btrfs: fix crash when trying to resume balance without the resume flag (git-fixes) - btrfs: fix describe_relocation when printing unknown flags (git-fixes) - btrfs: fix false EIO for missing device (git-fixes) - btrfs: tree-check: reduce stack consumption in check_dir_item (git-fixes) - btrfs: use correct compare function of dirty_metadata_bytes (git-fixes) - drm/amdkfd: Rework kfd_locked handling (bsc#1225872) - fix compat handling of FICLONERANGE, FIDEDUPERANGE and FS_IOC_FIEMAP (bsc#1225848). - fs: make fiemap work from compat_ioctl (bsc#1225848). - iommu/amd: Fix sysfs leak in iommu init (git-fixes). - iommu/vt-d: Allocate local memory for page request queue (git-fixes). - ipvs: Fix checksumming on GSO of SCTP packets (bsc#1221958) - kabi: blkcg_policy_data fix KABI (bsc#1216062 bsc#1225203). - mkspec-dtb: add toplevel symlinks also on arm - net: hsr: fix placement of logical operator in a multi-line statement (bsc#1223021). - net: usb: rtl8150 fix unintiatilzed variables in rtl8150_get_link_ksettings (git-fixes). - net: usb: smsc95xx: fix changing LED_SEL bit value updated from EEPROM (git-fixes). - nfsd: optimise recalculate_deny_mode() for a common case (bsc#1217912). - nvmet: fix ns enable/disable possible hang (git-fixes). - ocfs2: adjust enabling place for la window (bsc#1219224). - ocfs2: fix sparse warnings (bsc#1219224). - ocfs2: improve write IO performance when fragmentation is high (bsc#1219224). - ocfs2: speed up chain-list searching (bsc#1219224). - rpm/kernel-obs-build.spec.in: Add iso9660 (bsc#1226212) Some builds do not just create an iso9660 image, but also mount it during build. - rpm/kernel-obs-build.spec.in: Add networking modules for docker (bsc#1226211) docker needs more networking modules, even legacy iptable_nat and _filter. - rpm/kernel-obs-build.spec.in: Include algif_hash, aegis128 and xts modules afgif_hash is needed by some packages (e.g. iwd) for tests, xts is used for LUKS2 volumes by default and aegis128 is useful as AEAD cipher for LUKS2. Wrap the long line to make it readable. - rpm/mkspec-dtb: dtbs have moved to vendor sub-directories in 6.5 By commit 724ba6751532 ('ARM: dts: Move .dts files to vendor sub-directories'). So switch to them. - scsi: 3w-xxxx: Add error handling for initialization failure in tw_probe() (git-fixes). - scsi: 53c700: Check that command slot is not NULL (git-fixes). - scsi: be2iscsi: Add length check when parsing nlattrs (git-fixes). - scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle() (git-fixes). - scsi: bfa: Fix function pointer type mismatch for hcb_qe->cbfn (git-fixes). - scsi: bnx2fc: Fix skb double free in bnx2fc_rcv() (git-fixes). - scsi: core: Decrease scsi_device's iorequest_cnt if dispatch failed (git-fixes). - scsi: core: Fix legacy /proc parsing buffer overflow (git-fixes). - scsi: core: Fix possible memory leak if device_add() fails (git-fixes). - scsi: csiostor: Avoid function pointer casts (git-fixes). - scsi: isci: Fix an error code problem in isci_io_request_build() (git-fixes). - scsi: iscsi: Add length check for nlattr payload (git-fixes). - scsi: iscsi: Add strlen() check in iscsi_if_set{_host}_param() (git-fixes). - scsi: iscsi_tcp: restrict to TCP sockets (git-fixes). - scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() (git-fixes). - scsi: libsas: Add a helper sas_get_sas_addr_and_dev_type() (git-fixes). - scsi: libsas: Fix disk not being scanned in after being removed (git-fixes). - scsi: libsas: Introduce struct smp_disc_resp (git-fixes). - scsi: lpfc: Correct size for wqe for memset() (git-fixes). - scsi: lpfc: Fix double free in lpfc_cmpl_els_logo_acc() caused by lpfc_nlp_not_used() (git-fixes). - scsi: lpfc: Fix the NULL vs IS_ERR() bug for debugfs_create_file() (git-fixes). - scsi: megaraid_sas: Increase register read retry rount from 3 to 30 for selected registers (git-fixes). - scsi: mpt3sas: Fix in error path (git-fixes). - scsi: mpt3sas: Fix loop logic (git-fixes). - scsi: mpt3sas: Perform additional retries if doorbell read returns 0 (git-fixes). - scsi: qedf: Do not touch __user pointer in qedf_dbg_debug_cmd_read() directly (git-fixes). - scsi: qedf: Do not touch __user pointer in qedf_dbg_fp_int_cmd_read() directly (git-fixes). - scsi: qedf: Do not touch __user pointer in qedf_dbg_stop_io_on_error_cmd_read() directly (git-fixes). - scsi: qedf: Fix NULL dereference in error handling (git-fixes). - scsi: qedf: Fix firmware halt over suspend and resume (git-fixes). - scsi: qedi: Fix firmware halt over suspend and resume (git-fixes). - scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock (git-fixes). - scsi: qla2xxx: Fix off by one in qla_edif_app_getstats() (git-fixes). - scsi: qla4xxx: Add length check when parsing nlattrs (git-fixes). - scsi: snic: Fix double free in snic_tgt_create() (git-fixes). - scsi: snic: Fix possible memory leak if device_add() fails (git-fixes). - scsi: stex: Fix gcc 13 warnings (git-fixes). - scsi: target: core: Add TMF to tmr_list handling (bsc#1223018). - usb: port: Do not try to peer unused USB ports based on location (git-fixes). - usb: typec: tcpm: Skip hard reset when in error recovery (git-fixes). - x86/tsc: Trust initial offset in architectural TSC-adjust MSRs (bsc#1222015 bsc#1226962). The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-2024-2381,SUSE-SLE-RT-12-SP5-2024-2381 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2024/suse-su-20242381-1/ Link for SUSE-SU-2024:2381-1 https://lists.suse.com/pipermail/sle-updates/2024-July/035895.html E-Mail link for SUSE-SU-2024:2381-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1119113 SUSE Bug 1119113 https://bugzilla.suse.com/1191958 SUSE Bug 1191958 https://bugzilla.suse.com/1195065 SUSE Bug 1195065 https://bugzilla.suse.com/1195254 SUSE Bug 1195254 https://bugzilla.suse.com/1195775 SUSE Bug 1195775 https://bugzilla.suse.com/1204514 SUSE Bug 1204514 https://bugzilla.suse.com/1216062 SUSE Bug 1216062 https://bugzilla.suse.com/1217912 SUSE Bug 1217912 https://bugzilla.suse.com/1218148 SUSE Bug 1218148 https://bugzilla.suse.com/1219224 SUSE Bug 1219224 https://bugzilla.suse.com/1221010 SUSE Bug 1221010 https://bugzilla.suse.com/1221647 SUSE Bug 1221647 https://bugzilla.suse.com/1221654 SUSE Bug 1221654 https://bugzilla.suse.com/1221791 SUSE Bug 1221791 https://bugzilla.suse.com/1221958 SUSE Bug 1221958 https://bugzilla.suse.com/1222015 SUSE Bug 1222015 https://bugzilla.suse.com/1222080 SUSE Bug 1222080 https://bugzilla.suse.com/1222364 SUSE Bug 1222364 https://bugzilla.suse.com/1222385 SUSE Bug 1222385 https://bugzilla.suse.com/1222435 SUSE Bug 1222435 https://bugzilla.suse.com/1222809 SUSE Bug 1222809 https://bugzilla.suse.com/1222866 SUSE Bug 1222866 https://bugzilla.suse.com/1222879 SUSE Bug 1222879 https://bugzilla.suse.com/1222893 SUSE Bug 1222893 https://bugzilla.suse.com/1223013 SUSE Bug 1223013 https://bugzilla.suse.com/1223018 SUSE Bug 1223018 https://bugzilla.suse.com/1223021 SUSE Bug 1223021 https://bugzilla.suse.com/1223043 SUSE Bug 1223043 https://bugzilla.suse.com/1223532 SUSE Bug 1223532 https://bugzilla.suse.com/1223641 SUSE Bug 1223641 https://bugzilla.suse.com/1224177 SUSE Bug 1224177 https://bugzilla.suse.com/1224432 SUSE Bug 1224432 https://bugzilla.suse.com/1224504 SUSE Bug 1224504 https://bugzilla.suse.com/1224549 SUSE Bug 1224549 https://bugzilla.suse.com/1224552 SUSE Bug 1224552 https://bugzilla.suse.com/1224572 SUSE Bug 1224572 https://bugzilla.suse.com/1224575 SUSE Bug 1224575 https://bugzilla.suse.com/1224583 SUSE Bug 1224583 https://bugzilla.suse.com/1224588 SUSE Bug 1224588 https://bugzilla.suse.com/1224605 SUSE Bug 1224605 https://bugzilla.suse.com/1224651 SUSE Bug 1224651 https://bugzilla.suse.com/1224660 SUSE Bug 1224660 https://bugzilla.suse.com/1224661 SUSE Bug 1224661 https://bugzilla.suse.com/1224662 SUSE Bug 1224662 https://bugzilla.suse.com/1224664 SUSE Bug 1224664 https://bugzilla.suse.com/1224668 SUSE Bug 1224668 https://bugzilla.suse.com/1224670 SUSE Bug 1224670 https://bugzilla.suse.com/1224672 SUSE Bug 1224672 https://bugzilla.suse.com/1224674 SUSE Bug 1224674 https://bugzilla.suse.com/1224677 SUSE Bug 1224677 https://bugzilla.suse.com/1224678 SUSE Bug 1224678 https://bugzilla.suse.com/1224703 SUSE Bug 1224703 https://bugzilla.suse.com/1224735 SUSE Bug 1224735 https://bugzilla.suse.com/1224739 SUSE Bug 1224739 https://bugzilla.suse.com/1224763 SUSE Bug 1224763 https://bugzilla.suse.com/1224764 SUSE Bug 1224764 https://bugzilla.suse.com/1224765 SUSE Bug 1224765 https://bugzilla.suse.com/1224946 SUSE Bug 1224946 https://bugzilla.suse.com/1224951 SUSE Bug 1224951 https://bugzilla.suse.com/1224967 SUSE Bug 1224967 https://bugzilla.suse.com/1224976 SUSE Bug 1224976 https://bugzilla.suse.com/1224977 SUSE Bug 1224977 https://bugzilla.suse.com/1224978 SUSE Bug 1224978 https://bugzilla.suse.com/1224993 SUSE Bug 1224993 https://bugzilla.suse.com/1224997 SUSE Bug 1224997 https://bugzilla.suse.com/1225047 SUSE Bug 1225047 https://bugzilla.suse.com/1225140 SUSE Bug 1225140 https://bugzilla.suse.com/1225184 SUSE Bug 1225184 https://bugzilla.suse.com/1225203 SUSE Bug 1225203 https://bugzilla.suse.com/1225232 SUSE Bug 1225232 https://bugzilla.suse.com/1225261 SUSE Bug 1225261 https://bugzilla.suse.com/1225306 SUSE Bug 1225306 https://bugzilla.suse.com/1225337 SUSE Bug 1225337 https://bugzilla.suse.com/1225372 SUSE Bug 1225372 https://bugzilla.suse.com/1225463 SUSE Bug 1225463 https://bugzilla.suse.com/1225484 SUSE Bug 1225484 https://bugzilla.suse.com/1225487 SUSE Bug 1225487 https://bugzilla.suse.com/1225490 SUSE Bug 1225490 https://bugzilla.suse.com/1225514 SUSE Bug 1225514 https://bugzilla.suse.com/1225518 SUSE Bug 1225518 https://bugzilla.suse.com/1225548 SUSE Bug 1225548 https://bugzilla.suse.com/1225555 SUSE Bug 1225555 https://bugzilla.suse.com/1225556 SUSE Bug 1225556 https://bugzilla.suse.com/1225559 SUSE Bug 1225559 https://bugzilla.suse.com/1225571 SUSE Bug 1225571 https://bugzilla.suse.com/1225573 SUSE Bug 1225573 https://bugzilla.suse.com/1225577 SUSE Bug 1225577 https://bugzilla.suse.com/1225583 SUSE Bug 1225583 https://bugzilla.suse.com/1225585 SUSE Bug 1225585 https://bugzilla.suse.com/1225599 SUSE Bug 1225599 https://bugzilla.suse.com/1225602 SUSE Bug 1225602 https://bugzilla.suse.com/1225611 SUSE Bug 1225611 https://bugzilla.suse.com/1225642 SUSE Bug 1225642 https://bugzilla.suse.com/1225681 SUSE Bug 1225681 https://bugzilla.suse.com/1225704 SUSE Bug 1225704 https://bugzilla.suse.com/1225722 SUSE Bug 1225722 https://bugzilla.suse.com/1225749 SUSE Bug 1225749 https://bugzilla.suse.com/1225758 SUSE Bug 1225758 https://bugzilla.suse.com/1225760 SUSE Bug 1225760 https://bugzilla.suse.com/1225761 SUSE Bug 1225761 https://bugzilla.suse.com/1225767 SUSE Bug 1225767 https://bugzilla.suse.com/1225770 SUSE Bug 1225770 https://bugzilla.suse.com/1225815 SUSE Bug 1225815 https://bugzilla.suse.com/1225840 SUSE Bug 1225840 https://bugzilla.suse.com/1225848 SUSE Bug 1225848 https://bugzilla.suse.com/1225866 SUSE Bug 1225866 https://bugzilla.suse.com/1225872 SUSE Bug 1225872 https://bugzilla.suse.com/1225894 SUSE Bug 1225894 https://bugzilla.suse.com/1225895 SUSE Bug 1225895 https://bugzilla.suse.com/1225898 SUSE Bug 1225898 https://bugzilla.suse.com/1226211 SUSE Bug 1226211 https://bugzilla.suse.com/1226212 SUSE Bug 1226212 https://bugzilla.suse.com/1226537 SUSE Bug 1226537 https://bugzilla.suse.com/1226554 SUSE Bug 1226554 https://bugzilla.suse.com/1226557 SUSE Bug 1226557 https://bugzilla.suse.com/1226562 SUSE Bug 1226562 https://bugzilla.suse.com/1226567 SUSE Bug 1226567 https://bugzilla.suse.com/1226575 SUSE Bug 1226575 https://bugzilla.suse.com/1226577 SUSE Bug 1226577 https://bugzilla.suse.com/1226593 SUSE Bug 1226593 https://bugzilla.suse.com/1226595 SUSE Bug 1226595 https://bugzilla.suse.com/1226597 SUSE Bug 1226597 https://bugzilla.suse.com/1226610 SUSE Bug 1226610 https://bugzilla.suse.com/1226614 SUSE Bug 1226614 https://bugzilla.suse.com/1226619 SUSE Bug 1226619 https://bugzilla.suse.com/1226621 SUSE Bug 1226621 https://bugzilla.suse.com/1226634 SUSE Bug 1226634 https://bugzilla.suse.com/1226637 SUSE Bug 1226637 https://bugzilla.suse.com/1226670 SUSE Bug 1226670 https://bugzilla.suse.com/1226672 SUSE Bug 1226672 https://bugzilla.suse.com/1226692 SUSE Bug 1226692 https://bugzilla.suse.com/1226698 SUSE Bug 1226698 https://bugzilla.suse.com/1226699 SUSE Bug 1226699 https://bugzilla.suse.com/1226701 SUSE Bug 1226701 https://bugzilla.suse.com/1226705 SUSE Bug 1226705 https://bugzilla.suse.com/1226708 SUSE Bug 1226708 https://bugzilla.suse.com/1226711 SUSE Bug 1226711 https://bugzilla.suse.com/1226712 SUSE Bug 1226712 https://bugzilla.suse.com/1226716 SUSE Bug 1226716 https://bugzilla.suse.com/1226718 SUSE Bug 1226718 https://bugzilla.suse.com/1226732 SUSE Bug 1226732 https://bugzilla.suse.com/1226735 SUSE Bug 1226735 https://bugzilla.suse.com/1226744 SUSE Bug 1226744 https://bugzilla.suse.com/1226746 SUSE Bug 1226746 https://bugzilla.suse.com/1226747 SUSE Bug 1226747 https://bugzilla.suse.com/1226749 SUSE Bug 1226749 https://bugzilla.suse.com/1226754 SUSE Bug 1226754 https://bugzilla.suse.com/1226767 SUSE Bug 1226767 https://bugzilla.suse.com/1226769 SUSE Bug 1226769 https://bugzilla.suse.com/1226857 SUSE Bug 1226857 https://bugzilla.suse.com/1226876 SUSE Bug 1226876 https://bugzilla.suse.com/1226883 SUSE Bug 1226883 https://bugzilla.suse.com/1226886 SUSE Bug 1226886 https://bugzilla.suse.com/1226895 SUSE Bug 1226895 https://bugzilla.suse.com/1226948 SUSE Bug 1226948 https://bugzilla.suse.com/1226949 SUSE Bug 1226949 https://bugzilla.suse.com/1226950 SUSE Bug 1226950 https://bugzilla.suse.com/1226962 SUSE Bug 1226962 https://bugzilla.suse.com/1226976 SUSE Bug 1226976 https://bugzilla.suse.com/1226996 SUSE Bug 1226996 https://bugzilla.suse.com/1227101 SUSE Bug 1227101 https://www.suse.com/security/cve/CVE-2021-4439/ SUSE CVE CVE-2021-4439 page https://www.suse.com/security/cve/CVE-2021-47103/ SUSE CVE CVE-2021-47103 page https://www.suse.com/security/cve/CVE-2021-47191/ SUSE CVE CVE-2021-47191 page https://www.suse.com/security/cve/CVE-2021-47193/ SUSE CVE CVE-2021-47193 page https://www.suse.com/security/cve/CVE-2021-47267/ SUSE CVE CVE-2021-47267 page https://www.suse.com/security/cve/CVE-2021-47270/ SUSE CVE CVE-2021-47270 page https://www.suse.com/security/cve/CVE-2021-47293/ SUSE CVE CVE-2021-47293 page https://www.suse.com/security/cve/CVE-2021-47294/ SUSE CVE CVE-2021-47294 page https://www.suse.com/security/cve/CVE-2021-47297/ SUSE CVE CVE-2021-47297 page https://www.suse.com/security/cve/CVE-2021-47309/ SUSE CVE CVE-2021-47309 page https://www.suse.com/security/cve/CVE-2021-47328/ SUSE CVE CVE-2021-47328 page https://www.suse.com/security/cve/CVE-2021-47354/ SUSE CVE CVE-2021-47354 page https://www.suse.com/security/cve/CVE-2021-47372/ SUSE CVE CVE-2021-47372 page https://www.suse.com/security/cve/CVE-2021-47379/ SUSE CVE CVE-2021-47379 page https://www.suse.com/security/cve/CVE-2021-47407/ SUSE CVE CVE-2021-47407 page https://www.suse.com/security/cve/CVE-2021-47418/ SUSE CVE CVE-2021-47418 page https://www.suse.com/security/cve/CVE-2021-47434/ SUSE CVE CVE-2021-47434 page https://www.suse.com/security/cve/CVE-2021-47445/ SUSE CVE CVE-2021-47445 page https://www.suse.com/security/cve/CVE-2021-47518/ SUSE CVE CVE-2021-47518 page https://www.suse.com/security/cve/CVE-2021-47544/ SUSE CVE CVE-2021-47544 page https://www.suse.com/security/cve/CVE-2021-47566/ SUSE CVE CVE-2021-47566 page https://www.suse.com/security/cve/CVE-2021-47571/ SUSE CVE CVE-2021-47571 page https://www.suse.com/security/cve/CVE-2021-47576/ SUSE CVE CVE-2021-47576 page https://www.suse.com/security/cve/CVE-2021-47587/ SUSE CVE CVE-2021-47587 page https://www.suse.com/security/cve/CVE-2021-47589/ SUSE CVE CVE-2021-47589 page https://www.suse.com/security/cve/CVE-2021-47600/ SUSE CVE CVE-2021-47600 page https://www.suse.com/security/cve/CVE-2021-47602/ SUSE CVE CVE-2021-47602 page https://www.suse.com/security/cve/CVE-2021-47603/ SUSE CVE CVE-2021-47603 page https://www.suse.com/security/cve/CVE-2021-47609/ SUSE CVE CVE-2021-47609 page https://www.suse.com/security/cve/CVE-2021-47617/ SUSE CVE CVE-2021-47617 page https://www.suse.com/security/cve/CVE-2022-48711/ SUSE CVE CVE-2022-48711 page https://www.suse.com/security/cve/CVE-2022-48715/ SUSE CVE CVE-2022-48715 page https://www.suse.com/security/cve/CVE-2022-48722/ SUSE CVE CVE-2022-48722 page https://www.suse.com/security/cve/CVE-2022-48732/ SUSE CVE CVE-2022-48732 page https://www.suse.com/security/cve/CVE-2022-48733/ SUSE CVE CVE-2022-48733 page https://www.suse.com/security/cve/CVE-2022-48740/ SUSE CVE CVE-2022-48740 page https://www.suse.com/security/cve/CVE-2022-48743/ SUSE CVE CVE-2022-48743 page https://www.suse.com/security/cve/CVE-2022-48754/ SUSE CVE CVE-2022-48754 page https://www.suse.com/security/cve/CVE-2022-48756/ SUSE CVE CVE-2022-48756 page https://www.suse.com/security/cve/CVE-2022-48758/ SUSE CVE CVE-2022-48758 page https://www.suse.com/security/cve/CVE-2022-48759/ SUSE CVE CVE-2022-48759 page https://www.suse.com/security/cve/CVE-2022-48760/ SUSE CVE CVE-2022-48760 page https://www.suse.com/security/cve/CVE-2022-48761/ SUSE CVE CVE-2022-48761 page https://www.suse.com/security/cve/CVE-2022-48771/ SUSE CVE CVE-2022-48771 page https://www.suse.com/security/cve/CVE-2022-48772/ SUSE CVE CVE-2022-48772 page https://www.suse.com/security/cve/CVE-2023-24023/ SUSE CVE CVE-2023-24023 page https://www.suse.com/security/cve/CVE-2023-52622/ SUSE CVE CVE-2023-52622 page https://www.suse.com/security/cve/CVE-2023-52675/ SUSE CVE CVE-2023-52675 page https://www.suse.com/security/cve/CVE-2023-52737/ SUSE CVE CVE-2023-52737 page https://www.suse.com/security/cve/CVE-2023-52752/ SUSE CVE CVE-2023-52752 page https://www.suse.com/security/cve/CVE-2023-52754/ SUSE CVE CVE-2023-52754 page https://www.suse.com/security/cve/CVE-2023-52757/ SUSE CVE CVE-2023-52757 page https://www.suse.com/security/cve/CVE-2023-52762/ SUSE CVE CVE-2023-52762 page https://www.suse.com/security/cve/CVE-2023-52764/ SUSE CVE CVE-2023-52764 page https://www.suse.com/security/cve/CVE-2023-52784/ SUSE CVE CVE-2023-52784 page https://www.suse.com/security/cve/CVE-2023-52808/ SUSE CVE CVE-2023-52808 page https://www.suse.com/security/cve/CVE-2023-52809/ SUSE CVE CVE-2023-52809 page https://www.suse.com/security/cve/CVE-2023-52811/ SUSE CVE CVE-2023-52811 page https://www.suse.com/security/cve/CVE-2023-52832/ SUSE CVE CVE-2023-52832 page https://www.suse.com/security/cve/CVE-2023-52834/ SUSE CVE CVE-2023-52834 page https://www.suse.com/security/cve/CVE-2023-52835/ SUSE CVE CVE-2023-52835 page https://www.suse.com/security/cve/CVE-2023-52843/ SUSE CVE CVE-2023-52843 page https://www.suse.com/security/cve/CVE-2023-52845/ SUSE CVE CVE-2023-52845 page https://www.suse.com/security/cve/CVE-2023-52855/ SUSE CVE CVE-2023-52855 page https://www.suse.com/security/cve/CVE-2023-52881/ SUSE CVE CVE-2023-52881 page https://www.suse.com/security/cve/CVE-2024-26633/ SUSE CVE CVE-2024-26633 page https://www.suse.com/security/cve/CVE-2024-26641/ SUSE CVE CVE-2024-26641 page https://www.suse.com/security/cve/CVE-2024-26679/ SUSE CVE CVE-2024-26679 page https://www.suse.com/security/cve/CVE-2024-26687/ SUSE CVE CVE-2024-26687 page https://www.suse.com/security/cve/CVE-2024-26720/ SUSE CVE CVE-2024-26720 page https://www.suse.com/security/cve/CVE-2024-26813/ SUSE CVE CVE-2024-26813 page https://www.suse.com/security/cve/CVE-2024-26845/ SUSE CVE CVE-2024-26845 page https://www.suse.com/security/cve/CVE-2024-26863/ SUSE CVE CVE-2024-26863 page https://www.suse.com/security/cve/CVE-2024-26894/ SUSE CVE CVE-2024-26894 page https://www.suse.com/security/cve/CVE-2024-26928/ SUSE CVE CVE-2024-26928 page https://www.suse.com/security/cve/CVE-2024-26973/ SUSE CVE CVE-2024-26973 page https://www.suse.com/security/cve/CVE-2024-27399/ SUSE CVE CVE-2024-27399 page https://www.suse.com/security/cve/CVE-2024-27410/ SUSE CVE CVE-2024-27410 page https://www.suse.com/security/cve/CVE-2024-35247/ SUSE CVE CVE-2024-35247 page https://www.suse.com/security/cve/CVE-2024-35807/ SUSE CVE CVE-2024-35807 page https://www.suse.com/security/cve/CVE-2024-35822/ SUSE CVE CVE-2024-35822 page https://www.suse.com/security/cve/CVE-2024-35835/ SUSE CVE CVE-2024-35835 page https://www.suse.com/security/cve/CVE-2024-35862/ SUSE CVE CVE-2024-35862 page https://www.suse.com/security/cve/CVE-2024-35863/ SUSE CVE CVE-2024-35863 page https://www.suse.com/security/cve/CVE-2024-35864/ SUSE CVE CVE-2024-35864 page https://www.suse.com/security/cve/CVE-2024-35865/ SUSE CVE CVE-2024-35865 page https://www.suse.com/security/cve/CVE-2024-35867/ SUSE CVE CVE-2024-35867 page https://www.suse.com/security/cve/CVE-2024-35868/ SUSE CVE CVE-2024-35868 page https://www.suse.com/security/cve/CVE-2024-35870/ SUSE CVE CVE-2024-35870 page https://www.suse.com/security/cve/CVE-2024-35886/ SUSE CVE CVE-2024-35886 page https://www.suse.com/security/cve/CVE-2024-35896/ SUSE CVE CVE-2024-35896 page https://www.suse.com/security/cve/CVE-2024-35922/ SUSE CVE CVE-2024-35922 page https://www.suse.com/security/cve/CVE-2024-35925/ SUSE CVE CVE-2024-35925 page https://www.suse.com/security/cve/CVE-2024-35930/ SUSE CVE CVE-2024-35930 page https://www.suse.com/security/cve/CVE-2024-35950/ SUSE CVE CVE-2024-35950 page https://www.suse.com/security/cve/CVE-2024-35956/ SUSE CVE CVE-2024-35956 page https://www.suse.com/security/cve/CVE-2024-35958/ SUSE CVE CVE-2024-35958 page https://www.suse.com/security/cve/CVE-2024-35960/ SUSE CVE CVE-2024-35960 page https://www.suse.com/security/cve/CVE-2024-35962/ SUSE CVE CVE-2024-35962 page https://www.suse.com/security/cve/CVE-2024-35976/ SUSE CVE CVE-2024-35976 page https://www.suse.com/security/cve/CVE-2024-35979/ SUSE CVE CVE-2024-35979 page https://www.suse.com/security/cve/CVE-2024-35997/ SUSE CVE CVE-2024-35997 page https://www.suse.com/security/cve/CVE-2024-35998/ SUSE CVE CVE-2024-35998 page https://www.suse.com/security/cve/CVE-2024-36016/ SUSE CVE CVE-2024-36016 page https://www.suse.com/security/cve/CVE-2024-36017/ SUSE CVE CVE-2024-36017 page https://www.suse.com/security/cve/CVE-2024-36025/ SUSE CVE CVE-2024-36025 page https://www.suse.com/security/cve/CVE-2024-36479/ SUSE CVE CVE-2024-36479 page https://www.suse.com/security/cve/CVE-2024-36592/ SUSE CVE CVE-2024-36592 page https://www.suse.com/security/cve/CVE-2024-36880/ SUSE CVE CVE-2024-36880 page https://www.suse.com/security/cve/CVE-2024-36894/ SUSE CVE CVE-2024-36894 page https://www.suse.com/security/cve/CVE-2024-36915/ SUSE CVE CVE-2024-36915 page https://www.suse.com/security/cve/CVE-2024-36917/ SUSE CVE CVE-2024-36917 page https://www.suse.com/security/cve/CVE-2024-36919/ SUSE CVE CVE-2024-36919 page https://www.suse.com/security/cve/CVE-2024-36923/ SUSE CVE CVE-2024-36923 page https://www.suse.com/security/cve/CVE-2024-36934/ SUSE CVE CVE-2024-36934 page https://www.suse.com/security/cve/CVE-2024-36938/ SUSE CVE CVE-2024-36938 page https://www.suse.com/security/cve/CVE-2024-36940/ SUSE CVE CVE-2024-36940 page https://www.suse.com/security/cve/CVE-2024-36949/ SUSE CVE CVE-2024-36949 page https://www.suse.com/security/cve/CVE-2024-36950/ SUSE CVE CVE-2024-36950 page https://www.suse.com/security/cve/CVE-2024-36960/ SUSE CVE CVE-2024-36960 page https://www.suse.com/security/cve/CVE-2024-36964/ SUSE CVE CVE-2024-36964 page https://www.suse.com/security/cve/CVE-2024-37021/ SUSE CVE CVE-2024-37021 page https://www.suse.com/security/cve/CVE-2024-37354/ SUSE CVE CVE-2024-37354 page https://www.suse.com/security/cve/CVE-2024-38544/ SUSE CVE CVE-2024-38544 page https://www.suse.com/security/cve/CVE-2024-38545/ SUSE CVE CVE-2024-38545 page https://www.suse.com/security/cve/CVE-2024-38546/ SUSE CVE CVE-2024-38546 page https://www.suse.com/security/cve/CVE-2024-38549/ SUSE CVE CVE-2024-38549 page https://www.suse.com/security/cve/CVE-2024-38552/ SUSE CVE CVE-2024-38552 page https://www.suse.com/security/cve/CVE-2024-38553/ SUSE CVE CVE-2024-38553 page https://www.suse.com/security/cve/CVE-2024-38565/ SUSE CVE CVE-2024-38565 page https://www.suse.com/security/cve/CVE-2024-38567/ SUSE CVE CVE-2024-38567 page https://www.suse.com/security/cve/CVE-2024-38578/ SUSE CVE CVE-2024-38578 page https://www.suse.com/security/cve/CVE-2024-38579/ SUSE CVE CVE-2024-38579 page https://www.suse.com/security/cve/CVE-2024-38580/ SUSE CVE CVE-2024-38580 page https://www.suse.com/security/cve/CVE-2024-38597/ SUSE CVE CVE-2024-38597 page https://www.suse.com/security/cve/CVE-2024-38601/ SUSE CVE CVE-2024-38601 page https://www.suse.com/security/cve/CVE-2024-38608/ SUSE CVE CVE-2024-38608 page https://www.suse.com/security/cve/CVE-2024-38618/ SUSE CVE CVE-2024-38618 page https://www.suse.com/security/cve/CVE-2024-38621/ SUSE CVE CVE-2024-38621 page https://www.suse.com/security/cve/CVE-2024-38627/ SUSE CVE CVE-2024-38627 page https://www.suse.com/security/cve/CVE-2024-38659/ SUSE CVE CVE-2024-38659 page https://www.suse.com/security/cve/CVE-2024-38661/ SUSE CVE CVE-2024-38661 page https://www.suse.com/security/cve/CVE-2024-38780/ SUSE CVE CVE-2024-38780 page SUSE Linux Enterprise Real Time 12 SP5 cluster-md-kmp-rt-4.12.14-10.191.1 cluster-md-kmp-rt_debug-4.12.14-10.191.1 dlm-kmp-rt-4.12.14-10.191.1 dlm-kmp-rt_debug-4.12.14-10.191.1 gfs2-kmp-rt-4.12.14-10.191.1 gfs2-kmp-rt_debug-4.12.14-10.191.1 kernel-devel-rt-4.12.14-10.191.1 kernel-rt-4.12.14-10.191.1 kernel-rt-base-4.12.14-10.191.1 kernel-rt-devel-4.12.14-10.191.1 kernel-rt-extra-4.12.14-10.191.1 kernel-rt-kgraft-devel-4.12.14-10.191.1 kernel-rt_debug-4.12.14-10.191.1 kernel-rt_debug-base-4.12.14-10.191.1 kernel-rt_debug-devel-4.12.14-10.191.1 kernel-rt_debug-extra-4.12.14-10.191.1 kernel-rt_debug-kgraft-devel-4.12.14-10.191.1 kernel-source-rt-4.12.14-10.191.1 kernel-syms-rt-4.12.14-10.191.1 kselftests-kmp-rt-4.12.14-10.191.1 kselftests-kmp-rt_debug-4.12.14-10.191.1 ocfs2-kmp-rt-4.12.14-10.191.1 ocfs2-kmp-rt_debug-4.12.14-10.191.1 cluster-md-kmp-rt-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 dlm-kmp-rt-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 gfs2-kmp-rt-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 kernel-devel-rt-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 kernel-rt-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 kernel-rt-base-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 kernel-rt-devel-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 kernel-rt_debug-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 kernel-rt_debug-devel-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 kernel-source-rt-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 kernel-syms-rt-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 ocfs2-kmp-rt-4.12.14-10.191.1 as a component of SUSE Linux Enterprise Real Time 12 SP5 In the Linux kernel, the following vulnerability has been resolved: isdn: cpai: check ctr->cnr to avoid array index out of bound The cmtp_add_connection() would add a cmtp session to a controller and run a kernel thread to process cmtp. __module_get(THIS_MODULE); session->task = kthread_run(cmtp_session, session, "kcmtpd_ctr_%d", session->num); During this process, the kernel thread would call detach_capi_ctr() to detach a register controller. if the controller was not attached yet, detach_capi_ctr() would trigger an array-index-out-bounds bug. [ 46.866069][ T6479] UBSAN: array-index-out-of-bounds in drivers/isdn/capi/kcapi.c:483:21 [ 46.867196][ T6479] index -1 is out of range for type 'capi_ctr *[32]' [ 46.867982][ T6479] CPU: 1 PID: 6479 Comm: kcmtpd_ctr_0 Not tainted 5.15.0-rc2+ #8 [ 46.869002][ T6479] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [ 46.870107][ T6479] Call Trace: [ 46.870473][ T6479] dump_stack_lvl+0x57/0x7d [ 46.870974][ T6479] ubsan_epilogue+0x5/0x40 [ 46.871458][ T6479] __ubsan_handle_out_of_bounds.cold+0x43/0x48 [ 46.872135][ T6479] detach_capi_ctr+0x64/0xc0 [ 46.872639][ T6479] cmtp_session+0x5c8/0x5d0 [ 46.873131][ T6479] ? __init_waitqueue_head+0x60/0x60 [ 46.873712][ T6479] ? cmtp_add_msgpart+0x120/0x120 [ 46.874256][ T6479] kthread+0x147/0x170 [ 46.874709][ T6479] ? set_kthread_struct+0x40/0x40 [ 46.875248][ T6479] ret_from_fork+0x1f/0x30 [ 46.875773][ T6479] CVE-2021-4439 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-4439.html CVE-2021-4439 https://bugzilla.suse.com/1226670 SUSE Bug 1226670 In the Linux kernel, the following vulnerability has been resolved: inet: fully convert sk->sk_rx_dst to RCU rules syzbot reported various issues around early demux, one being included in this changelog [1] sk->sk_rx_dst is using RCU protection without clearly documenting it. And following sequences in tcp_v4_do_rcv()/tcp_v6_do_rcv() are not following standard RCU rules. [a] dst_release(dst); [b] sk->sk_rx_dst = NULL; They look wrong because a delete operation of RCU protected pointer is supposed to clear the pointer before the call_rcu()/synchronize_rcu() guarding actual memory freeing. In some cases indeed, dst could be freed before [b] is done. We could cheat by clearing sk_rx_dst before calling dst_release(), but this seems the right time to stick to standard RCU annotations and debugging facilities. [1] BUG: KASAN: use-after-free in dst_check include/net/dst.h:470 [inline] BUG: KASAN: use-after-free in tcp_v4_early_demux+0x95b/0x960 net/ipv4/tcp_ipv4.c:1792 Read of size 2 at addr ffff88807f1cb73a by task syz-executor.5/9204 CPU: 0 PID: 9204 Comm: syz-executor.5 Not tainted 5.16.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0x8d/0x320 mm/kasan/report.c:247 __kasan_report mm/kasan/report.c:433 [inline] kasan_report.cold+0x83/0xdf mm/kasan/report.c:450 dst_check include/net/dst.h:470 [inline] tcp_v4_early_demux+0x95b/0x960 net/ipv4/tcp_ipv4.c:1792 ip_rcv_finish_core.constprop.0+0x15de/0x1e80 net/ipv4/ip_input.c:340 ip_list_rcv_finish.constprop.0+0x1b2/0x6e0 net/ipv4/ip_input.c:583 ip_sublist_rcv net/ipv4/ip_input.c:609 [inline] ip_list_rcv+0x34e/0x490 net/ipv4/ip_input.c:644 __netif_receive_skb_list_ptype net/core/dev.c:5508 [inline] __netif_receive_skb_list_core+0x549/0x8e0 net/core/dev.c:5556 __netif_receive_skb_list net/core/dev.c:5608 [inline] netif_receive_skb_list_internal+0x75e/0xd80 net/core/dev.c:5699 gro_normal_list net/core/dev.c:5853 [inline] gro_normal_list net/core/dev.c:5849 [inline] napi_complete_done+0x1f1/0x880 net/core/dev.c:6590 virtqueue_napi_complete drivers/net/virtio_net.c:339 [inline] virtnet_poll+0xca2/0x11b0 drivers/net/virtio_net.c:1557 __napi_poll+0xaf/0x440 net/core/dev.c:7023 napi_poll net/core/dev.c:7090 [inline] net_rx_action+0x801/0xb40 net/core/dev.c:7177 __do_softirq+0x29b/0x9c2 kernel/softirq.c:558 invoke_softirq kernel/softirq.c:432 [inline] __irq_exit_rcu+0x123/0x180 kernel/softirq.c:637 irq_exit_rcu+0x5/0x20 kernel/softirq.c:649 common_interrupt+0x52/0xc0 arch/x86/kernel/irq.c:240 asm_common_interrupt+0x1e/0x40 arch/x86/include/asm/idtentry.h:629 RIP: 0033:0x7f5e972bfd57 Code: 39 d1 73 14 0f 1f 80 00 00 00 00 48 8b 50 f8 48 83 e8 08 48 39 ca 77 f3 48 39 c3 73 3e 48 89 13 48 8b 50 f8 48 89 38 49 8b 0e <48> 8b 3e 48 83 c3 08 48 83 c6 08 eb bc 48 39 d1 72 9e 48 39 d0 73 RSP: 002b:00007fff8a413210 EFLAGS: 00000283 RAX: 00007f5e97108990 RBX: 00007f5e97108338 RCX: ffffffff81d3aa45 RDX: ffffffff81d3aa45 RSI: 00007f5e97108340 RDI: ffffffff81d3aa45 RBP: 00007f5e97107eb8 R08: 00007f5e97108d88 R09: 0000000093c2e8d9 R10: 0000000000000000 R11: 0000000000000000 R12: 00007f5e97107eb0 R13: 00007f5e97108338 R14: 00007f5e97107ea8 R15: 0000000000000019 </TASK> Allocated by task 13: kasan_save_stack+0x1e/0x50 mm/kasan/common.c:38 kasan_set_track mm/kasan/common.c:46 [inline] set_alloc_info mm/kasan/common.c:434 [inline] __kasan_slab_alloc+0x90/0xc0 mm/kasan/common.c:467 kasan_slab_alloc include/linux/kasan.h:259 [inline] slab_post_alloc_hook mm/slab.h:519 [inline] slab_alloc_node mm/slub.c:3234 [inline] slab_alloc mm/slub.c:3242 [inline] kmem_cache_alloc+0x202/0x3a0 mm/slub.c:3247 dst_alloc+0x146/0x1f0 net/core/dst.c:92 rt_dst_alloc+0x73/0x430 net/ipv4/route.c:1613 ip_route_input_slow+0x1817/0x3a20 net/ipv4/route.c:234 ---truncated--- CVE-2021-47103 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47103.html CVE-2021-47103 https://bugzilla.suse.com/1221010 SUSE Bug 1221010 In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_debug: Fix out-of-bound read in resp_readcap16() The following warning was observed running syzkaller: [ 3813.830724] sg_write: data in/out 65466/242 bytes for SCSI command 0x9e-- guessing data in; [ 3813.830724] program syz-executor not setting count and/or reply_len properly [ 3813.836956] ================================================================== [ 3813.839465] BUG: KASAN: stack-out-of-bounds in sg_copy_buffer+0x157/0x1e0 [ 3813.841773] Read of size 4096 at addr ffff8883cf80f540 by task syz-executor/1549 [ 3813.846612] Call Trace: [ 3813.846995] dump_stack+0x108/0x15f [ 3813.847524] print_address_description+0xa5/0x372 [ 3813.848243] kasan_report.cold+0x236/0x2a8 [ 3813.849439] check_memory_region+0x240/0x270 [ 3813.850094] memcpy+0x30/0x80 [ 3813.850553] sg_copy_buffer+0x157/0x1e0 [ 3813.853032] sg_copy_from_buffer+0x13/0x20 [ 3813.853660] fill_from_dev_buffer+0x135/0x370 [ 3813.854329] resp_readcap16+0x1ac/0x280 [ 3813.856917] schedule_resp+0x41f/0x1630 [ 3813.858203] scsi_debug_queuecommand+0xb32/0x17e0 [ 3813.862699] scsi_dispatch_cmd+0x330/0x950 [ 3813.863329] scsi_request_fn+0xd8e/0x1710 [ 3813.863946] __blk_run_queue+0x10b/0x230 [ 3813.864544] blk_execute_rq_nowait+0x1d8/0x400 [ 3813.865220] sg_common_write.isra.0+0xe61/0x2420 [ 3813.871637] sg_write+0x6c8/0xef0 [ 3813.878853] __vfs_write+0xe4/0x800 [ 3813.883487] vfs_write+0x17b/0x530 [ 3813.884008] ksys_write+0x103/0x270 [ 3813.886268] __x64_sys_write+0x77/0xc0 [ 3813.886841] do_syscall_64+0x106/0x360 [ 3813.887415] entry_SYSCALL_64_after_hwframe+0x44/0xa9 This issue can be reproduced with the following syzkaller log: r0 = openat(0xffffffffffffff9c, &(0x7f0000000040)='./file0\x00', 0x26e1, 0x0) r1 = syz_open_procfs(0xffffffffffffffff, &(0x7f0000000000)='fd/3\x00') open_by_handle_at(r1, &(0x7f00000003c0)=ANY=[@ANYRESHEX], 0x602000) r2 = syz_open_dev$sg(&(0x7f0000000000), 0x0, 0x40782) write$binfmt_aout(r2, &(0x7f0000000340)=ANY=[@ANYBLOB="00000000deff000000000000000000000000000000000000000000000000000047f007af9e107a41ec395f1bded7be24277a1501ff6196a83366f4e6362bc0ff2b247f68a972989b094b2da4fb3607fcf611a22dd04310d28c75039d"], 0x126) In resp_readcap16() we get "int alloc_len" value -1104926854, and then pass the huge arr_len to fill_from_dev_buffer(), but arr is only 32 bytes. This leads to OOB in sg_copy_buffer(). To solve this issue, define alloc_len as u32. CVE-2021-47191 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47191.html CVE-2021-47191 https://bugzilla.suse.com/1222866 SUSE Bug 1222866 In the Linux kernel, the following vulnerability has been resolved: scsi: pm80xx: Fix memory leak during rmmod Driver failed to release all memory allocated. This would lead to memory leak during driver removal. Properly free memory when the module is removed. CVE-2021-47193 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47193.html CVE-2021-47193 https://bugzilla.suse.com/1222879 SUSE Bug 1222879 In the Linux kernel, the following vulnerability has been resolved: usb: fix various gadget panics on 10gbps cabling usb_assign_descriptors() is called with 5 parameters, the last 4 of which are the usb_descriptor_header for: full-speed (USB1.1 - 12Mbps [including USB1.0 low-speed @ 1.5Mbps), high-speed (USB2.0 - 480Mbps), super-speed (USB3.0 - 5Gbps), super-speed-plus (USB3.1 - 10Gbps). The differences between full/high/super-speed descriptors are usually substantial (due to changes in the maximum usb block size from 64 to 512 to 1024 bytes and other differences in the specs), while the difference between 5 and 10Gbps descriptors may be as little as nothing (in many cases the same tuning is simply good enough). However if a gadget driver calls usb_assign_descriptors() with a NULL descriptor for super-speed-plus and is then used on a max 10gbps configuration, the kernel will crash with a null pointer dereference, when a 10gbps capable device port + cable + host port combination shows up. (This wouldn't happen if the gadget max-speed was set to 5gbps, but it of course defaults to the maximum, and there's no real reason to artificially limit it) The fix is to simply use the 5gbps descriptor as the 10gbps descriptor, if a 10gbps descriptor wasn't provided. Obviously this won't fix the problem if the 5gbps descriptor is also NULL, but such cases can't be so trivially solved (and any such gadgets are unlikely to be used with USB3 ports any way). CVE-2021-47267 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47267.html CVE-2021-47267 https://bugzilla.suse.com/1224993 SUSE Bug 1224993 In the Linux kernel, the following vulnerability has been resolved: usb: fix various gadgets null ptr deref on 10gbps cabling. This avoids a null pointer dereference in f_{ecm,eem,hid,loopback,printer,rndis,serial,sourcesink,subset,tcm} by simply reusing the 5gbps config for 10gbps. CVE-2021-47270 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47270.html CVE-2021-47270 https://bugzilla.suse.com/1224997 SUSE Bug 1224997 In the Linux kernel, the following vulnerability has been resolved: net/sched: act_skbmod: Skip non-Ethernet packets Currently tcf_skbmod_act() assumes that packets use Ethernet as their L2 protocol, which is not always the case. As an example, for CAN devices: $ ip link add dev vcan0 type vcan $ ip link set up vcan0 $ tc qdisc add dev vcan0 root handle 1: htb $ tc filter add dev vcan0 parent 1: protocol ip prio 10 \ matchall action skbmod swap mac Doing the above silently corrupts all the packets. Do not perform skbmod actions for non-Ethernet packets. CVE-2021-47293 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47293.html CVE-2021-47293 https://bugzilla.suse.com/1224978 SUSE Bug 1224978 In the Linux kernel, the following vulnerability has been resolved: netrom: Decrease sock refcount when sock timers expire Commit 63346650c1a9 ("netrom: switch to sock timer API") switched to use sock timer API. It replaces mod_timer() by sk_reset_timer(), and del_timer() by sk_stop_timer(). Function sk_reset_timer() will increase the refcount of sock if it is called on an inactive timer, hence, in case the timer expires, we need to decrease the refcount ourselves in the handler, otherwise, the sock refcount will be unbalanced and the sock will never be freed. CVE-2021-47294 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47294.html CVE-2021-47294 https://bugzilla.suse.com/1224977 SUSE Bug 1224977 In the Linux kernel, the following vulnerability has been resolved: net: fix uninit-value in caif_seqpkt_sendmsg When nr_segs equal to zero in iovec_from_user, the object msg->msg_iter.iov is uninit stack memory in caif_seqpkt_sendmsg which is defined in ___sys_sendmsg. So we cann't just judge msg->msg_iter.iov->base directlly. We can use nr_segs to judge msg in caif_seqpkt_sendmsg whether has data buffers. ===================================================== BUG: KMSAN: uninit-value in caif_seqpkt_sendmsg+0x693/0xf60 net/caif/caif_socket.c:542 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1c9/0x220 lib/dump_stack.c:118 kmsan_report+0xf7/0x1e0 mm/kmsan/kmsan_report.c:118 __msan_warning+0x58/0xa0 mm/kmsan/kmsan_instr.c:215 caif_seqpkt_sendmsg+0x693/0xf60 net/caif/caif_socket.c:542 sock_sendmsg_nosec net/socket.c:652 [inline] sock_sendmsg net/socket.c:672 [inline] ____sys_sendmsg+0x12b6/0x1350 net/socket.c:2343 ___sys_sendmsg net/socket.c:2397 [inline] __sys_sendmmsg+0x808/0xc90 net/socket.c:2480 __compat_sys_sendmmsg net/compat.c:656 [inline] CVE-2021-47297 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47297.html CVE-2021-47297 https://bugzilla.suse.com/1224976 SUSE Bug 1224976 In the Linux kernel, the following vulnerability has been resolved: net: validate lwtstate->data before returning from skb_tunnel_info() skb_tunnel_info() returns pointer of lwtstate->data as ip_tunnel_info type without validation. lwtstate->data can have various types such as mpls_iptunnel_encap, etc and these are not compatible. So skb_tunnel_info() should validate before returning that pointer. Splat looks like: BUG: KASAN: slab-out-of-bounds in vxlan_get_route+0x418/0x4b0 [vxlan] Read of size 2 at addr ffff888106ec2698 by task ping/811 CPU: 1 PID: 811 Comm: ping Not tainted 5.13.0+ #1195 Call Trace: dump_stack_lvl+0x56/0x7b print_address_description.constprop.8.cold.13+0x13/0x2ee ? vxlan_get_route+0x418/0x4b0 [vxlan] ? vxlan_get_route+0x418/0x4b0 [vxlan] kasan_report.cold.14+0x83/0xdf ? vxlan_get_route+0x418/0x4b0 [vxlan] vxlan_get_route+0x418/0x4b0 [vxlan] [ ... ] vxlan_xmit_one+0x148b/0x32b0 [vxlan] [ ... ] vxlan_xmit+0x25c5/0x4780 [vxlan] [ ... ] dev_hard_start_xmit+0x1ae/0x6e0 __dev_queue_xmit+0x1f39/0x31a0 [ ... ] neigh_xmit+0x2f9/0x940 mpls_xmit+0x911/0x1600 [mpls_iptunnel] lwtunnel_xmit+0x18f/0x450 ip_finish_output2+0x867/0x2040 [ ... ] CVE-2021-47309 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47309.html CVE-2021-47309 https://bugzilla.suse.com/1224967 SUSE Bug 1224967 In the Linux kernel, the following vulnerability has been resolved: scsi: iscsi: Fix conn use after free during resets If we haven't done a unbind target call we can race where iscsi_conn_teardown wakes up the EH thread and then frees the conn while those threads are still accessing the conn ehwait. We can only do one TMF per session so this just moves the TMF fields from the conn to the session. We can then rely on the iscsi_session_teardown->iscsi_remove_session->__iscsi_unbind_session call to remove the target and it's devices, and know after that point there is no device or scsi-ml callout trying to access the session. CVE-2021-47328 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47328.html CVE-2021-47328 https://bugzilla.suse.com/1225047 SUSE Bug 1225047 https://bugzilla.suse.com/1225080 SUSE Bug 1225080 In the Linux kernel, the following vulnerability has been resolved: drm/sched: Avoid data corruptions Wait for all dependencies of a job to complete before killing it to avoid data corruptions. CVE-2021-47354 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47354.html CVE-2021-47354 https://bugzilla.suse.com/1225140 SUSE Bug 1225140 In the Linux kernel, the following vulnerability has been resolved: net: macb: fix use after free on rmmod plat_dev->dev->platform_data is released by platform_device_unregister(), use of pclk and hclk is a use-after-free. Since device unregister won't need a clk device we adjust the function call sequence to fix this issue. [ 31.261225] BUG: KASAN: use-after-free in macb_remove+0x77/0xc6 [macb_pci] [ 31.275563] Freed by task 306: [ 30.276782] platform_device_release+0x25/0x80 CVE-2021-47372 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47372.html CVE-2021-47372 https://bugzilla.suse.com/1225184 SUSE Bug 1225184 https://bugzilla.suse.com/1229946 SUSE Bug 1229946 In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix UAF by grabbing blkcg lock before destroying blkg pd KASAN reports a use-after-free report when doing fuzz test: [693354.104835] ================================================================== [693354.105094] BUG: KASAN: use-after-free in bfq_io_set_weight_legacy+0xd3/0x160 [693354.105336] Read of size 4 at addr ffff888be0a35664 by task sh/1453338 [693354.105607] CPU: 41 PID: 1453338 Comm: sh Kdump: loaded Not tainted 4.18.0-147 [693354.105610] Hardware name: Huawei 2288H V5/BC11SPSCB0, BIOS 0.81 07/02/2018 [693354.105612] Call Trace: [693354.105621] dump_stack+0xf1/0x19b [693354.105626] ? show_regs_print_info+0x5/0x5 [693354.105634] ? printk+0x9c/0xc3 [693354.105638] ? cpumask_weight+0x1f/0x1f [693354.105648] print_address_description+0x70/0x360 [693354.105654] kasan_report+0x1b2/0x330 [693354.105659] ? bfq_io_set_weight_legacy+0xd3/0x160 [693354.105665] ? bfq_io_set_weight_legacy+0xd3/0x160 [693354.105670] bfq_io_set_weight_legacy+0xd3/0x160 [693354.105675] ? bfq_cpd_init+0x20/0x20 [693354.105683] cgroup_file_write+0x3aa/0x510 [693354.105693] ? ___slab_alloc+0x507/0x540 [693354.105698] ? cgroup_file_poll+0x60/0x60 [693354.105702] ? 0xffffffff89600000 [693354.105708] ? usercopy_abort+0x90/0x90 [693354.105716] ? mutex_lock+0xef/0x180 [693354.105726] kernfs_fop_write+0x1ab/0x280 [693354.105732] ? cgroup_file_poll+0x60/0x60 [693354.105738] vfs_write+0xe7/0x230 [693354.105744] ksys_write+0xb0/0x140 [693354.105749] ? __ia32_sys_read+0x50/0x50 [693354.105760] do_syscall_64+0x112/0x370 [693354.105766] ? syscall_return_slowpath+0x260/0x260 [693354.105772] ? do_page_fault+0x9b/0x270 [693354.105779] ? prepare_exit_to_usermode+0xf9/0x1a0 [693354.105784] ? enter_from_user_mode+0x30/0x30 [693354.105793] entry_SYSCALL_64_after_hwframe+0x65/0xca [693354.105875] Allocated by task 1453337: [693354.106001] kasan_kmalloc+0xa0/0xd0 [693354.106006] kmem_cache_alloc_node_trace+0x108/0x220 [693354.106010] bfq_pd_alloc+0x96/0x120 [693354.106015] blkcg_activate_policy+0x1b7/0x2b0 [693354.106020] bfq_create_group_hierarchy+0x1e/0x80 [693354.106026] bfq_init_queue+0x678/0x8c0 [693354.106031] blk_mq_init_sched+0x1f8/0x460 [693354.106037] elevator_switch_mq+0xe1/0x240 [693354.106041] elevator_switch+0x25/0x40 [693354.106045] elv_iosched_store+0x1a1/0x230 [693354.106049] queue_attr_store+0x78/0xb0 [693354.106053] kernfs_fop_write+0x1ab/0x280 [693354.106056] vfs_write+0xe7/0x230 [693354.106060] ksys_write+0xb0/0x140 [693354.106064] do_syscall_64+0x112/0x370 [693354.106069] entry_SYSCALL_64_after_hwframe+0x65/0xca [693354.106114] Freed by task 1453336: [693354.106225] __kasan_slab_free+0x130/0x180 [693354.106229] kfree+0x90/0x1b0 [693354.106233] blkcg_deactivate_policy+0x12c/0x220 [693354.106238] bfq_exit_queue+0xf5/0x110 [693354.106241] blk_mq_exit_sched+0x104/0x130 [693354.106245] __elevator_exit+0x45/0x60 [693354.106249] elevator_switch_mq+0xd6/0x240 [693354.106253] elevator_switch+0x25/0x40 [693354.106257] elv_iosched_store+0x1a1/0x230 [693354.106261] queue_attr_store+0x78/0xb0 [693354.106264] kernfs_fop_write+0x1ab/0x280 [693354.106268] vfs_write+0xe7/0x230 [693354.106271] ksys_write+0xb0/0x140 [693354.106275] do_syscall_64+0x112/0x370 [693354.106280] entry_SYSCALL_64_after_hwframe+0x65/0xca [693354.106329] The buggy address belongs to the object at ffff888be0a35580 which belongs to the cache kmalloc-1k of size 1024 [693354.106736] The buggy address is located 228 bytes inside of 1024-byte region [ffff888be0a35580, ffff888be0a35980) [693354.107114] The buggy address belongs to the page: [693354.107273] page:ffffea002f828c00 count:1 mapcount:0 mapping:ffff888107c17080 index:0x0 compound_mapcount: 0 [693354.107606] flags: 0x17ffffc0008100(slab|head) [693354.107760] raw: 0017ffffc0008100 ffffea002fcbc808 ffffea0030bd3a08 ffff888107c17080 [693354.108020] r ---truncated--- CVE-2021-47379 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47379.html CVE-2021-47379 https://bugzilla.suse.com/1225203 SUSE Bug 1225203 https://bugzilla.suse.com/1225204 SUSE Bug 1225204 In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Handle SRCU initialization failure during page track init Check the return of init_srcu_struct(), which can fail due to OOM, when initializing the page track mechanism. Lack of checking leads to a NULL pointer deref found by a modified syzkaller. [Move the call towards the beginning of kvm_arch_init_vm. - Paolo] CVE-2021-47407 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47407.html CVE-2021-47407 https://bugzilla.suse.com/1225306 SUSE Bug 1225306 In the Linux kernel, the following vulnerability has been resolved: net_sched: fix NULL deref in fifo_set_limit() syzbot reported another NULL deref in fifo_set_limit() [1] I could repro the issue with : unshare -n tc qd add dev lo root handle 1:0 tbf limit 200000 burst 70000 rate 100Mbit tc qd replace dev lo parent 1:0 pfifo_fast tc qd change dev lo root handle 1:0 tbf limit 300000 burst 70000 rate 100Mbit pfifo_fast does not have a change() operation. Make fifo_set_limit() more robust about this. [1] BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 1cf99067 P4D 1cf99067 PUD 7ca49067 PMD 0 Oops: 0010 [#1] PREEMPT SMP KASAN CPU: 1 PID: 14443 Comm: syz-executor959 Not tainted 5.15.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:0x0 Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. RSP: 0018:ffffc9000e2f7310 EFLAGS: 00010246 RAX: dffffc0000000000 RBX: ffffffff8d6ecc00 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff888024c27910 RDI: ffff888071e34000 RBP: ffff888071e34000 R08: 0000000000000001 R09: ffffffff8fcfb947 R10: 0000000000000001 R11: 0000000000000000 R12: ffff888024c27910 R13: ffff888071e34018 R14: 0000000000000000 R15: ffff88801ef74800 FS: 00007f321d897700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffffffffd6 CR3: 00000000722c3000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: fifo_set_limit net/sched/sch_fifo.c:242 [inline] fifo_set_limit+0x198/0x210 net/sched/sch_fifo.c:227 tbf_change+0x6ec/0x16d0 net/sched/sch_tbf.c:418 qdisc_change net/sched/sch_api.c:1332 [inline] tc_modify_qdisc+0xd9a/0x1a60 net/sched/sch_api.c:1634 rtnetlink_rcv_msg+0x413/0xb80 net/core/rtnetlink.c:5572 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2504 netlink_unicast_kernel net/netlink/af_netlink.c:1314 [inline] netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1340 netlink_sendmsg+0x86d/0xdb0 net/netlink/af_netlink.c:1929 sock_sendmsg_nosec net/socket.c:704 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:724 ____sys_sendmsg+0x6e8/0x810 net/socket.c:2409 ___sys_sendmsg+0xf3/0x170 net/socket.c:2463 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2492 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae CVE-2021-47418 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47418.html CVE-2021-47418 https://bugzilla.suse.com/1225337 SUSE Bug 1225337 In the Linux kernel, the following vulnerability has been resolved: xhci: Fix command ring pointer corruption while aborting a command The command ring pointer is located at [6:63] bits of the command ring control register (CRCR). All the control bits like command stop, abort are located at [0:3] bits. While aborting a command, we read the CRCR and set the abort bit and write to the CRCR. The read will always give command ring pointer as all zeros. So we essentially write only the control bits. Since we split the 64 bit write into two 32 bit writes, there is a possibility of xHC command ring stopped before the upper dword (all zeros) is written. If that happens, xHC updates the upper dword of its internal command ring pointer with all zeros. Next time, when the command ring is restarted, we see xHC memory access failures. Fix this issue by only writing to the lower dword of CRCR where all control bits are located. CVE-2021-47434 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47434.html CVE-2021-47434 https://bugzilla.suse.com/1225232 SUSE Bug 1225232 In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix null pointer dereference on pointer edp The initialization of pointer dev dereferences pointer edp before edp is null checked, so there is a potential null pointer deference issue. Fix this by only dereferencing edp after edp has been null checked. Addresses-Coverity: ("Dereference before null check") CVE-2021-47445 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47445.html CVE-2021-47445 https://bugzilla.suse.com/1225261 SUSE Bug 1225261 In the Linux kernel, the following vulnerability has been resolved: nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done The done() netlink callback nfc_genl_dump_ses_done() should check if received argument is non-NULL, because its allocation could fail earlier in dumpit() (nfc_genl_dump_ses()). CVE-2021-47518 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47518.html CVE-2021-47518 https://bugzilla.suse.com/1225372 SUSE Bug 1225372 In the Linux kernel, the following vulnerability has been resolved: tcp: fix page frag corruption on page fault Steffen reported a TCP stream corruption for HTTP requests served by the apache web-server using a cifs mount-point and memory mapping the relevant file. The root cause is quite similar to the one addressed by commit 20eb4f29b602 ("net: fix sk_page_frag() recursion from memory reclaim"). Here the nested access to the task page frag is caused by a page fault on the (mmapped) user-space memory buffer coming from the cifs file. The page fault handler performs an smb transaction on a different socket, inside the same process context. Since sk->sk_allaction for such socket does not prevent the usage for the task_frag, the nested allocation modify "under the hood" the page frag in use by the outer sendmsg call, corrupting the stream. The overall relevant stack trace looks like the following: httpd 78268 [001] 3461630.850950: probe:tcp_sendmsg_locked: ffffffff91461d91 tcp_sendmsg_locked+0x1 ffffffff91462b57 tcp_sendmsg+0x27 ffffffff9139814e sock_sendmsg+0x3e ffffffffc06dfe1d smb_send_kvec+0x28 [...] ffffffffc06cfaf8 cifs_readpages+0x213 ffffffff90e83c4b read_pages+0x6b ffffffff90e83f31 __do_page_cache_readahead+0x1c1 ffffffff90e79e98 filemap_fault+0x788 ffffffff90eb0458 __do_fault+0x38 ffffffff90eb5280 do_fault+0x1a0 ffffffff90eb7c84 __handle_mm_fault+0x4d4 ffffffff90eb8093 handle_mm_fault+0xc3 ffffffff90c74f6d __do_page_fault+0x1ed ffffffff90c75277 do_page_fault+0x37 ffffffff9160111e page_fault+0x1e ffffffff9109e7b5 copyin+0x25 ffffffff9109eb40 _copy_from_iter_full+0xe0 ffffffff91462370 tcp_sendmsg_locked+0x5e0 ffffffff91462370 tcp_sendmsg_locked+0x5e0 ffffffff91462b57 tcp_sendmsg+0x27 ffffffff9139815c sock_sendmsg+0x4c ffffffff913981f7 sock_write_iter+0x97 ffffffff90f2cc56 do_iter_readv_writev+0x156 ffffffff90f2dff0 do_iter_write+0x80 ffffffff90f2e1c3 vfs_writev+0xa3 ffffffff90f2e27c do_writev+0x5c ffffffff90c042bb do_syscall_64+0x5b ffffffff916000ad entry_SYSCALL_64_after_hwframe+0x65 The cifs filesystem rightfully sets sk_allocations to GFP_NOFS, we can avoid the nesting using the sk page frag for allocation lacking the __GFP_FS flag. Do not define an additional mm-helper for that, as this is strictly tied to the sk page frag usage. v1 -> v2: - use a stricted sk_page_frag() check instead of reordering the code (Eric) CVE-2021-47544 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47544.html CVE-2021-47544 https://bugzilla.suse.com/1225463 SUSE Bug 1225463 In the Linux kernel, the following vulnerability has been resolved: proc/vmcore: fix clearing user buffer by properly using clear_user() To clear a user buffer we cannot simply use memset, we have to use clear_user(). With a virtio-mem device that registers a vmcore_cb and has some logically unplugged memory inside an added Linux memory block, I can easily trigger a BUG by copying the vmcore via "cp": systemd[1]: Starting Kdump Vmcore Save Service... kdump[420]: Kdump is using the default log level(3). kdump[453]: saving to /sysroot/var/crash/127.0.0.1-2021-11-11-14:59:22/ kdump[458]: saving vmcore-dmesg.txt to /sysroot/var/crash/127.0.0.1-2021-11-11-14:59:22/ kdump[465]: saving vmcore-dmesg.txt complete kdump[467]: saving vmcore BUG: unable to handle page fault for address: 00007f2374e01000 #PF: supervisor write access in kernel mode #PF: error_code(0x0003) - permissions violation PGD 7a523067 P4D 7a523067 PUD 7a528067 PMD 7a525067 PTE 800000007048f867 Oops: 0003 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 468 Comm: cp Not tainted 5.15.0+ #6 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-27-g64f37cc530f1-prebuilt.qemu.org 04/01/2014 RIP: 0010:read_from_oldmem.part.0.cold+0x1d/0x86 Code: ff ff ff e8 05 ff fe ff e9 b9 e9 7f ff 48 89 de 48 c7 c7 38 3b 60 82 e8 f1 fe fe ff 83 fd 08 72 3c 49 8d 7d 08 4c 89 e9 89 e8 <49> c7 45 00 00 00 00 00 49 c7 44 05 f8 00 00 00 00 48 83 e7 f81 RSP: 0018:ffffc9000073be08 EFLAGS: 00010212 RAX: 0000000000001000 RBX: 00000000002fd000 RCX: 00007f2374e01000 RDX: 0000000000000001 RSI: 00000000ffffdfff RDI: 00007f2374e01008 RBP: 0000000000001000 R08: 0000000000000000 R09: ffffc9000073bc50 R10: ffffc9000073bc48 R11: ffffffff829461a8 R12: 000000000000f000 R13: 00007f2374e01000 R14: 0000000000000000 R15: ffff88807bd421e8 FS: 00007f2374e12140(0000) GS:ffff88807f000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f2374e01000 CR3: 000000007a4aa000 CR4: 0000000000350eb0 Call Trace: read_vmcore+0x236/0x2c0 proc_reg_read+0x55/0xa0 vfs_read+0x95/0x190 ksys_read+0x4f/0xc0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae Some x86-64 CPUs have a CPU feature called "Supervisor Mode Access Prevention (SMAP)", which is used to detect wrong access from the kernel to user buffers like this: SMAP triggers a permissions violation on wrong access. In the x86-64 variant of clear_user(), SMAP is properly handled via clac()+stac(). To fix, properly use clear_user() when we're dealing with a user buffer. CVE-2021-47566 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47566.html CVE-2021-47566 https://bugzilla.suse.com/1225514 SUSE Bug 1225514 In the Linux kernel, the following vulnerability has been resolved: staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() The free_rtllib() function frees the "dev" pointer so there is use after free on the next line. Re-arrange things to avoid that. CVE-2021-47571 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47571.html CVE-2021-47571 https://bugzilla.suse.com/1225518 SUSE Bug 1225518 https://bugzilla.suse.com/1227551 SUSE Bug 1227551 In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select() In resp_mode_select() sanity check the block descriptor len to avoid UAF. BUG: KASAN: use-after-free in resp_mode_select+0xa4c/0xb40 drivers/scsi/scsi_debug.c:2509 Read of size 1 at addr ffff888026670f50 by task scsicmd/15032 CPU: 1 PID: 15032 Comm: scsicmd Not tainted 5.15.0-01d0625 #15 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Call Trace: <TASK> dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:107 print_address_description.constprop.9+0x28/0x160 mm/kasan/report.c:257 kasan_report.cold.14+0x7d/0x117 mm/kasan/report.c:443 __asan_report_load1_noabort+0x14/0x20 mm/kasan/report_generic.c:306 resp_mode_select+0xa4c/0xb40 drivers/scsi/scsi_debug.c:2509 schedule_resp+0x4af/0x1a10 drivers/scsi/scsi_debug.c:5483 scsi_debug_queuecommand+0x8c9/0x1e70 drivers/scsi/scsi_debug.c:7537 scsi_queue_rq+0x16b4/0x2d10 drivers/scsi/scsi_lib.c:1521 blk_mq_dispatch_rq_list+0xb9b/0x2700 block/blk-mq.c:1640 __blk_mq_sched_dispatch_requests+0x28f/0x590 block/blk-mq-sched.c:325 blk_mq_sched_dispatch_requests+0x105/0x190 block/blk-mq-sched.c:358 __blk_mq_run_hw_queue+0xe5/0x150 block/blk-mq.c:1762 __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1839 blk_mq_run_hw_queue+0x18d/0x350 block/blk-mq.c:1891 blk_mq_sched_insert_request+0x3db/0x4e0 block/blk-mq-sched.c:474 blk_execute_rq_nowait+0x16b/0x1c0 block/blk-exec.c:63 sg_common_write.isra.18+0xeb3/0x2000 drivers/scsi/sg.c:837 sg_new_write.isra.19+0x570/0x8c0 drivers/scsi/sg.c:775 sg_ioctl_common+0x14d6/0x2710 drivers/scsi/sg.c:941 sg_ioctl+0xa2/0x180 drivers/scsi/sg.c:1166 __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:52 do_syscall_64+0x3a/0x80 arch/x86/entry/common.c:50 entry_SYSCALL_64_after_hwframe+0x44/0xae arch/x86/entry/entry_64.S:113 CVE-2021-47576 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 low 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47576.html CVE-2021-47576 https://bugzilla.suse.com/1226537 SUSE Bug 1226537 In the Linux kernel, the following vulnerability has been resolved: net: systemport: Add global locking for descriptor lifecycle The descriptor list is a shared resource across all of the transmit queues, and the locking mechanism used today only protects concurrency across a given transmit queue between the transmit and reclaiming. This creates an opportunity for the SYSTEMPORT hardware to work on corrupted descriptors if we have multiple producers at once which is the case when using multiple transmit queues. This was particularly noticeable when using multiple flows/transmit queues and it showed up in interesting ways in that UDP packets would get a correct UDP header checksum being calculated over an incorrect packet length. Similarly TCP packets would get an equally correct checksum computed by the hardware over an incorrect packet length. The SYSTEMPORT hardware maintains an internal descriptor list that it re-arranges when the driver produces a new descriptor anytime it writes to the WRITE_PORT_{HI,LO} registers, there is however some delay in the hardware to re-organize its descriptors and it is possible that concurrent TX queues eventually break this internal allocation scheme to the point where the length/status part of the descriptor gets used for an incorrect data buffer. The fix is to impose a global serialization for all TX queues in the short section where we are writing to the WRITE_PORT_{HI,LO} registers which solves the corruption even with multiple concurrent TX queues being used. CVE-2021-47587 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47587.html CVE-2021-47587 https://bugzilla.suse.com/1226567 SUSE Bug 1226567 In the Linux kernel, the following vulnerability has been resolved: igbvf: fix double free in `igbvf_probe` In `igbvf_probe`, if register_netdev() fails, the program will go to label err_hw_init, and then to label err_ioremap. In free_netdev() which is just below label err_ioremap, there is `list_for_each_entry_safe` and `netif_napi_del` which aims to delete all entries in `dev->napi_list`. The program has added an entry `adapter->rx_ring->napi` which is added by `netif_napi_add` in igbvf_alloc_queues(). However, adapter->rx_ring has been freed below label err_hw_init. So this a UAF. In terms of how to patch the problem, we can refer to igbvf_remove() and delete the entry before `adapter->rx_ring`. The KASAN logs are as follows: [ 35.126075] BUG: KASAN: use-after-free in free_netdev+0x1fd/0x450 [ 35.127170] Read of size 8 at addr ffff88810126d990 by task modprobe/366 [ 35.128360] [ 35.128643] CPU: 1 PID: 366 Comm: modprobe Not tainted 5.15.0-rc2+ #14 [ 35.129789] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014 [ 35.131749] Call Trace: [ 35.132199] dump_stack_lvl+0x59/0x7b [ 35.132865] print_address_description+0x7c/0x3b0 [ 35.133707] ? free_netdev+0x1fd/0x450 [ 35.134378] __kasan_report+0x160/0x1c0 [ 35.135063] ? free_netdev+0x1fd/0x450 [ 35.135738] kasan_report+0x4b/0x70 [ 35.136367] free_netdev+0x1fd/0x450 [ 35.137006] igbvf_probe+0x121d/0x1a10 [igbvf] [ 35.137808] ? igbvf_vlan_rx_add_vid+0x100/0x100 [igbvf] [ 35.138751] local_pci_probe+0x13c/0x1f0 [ 35.139461] pci_device_probe+0x37e/0x6c0 [ 35.165526] [ 35.165806] Allocated by task 366: [ 35.166414] ____kasan_kmalloc+0xc4/0xf0 [ 35.167117] foo_kmem_cache_alloc_trace+0x3c/0x50 [igbvf] [ 35.168078] igbvf_probe+0x9c5/0x1a10 [igbvf] [ 35.168866] local_pci_probe+0x13c/0x1f0 [ 35.169565] pci_device_probe+0x37e/0x6c0 [ 35.179713] [ 35.179993] Freed by task 366: [ 35.180539] kasan_set_track+0x4c/0x80 [ 35.181211] kasan_set_free_info+0x1f/0x40 [ 35.181942] ____kasan_slab_free+0x103/0x140 [ 35.182703] kfree+0xe3/0x250 [ 35.183239] igbvf_probe+0x1173/0x1a10 [igbvf] [ 35.184040] local_pci_probe+0x13c/0x1f0 CVE-2021-47589 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47589.html CVE-2021-47589 https://bugzilla.suse.com/1226557 SUSE Bug 1226557 In the Linux kernel, the following vulnerability has been resolved: dm btree remove: fix use after free in rebalance_children() Move dm_tm_unlock() after dm_tm_dec(). CVE-2021-47600 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47600.html CVE-2021-47600 https://bugzilla.suse.com/1226575 SUSE Bug 1226575 https://bugzilla.suse.com/1227472 SUSE Bug 1227472 In the Linux kernel, the following vulnerability has been resolved: mac80211: track only QoS data frames for admission control For admission control, obviously all of that only works for QoS data frames, otherwise we cannot even access the QoS field in the header. Syzbot reported (see below) an uninitialized value here due to a status of a non-QoS nullfunc packet, which isn't even long enough to contain the QoS header. Fix this to only do anything for QoS data packets. CVE-2021-47602 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47602.html CVE-2021-47602 https://bugzilla.suse.com/1226554 SUSE Bug 1226554 In the Linux kernel, the following vulnerability has been resolved: audit: improve robustness of the audit queue handling If the audit daemon were ever to get stuck in a stopped state the kernel's kauditd_thread() could get blocked attempting to send audit records to the userspace audit daemon. With the kernel thread blocked it is possible that the audit queue could grow unbounded as certain audit record generating events must be exempt from the queue limits else the system enter a deadlock state. This patch resolves this problem by lowering the kernel thread's socket sending timeout from MAX_SCHEDULE_TIMEOUT to HZ/10 and tweaks the kauditd_send_queue() function to better manage the various audit queues when connection problems occur between the kernel and the audit daemon. With this patch, the backlog may temporarily grow beyond the defined limits when the audit daemon is stopped and the system is under heavy audit pressure, but kauditd_thread() will continue to make progress and drain the queues as it would for other connection problems. For example, with the audit daemon put into a stopped state and the system configured to audit every syscall it was still possible to shutdown the system without a kernel panic, deadlock, etc.; granted, the system was slow to shutdown but that is to be expected given the extreme pressure of recording every syscall. The timeout value of HZ/10 was chosen primarily through experimentation and this developer's "gut feeling". There is likely no one perfect value, but as this scenario is limited in scope (root privileges would be needed to send SIGSTOP to the audit daemon), it is likely not worth exposing this as a tunable at present. This can always be done at a later date if it proves necessary. CVE-2021-47603 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47603.html CVE-2021-47603 https://bugzilla.suse.com/1226577 SUSE Bug 1226577 In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scpi: Fix string overflow in SCPI genpd driver Without the bound checks for scpi_pd->name, it could result in the buffer overflow when copying the SCPI device name from the corresponding device tree node as the name string is set at maximum size of 30. Let us fix it by using devm_kasprintf so that the string buffer is allocated dynamically. CVE-2021-47609 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47609.html CVE-2021-47609 https://bugzilla.suse.com/1226562 SUSE Bug 1226562 In the Linux kernel, the following vulnerability has been resolved: PCI: pciehp: Fix infinite loop in IRQ handler upon power fault The Power Fault Detected bit in the Slot Status register differs from all other hotplug events in that it is sticky: It can only be cleared after turning off slot power. Per PCIe r5.0, sec. 6.7.1.8: If a power controller detects a main power fault on the hot-plug slot, it must automatically set its internal main power fault latch [...]. The main power fault latch is cleared when software turns off power to the hot-plug slot. The stickiness used to cause interrupt storms and infinite loops which were fixed in 2009 by commits 5651c48cfafe ("PCI pciehp: fix power fault interrupt storm problem") and 99f0169c17f3 ("PCI: pciehp: enable software notification on empty slots"). Unfortunately in 2020 the infinite loop issue was inadvertently reintroduced by commit 8edf5332c393 ("PCI: pciehp: Fix MSI interrupt race"): The hardirq handler pciehp_isr() clears the PFD bit until pciehp's power_fault_detected flag is set. That happens in the IRQ thread pciehp_ist(), which never learns of the event because the hardirq handler is stuck in an infinite loop. Fix by setting the power_fault_detected flag already in the hardirq handler. CVE-2021-47617 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2021-47617.html CVE-2021-47617 https://bugzilla.suse.com/1226614 SUSE Bug 1226614 In the Linux kernel, the following vulnerability has been resolved: tipc: improve size validations for received domain records The function tipc_mon_rcv() allows a node to receive and process domain_record structs from peer nodes to track their views of the network topology. This patch verifies that the number of members in a received domain record does not exceed the limit defined by MAX_MON_DOMAIN, something that may otherwise lead to a stack overflow. tipc_mon_rcv() is called from the function tipc_link_proto_rcv(), where we are reading a 32 bit message data length field into a uint16. To avert any risk of bit overflow, we add an extra sanity check for this in that function. We cannot see that happen with the current code, but future designers being unaware of this risk, may introduce it by allowing delivery of very large (> 64k) sk buffers from the bearer layer. This potential problem was identified by Eric Dumazet. This fixes CVE-2022-0435 CVE-2022-48711 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48711.html CVE-2022-48711 https://bugzilla.suse.com/1226672 SUSE Bug 1226672 https://bugzilla.suse.com/1227473 SUSE Bug 1227473 In the Linux kernel, the following vulnerability has been resolved: scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe Running tests with a debug kernel shows that bnx2fc_recv_frame() is modifying the per_cpu lport stats counters in a non-mpsafe way. Just boot a debug kernel and run the bnx2fc driver with the hardware enabled. [ 1391.699147] BUG: using smp_processor_id() in preemptible [00000000] code: bnx2fc_ [ 1391.699160] caller is bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc] [ 1391.699174] CPU: 2 PID: 4355 Comm: bnx2fc_l2_threa Kdump: loaded Tainted: G B [ 1391.699180] Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013 [ 1391.699183] Call Trace: [ 1391.699188] dump_stack_lvl+0x57/0x7d [ 1391.699198] check_preemption_disabled+0xc8/0xd0 [ 1391.699205] bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc] [ 1391.699215] ? do_raw_spin_trylock+0xb5/0x180 [ 1391.699221] ? bnx2fc_npiv_create_vports.isra.0+0x4e0/0x4e0 [bnx2fc] [ 1391.699229] ? bnx2fc_l2_rcv_thread+0xb7/0x3a0 [bnx2fc] [ 1391.699240] bnx2fc_l2_rcv_thread+0x1af/0x3a0 [bnx2fc] [ 1391.699250] ? bnx2fc_ulp_init+0xc0/0xc0 [bnx2fc] [ 1391.699258] kthread+0x364/0x420 [ 1391.699263] ? _raw_spin_unlock_irq+0x24/0x50 [ 1391.699268] ? set_kthread_struct+0x100/0x100 [ 1391.699273] ret_from_fork+0x22/0x30 Restore the old get_cpu/put_cpu code with some modifications to reduce the size of the critical section. CVE-2022-48715 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 low 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48715.html CVE-2022-48715 https://bugzilla.suse.com/1226621 SUSE Bug 1226621 In the Linux kernel, the following vulnerability has been resolved: net: ieee802154: ca8210: Stop leaking skb's Upon error the ieee802154_xmit_complete() helper is not called. Only ieee802154_wake_queue() is called manually. We then leak the skb structure. Free the skb structure upon error before returning. CVE-2022-48722 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48722.html CVE-2022-48722 https://bugzilla.suse.com/1226619 SUSE Bug 1226619 In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix off by one in BIOS boundary checking Bounds checking when parsing init scripts embedded in the BIOS reject access to the last byte. This causes driver initialization to fail on Apple eMac's with GeForce 2 MX GPUs, leaving the system with no working console. This is probably only seen on OpenFirmware machines like PowerPC Macs because the BIOS image provided by OF is only the used parts of the ROM, not a power-of-two blocks read from PCI directly so PCs always have empty bytes at the end that are never accessed. CVE-2022-48732 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48732.html CVE-2022-48732 https://bugzilla.suse.com/1226716 SUSE Bug 1226716 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix use-after-free after failure to create a snapshot At ioctl.c:create_snapshot(), we allocate a pending snapshot structure and then attach it to the transaction's list of pending snapshots. After that we call btrfs_commit_transaction(), and if that returns an error we jump to 'fail' label, where we kfree() the pending snapshot structure. This can result in a later use-after-free of the pending snapshot: 1) We allocated the pending snapshot and added it to the transaction's list of pending snapshots; 2) We call btrfs_commit_transaction(), and it fails either at the first call to btrfs_run_delayed_refs() or btrfs_start_dirty_block_groups(). In both cases, we don't abort the transaction and we release our transaction handle. We jump to the 'fail' label and free the pending snapshot structure. We return with the pending snapshot still in the transaction's list; 3) Another task commits the transaction. This time there's no error at all, and then during the transaction commit it accesses a pointer to the pending snapshot structure that the snapshot creation task has already freed, resulting in a user-after-free. This issue could actually be detected by smatch, which produced the following warning: fs/btrfs/ioctl.c:843 create_snapshot() warn: '&pending_snapshot->list' not removed from list So fix this by not having the snapshot creation ioctl directly add the pending snapshot to the transaction's list. Instead add the pending snapshot to the transaction handle, and then at btrfs_commit_transaction() we add the snapshot to the list only when we can guarantee that any error returned after that point will result in a transaction abort, in which case the ioctl code can safely free the pending snapshot and no one can access it anymore. CVE-2022-48733 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48733.html CVE-2022-48733 https://bugzilla.suse.com/1226718 SUSE Bug 1226718 In the Linux kernel, the following vulnerability has been resolved: selinux: fix double free of cond_list on error paths On error path from cond_read_list() and duplicate_policydb_cond_list() the cond_list_destroy() gets called a second time in caller functions, resulting in NULL pointer deref. Fix this by resetting the cond_list_len to 0 in cond_list_destroy(), making subsequent calls a noop. Also consistently reset the cond_list pointer to NULL after freeing. [PM: fix line lengths in the description] CVE-2022-48740 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48740.html CVE-2022-48740 https://bugzilla.suse.com/1226699 SUSE Bug 1226699 In the Linux kernel, the following vulnerability has been resolved: net: amd-xgbe: Fix skb data length underflow There will be BUG_ON() triggered in include/linux/skbuff.h leading to intermittent kernel panic, when the skb length underflow is detected. Fix this by dropping the packet if such length underflows are seen because of inconsistencies in the hardware descriptors. CVE-2022-48743 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48743.html CVE-2022-48743 https://bugzilla.suse.com/1226705 SUSE Bug 1226705 In the Linux kernel, the following vulnerability has been resolved: phylib: fix potential use-after-free Commit bafbdd527d56 ("phylib: Add device reset GPIO support") added call to phy_device_reset(phydev) after the put_device() call in phy_detach(). The comment before the put_device() call says that the phydev might go away with put_device(). Fix potential use-after-free by calling phy_device_reset() before put_device(). CVE-2022-48754 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48754.html CVE-2022-48754 https://bugzilla.suse.com/1226692 SUSE Bug 1226692 In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable The function performs a check on the "phy" input parameter, however, it is used before the check. Initialize the "dev" variable after the sanity check to avoid a possible NULL pointer dereference. Addresses-Coverity-ID: 1493860 ("Null pointer dereference") CVE-2022-48756 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48756.html CVE-2022-48756 https://bugzilla.suse.com/1226698 SUSE Bug 1226698 In the Linux kernel, the following vulnerability has been resolved: scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put() The bnx2fc_destroy() functions are removing the interface before calling destroy_work. This results multiple WARNings from sysfs_remove_group() as the controller rport device attributes are removed too early. Replace the fcoe_port's destroy_work queue. It's not needed. The problem is easily reproducible with the following steps. Example: $ dmesg -w & $ systemctl enable --now fcoe $ fipvlan -s -c ens2f1 $ fcoeadm -d ens2f1.802 [ 583.464488] host2: libfc: Link down on port (7500a1) [ 583.472651] bnx2fc: 7500a1 - rport not created Yet!! [ 583.490468] ------------[ cut here ]------------ [ 583.538725] sysfs group 'power' not found for kobject 'rport-2:0-0' [ 583.568814] WARNING: CPU: 3 PID: 192 at fs/sysfs/group.c:279 sysfs_remove_group+0x6f/0x80 [ 583.607130] Modules linked in: dm_service_time 8021q garp mrp stp llc bnx2fc cnic uio rpcsec_gss_krb5 auth_rpcgss nfsv4 ... [ 583.942994] CPU: 3 PID: 192 Comm: kworker/3:2 Kdump: loaded Not tainted 5.14.0-39.el9.x86_64 #1 [ 583.984105] Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013 [ 584.016535] Workqueue: fc_wq_2 fc_rport_final_delete [scsi_transport_fc] [ 584.050691] RIP: 0010:sysfs_remove_group+0x6f/0x80 [ 584.074725] Code: ff 5b 48 89 ef 5d 41 5c e9 ee c0 ff ff 48 89 ef e8 f6 b8 ff ff eb d1 49 8b 14 24 48 8b 33 48 c7 c7 ... [ 584.162586] RSP: 0018:ffffb567c15afdc0 EFLAGS: 00010282 [ 584.188225] RAX: 0000000000000000 RBX: ffffffff8eec4220 RCX: 0000000000000000 [ 584.221053] RDX: ffff8c1586ce84c0 RSI: ffff8c1586cd7cc0 RDI: ffff8c1586cd7cc0 [ 584.255089] RBP: 0000000000000000 R08: 0000000000000000 R09: ffffb567c15afc00 [ 584.287954] R10: ffffb567c15afbf8 R11: ffffffff8fbe7f28 R12: ffff8c1486326400 [ 584.322356] R13: ffff8c1486326480 R14: ffff8c1483a4a000 R15: 0000000000000004 [ 584.355379] FS: 0000000000000000(0000) GS:ffff8c1586cc0000(0000) knlGS:0000000000000000 [ 584.394419] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 584.421123] CR2: 00007fe95a6f7840 CR3: 0000000107674002 CR4: 00000000000606e0 [ 584.454888] Call Trace: [ 584.466108] device_del+0xb2/0x3e0 [ 584.481701] device_unregister+0x13/0x60 [ 584.501306] bsg_unregister_queue+0x5b/0x80 [ 584.522029] bsg_remove_queue+0x1c/0x40 [ 584.541884] fc_rport_final_delete+0xf3/0x1d0 [scsi_transport_fc] [ 584.573823] process_one_work+0x1e3/0x3b0 [ 584.592396] worker_thread+0x50/0x3b0 [ 584.609256] ? rescuer_thread+0x370/0x370 [ 584.628877] kthread+0x149/0x170 [ 584.643673] ? set_kthread_struct+0x40/0x40 [ 584.662909] ret_from_fork+0x22/0x30 [ 584.680002] ---[ end trace 53575ecefa942ece ]--- CVE-2022-48758 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48758.html CVE-2022-48758 https://bugzilla.suse.com/1226708 SUSE Bug 1226708 In the Linux kernel, the following vulnerability has been resolved: rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev struct rpmsg_ctrldev contains a struct cdev. The current code frees the rpmsg_ctrldev struct in rpmsg_ctrldev_release_device(), but the cdev is a managed object, therefore its release is not predictable and the rpmsg_ctrldev could be freed before the cdev is entirely released, as in the backtrace below. [ 93.625603] ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x7c [ 93.636115] WARNING: CPU: 0 PID: 12 at lib/debugobjects.c:488 debug_print_object+0x13c/0x1b0 [ 93.644799] Modules linked in: veth xt_cgroup xt_MASQUERADE rfcomm algif_hash algif_skcipher af_alg uinput ip6table_nat fuse uvcvideo videobuf2_vmalloc venus_enc venus_dec videobuf2_dma_contig hci_uart btandroid btqca snd_soc_rt5682_i2c bluetooth qcom_spmi_temp_alarm snd_soc_rt5682v [ 93.715175] CPU: 0 PID: 12 Comm: kworker/0:1 Tainted: G B 5.4.163-lockdep #26 [ 93.723855] Hardware name: Google Lazor (rev3 - 8) with LTE (DT) [ 93.730055] Workqueue: events kobject_delayed_cleanup [ 93.735271] pstate: 60c00009 (nZCv daif +PAN +UAO) [ 93.740216] pc : debug_print_object+0x13c/0x1b0 [ 93.744890] lr : debug_print_object+0x13c/0x1b0 [ 93.749555] sp : ffffffacf5bc7940 [ 93.752978] x29: ffffffacf5bc7940 x28: dfffffd000000000 [ 93.758448] x27: ffffffacdb11a800 x26: dfffffd000000000 [ 93.763916] x25: ffffffd0734f856c x24: dfffffd000000000 [ 93.769389] x23: 0000000000000000 x22: ffffffd0733c35b0 [ 93.774860] x21: ffffffd0751994a0 x20: ffffffd075ec27c0 [ 93.780338] x19: ffffffd075199100 x18: 00000000000276e0 [ 93.785814] x17: 0000000000000000 x16: dfffffd000000000 [ 93.791291] x15: ffffffffffffffff x14: 6e6968207473696c [ 93.796768] x13: 0000000000000000 x12: ffffffd075e2b000 [ 93.802244] x11: 0000000000000001 x10: 0000000000000000 [ 93.807723] x9 : d13400dff1921900 x8 : d13400dff1921900 [ 93.813200] x7 : 0000000000000000 x6 : 0000000000000000 [ 93.818676] x5 : 0000000000000080 x4 : 0000000000000000 [ 93.824152] x3 : ffffffd0732a0fa4 x2 : 0000000000000001 [ 93.829628] x1 : ffffffacf5bc7580 x0 : 0000000000000061 [ 93.835104] Call trace: [ 93.837644] debug_print_object+0x13c/0x1b0 [ 93.841963] __debug_check_no_obj_freed+0x25c/0x3c0 [ 93.846987] debug_check_no_obj_freed+0x18/0x20 [ 93.851669] slab_free_freelist_hook+0xbc/0x1e4 [ 93.856346] kfree+0xfc/0x2f4 [ 93.859416] rpmsg_ctrldev_release_device+0x78/0xb8 [ 93.864445] device_release+0x84/0x168 [ 93.868310] kobject_cleanup+0x12c/0x298 [ 93.872356] kobject_delayed_cleanup+0x10/0x18 [ 93.876948] process_one_work+0x578/0x92c [ 93.881086] worker_thread+0x804/0xcf8 [ 93.884963] kthread+0x2a8/0x314 [ 93.888303] ret_from_fork+0x10/0x18 The cdev_device_add/del() API was created to address this issue (see commit '233ed09d7fda ("chardev: add helper function to register char devs with a struct device")'), use it instead of cdev add/del(). CVE-2022-48759 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48759.html CVE-2022-48759 https://bugzilla.suse.com/1226711 SUSE Bug 1226711 In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix hang in usb_kill_urb by adding memory barriers The syzbot fuzzer has identified a bug in which processes hang waiting for usb_kill_urb() to return. It turns out the issue is not unlinking the URB; that works just fine. Rather, the problem arises when the wakeup notification that the URB has completed is not received. The reason is memory-access ordering on SMP systems. In outline form, usb_kill_urb() and __usb_hcd_giveback_urb() operating concurrently on different CPUs perform the following actions: CPU 0 CPU 1 ---------------------------- --------------------------------- usb_kill_urb(): __usb_hcd_giveback_urb(): ... ... atomic_inc(&urb->reject); atomic_dec(&urb->use_count); ... ... wait_event(usb_kill_urb_queue, atomic_read(&urb->use_count) == 0); if (atomic_read(&urb->reject)) wake_up(&usb_kill_urb_queue); Confining your attention to urb->reject and urb->use_count, you can see that the overall pattern of accesses on CPU 0 is: write urb->reject, then read urb->use_count; whereas the overall pattern of accesses on CPU 1 is: write urb->use_count, then read urb->reject. This pattern is referred to in memory-model circles as SB (for "Store Buffering"), and it is well known that without suitable enforcement of the desired order of accesses -- in the form of memory barriers -- it is entirely possible for one or both CPUs to execute their reads ahead of their writes. The end result will be that sometimes CPU 0 sees the old un-decremented value of urb->use_count while CPU 1 sees the old un-incremented value of urb->reject. Consequently CPU 0 ends up on the wait queue and never gets woken up, leading to the observed hang in usb_kill_urb(). The same pattern of accesses occurs in usb_poison_urb() and the failure pathway of usb_hcd_submit_urb(). The problem is fixed by adding suitable memory barriers. To provide proper memory-access ordering in the SB pattern, a full barrier is required on both CPUs. The atomic_inc() and atomic_dec() accesses themselves don't provide any memory ordering, but since they are present, we can use the optimized smp_mb__after_atomic() memory barrier in the various routines to obtain the desired effect. This patch adds the necessary memory barriers. CVE-2022-48760 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48760.html CVE-2022-48760 https://bugzilla.suse.com/1226712 SUSE Bug 1226712 In the Linux kernel, the following vulnerability has been resolved: usb: xhci-plat: fix crash when suspend if remote wake enable Crashed at i.mx8qm platform when suspend if enable remote wakeup Internal error: synchronous external abort: 96000210 [#1] PREEMPT SMP Modules linked in: CPU: 2 PID: 244 Comm: kworker/u12:6 Not tainted 5.15.5-dirty #12 Hardware name: Freescale i.MX8QM MEK (DT) Workqueue: events_unbound async_run_entry_fn pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : xhci_disable_hub_port_wake.isra.62+0x60/0xf8 lr : xhci_disable_hub_port_wake.isra.62+0x34/0xf8 sp : ffff80001394bbf0 x29: ffff80001394bbf0 x28: 0000000000000000 x27: ffff00081193b578 x26: ffff00081193b570 x25: 0000000000000000 x24: 0000000000000000 x23: ffff00081193a29c x22: 0000000000020001 x21: 0000000000000001 x20: 0000000000000000 x19: ffff800014e90490 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000000 x13: 0000000000000002 x12: 0000000000000000 x11: 0000000000000000 x10: 0000000000000960 x9 : ffff80001394baa0 x8 : ffff0008145d1780 x7 : ffff0008f95b8e80 x6 : 000000001853b453 x5 : 0000000000000496 x4 : 0000000000000000 x3 : ffff00081193a29c x2 : 0000000000000001 x1 : 0000000000000000 x0 : ffff000814591620 Call trace: xhci_disable_hub_port_wake.isra.62+0x60/0xf8 xhci_suspend+0x58/0x510 xhci_plat_suspend+0x50/0x78 platform_pm_suspend+0x2c/0x78 dpm_run_callback.isra.25+0x50/0xe8 __device_suspend+0x108/0x3c0 The basic flow: 1. run time suspend call xhci_suspend, xhci parent devices gate the clock. 2. echo mem >/sys/power/state, system _device_suspend call xhci_suspend 3. xhci_suspend call xhci_disable_hub_port_wake, which access register, but clock already gated by run time suspend. This problem was hidden by power domain driver, which call run time resume before it. But the below commit remove it and make this issue happen. commit c1df456d0f06e ("PM: domains: Don't runtime resume devices at genpd_prepare()") This patch call run time resume before suspend to make sure clock is on before access register. Testeb-by: Abel Vesa <abel.vesa@nxp.com> CVE-2022-48761 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48761.html CVE-2022-48761 https://bugzilla.suse.com/1226701 SUSE Bug 1226701 In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Fix stale file descriptors on failed usercopy A failing usercopy of the fence_rep object will lead to a stale entry in the file descriptor table as put_unused_fd() won't release it. This enables userland to refer to a dangling 'file' object through that still valid file descriptor, leading to all kinds of use-after-free exploitation scenarios. Fix this by deferring the call to fd_install() until after the usercopy has succeeded. CVE-2022-48771 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48771.html CVE-2022-48771 https://bugzilla.suse.com/1226732 SUSE Bug 1226732 In the Linux kernel, the following vulnerability has been resolved: media: lgdt3306a: Add a check against null-pointer-def The driver should check whether the client provides the platform_data. The following log reveals it: [ 29.610324] BUG: KASAN: null-ptr-deref in kmemdup+0x30/0x40 [ 29.610730] Read of size 40 at addr 0000000000000000 by task bash/414 [ 29.612820] Call Trace: [ 29.613030] <TASK> [ 29.613201] dump_stack_lvl+0x56/0x6f [ 29.613496] ? kmemdup+0x30/0x40 [ 29.613754] print_report.cold+0x494/0x6b7 [ 29.614082] ? kmemdup+0x30/0x40 [ 29.614340] kasan_report+0x8a/0x190 [ 29.614628] ? kmemdup+0x30/0x40 [ 29.614888] kasan_check_range+0x14d/0x1d0 [ 29.615213] memcpy+0x20/0x60 [ 29.615454] kmemdup+0x30/0x40 [ 29.615700] lgdt3306a_probe+0x52/0x310 [ 29.616339] i2c_device_probe+0x951/0xa90 CVE-2022-48772 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2022-48772.html CVE-2022-48772 https://bugzilla.suse.com/1226976 SUSE Bug 1226976 Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS. CVE-2023-24023 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-24023.html CVE-2023-24023 https://bugzilla.suse.com/1218148 SUSE Bug 1218148 In the Linux kernel, the following vulnerability has been resolved: ext4: avoid online resizing failures due to oversized flex bg When we online resize an ext4 filesystem with a oversized flexbg_size, mkfs.ext4 -F -G 67108864 $dev -b 4096 100M mount $dev $dir resize2fs $dev 16G the following WARN_ON is triggered: ================================================================== WARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550 Modules linked in: sg(E) CPU: 0 PID: 427 Comm: resize2fs Tainted: G E 6.6.0-rc5+ #314 RIP: 0010:__alloc_pages+0x411/0x550 Call Trace: <TASK> __kmalloc_large_node+0xa2/0x200 __kmalloc+0x16e/0x290 ext4_resize_fs+0x481/0xd80 __ext4_ioctl+0x1616/0x1d90 ext4_ioctl+0x12/0x20 __x64_sys_ioctl+0xf0/0x150 do_syscall_64+0x3b/0x90 ================================================================== This is because flexbg_size is too large and the size of the new_group_data array to be allocated exceeds MAX_ORDER. Currently, the minimum value of MAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding maximum number of groups that can be allocated is: (PAGE_SIZE << MAX_ORDER) / sizeof(struct ext4_new_group_data) ~ 21845 And the value that is down-aligned to the power of 2 is 16384. Therefore, this value is defined as MAX_RESIZE_BG, and the number of groups added each time does not exceed this value during resizing, and is added multiple times to complete the online resizing. The difference is that the metadata in a flex_bg may be more dispersed. CVE-2023-52622 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52622.html CVE-2023-52622 https://bugzilla.suse.com/1222080 SUSE Bug 1222080 In the Linux kernel, the following vulnerability has been resolved: powerpc/imc-pmu: Add a null pointer check in update_events_in_group() kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. CVE-2023-52675 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52675.html CVE-2023-52675 https://bugzilla.suse.com/1224504 SUSE Bug 1224504 In the Linux kernel, the following vulnerability has been resolved: btrfs: lock the inode in shared mode before starting fiemap Currently fiemap does not take the inode's lock (VFS lock), it only locks a file range in the inode's io tree. This however can lead to a deadlock if we have a concurrent fsync on the file and fiemap code triggers a fault when accessing the user space buffer with fiemap_fill_next_extent(). The deadlock happens on the inode's i_mmap_lock semaphore, which is taken both by fsync and btrfs_page_mkwrite(). This deadlock was recently reported by syzbot and triggers a trace like the following: task:syz-executor361 state:D stack:20264 pid:5668 ppid:5119 flags:0x00004004 Call Trace: <TASK> context_switch kernel/sched/core.c:5293 [inline] __schedule+0x995/0xe20 kernel/sched/core.c:6606 schedule+0xcb/0x190 kernel/sched/core.c:6682 wait_on_state fs/btrfs/extent-io-tree.c:707 [inline] wait_extent_bit+0x577/0x6f0 fs/btrfs/extent-io-tree.c:751 lock_extent+0x1c2/0x280 fs/btrfs/extent-io-tree.c:1742 find_lock_delalloc_range+0x4e6/0x9c0 fs/btrfs/extent_io.c:488 writepage_delalloc+0x1ef/0x540 fs/btrfs/extent_io.c:1863 __extent_writepage+0x736/0x14e0 fs/btrfs/extent_io.c:2174 extent_write_cache_pages+0x983/0x1220 fs/btrfs/extent_io.c:3091 extent_writepages+0x219/0x540 fs/btrfs/extent_io.c:3211 do_writepages+0x3c3/0x680 mm/page-writeback.c:2581 filemap_fdatawrite_wbc+0x11e/0x170 mm/filemap.c:388 __filemap_fdatawrite_range mm/filemap.c:421 [inline] filemap_fdatawrite_range+0x175/0x200 mm/filemap.c:439 btrfs_fdatawrite_range fs/btrfs/file.c:3850 [inline] start_ordered_ops fs/btrfs/file.c:1737 [inline] btrfs_sync_file+0x4ff/0x1190 fs/btrfs/file.c:1839 generic_write_sync include/linux/fs.h:2885 [inline] btrfs_do_write_iter+0xcd3/0x1280 fs/btrfs/file.c:1684 call_write_iter include/linux/fs.h:2189 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x7dc/0xc50 fs/read_write.c:584 ksys_write+0x177/0x2a0 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f7d4054e9b9 RSP: 002b:00007f7d404fa2f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f7d405d87a0 RCX: 00007f7d4054e9b9 RDX: 0000000000000090 RSI: 0000000020000000 RDI: 0000000000000006 RBP: 00007f7d405a51d0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 61635f65646f6e69 R13: 65646f7475616f6e R14: 7261637369646f6e R15: 00007f7d405d87a8 </TASK> INFO: task syz-executor361:5697 blocked for more than 145 seconds. Not tainted 6.2.0-rc3-syzkaller-00376-g7c6984405241 #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor361 state:D stack:21216 pid:5697 ppid:5119 flags:0x00004004 Call Trace: <TASK> context_switch kernel/sched/core.c:5293 [inline] __schedule+0x995/0xe20 kernel/sched/core.c:6606 schedule+0xcb/0x190 kernel/sched/core.c:6682 rwsem_down_read_slowpath+0x5f9/0x930 kernel/locking/rwsem.c:1095 __down_read_common+0x54/0x2a0 kernel/locking/rwsem.c:1260 btrfs_page_mkwrite+0x417/0xc80 fs/btrfs/inode.c:8526 do_page_mkwrite+0x19e/0x5e0 mm/memory.c:2947 wp_page_shared+0x15e/0x380 mm/memory.c:3295 handle_pte_fault mm/memory.c:4949 [inline] __handle_mm_fault mm/memory.c:5073 [inline] handle_mm_fault+0x1b79/0x26b0 mm/memory.c:5219 do_user_addr_fault+0x69b/0xcb0 arch/x86/mm/fault.c:1428 handle_page_fault arch/x86/mm/fault.c:1519 [inline] exc_page_fault+0x7a/0x110 arch/x86/mm/fault.c:1575 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570 RIP: 0010:copy_user_short_string+0xd/0x40 arch/x86/lib/copy_user_64.S:233 Code: 74 0a 89 (...) RSP: 0018:ffffc9000570f330 EFLAGS: 000502 ---truncated--- CVE-2023-52737 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52737.html CVE-2023-52737 https://bugzilla.suse.com/1225484 SUSE Bug 1225484 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() Skip SMB sessions that are being teared down (e.g. @ses->ses_status == SES_EXITING) in cifs_debug_data_proc_show() to avoid use-after-free in @ses. This fixes the following GPF when reading from /proc/fs/cifs/DebugData while mounting and umounting [ 816.251274] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6d81: 0000 [#1] PREEMPT SMP NOPTI ... [ 816.260138] Call Trace: [ 816.260329] <TASK> [ 816.260499] ? die_addr+0x36/0x90 [ 816.260762] ? exc_general_protection+0x1b3/0x410 [ 816.261126] ? asm_exc_general_protection+0x26/0x30 [ 816.261502] ? cifs_debug_tcon+0xbd/0x240 [cifs] [ 816.261878] ? cifs_debug_tcon+0xab/0x240 [cifs] [ 816.262249] cifs_debug_data_proc_show+0x516/0xdb0 [cifs] [ 816.262689] ? seq_read_iter+0x379/0x470 [ 816.262995] seq_read_iter+0x118/0x470 [ 816.263291] proc_reg_read_iter+0x53/0x90 [ 816.263596] ? srso_alias_return_thunk+0x5/0x7f [ 816.263945] vfs_read+0x201/0x350 [ 816.264211] ksys_read+0x75/0x100 [ 816.264472] do_syscall_64+0x3f/0x90 [ 816.264750] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 816.265135] RIP: 0033:0x7fd5e669d381 CVE-2023-52752 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52752.html CVE-2023-52752 https://bugzilla.suse.com/1225487 SUSE Bug 1225487 https://bugzilla.suse.com/1225819 SUSE Bug 1225819 In the Linux kernel, the following vulnerability has been resolved: media: imon: fix access to invalid resource for the second interface imon driver probes two USB interfaces, and at the probe of the second interface, the driver assumes blindly that the first interface got bound with the same imon driver. It's usually true, but it's still possible that the first interface is bound with another driver via a malformed descriptor. Then it may lead to a memory corruption, as spotted by syzkaller; imon driver accesses the data from drvdata as struct imon_context object although it's a completely different one that was assigned by another driver. This patch adds a sanity check -- whether the first interface is really bound with the imon driver or not -- for avoiding the problem above at the probe time. CVE-2023-52754 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52754.html CVE-2023-52754 https://bugzilla.suse.com/1225490 SUSE Bug 1225490 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential deadlock when releasing mids All release_mid() callers seem to hold a reference of @mid so there is no need to call kref_put(&mid->refcount, __release_mid) under @server->mid_lock spinlock. If they don't, then an use-after-free bug would have occurred anyways. By getting rid of such spinlock also fixes a potential deadlock as shown below CPU 0 CPU 1 ------------------------------------------------------------------ cifs_demultiplex_thread() cifs_debug_data_proc_show() release_mid() spin_lock(&server->mid_lock); spin_lock(&cifs_tcp_ses_lock) spin_lock(&server->mid_lock) __release_mid() smb2_find_smb_tcon() spin_lock(&cifs_tcp_ses_lock) *deadlock* CVE-2023-52757 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52757.html CVE-2023-52757 https://bugzilla.suse.com/1225548 SUSE Bug 1225548 In the Linux kernel, the following vulnerability has been resolved: virtio-blk: fix implicit overflow on virtio_max_dma_size The following codes have an implicit conversion from size_t to u32: (u32)max_size = (size_t)virtio_max_dma_size(vdev); This may lead overflow, Ex (size_t)4G -> (u32)0. Once virtio_max_dma_size() has a larger size than U32_MAX, use U32_MAX instead. CVE-2023-52762 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52762.html CVE-2023-52762 https://bugzilla.suse.com/1225573 SUSE Bug 1225573 In the Linux kernel, the following vulnerability has been resolved: media: gspca: cpia1: shift-out-of-bounds in set_flicker Syzkaller reported the following issue: UBSAN: shift-out-of-bounds in drivers/media/usb/gspca/cpia1.c:1031:27 shift exponent 245 is too large for 32-bit type 'int' When the value of the variable "sd->params.exposure.gain" exceeds the number of bits in an integer, a shift-out-of-bounds error is reported. It is triggered because the variable "currentexp" cannot be left-shifted by more than the number of bits in an integer. In order to avoid invalid range during left-shift, the conditional expression is added. CVE-2023-52764 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52764.html CVE-2023-52764 https://bugzilla.suse.com/1225571 SUSE Bug 1225571 In the Linux kernel, the following vulnerability has been resolved: bonding: stop the device in bond_setup_by_slave() Commit 9eed321cde22 ("net: lapbether: only support ethernet devices") has been able to keep syzbot away from net/lapb, until today. In the following splat [1], the issue is that a lapbether device has been created on a bonding device without members. Then adding a non ARPHRD_ETHER member forced the bonding master to change its type. The fix is to make sure we call dev_close() in bond_setup_by_slave() so that the potential linked lapbether devices (or any other devices having assumptions on the physical device) are removed. A similar bug has been addressed in commit 40baec225765 ("bonding: fix panic on non-ARPHRD_ETHER enslave failure") [1] skbuff: skb_under_panic: text:ffff800089508810 len:44 put:40 head:ffff0000c78e7c00 data:ffff0000c78e7bea tail:0x16 end:0x140 dev:bond0 kernel BUG at net/core/skbuff.c:192 ! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 0 PID: 6007 Comm: syz-executor383 Not tainted 6.6.0-rc3-syzkaller-gbf6547d8715b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : skb_panic net/core/skbuff.c:188 [inline] pc : skb_under_panic+0x13c/0x140 net/core/skbuff.c:202 lr : skb_panic net/core/skbuff.c:188 [inline] lr : skb_under_panic+0x13c/0x140 net/core/skbuff.c:202 sp : ffff800096a06aa0 x29: ffff800096a06ab0 x28: ffff800096a06ba0 x27: dfff800000000000 x26: ffff0000ce9b9b50 x25: 0000000000000016 x24: ffff0000c78e7bea x23: ffff0000c78e7c00 x22: 000000000000002c x21: 0000000000000140 x20: 0000000000000028 x19: ffff800089508810 x18: ffff800096a06100 x17: 0000000000000000 x16: ffff80008a629a3c x15: 0000000000000001 x14: 1fffe00036837a32 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000201 x10: 0000000000000000 x9 : cb50b496c519aa00 x8 : cb50b496c519aa00 x7 : 0000000000000001 x6 : 0000000000000001 x5 : ffff800096a063b8 x4 : ffff80008e280f80 x3 : ffff8000805ad11c x2 : 0000000000000001 x1 : 0000000100000201 x0 : 0000000000000086 Call trace: skb_panic net/core/skbuff.c:188 [inline] skb_under_panic+0x13c/0x140 net/core/skbuff.c:202 skb_push+0xf0/0x108 net/core/skbuff.c:2446 ip6gre_header+0xbc/0x738 net/ipv6/ip6_gre.c:1384 dev_hard_header include/linux/netdevice.h:3136 [inline] lapbeth_data_transmit+0x1c4/0x298 drivers/net/wan/lapbether.c:257 lapb_data_transmit+0x8c/0xb0 net/lapb/lapb_iface.c:447 lapb_transmit_buffer+0x178/0x204 net/lapb/lapb_out.c:149 lapb_send_control+0x220/0x320 net/lapb/lapb_subr.c:251 __lapb_disconnect_request+0x9c/0x17c net/lapb/lapb_iface.c:326 lapb_device_event+0x288/0x4e0 net/lapb/lapb_iface.c:492 notifier_call_chain+0x1a4/0x510 kernel/notifier.c:93 raw_notifier_call_chain+0x3c/0x50 kernel/notifier.c:461 call_netdevice_notifiers_info net/core/dev.c:1970 [inline] call_netdevice_notifiers_extack net/core/dev.c:2008 [inline] call_netdevice_notifiers net/core/dev.c:2022 [inline] __dev_close_many+0x1b8/0x3c4 net/core/dev.c:1508 dev_close_many+0x1e0/0x470 net/core/dev.c:1559 dev_close+0x174/0x250 net/core/dev.c:1585 lapbeth_device_event+0x2e4/0x958 drivers/net/wan/lapbether.c:466 notifier_call_chain+0x1a4/0x510 kernel/notifier.c:93 raw_notifier_call_chain+0x3c/0x50 kernel/notifier.c:461 call_netdevice_notifiers_info net/core/dev.c:1970 [inline] call_netdevice_notifiers_extack net/core/dev.c:2008 [inline] call_netdevice_notifiers net/core/dev.c:2022 [inline] __dev_close_many+0x1b8/0x3c4 net/core/dev.c:1508 dev_close_many+0x1e0/0x470 net/core/dev.c:1559 dev_close+0x174/0x250 net/core/dev.c:1585 bond_enslave+0x2298/0x30cc drivers/net/bonding/bond_main.c:2332 bond_do_ioctl+0x268/0xc64 drivers/net/bonding/bond_main.c:4539 dev_ifsioc+0x754/0x9ac dev_ioctl+0x4d8/0xd34 net/core/dev_ioctl.c:786 sock_do_ioctl+0x1d4/0x2d0 net/socket.c:1217 sock_ioctl+0x4e8/0x834 net/socket.c:1322 vfs_ioctl fs/ioctl.c:51 [inline] __do_ ---truncated--- CVE-2023-52784 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52784.html CVE-2023-52784 https://bugzilla.suse.com/1224946 SUSE Bug 1224946 In the Linux kernel, the following vulnerability has been resolved: scsi: hisi_sas: Set debugfs_dir pointer to NULL after removing debugfs If init debugfs failed during device registration due to memory allocation failure, debugfs_remove_recursive() is called, after which debugfs_dir is not set to NULL. debugfs_remove_recursive() will be called again during device removal. As a result, illegal pointer is accessed. [ 1665.467244] hisi_sas_v3_hw 0000:b4:02.0: failed to init debugfs! ... [ 1669.836708] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a0 [ 1669.872669] pc : down_write+0x24/0x70 [ 1669.876315] lr : down_write+0x1c/0x70 [ 1669.879961] sp : ffff000036f53a30 [ 1669.883260] x29: ffff000036f53a30 x28: ffffa027c31549f8 [ 1669.888547] x27: ffffa027c3140000 x26: 0000000000000000 [ 1669.893834] x25: ffffa027bf37c270 x24: ffffa027bf37c270 [ 1669.899122] x23: ffff0000095406b8 x22: ffff0000095406a8 [ 1669.904408] x21: 0000000000000000 x20: ffffa027bf37c310 [ 1669.909695] x19: 00000000000000a0 x18: ffff8027dcd86f10 [ 1669.914982] x17: 0000000000000000 x16: 0000000000000000 [ 1669.920268] x15: 0000000000000000 x14: ffffa0274014f870 [ 1669.925555] x13: 0000000000000040 x12: 0000000000000228 [ 1669.930842] x11: 0000000000000020 x10: 0000000000000bb0 [ 1669.936129] x9 : ffff000036f537f0 x8 : ffff80273088ca10 [ 1669.941416] x7 : 000000000000001d x6 : 00000000ffffffff [ 1669.946702] x5 : ffff000008a36310 x4 : ffff80273088be00 [ 1669.951989] x3 : ffff000009513e90 x2 : 0000000000000000 [ 1669.957276] x1 : 00000000000000a0 x0 : ffffffff00000001 [ 1669.962563] Call trace: [ 1669.965000] down_write+0x24/0x70 [ 1669.968301] debugfs_remove_recursive+0x5c/0x1b0 [ 1669.972905] hisi_sas_debugfs_exit+0x24/0x30 [hisi_sas_main] [ 1669.978541] hisi_sas_v3_remove+0x130/0x150 [hisi_sas_v3_hw] [ 1669.984175] pci_device_remove+0x48/0xd8 [ 1669.988082] device_release_driver_internal+0x1b4/0x250 [ 1669.993282] device_release_driver+0x28/0x38 [ 1669.997534] pci_stop_bus_device+0x84/0xb8 [ 1670.001611] pci_stop_and_remove_bus_device_locked+0x24/0x40 [ 1670.007244] remove_store+0xfc/0x140 [ 1670.010802] dev_attr_store+0x44/0x60 [ 1670.014448] sysfs_kf_write+0x58/0x80 [ 1670.018095] kernfs_fop_write+0xe8/0x1f0 [ 1670.022000] __vfs_write+0x60/0x190 [ 1670.025472] vfs_write+0xac/0x1c0 [ 1670.028771] ksys_write+0x6c/0xd8 [ 1670.032071] __arm64_sys_write+0x24/0x30 [ 1670.035977] el0_svc_common+0x78/0x130 [ 1670.039710] el0_svc_handler+0x38/0x78 [ 1670.043442] el0_svc+0x8/0xc To fix this, set debugfs_dir to NULL after debugfs_remove_recursive(). CVE-2023-52808 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52808.html CVE-2023-52808 https://bugzilla.suse.com/1225555 SUSE Bug 1225555 In the Linux kernel, the following vulnerability has been resolved: scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() fc_lport_ptp_setup() did not check the return value of fc_rport_create() which can return NULL and would cause a NULL pointer dereference. Address this issue by checking return value of fc_rport_create() and log error message on fc_rport_create() failed. CVE-2023-52809 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52809.html CVE-2023-52809 https://bugzilla.suse.com/1225556 SUSE Bug 1225556 In the Linux kernel, the following vulnerability has been resolved: scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool In practice the driver should never send more commands than are allocated to a queue's event pool. In the unlikely event that this happens, the code asserts a BUG_ON, and in the case that the kernel is not configured to crash on panic returns a junk event pointer from the empty event list causing things to spiral from there. This BUG_ON is a historical artifact of the ibmvfc driver first being upstreamed, and it is well known now that the use of BUG_ON is bad practice except in the most unrecoverable scenario. There is nothing about this scenario that prevents the driver from recovering and carrying on. Remove the BUG_ON in question from ibmvfc_get_event() and return a NULL pointer in the case of an empty event pool. Update all call sites to ibmvfc_get_event() to check for a NULL pointer and perfrom the appropriate failure or recovery action. CVE-2023-52811 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52811.html CVE-2023-52811 https://bugzilla.suse.com/1225559 SUSE Bug 1225559 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don't return unset power in ieee80211_get_tx_power() We can get a UBSAN warning if ieee80211_get_tx_power() returns the INT_MIN value mac80211 internally uses for "unset power level". UBSAN: signed-integer-overflow in net/wireless/nl80211.c:3816:5 -2147483648 * 100 cannot be represented in type 'int' CPU: 0 PID: 20433 Comm: insmod Tainted: G WC OE Call Trace: dump_stack+0x74/0x92 ubsan_epilogue+0x9/0x50 handle_overflow+0x8d/0xd0 __ubsan_handle_mul_overflow+0xe/0x10 nl80211_send_iface+0x688/0x6b0 [cfg80211] [...] cfg80211_register_wdev+0x78/0xb0 [cfg80211] cfg80211_netdev_notifier_call+0x200/0x620 [cfg80211] [...] ieee80211_if_add+0x60e/0x8f0 [mac80211] ieee80211_register_hw+0xda5/0x1170 [mac80211] In this case, simply return an error instead, to indicate that no data is available. CVE-2023-52832 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52832.html CVE-2023-52832 https://bugzilla.suse.com/1225577 SUSE Bug 1225577 In the Linux kernel, the following vulnerability has been resolved: atl1c: Work around the DMA RX overflow issue This is based on alx driver commit 881d0327db37 ("net: alx: Work around the DMA RX overflow issue"). The alx and atl1c drivers had RX overflow error which was why a custom allocator was created to avoid certain addresses. The simpler workaround then created for alx driver, but not for atl1c due to lack of tester. Instead of using a custom allocator, check the allocated skb address and use skb_reserve() to move away from problematic 0x...fc0 address. Tested on AR8131 on Acer 4540. CVE-2023-52834 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52834.html CVE-2023-52834 https://bugzilla.suse.com/1225599 SUSE Bug 1225599 In the Linux kernel, the following vulnerability has been resolved: perf/core: Bail out early if the request AUX area is out of bound When perf-record with a large AUX area, e.g 4GB, it fails with: #perf record -C 0 -m ,4G -e arm_spe_0// -- sleep 1 failed to mmap with 12 (Cannot allocate memory) and it reveals a WARNING with __alloc_pages(): ------------[ cut here ]------------ WARNING: CPU: 44 PID: 17573 at mm/page_alloc.c:5568 __alloc_pages+0x1ec/0x248 Call trace: __alloc_pages+0x1ec/0x248 __kmalloc_large_node+0xc0/0x1f8 __kmalloc_node+0x134/0x1e8 rb_alloc_aux+0xe0/0x298 perf_mmap+0x440/0x660 mmap_region+0x308/0x8a8 do_mmap+0x3c0/0x528 vm_mmap_pgoff+0xf4/0x1b8 ksys_mmap_pgoff+0x18c/0x218 __arm64_sys_mmap+0x38/0x58 invoke_syscall+0x50/0x128 el0_svc_common.constprop.0+0x58/0x188 do_el0_svc+0x34/0x50 el0_svc+0x34/0x108 el0t_64_sync_handler+0xb8/0xc0 el0t_64_sync+0x1a4/0x1a8 'rb->aux_pages' allocated by kcalloc() is a pointer array which is used to maintains AUX trace pages. The allocated page for this array is physically contiguous (and virtually contiguous) with an order of 0..MAX_ORDER. If the size of pointer array crosses the limitation set by MAX_ORDER, it reveals a WARNING. So bail out early with -ENOMEM if the request AUX area is out of bound, e.g.: #perf record -C 0 -m ,4G -e arm_spe_0// -- sleep 1 failed to mmap with 12 (Cannot allocate memory) CVE-2023-52835 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 low 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52835.html CVE-2023-52835 https://bugzilla.suse.com/1225602 SUSE Bug 1225602 In the Linux kernel, the following vulnerability has been resolved: llc: verify mac len before reading mac header LLC reads the mac header with eth_hdr without verifying that the skb has an Ethernet header. Syzbot was able to enter llc_rcv on a tun device. Tun can insert packets without mac len and with user configurable skb->protocol (passing a tun_pi header when not configuring IFF_NO_PI). BUG: KMSAN: uninit-value in llc_station_ac_send_test_r net/llc/llc_station.c:81 [inline] BUG: KMSAN: uninit-value in llc_station_rcv+0x6fb/0x1290 net/llc/llc_station.c:111 llc_station_ac_send_test_r net/llc/llc_station.c:81 [inline] llc_station_rcv+0x6fb/0x1290 net/llc/llc_station.c:111 llc_rcv+0xc5d/0x14a0 net/llc/llc_input.c:218 __netif_receive_skb_one_core net/core/dev.c:5523 [inline] __netif_receive_skb+0x1a6/0x5a0 net/core/dev.c:5637 netif_receive_skb_internal net/core/dev.c:5723 [inline] netif_receive_skb+0x58/0x660 net/core/dev.c:5782 tun_rx_batched+0x3ee/0x980 drivers/net/tun.c:1555 tun_get_user+0x54c5/0x69c0 drivers/net/tun.c:2002 Add a mac_len test before all three eth_hdr(skb) calls under net/llc. There are further uses in include/net/llc_pdu.h. All these are protected by a test skb->protocol == ETH_P_802_2. Which does not protect against this tun scenario. But the mac_len test added in this patch in llc_fixup_skb will indirectly protect those too. That is called from llc_rcv before any other LLC code. It is tempting to just add a blanket mac_len check in llc_rcv, but not sure whether that could break valid LLC paths that do not assume an Ethernet header. 802.2 LLC may be used on top of non-802.3 protocols in principle. The below referenced commit shows that used to, on top of Token Ring. At least one of the three eth_hdr uses goes back to before the start of git history. But the one that syzbot exercises is introduced in this commit. That commit is old enough (2008), that effectively all stable kernels should receive this. CVE-2023-52843 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52843.html CVE-2023-52843 https://bugzilla.suse.com/1224951 SUSE Bug 1224951 In the Linux kernel, the following vulnerability has been resolved: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING syzbot reported the following uninit-value access issue [1]: ===================================================== BUG: KMSAN: uninit-value in strlen lib/string.c:418 [inline] BUG: KMSAN: uninit-value in strstr+0xb8/0x2f0 lib/string.c:756 strlen lib/string.c:418 [inline] strstr+0xb8/0x2f0 lib/string.c:756 tipc_nl_node_reset_link_stats+0x3ea/0xb50 net/tipc/node.c:2595 genl_family_rcv_msg_doit net/netlink/genetlink.c:971 [inline] genl_family_rcv_msg net/netlink/genetlink.c:1051 [inline] genl_rcv_msg+0x11ec/0x1290 net/netlink/genetlink.c:1066 netlink_rcv_skb+0x371/0x650 net/netlink/af_netlink.c:2545 genl_rcv+0x40/0x60 net/netlink/genetlink.c:1075 netlink_unicast_kernel net/netlink/af_netlink.c:1342 [inline] netlink_unicast+0xf47/0x1250 net/netlink/af_netlink.c:1368 netlink_sendmsg+0x1238/0x13d0 net/netlink/af_netlink.c:1910 sock_sendmsg_nosec net/socket.c:730 [inline] sock_sendmsg net/socket.c:753 [inline] ____sys_sendmsg+0x9c2/0xd60 net/socket.c:2541 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2595 __sys_sendmsg net/socket.c:2624 [inline] __do_sys_sendmsg net/socket.c:2633 [inline] __se_sys_sendmsg net/socket.c:2631 [inline] __x64_sys_sendmsg+0x307/0x490 net/socket.c:2631 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd Uninit was created at: slab_post_alloc_hook+0x12f/0xb70 mm/slab.h:767 slab_alloc_node mm/slub.c:3478 [inline] kmem_cache_alloc_node+0x577/0xa80 mm/slub.c:3523 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:559 __alloc_skb+0x318/0x740 net/core/skbuff.c:650 alloc_skb include/linux/skbuff.h:1286 [inline] netlink_alloc_large_skb net/netlink/af_netlink.c:1214 [inline] netlink_sendmsg+0xb34/0x13d0 net/netlink/af_netlink.c:1885 sock_sendmsg_nosec net/socket.c:730 [inline] sock_sendmsg net/socket.c:753 [inline] ____sys_sendmsg+0x9c2/0xd60 net/socket.c:2541 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2595 __sys_sendmsg net/socket.c:2624 [inline] __do_sys_sendmsg net/socket.c:2633 [inline] __se_sys_sendmsg net/socket.c:2631 [inline] __x64_sys_sendmsg+0x307/0x490 net/socket.c:2631 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd TIPC bearer-related names including link names must be null-terminated strings. If a link name which is not null-terminated is passed through netlink, strstr() and similar functions can cause buffer overrun. This causes the above issue. This patch changes the nla_policy for bearer-related names from NLA_STRING to NLA_NUL_STRING. This resolves the issue by ensuring that only null-terminated strings are accepted as bearer-related names. syzbot reported similar uninit-value issue related to bearer names [2]. The root cause of this issue is that a non-null-terminated bearer name was passed. This patch also resolved this issue. CVE-2023-52845 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52845.html CVE-2023-52845 https://bugzilla.suse.com/1225585 SUSE Bug 1225585 In the Linux kernel, the following vulnerability has been resolved: usb: dwc2: fix possible NULL pointer dereference caused by driver concurrency In _dwc2_hcd_urb_enqueue(), "urb->hcpriv = NULL" is executed without holding the lock "hsotg->lock". In _dwc2_hcd_urb_dequeue(): spin_lock_irqsave(&hsotg->lock, flags); ... if (!urb->hcpriv) { dev_dbg(hsotg->dev, "## urb->hcpriv is NULL ##\n"); goto out; } rc = dwc2_hcd_urb_dequeue(hsotg, urb->hcpriv); // Use urb->hcpriv ... out: spin_unlock_irqrestore(&hsotg->lock, flags); When _dwc2_hcd_urb_enqueue() and _dwc2_hcd_urb_dequeue() are concurrently executed, the NULL check of "urb->hcpriv" can be executed before "urb->hcpriv = NULL". After urb->hcpriv is NULL, it can be used in the function call to dwc2_hcd_urb_dequeue(), which can cause a NULL pointer dereference. This possible bug is found by an experimental static analysis tool developed by myself. This tool analyzes the locking APIs to extract function pairs that can be concurrently executed, and then analyzes the instructions in the paired functions to identify possible concurrency bugs including data races and atomicity violations. The above possible bug is reported, when my tool analyzes the source code of Linux 6.5. To fix this possible bug, "urb->hcpriv = NULL" should be executed with holding the lock "hsotg->lock". After using this patch, my tool never reports the possible bug, with the kernelconfiguration allyesconfig for x86_64. Because I have no associated hardware, I cannot test the patch in runtime testing, and just verify it according to the code logic. CVE-2023-52855 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52855.html CVE-2023-52855 https://bugzilla.suse.com/1225583 SUSE Bug 1225583 In the Linux kernel, the following vulnerability has been resolved: tcp: do not accept ACK of bytes we never sent This patch is based on a detailed report and ideas from Yepeng Pan and Christian Rossow. ACK seq validation is currently following RFC 5961 5.2 guidelines: The ACK value is considered acceptable only if it is in the range of ((SND.UNA - MAX.SND.WND) <= SEG.ACK <= SND.NXT). All incoming segments whose ACK value doesn't satisfy the above condition MUST be discarded and an ACK sent back. It needs to be noted that RFC 793 on page 72 (fifth check) says: "If the ACK is a duplicate (SEG.ACK < SND.UNA), it can be ignored. If the ACK acknowledges something not yet sent (SEG.ACK > SND.NXT) then send an ACK, drop the segment, and return". The "ignored" above implies that the processing of the incoming data segment continues, which means the ACK value is treated as acceptable. This mitigation makes the ACK check more stringent since any ACK < SND.UNA wouldn't be accepted, instead only ACKs that are in the range ((SND.UNA - MAX.SND.WND) <= SEG.ACK <= SND.NXT) get through. This can be refined for new (and possibly spoofed) flows, by not accepting ACK for bytes that were never sent. This greatly improves TCP security at a little cost. I added a Fixes: tag to make sure this patch will reach stable trees, even if the 'blamed' patch was adhering to the RFC. tp->bytes_acked was added in linux-4.2 Following packetdrill test (courtesy of Yepeng Pan) shows the issue at hand: 0 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3 +0 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 +0 bind(3, ..., ...) = 0 +0 listen(3, 1024) = 0 // ---------------- Handshake ------------------- // // when window scale is set to 14 the window size can be extended to // 65535 * (2^14) = 1073725440. Linux would accept an ACK packet // with ack number in (Server_ISN+1-1073725440. Server_ISN+1) // ,though this ack number acknowledges some data never // sent by the server. +0 < S 0:0(0) win 65535 <mss 1400,nop,wscale 14> +0 > S. 0:0(0) ack 1 <...> +0 < . 1:1(0) ack 1 win 65535 +0 accept(3, ..., ...) = 4 // For the established connection, we send an ACK packet, // the ack packet uses ack number 1 - 1073725300 + 2^32, // where 2^32 is used to wrap around. // Note: we used 1073725300 instead of 1073725440 to avoid possible // edge cases. // 1 - 1073725300 + 2^32 = 3221241997 // Oops, old kernels happily accept this packet. +0 < . 1:1001(1000) ack 3221241997 win 65535 // After the kernel fix the following will be replaced by a challenge ACK, // and prior malicious frame would be dropped. +0 > . 1:1(0) ack 1001 CVE-2023-52881 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2023-52881.html CVE-2023-52881 https://bugzilla.suse.com/1223384 SUSE Bug 1223384 https://bugzilla.suse.com/1225611 SUSE Bug 1225611 https://bugzilla.suse.com/1226152 SUSE Bug 1226152 In the Linux kernel, the following vulnerability has been resolved: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() syzbot pointed out [1] that NEXTHDR_FRAGMENT handling is broken. Reading frag_off can only be done if we pulled enough bytes to skb->head. Currently we might access garbage. [1] BUG: KMSAN: uninit-value in ip6_tnl_parse_tlv_enc_lim+0x94f/0xbb0 ip6_tnl_parse_tlv_enc_lim+0x94f/0xbb0 ipxip6_tnl_xmit net/ipv6/ip6_tunnel.c:1326 [inline] ip6_tnl_start_xmit+0xab2/0x1a70 net/ipv6/ip6_tunnel.c:1432 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x247/0xa10 net/core/dev.c:3564 __dev_queue_xmit+0x33b8/0x5130 net/core/dev.c:4349 dev_queue_xmit include/linux/netdevice.h:3134 [inline] neigh_connected_output+0x569/0x660 net/core/neighbour.c:1592 neigh_output include/net/neighbour.h:542 [inline] ip6_finish_output2+0x23a9/0x2b30 net/ipv6/ip6_output.c:137 ip6_finish_output+0x855/0x12b0 net/ipv6/ip6_output.c:222 NF_HOOK_COND include/linux/netfilter.h:303 [inline] ip6_output+0x323/0x610 net/ipv6/ip6_output.c:243 dst_output include/net/dst.h:451 [inline] ip6_local_out+0xe9/0x140 net/ipv6/output_core.c:155 ip6_send_skb net/ipv6/ip6_output.c:1952 [inline] ip6_push_pending_frames+0x1f9/0x560 net/ipv6/ip6_output.c:1972 rawv6_push_pending_frames+0xbe8/0xdf0 net/ipv6/raw.c:582 rawv6_sendmsg+0x2b66/0x2e70 net/ipv6/raw.c:920 inet_sendmsg+0x105/0x190 net/ipv4/af_inet.c:847 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] ____sys_sendmsg+0x9c2/0xd60 net/socket.c:2584 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2638 __sys_sendmsg net/socket.c:2667 [inline] __do_sys_sendmsg net/socket.c:2676 [inline] __se_sys_sendmsg net/socket.c:2674 [inline] __x64_sys_sendmsg+0x307/0x490 net/socket.c:2674 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Uninit was created at: slab_post_alloc_hook+0x129/0xa70 mm/slab.h:768 slab_alloc_node mm/slub.c:3478 [inline] __kmem_cache_alloc_node+0x5c9/0x970 mm/slub.c:3517 __do_kmalloc_node mm/slab_common.c:1006 [inline] __kmalloc_node_track_caller+0x118/0x3c0 mm/slab_common.c:1027 kmalloc_reserve+0x249/0x4a0 net/core/skbuff.c:582 pskb_expand_head+0x226/0x1a00 net/core/skbuff.c:2098 __pskb_pull_tail+0x13b/0x2310 net/core/skbuff.c:2655 pskb_may_pull_reason include/linux/skbuff.h:2673 [inline] pskb_may_pull include/linux/skbuff.h:2681 [inline] ip6_tnl_parse_tlv_enc_lim+0x901/0xbb0 net/ipv6/ip6_tunnel.c:408 ipxip6_tnl_xmit net/ipv6/ip6_tunnel.c:1326 [inline] ip6_tnl_start_xmit+0xab2/0x1a70 net/ipv6/ip6_tunnel.c:1432 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x247/0xa10 net/core/dev.c:3564 __dev_queue_xmit+0x33b8/0x5130 net/core/dev.c:4349 dev_queue_xmit include/linux/netdevice.h:3134 [inline] neigh_connected_output+0x569/0x660 net/core/neighbour.c:1592 neigh_output include/net/neighbour.h:542 [inline] ip6_finish_output2+0x23a9/0x2b30 net/ipv6/ip6_output.c:137 ip6_finish_output+0x855/0x12b0 net/ipv6/ip6_output.c:222 NF_HOOK_COND include/linux/netfilter.h:303 [inline] ip6_output+0x323/0x610 net/ipv6/ip6_output.c:243 dst_output include/net/dst.h:451 [inline] ip6_local_out+0xe9/0x140 net/ipv6/output_core.c:155 ip6_send_skb net/ipv6/ip6_output.c:1952 [inline] ip6_push_pending_frames+0x1f9/0x560 net/ipv6/ip6_output.c:1972 rawv6_push_pending_frames+0xbe8/0xdf0 net/ipv6/raw.c:582 rawv6_sendmsg+0x2b66/0x2e70 net/ipv6/raw.c:920 inet_sendmsg+0x105/0x190 net/ipv4/af_inet.c:847 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] ____sys_sendmsg+0x9c2/0xd60 net/socket.c:2584 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2638 __sys_sendmsg net/socket.c:2667 [inline] __do_sys_sendms ---truncated--- CVE-2024-26633 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26633.html CVE-2024-26633 https://bugzilla.suse.com/1221647 SUSE Bug 1221647 In the Linux kernel, the following vulnerability has been resolved: ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() syzbot found __ip6_tnl_rcv() could access unitiliazed data [1]. Call pskb_inet_may_pull() to fix this, and initialize ipv6h variable after this call as it can change skb->head. [1] BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline] BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline] BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7df/0x1e50 include/net/inet_ecn.h:321 __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline] INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline] IP6_ECN_decapsulate+0x7df/0x1e50 include/net/inet_ecn.h:321 ip6ip6_dscp_ecn_decapsulate+0x178/0x1b0 net/ipv6/ip6_tunnel.c:727 __ip6_tnl_rcv+0xd4e/0x1590 net/ipv6/ip6_tunnel.c:845 ip6_tnl_rcv+0xce/0x100 net/ipv6/ip6_tunnel.c:888 gre_rcv+0x143f/0x1870 ip6_protocol_deliver_rcu+0xda6/0x2a60 net/ipv6/ip6_input.c:438 ip6_input_finish net/ipv6/ip6_input.c:483 [inline] NF_HOOK include/linux/netfilter.h:314 [inline] ip6_input+0x15d/0x430 net/ipv6/ip6_input.c:492 ip6_mc_input+0xa7e/0xc80 net/ipv6/ip6_input.c:586 dst_input include/net/dst.h:461 [inline] ip6_rcv_finish+0x5db/0x870 net/ipv6/ip6_input.c:79 NF_HOOK include/linux/netfilter.h:314 [inline] ipv6_rcv+0xda/0x390 net/ipv6/ip6_input.c:310 __netif_receive_skb_one_core net/core/dev.c:5532 [inline] __netif_receive_skb+0x1a6/0x5a0 net/core/dev.c:5646 netif_receive_skb_internal net/core/dev.c:5732 [inline] netif_receive_skb+0x58/0x660 net/core/dev.c:5791 tun_rx_batched+0x3ee/0x980 drivers/net/tun.c:1555 tun_get_user+0x53af/0x66d0 drivers/net/tun.c:2002 tun_chr_write_iter+0x3af/0x5d0 drivers/net/tun.c:2048 call_write_iter include/linux/fs.h:2084 [inline] new_sync_write fs/read_write.c:497 [inline] vfs_write+0x786/0x1200 fs/read_write.c:590 ksys_write+0x20f/0x4c0 fs/read_write.c:643 __do_sys_write fs/read_write.c:655 [inline] __se_sys_write fs/read_write.c:652 [inline] __x64_sys_write+0x93/0xd0 fs/read_write.c:652 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x6d/0x140 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Uninit was created at: slab_post_alloc_hook+0x129/0xa70 mm/slab.h:768 slab_alloc_node mm/slub.c:3478 [inline] kmem_cache_alloc_node+0x5e9/0xb10 mm/slub.c:3523 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:560 __alloc_skb+0x318/0x740 net/core/skbuff.c:651 alloc_skb include/linux/skbuff.h:1286 [inline] alloc_skb_with_frags+0xc8/0xbd0 net/core/skbuff.c:6334 sock_alloc_send_pskb+0xa80/0xbf0 net/core/sock.c:2787 tun_alloc_skb drivers/net/tun.c:1531 [inline] tun_get_user+0x1e8a/0x66d0 drivers/net/tun.c:1846 tun_chr_write_iter+0x3af/0x5d0 drivers/net/tun.c:2048 call_write_iter include/linux/fs.h:2084 [inline] new_sync_write fs/read_write.c:497 [inline] vfs_write+0x786/0x1200 fs/read_write.c:590 ksys_write+0x20f/0x4c0 fs/read_write.c:643 __do_sys_write fs/read_write.c:655 [inline] __se_sys_write fs/read_write.c:652 [inline] __x64_sys_write+0x93/0xd0 fs/read_write.c:652 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x6d/0x140 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b CPU: 0 PID: 5034 Comm: syz-executor331 Not tainted 6.7.0-syzkaller-00562-g9f8413c4a66f #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 CVE-2024-26641 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26641.html CVE-2024-26641 https://bugzilla.suse.com/1221654 SUSE Bug 1221654 In the Linux kernel, the following vulnerability has been resolved: inet: read sk->sk_family once in inet_recv_error() inet_recv_error() is called without holding the socket lock. IPv6 socket could mutate to IPv4 with IPV6_ADDRFORM socket option and trigger a KCSAN warning. CVE-2024-26679 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26679.html CVE-2024-26679 https://bugzilla.suse.com/1222385 SUSE Bug 1222385 In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bind_pirq -> returns just freed evtchn e set_evtchn_to_irq(e, irq) } xen_irq_info_cleanup() { set_evtchn_to_irq(e, -1) } } Assume here event channel e refers here to the same event channel number. After this race the evtchn_to_irq mapping for e is invalid (-1). - __startup_pirq races with __unbind_from_irq in a similar way. Because __startup_pirq doesn't take irq_mapping_update_lock it can grab the evtchn that __unbind_from_irq is currently freeing and cleaning up. In this case even though the event channel is allocated, its mapping can be unset in evtchn_to_irq. The fix is to first cleanup the mappings and then close the event channel. In this way, when an event channel gets allocated it's potential previous evtchn_to_irq mappings are guaranteed to be unset already. This is also the reverse order of the allocation where first the event channel is allocated and then the mappings are setup. On a 5.10 kernel prior to commit 3fcdaf3d7634 ("xen/events: modify internal [un]bind interfaces"), we hit a BUG like the following during probing of NVMe devices. The issue is that during nvme_setup_io_queues, pci_free_irq is called for every device which results in a call to shutdown_pirq. With many nvme devices it's therefore likely to hit this race during boot because there will be multiple calls to shutdown_pirq and startup_pirq are running potentially in parallel. ------------[ cut here ]------------ blkfront: xvda: barrier or flush: disabled; persistent grants: enabled; indirect descriptors: enabled; bounce buffer: enabled kernel BUG at drivers/xen/events/events_base.c:499! invalid opcode: 0000 [#1] SMP PTI CPU: 44 PID: 375 Comm: kworker/u257:23 Not tainted 5.10.201-191.748.amzn2.x86_64 #1 Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006 Workqueue: nvme-reset-wq nvme_reset_work RIP: 0010:bind_evtchn_to_cpu+0xdf/0xf0 Code: 5d 41 5e c3 cc cc cc cc 44 89 f7 e8 2b 55 ad ff 49 89 c5 48 85 c0 0f 84 64 ff ff ff 4c 8b 68 30 41 83 fe ff 0f 85 60 ff ff ff <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 1f 44 00 00 RSP: 0000:ffffc9000d533b08 EFLAGS: 00010046 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006 RDX: 0000000000000028 RSI: 00000000ffffffff RDI: 00000000ffffffff RBP: ffff888107419680 R08: 0000000000000000 R09: ffffffff82d72b00 R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000001ed R13: 0000000000000000 R14: 00000000ffffffff R15: 0000000000000002 FS: 0000000000000000(0000) GS:ffff88bc8b500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000002610001 CR4: 00000000001706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? show_trace_log_lvl+0x1c1/0x2d9 ? show_trace_log_lvl+0x1c1/0x2d9 ? set_affinity_irq+0xdc/0x1c0 ? __die_body.cold+0x8/0xd ? die+0x2b/0x50 ? do_trap+0x90/0x110 ? bind_evtchn_to_cpu+0xdf/0xf0 ? do_error_trap+0x65/0x80 ? bind_evtchn_to_cpu+0xdf/0xf0 ? exc_invalid_op+0x4e/0x70 ? bind_evtchn_to_cpu+0xdf/0xf0 ? asm_exc_invalid_op+0x12/0x20 ? bind_evtchn_to_cpu+0xdf/0x ---truncated--- CVE-2024-26687 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26687.html CVE-2024-26687 https://bugzilla.suse.com/1222435 SUSE Bug 1222435 ** REJECT ** This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. CVE-2024-26720 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26720.html CVE-2024-26720 https://bugzilla.suse.com/1222364 SUSE Bug 1222364 In the Linux kernel, the following vulnerability has been resolved: vfio/platform: Create persistent IRQ handlers The vfio-platform SET_IRQS ioctl currently allows loopback triggering of an interrupt before a signaling eventfd has been configured by the user, which thereby allows a NULL pointer dereference. Rather than register the IRQ relative to a valid trigger, register all IRQs in a disabled state in the device open path. This allows mask operations on the IRQ to nest within the overall enable state governed by a valid eventfd signal. This decouples @masked, protected by the @locked spinlock from @trigger, protected via the @igate mutex. In doing so, it's guaranteed that changes to @trigger cannot race the IRQ handlers because the IRQ handler is synchronously disabled before modifying the trigger, and loopback triggering of the IRQ via ioctl is safe due to serialization with trigger changes via igate. For compatibility, request_irq() failures are maintained to be local to the SET_IRQS ioctl rather than a fatal error in the open device path. This allows, for example, a userspace driver with polling mode support to continue to work regardless of moving the request_irq() call site. This necessarily blocks all SET_IRQS access to the failed index. CVE-2024-26813 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26813.html CVE-2024-26813 https://bugzilla.suse.com/1222809 SUSE Bug 1222809 In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Add TMF to tmr_list handling An abort that is responded to by iSCSI itself is added to tmr_list but does not go to target core. A LUN_RESET that goes through tmr_list takes a refcounter on the abort and waits for completion. However, the abort will be never complete because it was not started in target core. Unable to locate ITT: 0x05000000 on CID: 0 Unable to locate RefTaskTag: 0x05000000 on CID: 0. wait_for_tasks: Stopping tmf LUN_RESET with tag 0x0 ref_task_tag 0x0 i_state 34 t_state ISTATE_PROCESSING refcnt 2 transport_state active,stop,fabric_stop wait for tasks: tmf LUN_RESET with tag 0x0 ref_task_tag 0x0 i_state 34 t_state ISTATE_PROCESSING refcnt 2 transport_state active,stop,fabric_stop ... INFO: task kworker/0:2:49 blocked for more than 491 seconds. task:kworker/0:2 state:D stack: 0 pid: 49 ppid: 2 flags:0x00000800 Workqueue: events target_tmr_work [target_core_mod] Call Trace: __switch_to+0x2c4/0x470 _schedule+0x314/0x1730 schedule+0x64/0x130 schedule_timeout+0x168/0x430 wait_for_completion+0x140/0x270 target_put_cmd_and_wait+0x64/0xb0 [target_core_mod] core_tmr_lun_reset+0x30/0xa0 [target_core_mod] target_tmr_work+0xc8/0x1b0 [target_core_mod] process_one_work+0x2d4/0x5d0 worker_thread+0x78/0x6c0 To fix this, only add abort to tmr_list if it will be handled by target core. CVE-2024-26845 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26845.html CVE-2024-26845 https://bugzilla.suse.com/1223018 SUSE Bug 1223018 In the Linux kernel, the following vulnerability has been resolved: hsr: Fix uninit-value access in hsr_get_node() KMSAN reported the following uninit-value access issue [1]: ===================================================== BUG: KMSAN: uninit-value in hsr_get_node+0xa2e/0xa40 net/hsr/hsr_framereg.c:246 hsr_get_node+0xa2e/0xa40 net/hsr/hsr_framereg.c:246 fill_frame_info net/hsr/hsr_forward.c:577 [inline] hsr_forward_skb+0xe12/0x30e0 net/hsr/hsr_forward.c:615 hsr_dev_xmit+0x1a1/0x270 net/hsr/hsr_device.c:223 __netdev_start_xmit include/linux/netdevice.h:4940 [inline] netdev_start_xmit include/linux/netdevice.h:4954 [inline] xmit_one net/core/dev.c:3548 [inline] dev_hard_start_xmit+0x247/0xa10 net/core/dev.c:3564 __dev_queue_xmit+0x33b8/0x5130 net/core/dev.c:4349 dev_queue_xmit include/linux/netdevice.h:3134 [inline] packet_xmit+0x9c/0x6b0 net/packet/af_packet.c:276 packet_snd net/packet/af_packet.c:3087 [inline] packet_sendmsg+0x8b1d/0x9f30 net/packet/af_packet.c:3119 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] __sys_sendto+0x735/0xa10 net/socket.c:2191 __do_sys_sendto net/socket.c:2203 [inline] __se_sys_sendto net/socket.c:2199 [inline] __x64_sys_sendto+0x125/0x1c0 net/socket.c:2199 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x6d/0x140 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Uninit was created at: slab_post_alloc_hook+0x129/0xa70 mm/slab.h:768 slab_alloc_node mm/slub.c:3478 [inline] kmem_cache_alloc_node+0x5e9/0xb10 mm/slub.c:3523 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:560 __alloc_skb+0x318/0x740 net/core/skbuff.c:651 alloc_skb include/linux/skbuff.h:1286 [inline] alloc_skb_with_frags+0xc8/0xbd0 net/core/skbuff.c:6334 sock_alloc_send_pskb+0xa80/0xbf0 net/core/sock.c:2787 packet_alloc_skb net/packet/af_packet.c:2936 [inline] packet_snd net/packet/af_packet.c:3030 [inline] packet_sendmsg+0x70e8/0x9f30 net/packet/af_packet.c:3119 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] __sys_sendto+0x735/0xa10 net/socket.c:2191 __do_sys_sendto net/socket.c:2203 [inline] __se_sys_sendto net/socket.c:2199 [inline] __x64_sys_sendto+0x125/0x1c0 net/socket.c:2199 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x6d/0x140 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b CPU: 1 PID: 5033 Comm: syz-executor334 Not tainted 6.7.0-syzkaller-00562-g9f8413c4a66f #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 ===================================================== If the packet type ID field in the Ethernet header is either ETH_P_PRP or ETH_P_HSR, but it is not followed by an HSR tag, hsr_get_skb_sequence_nr() reads an invalid value as a sequence number. This causes the above issue. This patch fixes the issue by returning NULL if the Ethernet header is not followed by an HSR tag. CVE-2024-26863 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26863.html CVE-2024-26863 https://bugzilla.suse.com/1223021 SUSE Bug 1223021 In the Linux kernel, the following vulnerability has been resolved: ACPI: processor_idle: Fix memory leak in acpi_processor_power_exit() After unregistering the CPU idle device, the memory associated with it is not freed, leading to a memory leak: unreferenced object 0xffff896282f6c000 (size 1024): comm "swapper/0", pid 1, jiffies 4294893170 hex dump (first 32 bytes): 00 00 00 00 0b 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 (crc 8836a742): [<ffffffff993495ed>] kmalloc_trace+0x29d/0x340 [<ffffffff9972f3b3>] acpi_processor_power_init+0xf3/0x1c0 [<ffffffff9972d263>] __acpi_processor_start+0xd3/0xf0 [<ffffffff9972d2bc>] acpi_processor_start+0x2c/0x50 [<ffffffff99805872>] really_probe+0xe2/0x480 [<ffffffff99805c98>] __driver_probe_device+0x78/0x160 [<ffffffff99805daf>] driver_probe_device+0x1f/0x90 [<ffffffff9980601e>] __driver_attach+0xce/0x1c0 [<ffffffff99803170>] bus_for_each_dev+0x70/0xc0 [<ffffffff99804822>] bus_add_driver+0x112/0x210 [<ffffffff99807245>] driver_register+0x55/0x100 [<ffffffff9aee4acb>] acpi_processor_driver_init+0x3b/0xc0 [<ffffffff990012d1>] do_one_initcall+0x41/0x300 [<ffffffff9ae7c4b0>] kernel_init_freeable+0x320/0x470 [<ffffffff99b231f6>] kernel_init+0x16/0x1b0 [<ffffffff99042e6d>] ret_from_fork+0x2d/0x50 Fix this by freeing the CPU idle device after unregistering it. CVE-2024-26894 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26894.html CVE-2024-26894 https://bugzilla.suse.com/1223043 SUSE Bug 1223043 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in cifs_debug_files_proc_show() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF. CVE-2024-26928 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26928.html CVE-2024-26928 https://bugzilla.suse.com/1223532 SUSE Bug 1223532 In the Linux kernel, the following vulnerability has been resolved: fat: fix uninitialized field in nostale filehandles When fat_encode_fh_nostale() encodes file handle without a parent it stores only first 10 bytes of the file handle. However the length of the file handle must be a multiple of 4 so the file handle is actually 12 bytes long and the last two bytes remain uninitialized. This is not great at we potentially leak uninitialized information with the handle to userspace. Properly initialize the full handle length. CVE-2024-26973 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-26973.html CVE-2024-26973 https://bugzilla.suse.com/1223641 SUSE Bug 1223641 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout There is a race condition between l2cap_chan_timeout() and l2cap_chan_del(). When we use l2cap_chan_del() to delete the channel, the chan->conn will be set to null. But the conn could be dereferenced again in the mutex_lock() of l2cap_chan_timeout(). As a result the null pointer dereference bug will happen. The KASAN report triggered by POC is shown below: [ 472.074580] ================================================================== [ 472.075284] BUG: KASAN: null-ptr-deref in mutex_lock+0x68/0xc0 [ 472.075308] Write of size 8 at addr 0000000000000158 by task kworker/0:0/7 [ 472.075308] [ 472.075308] CPU: 0 PID: 7 Comm: kworker/0:0 Not tainted 6.9.0-rc5-00356-g78c0094a146b #36 [ 472.075308] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu4 [ 472.075308] Workqueue: events l2cap_chan_timeout [ 472.075308] Call Trace: [ 472.075308] <TASK> [ 472.075308] dump_stack_lvl+0x137/0x1a0 [ 472.075308] print_report+0x101/0x250 [ 472.075308] ? __virt_addr_valid+0x77/0x160 [ 472.075308] ? mutex_lock+0x68/0xc0 [ 472.075308] kasan_report+0x139/0x170 [ 472.075308] ? mutex_lock+0x68/0xc0 [ 472.075308] kasan_check_range+0x2c3/0x2e0 [ 472.075308] mutex_lock+0x68/0xc0 [ 472.075308] l2cap_chan_timeout+0x181/0x300 [ 472.075308] process_one_work+0x5d2/0xe00 [ 472.075308] worker_thread+0xe1d/0x1660 [ 472.075308] ? pr_cont_work+0x5e0/0x5e0 [ 472.075308] kthread+0x2b7/0x350 [ 472.075308] ? pr_cont_work+0x5e0/0x5e0 [ 472.075308] ? kthread_blkcg+0xd0/0xd0 [ 472.075308] ret_from_fork+0x4d/0x80 [ 472.075308] ? kthread_blkcg+0xd0/0xd0 [ 472.075308] ret_from_fork_asm+0x11/0x20 [ 472.075308] </TASK> [ 472.075308] ================================================================== [ 472.094860] Disabling lock debugging due to kernel taint [ 472.096136] BUG: kernel NULL pointer dereference, address: 0000000000000158 [ 472.096136] #PF: supervisor write access in kernel mode [ 472.096136] #PF: error_code(0x0002) - not-present page [ 472.096136] PGD 0 P4D 0 [ 472.096136] Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI [ 472.096136] CPU: 0 PID: 7 Comm: kworker/0:0 Tainted: G B 6.9.0-rc5-00356-g78c0094a146b #36 [ 472.096136] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu4 [ 472.096136] Workqueue: events l2cap_chan_timeout [ 472.096136] RIP: 0010:mutex_lock+0x88/0xc0 [ 472.096136] Code: be 08 00 00 00 e8 f8 23 1f fd 4c 89 f7 be 08 00 00 00 e8 eb 23 1f fd 42 80 3c 23 00 74 08 48 88 [ 472.096136] RSP: 0018:ffff88800744fc78 EFLAGS: 00000246 [ 472.096136] RAX: 0000000000000000 RBX: 1ffff11000e89f8f RCX: ffffffff8457c865 [ 472.096136] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffff88800744fc78 [ 472.096136] RBP: 0000000000000158 R08: ffff88800744fc7f R09: 1ffff11000e89f8f [ 472.096136] R10: dffffc0000000000 R11: ffffed1000e89f90 R12: dffffc0000000000 [ 472.096136] R13: 0000000000000158 R14: ffff88800744fc78 R15: ffff888007405a00 [ 472.096136] FS: 0000000000000000(0000) GS:ffff88806d200000(0000) knlGS:0000000000000000 [ 472.096136] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 472.096136] CR2: 0000000000000158 CR3: 000000000da32000 CR4: 00000000000006f0 [ 472.096136] Call Trace: [ 472.096136] <TASK> [ 472.096136] ? __die_body+0x8d/0xe0 [ 472.096136] ? page_fault_oops+0x6b8/0x9a0 [ 472.096136] ? kernelmode_fixup_or_oops+0x20c/0x2a0 [ 472.096136] ? do_user_addr_fault+0x1027/0x1340 [ 472.096136] ? _printk+0x7a/0xa0 [ 472.096136] ? mutex_lock+0x68/0xc0 [ 472.096136] ? add_taint+0x42/0xd0 [ 472.096136] ? exc_page_fault+0x6a/0x1b0 [ 472.096136] ? asm_exc_page_fault+0x26/0x30 [ 472.096136] ? mutex_lock+0x75/0xc0 [ 472.096136] ? mutex_lock+0x88/0xc0 [ 472.096136] ? mutex_lock+0x75/0xc0 [ 472.096136] l2cap_chan_timeo ---truncated--- CVE-2024-27399 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-27399.html CVE-2024-27399 https://bugzilla.suse.com/1224177 SUSE Bug 1224177 In the Linux kernel, the following vulnerability has been resolved: wifi: nl80211: reject iftype change with mesh ID change It's currently possible to change the mesh ID when the interface isn't yet in mesh mode, at the same time as changing it into mesh mode. This leads to an overwrite of data in the wdev->u union for the interface type it currently has, causing cfg80211_change_iface() to do wrong things when switching. We could probably allow setting an interface to mesh while setting the mesh ID at the same time by doing a different order of operations here, but realistically there's no userspace that's going to do this, so just disallow changes in iftype when setting mesh ID. CVE-2024-27410 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-27410.html CVE-2024-27410 https://bugzilla.suse.com/1224432 SUSE Bug 1224432 In the Linux kernel, the following vulnerability has been resolved: fpga: region: add owner module and take its refcount The current implementation of the fpga region assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the region during programming if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_region struct and use it to take the module's refcount. Modify the functions for registering a region to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the region as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a region without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga region. CVE-2024-35247 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35247.html CVE-2024-35247 https://bugzilla.suse.com/1226948 SUSE Bug 1226948 In the Linux kernel, the following vulnerability has been resolved: ext4: fix corruption during on-line resize We observed a corruption during on-line resize of a file system that is larger than 16 TiB with 4k block size. With having more then 2^32 blocks resize_inode is turned off by default by mke2fs. The issue can be reproduced on a smaller file system for convenience by explicitly turning off resize_inode. An on-line resize across an 8 GiB boundary (the size of a meta block group in this setup) then leads to a corruption: dev=/dev/<some_dev> # should be >= 16 GiB mkdir -p /corruption /sbin/mke2fs -t ext4 -b 4096 -O ^resize_inode $dev $((2 * 2**21 - 2**15)) mount -t ext4 $dev /corruption dd if=/dev/zero bs=4096 of=/corruption/test count=$((2*2**21 - 4*2**15)) sha1sum /corruption/test # 79d2658b39dcfd77274e435b0934028adafaab11 /corruption/test /sbin/resize2fs $dev $((2*2**21)) # drop page cache to force reload the block from disk echo 1 > /proc/sys/vm/drop_caches sha1sum /corruption/test # 3c2abc63cbf1a94c9e6977e0fbd72cd832c4d5c3 /corruption/test 2^21 = 2^15*2^6 equals 8 GiB whereof 2^15 is the number of blocks per block group and 2^6 are the number of block groups that make a meta block group. The last checksum might be different depending on how the file is laid out across the physical blocks. The actual corruption occurs at physical block 63*2^15 = 2064384 which would be the location of the backup of the meta block group's block descriptor. During the on-line resize the file system will be converted to meta_bg starting at s_first_meta_bg which is 2 in the example - meaning all block groups after 16 GiB. However, in ext4_flex_group_add we might add block groups that are not part of the first meta block group yet. In the reproducer we achieved this by substracting the size of a whole block group from the point where the meta block group would start. This must be considered when updating the backup block group descriptors to follow the non-meta_bg layout. The fix is to add a test whether the group to add is already part of the meta block group or not. CVE-2024-35807 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35807.html CVE-2024-35807 https://bugzilla.suse.com/1224735 SUSE Bug 1224735 In the Linux kernel, the following vulnerability has been resolved: usb: udc: remove warning when queue disabled ep It is possible trigger below warning message from mass storage function, WARNING: CPU: 6 PID: 3839 at drivers/usb/gadget/udc/core.c:294 usb_ep_queue+0x7c/0x104 pc : usb_ep_queue+0x7c/0x104 lr : fsg_main_thread+0x494/0x1b3c Root cause is mass storage function try to queue request from main thread, but other thread may already disable ep when function disable. As there is no function failure in the driver, in order to avoid effort to fix warning, change WARN_ON_ONCE() in usb_ep_queue() to pr_debug(). CVE-2024-35822 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 low 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35822.html CVE-2024-35822 https://bugzilla.suse.com/1224739 SUSE Bug 1224739 In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: fix a double-free in arfs_create_groups When `in` allocated by kvzalloc fails, arfs_create_groups will free ft->g and return an error. However, arfs_create_table, the only caller of arfs_create_groups, will hold this error and call to mlx5e_destroy_flow_table, in which the ft->g will be freed again. CVE-2024-35835 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35835.html CVE-2024-35835 https://bugzilla.suse.com/1224605 SUSE Bug 1224605 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in smb2_is_network_name_deleted() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF. CVE-2024-35862 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35862.html CVE-2024-35862 https://bugzilla.suse.com/1224764 SUSE Bug 1224764 https://bugzilla.suse.com/1225311 SUSE Bug 1225311 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in is_valid_oplock_break() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF. CVE-2024-35863 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35863.html CVE-2024-35863 https://bugzilla.suse.com/1224763 SUSE Bug 1224763 https://bugzilla.suse.com/1225011 SUSE Bug 1225011 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in smb2_is_valid_lease_break() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF. CVE-2024-35864 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35864.html CVE-2024-35864 https://bugzilla.suse.com/1224765 SUSE Bug 1224765 https://bugzilla.suse.com/1225309 SUSE Bug 1225309 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in smb2_is_valid_oplock_break() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF. CVE-2024-35865 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35865.html CVE-2024-35865 https://bugzilla.suse.com/1224668 SUSE Bug 1224668 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in cifs_stats_proc_show() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF. CVE-2024-35867 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35867.html CVE-2024-35867 https://bugzilla.suse.com/1224664 SUSE Bug 1224664 https://bugzilla.suse.com/1225012 SUSE Bug 1225012 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in cifs_stats_proc_write() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF. CVE-2024-35868 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35868.html CVE-2024-35868 https://bugzilla.suse.com/1224678 SUSE Bug 1224678 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in smb2_reconnect_server() The UAF bug is due to smb2_reconnect_server() accessing a session that is already being teared down by another thread that is executing __cifs_put_smb_ses(). This can happen when (a) the client has connection to the server but no session or (b) another thread ends up setting @ses->ses_status again to something different than SES_EXITING. To fix this, we need to make sure to unconditionally set @ses->ses_status to SES_EXITING and prevent any other threads from setting a new status while we're still tearing it down. The following can be reproduced by adding some delay to right after the ipc is freed in __cifs_put_smb_ses() - which will give smb2_reconnect_server() worker a chance to run and then accessing @ses->ipc: kinit ... mount.cifs //srv/share /mnt/1 -o sec=krb5,nohandlecache,echo_interval=10 [disconnect srv] ls /mnt/1 &>/dev/null sleep 30 kdestroy [reconnect srv] sleep 10 umount /mnt/1 ... CIFS: VFS: Verify user has a krb5 ticket and keyutils is installed CIFS: VFS: \\srv Send error in SessSetup = -126 CIFS: VFS: Verify user has a krb5 ticket and keyutils is installed CIFS: VFS: \\srv Send error in SessSetup = -126 general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6b6b: 0000 [#1] PREEMPT SMP NOPTI CPU: 3 PID: 50 Comm: kworker/3:1 Not tainted 6.9.0-rc2 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-1.fc39 04/01/2014 Workqueue: cifsiod smb2_reconnect_server [cifs] RIP: 0010:__list_del_entry_valid_or_report+0x33/0xf0 Code: 4f 08 48 85 d2 74 42 48 85 c9 74 59 48 b8 00 01 00 00 00 00 ad de 48 39 c2 74 61 48 b8 22 01 00 00 00 00 74 69 <48> 8b 01 48 39 f8 75 7b 48 8b 72 08 48 39 c6 0f 85 88 00 00 00 b8 RSP: 0018:ffffc900001bfd70 EFLAGS: 00010a83 RAX: dead000000000122 RBX: ffff88810da53838 RCX: 6b6b6b6b6b6b6b6b RDX: 6b6b6b6b6b6b6b6b RSI: ffffffffc02f6878 RDI: ffff88810da53800 RBP: ffff88810da53800 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000001 R12: ffff88810c064000 R13: 0000000000000001 R14: ffff88810c064000 R15: ffff8881039cc000 FS: 0000000000000000(0000) GS:ffff888157c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe3728b1000 CR3: 000000010caa4000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> ? die_addr+0x36/0x90 ? exc_general_protection+0x1c1/0x3f0 ? asm_exc_general_protection+0x26/0x30 ? __list_del_entry_valid_or_report+0x33/0xf0 __cifs_put_smb_ses+0x1ae/0x500 [cifs] smb2_reconnect_server+0x4ed/0x710 [cifs] process_one_work+0x205/0x6b0 worker_thread+0x191/0x360 ? __pfx_worker_thread+0x10/0x10 kthread+0xe2/0x110 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x34/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> CVE-2024-35870 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35870.html CVE-2024-35870 https://bugzilla.suse.com/1224672 SUSE Bug 1224672 In the Linux kernel, the following vulnerability has been resolved: ipv6: Fix infinite recursion in fib6_dump_done(). syzkaller reported infinite recursive calls of fib6_dump_done() during netlink socket destruction. [1] From the log, syzkaller sent an AF_UNSPEC RTM_GETROUTE message, and then the response was generated. The following recvmmsg() resumed the dump for IPv6, but the first call of inet6_dump_fib() failed at kzalloc() due to the fault injection. [0] 12:01:34 executing program 3: r0 = socket$nl_route(0x10, 0x3, 0x0) sendmsg$nl_route(r0, ... snip ...) recvmmsg(r0, ... snip ...) (fail_nth: 8) Here, fib6_dump_done() was set to nlk_sk(sk)->cb.done, and the next call of inet6_dump_fib() set it to nlk_sk(sk)->cb.args[3]. syzkaller stopped receiving the response halfway through, and finally netlink_sock_destruct() called nlk_sk(sk)->cb.done(). fib6_dump_done() calls fib6_dump_end() and nlk_sk(sk)->cb.done() if it is still not NULL. fib6_dump_end() rewrites nlk_sk(sk)->cb.done() by nlk_sk(sk)->cb.args[3], but it has the same function, not NULL, calling itself recursively and hitting the stack guard page. To avoid the issue, let's set the destructor after kzalloc(). [0]: FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 CPU: 1 PID: 432110 Comm: syz-executor.3 Not tainted 6.8.0-12821-g537c2e91d354-dirty #11 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:117) should_fail_ex (lib/fault-inject.c:52 lib/fault-inject.c:153) should_failslab (mm/slub.c:3733) kmalloc_trace (mm/slub.c:3748 mm/slub.c:3827 mm/slub.c:3992) inet6_dump_fib (./include/linux/slab.h:628 ./include/linux/slab.h:749 net/ipv6/ip6_fib.c:662) rtnl_dump_all (net/core/rtnetlink.c:4029) netlink_dump (net/netlink/af_netlink.c:2269) netlink_recvmsg (net/netlink/af_netlink.c:1988) ____sys_recvmsg (net/socket.c:1046 net/socket.c:2801) ___sys_recvmsg (net/socket.c:2846) do_recvmmsg (net/socket.c:2943) __x64_sys_recvmmsg (net/socket.c:3041 net/socket.c:3034 net/socket.c:3034) [1]: BUG: TASK stack guard page was hit at 00000000f2fa9af1 (stack is 00000000b7912430..000000009a436beb) stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 1 PID: 223719 Comm: kworker/1:3 Not tainted 6.8.0-12821-g537c2e91d354-dirty #11 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 Workqueue: events netlink_sock_destruct_work RIP: 0010:fib6_dump_done (net/ipv6/ip6_fib.c:570) Code: 3c 24 e8 f3 e9 51 fd e9 28 fd ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 41 57 41 56 41 55 41 54 55 48 89 fd <53> 48 8d 5d 60 e8 b6 4d 07 fd 48 89 da 48 b8 00 00 00 00 00 fc ff RSP: 0018:ffffc9000d980000 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffffffff84405990 RCX: ffffffff844059d3 RDX: ffff8881028e0000 RSI: ffffffff84405ac2 RDI: ffff88810c02f358 RBP: ffff88810c02f358 R08: 0000000000000007 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000224 R12: 0000000000000000 R13: ffff888007c82c78 R14: ffff888007c82c68 R15: ffff888007c82c68 FS: 0000000000000000(0000) GS:ffff88811b100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc9000d97fff8 CR3: 0000000102309002 CR4: 0000000000770ef0 PKRU: 55555554 Call Trace: <#DF> </#DF> <TASK> fib6_dump_done (net/ipv6/ip6_fib.c:572 (discriminator 1)) fib6_dump_done (net/ipv6/ip6_fib.c:572 (discriminator 1)) ... fib6_dump_done (net/ipv6/ip6_fib.c:572 (discriminator 1)) fib6_dump_done (net/ipv6/ip6_fib.c:572 (discriminator 1)) netlink_sock_destruct (net/netlink/af_netlink.c:401) __sk_destruct (net/core/sock.c:2177 (discriminator 2)) sk_destruct (net/core/sock.c:2224) __sk_free (net/core/sock.c:2235) sk_free (net/core/sock.c:2246) process_one_work (kernel/workqueue.c:3259) worker_thread (kernel/workqueue.c:3329 kernel/workqueue. ---truncated--- CVE-2024-35886 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35886.html CVE-2024-35886 https://bugzilla.suse.com/1224670 SUSE Bug 1224670 In the Linux kernel, the following vulnerability has been resolved: netfilter: validate user input for expected length I got multiple syzbot reports showing old bugs exposed by BPF after commit 20f2505fb436 ("bpf: Try to avoid kzalloc in cgroup/{s,g}etsockopt") setsockopt() @optlen argument should be taken into account before copying data. BUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset include/linux/sockptr.h:49 [inline] BUG: KASAN: slab-out-of-bounds in copy_from_sockptr include/linux/sockptr.h:55 [inline] BUG: KASAN: slab-out-of-bounds in do_replace net/ipv4/netfilter/ip_tables.c:1111 [inline] BUG: KASAN: slab-out-of-bounds in do_ipt_set_ctl+0x902/0x3dd0 net/ipv4/netfilter/ip_tables.c:1627 Read of size 96 at addr ffff88802cd73da0 by task syz-executor.4/7238 CPU: 1 PID: 7238 Comm: syz-executor.4 Not tainted 6.9.0-rc2-next-20240403-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105 copy_from_sockptr_offset include/linux/sockptr.h:49 [inline] copy_from_sockptr include/linux/sockptr.h:55 [inline] do_replace net/ipv4/netfilter/ip_tables.c:1111 [inline] do_ipt_set_ctl+0x902/0x3dd0 net/ipv4/netfilter/ip_tables.c:1627 nf_setsockopt+0x295/0x2c0 net/netfilter/nf_sockopt.c:101 do_sock_setsockopt+0x3af/0x720 net/socket.c:2311 __sys_setsockopt+0x1ae/0x250 net/socket.c:2334 __do_sys_setsockopt net/socket.c:2343 [inline] __se_sys_setsockopt net/socket.c:2340 [inline] __x64_sys_setsockopt+0xb5/0xd0 net/socket.c:2340 do_syscall_64+0xfb/0x240 entry_SYSCALL_64_after_hwframe+0x72/0x7a RIP: 0033:0x7fd22067dde9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fd21f9ff0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000036 RAX: ffffffffffffffda RBX: 00007fd2207abf80 RCX: 00007fd22067dde9 RDX: 0000000000000040 RSI: 0000000000000000 RDI: 0000000000000003 RBP: 00007fd2206ca47a R08: 0000000000000001 R09: 0000000000000000 R10: 0000000020000880 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007fd2207abf80 R15: 00007ffd2d0170d8 </TASK> Allocated by task 7238: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:370 [inline] __kasan_kmalloc+0x98/0xb0 mm/kasan/common.c:387 kasan_kmalloc include/linux/kasan.h:211 [inline] __do_kmalloc_node mm/slub.c:4069 [inline] __kmalloc_noprof+0x200/0x410 mm/slub.c:4082 kmalloc_noprof include/linux/slab.h:664 [inline] __cgroup_bpf_run_filter_setsockopt+0xd47/0x1050 kernel/bpf/cgroup.c:1869 do_sock_setsockopt+0x6b4/0x720 net/socket.c:2293 __sys_setsockopt+0x1ae/0x250 net/socket.c:2334 __do_sys_setsockopt net/socket.c:2343 [inline] __se_sys_setsockopt net/socket.c:2340 [inline] __x64_sys_setsockopt+0xb5/0xd0 net/socket.c:2340 do_syscall_64+0xfb/0x240 entry_SYSCALL_64_after_hwframe+0x72/0x7a The buggy address belongs to the object at ffff88802cd73da0 which belongs to the cache kmalloc-8 of size 8 The buggy address is located 0 bytes inside of allocated 1-byte region [ffff88802cd73da0, ffff88802cd73da1) The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff88802cd73020 pfn:0x2cd73 flags: 0xfff80000000000(node=0|zone=1|lastcpupid=0xfff) page_type: 0xffffefff(slab) raw: 00fff80000000000 ffff888015041280 dead000000000100 dead000000000122 raw: ffff88802cd73020 000000008080007f 00000001ffffefff 00 ---truncated--- CVE-2024-35896 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35896.html CVE-2024-35896 https://bugzilla.suse.com/1224662 SUSE Bug 1224662 In the Linux kernel, the following vulnerability has been resolved: fbmon: prevent division by zero in fb_videomode_from_videomode() The expression htotal * vtotal can have a zero value on overflow. It is necessary to prevent division by zero like in fb_var_to_videomode(). Found by Linux Verification Center (linuxtesting.org) with Svace. CVE-2024-35922 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35922.html CVE-2024-35922 https://bugzilla.suse.com/1224660 SUSE Bug 1224660 In the Linux kernel, the following vulnerability has been resolved: block: prevent division by zero in blk_rq_stat_sum() The expression dst->nr_samples + src->nr_samples may have zero value on overflow. It is necessary to add a check to avoid division by zero. Found by Linux Verification Center (linuxtesting.org) with Svace. CVE-2024-35925 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35925.html CVE-2024-35925 https://bugzilla.suse.com/1224661 SUSE Bug 1224661 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc() The call to lpfc_sli4_resume_rpi() in lpfc_rcv_padisc() may return an unsuccessful status. In such cases, the elsiocb is not issued, the completion is not called, and thus the elsiocb resource is leaked. Check return value after calling lpfc_sli4_resume_rpi() and conditionally release the elsiocb resource. CVE-2024-35930 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35930.html CVE-2024-35930 https://bugzilla.suse.com/1224651 SUSE Bug 1224651 In the Linux kernel, the following vulnerability has been resolved: drm/client: Fully protect modes[] with dev->mode_config.mutex The modes[] array contains pointers to modes on the connectors' mode lists, which are protected by dev->mode_config.mutex. Thus we need to extend modes[] the same protection or by the time we use it the elements may already be pointing to freed/reused memory. CVE-2024-35950 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35950.html CVE-2024-35950 https://bugzilla.suse.com/1224703 SUSE Bug 1224703 https://bugzilla.suse.com/1225310 SUSE Bug 1225310 In the Linux kernel, the following vulnerability has been resolved: btrfs: qgroup: fix qgroup prealloc rsv leak in subvolume operations Create subvolume, create snapshot and delete subvolume all use btrfs_subvolume_reserve_metadata() to reserve metadata for the changes done to the parent subvolume's fs tree, which cannot be mediated in the normal way via start_transaction. When quota groups (squota or qgroups) are enabled, this reserves qgroup metadata of type PREALLOC. Once the operation is associated to a transaction, we convert PREALLOC to PERTRANS, which gets cleared in bulk at the end of the transaction. However, the error paths of these three operations were not implementing this lifecycle correctly. They unconditionally converted the PREALLOC to PERTRANS in a generic cleanup step regardless of errors or whether the operation was fully associated to a transaction or not. This resulted in error paths occasionally converting this rsv to PERTRANS without calling record_root_in_trans successfully, which meant that unless that root got recorded in the transaction by some other thread, the end of the transaction would not free that root's PERTRANS, leaking it. Ultimately, this resulted in hitting a WARN in CONFIG_BTRFS_DEBUG builds at unmount for the leaked reservation. The fix is to ensure that every qgroup PREALLOC reservation observes the following properties: 1. any failure before record_root_in_trans is called successfully results in freeing the PREALLOC reservation. 2. after record_root_in_trans, we convert to PERTRANS, and now the transaction owns freeing the reservation. This patch enforces those properties on the three operations. Without it, generic/269 with squotas enabled at mkfs time would fail in ~5-10 runs on my system. With this patch, it ran successfully 1000 times in a row. CVE-2024-35956 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35956.html CVE-2024-35956 https://bugzilla.suse.com/1224674 SUSE Bug 1224674 In the Linux kernel, the following vulnerability has been resolved: net: ena: Fix incorrect descriptor free behavior ENA has two types of TX queues: - queues which only process TX packets arriving from the network stack - queues which only process TX packets forwarded to it by XDP_REDIRECT or XDP_TX instructions The ena_free_tx_bufs() cycles through all descriptors in a TX queue and unmaps + frees every descriptor that hasn't been acknowledged yet by the device (uncompleted TX transactions). The function assumes that the processed TX queue is necessarily from the first category listed above and ends up using napi_consume_skb() for descriptors belonging to an XDP specific queue. This patch solves a bug in which, in case of a VF reset, the descriptors aren't freed correctly, leading to crashes. CVE-2024-35958 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35958.html CVE-2024-35958 https://bugzilla.suse.com/1224677 SUSE Bug 1224677 In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Properly link new fs rules into the tree Previously, add_rule_fg would only add newly created rules from the handle into the tree when they had a refcount of 1. On the other hand, create_flow_handle tries hard to find and reference already existing identical rules instead of creating new ones. These two behaviors can result in a situation where create_flow_handle 1) creates a new rule and references it, then 2) in a subsequent step during the same handle creation references it again, resulting in a rule with a refcount of 2 that is not linked into the tree, will have a NULL parent and root and will result in a crash when the flow group is deleted because del_sw_hw_rule, invoked on rule deletion, assumes node->parent is != NULL. This happened in the wild, due to another bug related to incorrect handling of duplicate pkt_reformat ids, which lead to the code in create_flow_handle incorrectly referencing a just-added rule in the same flow handle, resulting in the problem described above. Full details are at [1]. This patch changes add_rule_fg to add new rules without parents into the tree, properly initializing them and avoiding the crash. This makes it more consistent with how rules are added to an FTE in create_flow_handle. CVE-2024-35960 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35960.html CVE-2024-35960 https://bugzilla.suse.com/1224588 SUSE Bug 1224588 In the Linux kernel, the following vulnerability has been resolved: netfilter: complete validation of user input In my recent commit, I missed that do_replace() handlers use copy_from_sockptr() (which I fixed), followed by unsafe copy_from_sockptr_offset() calls. In all functions, we can perform the @optlen validation before even calling xt_alloc_table_info() with the following check: if ((u64)optlen < (u64)tmp.size + sizeof(tmp)) return -EINVAL; CVE-2024-35962 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35962.html CVE-2024-35962 https://bugzilla.suse.com/1224583 SUSE Bug 1224583 In the Linux kernel, the following vulnerability has been resolved: xsk: validate user input for XDP_{UMEM|COMPLETION}_FILL_RING syzbot reported an illegal copy in xsk_setsockopt() [1] Make sure to validate setsockopt() @optlen parameter. [1] BUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset include/linux/sockptr.h:49 [inline] BUG: KASAN: slab-out-of-bounds in copy_from_sockptr include/linux/sockptr.h:55 [inline] BUG: KASAN: slab-out-of-bounds in xsk_setsockopt+0x909/0xa40 net/xdp/xsk.c:1420 Read of size 4 at addr ffff888028c6cde3 by task syz-executor.0/7549 CPU: 0 PID: 7549 Comm: syz-executor.0 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 copy_from_sockptr_offset include/linux/sockptr.h:49 [inline] copy_from_sockptr include/linux/sockptr.h:55 [inline] xsk_setsockopt+0x909/0xa40 net/xdp/xsk.c:1420 do_sock_setsockopt+0x3af/0x720 net/socket.c:2311 __sys_setsockopt+0x1ae/0x250 net/socket.c:2334 __do_sys_setsockopt net/socket.c:2343 [inline] __se_sys_setsockopt net/socket.c:2340 [inline] __x64_sys_setsockopt+0xb5/0xd0 net/socket.c:2340 do_syscall_64+0xfb/0x240 entry_SYSCALL_64_after_hwframe+0x6d/0x75 RIP: 0033:0x7fb40587de69 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fb40665a0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000036 RAX: ffffffffffffffda RBX: 00007fb4059abf80 RCX: 00007fb40587de69 RDX: 0000000000000005 RSI: 000000000000011b RDI: 0000000000000006 RBP: 00007fb4058ca47a R08: 0000000000000002 R09: 0000000000000000 R10: 0000000020001980 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007fb4059abf80 R15: 00007fff57ee4d08 </TASK> Allocated by task 7549: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:370 [inline] __kasan_kmalloc+0x98/0xb0 mm/kasan/common.c:387 kasan_kmalloc include/linux/kasan.h:211 [inline] __do_kmalloc_node mm/slub.c:3966 [inline] __kmalloc+0x233/0x4a0 mm/slub.c:3979 kmalloc include/linux/slab.h:632 [inline] __cgroup_bpf_run_filter_setsockopt+0xd2f/0x1040 kernel/bpf/cgroup.c:1869 do_sock_setsockopt+0x6b4/0x720 net/socket.c:2293 __sys_setsockopt+0x1ae/0x250 net/socket.c:2334 __do_sys_setsockopt net/socket.c:2343 [inline] __se_sys_setsockopt net/socket.c:2340 [inline] __x64_sys_setsockopt+0xb5/0xd0 net/socket.c:2340 do_syscall_64+0xfb/0x240 entry_SYSCALL_64_after_hwframe+0x6d/0x75 The buggy address belongs to the object at ffff888028c6cde0 which belongs to the cache kmalloc-8 of size 8 The buggy address is located 1 bytes to the right of allocated 2-byte region [ffff888028c6cde0, ffff888028c6cde2) The buggy address belongs to the physical page: page:ffffea0000a31b00 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888028c6c9c0 pfn:0x28c6c anon flags: 0xfff00000000800(slab|node=0|zone=1|lastcpupid=0x7ff) page_type: 0xffffffff() raw: 00fff00000000800 ffff888014c41280 0000000000000000 dead000000000001 raw: ffff888028c6c9c0 0000000080800057 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x112cc0(GFP_USER|__GFP_NOWARN|__GFP_NORETRY), pid 6648, tgid 6644 (syz-executor.0), ts 133906047828, free_ts 133859922223 set_page_owner include/linux/page_owner.h:31 [inline] post_alloc_hook+0x1ea/0x210 mm/page_alloc.c:1533 prep_new_page mm/page_alloc.c: ---truncated--- CVE-2024-35976 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35976.html CVE-2024-35976 https://bugzilla.suse.com/1224575 SUSE Bug 1224575 In the Linux kernel, the following vulnerability has been resolved: raid1: fix use-after-free for original bio in raid1_write_request() r1_bio->bios[] is used to record new bios that will be issued to underlying disks, however, in raid1_write_request(), r1_bio->bios[] will set to the original bio temporarily. Meanwhile, if blocked rdev is set, free_r1bio() will be called causing that all r1_bio->bios[] to be freed: raid1_write_request() r1_bio = alloc_r1bio(mddev, bio); -> r1_bio->bios[] is NULL for (i = 0; i < disks; i++) -> for each rdev in conf // first rdev is normal r1_bio->bios[0] = bio; -> set to original bio // second rdev is blocked if (test_bit(Blocked, &rdev->flags)) break if (blocked_rdev) free_r1bio() put_all_bios() bio_put(r1_bio->bios[0]) -> original bio is freed Test scripts: mdadm -CR /dev/md0 -l1 -n4 /dev/sd[abcd] --assume-clean fio -filename=/dev/md0 -ioengine=libaio -rw=write -bs=4k -numjobs=1 \ -iodepth=128 -name=test -direct=1 echo blocked > /sys/block/md0/md/rd2/state Test result: BUG bio-264 (Not tainted): Object already free ----------------------------------------------------------------------------- Allocated in mempool_alloc_slab+0x24/0x50 age=1 cpu=1 pid=869 kmem_cache_alloc+0x324/0x480 mempool_alloc_slab+0x24/0x50 mempool_alloc+0x6e/0x220 bio_alloc_bioset+0x1af/0x4d0 blkdev_direct_IO+0x164/0x8a0 blkdev_write_iter+0x309/0x440 aio_write+0x139/0x2f0 io_submit_one+0x5ca/0xb70 __do_sys_io_submit+0x86/0x270 __x64_sys_io_submit+0x22/0x30 do_syscall_64+0xb1/0x210 entry_SYSCALL_64_after_hwframe+0x6c/0x74 Freed in mempool_free_slab+0x1f/0x30 age=1 cpu=1 pid=869 kmem_cache_free+0x28c/0x550 mempool_free_slab+0x1f/0x30 mempool_free+0x40/0x100 bio_free+0x59/0x80 bio_put+0xf0/0x220 free_r1bio+0x74/0xb0 raid1_make_request+0xadf/0x1150 md_handle_request+0xc7/0x3b0 md_submit_bio+0x76/0x130 __submit_bio+0xd8/0x1d0 submit_bio_noacct_nocheck+0x1eb/0x5c0 submit_bio_noacct+0x169/0xd40 submit_bio+0xee/0x1d0 blkdev_direct_IO+0x322/0x8a0 blkdev_write_iter+0x309/0x440 aio_write+0x139/0x2f0 Since that bios for underlying disks are not allocated yet, fix this problem by using mempool_free() directly to free the r1_bio. CVE-2024-35979 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35979.html CVE-2024-35979 https://bugzilla.suse.com/1224572 SUSE Bug 1224572 In the Linux kernel, the following vulnerability has been resolved: HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up The flag I2C_HID_READ_PENDING is used to serialize I2C operations. However, this is not necessary, because I2C core already has its own locking for that. More importantly, this flag can cause a lock-up: if the flag is set in i2c_hid_xfer() and an interrupt happens, the interrupt handler (i2c_hid_irq) will check this flag and return immediately without doing anything, then the interrupt handler will be invoked again in an infinite loop. Since interrupt handler is an RT task, it takes over the CPU and the flag-clearing task never gets scheduled, thus we have a lock-up. Delete this unnecessary flag. CVE-2024-35997 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35997.html CVE-2024-35997 https://bugzilla.suse.com/1224552 SUSE Bug 1224552 In the Linux kernel, the following vulnerability has been resolved: smb3: fix lock ordering potential deadlock in cifs_sync_mid_result Coverity spotted that the cifs_sync_mid_result function could deadlock "Thread deadlock (ORDER_REVERSAL) lock_order: Calling spin_lock acquires lock TCP_Server_Info.srv_lock while holding lock TCP_Server_Info.mid_lock" Addresses-Coverity: 1590401 ("Thread deadlock (ORDER_REVERSAL)") CVE-2024-35998 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-35998.html CVE-2024-35998 https://bugzilla.suse.com/1224549 SUSE Bug 1224549 In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() Assuming the following: - side A configures the n_gsm in basic option mode - side B sends the header of a basic option mode frame with data length 1 - side A switches to advanced option mode - side B sends 2 data bytes which exceeds gsm->len Reason: gsm->len is not used in advanced option mode. - side A switches to basic option mode - side B keeps sending until gsm0_receive() writes past gsm->buf Reason: Neither gsm->state nor gsm->len have been reset after reconfiguration. Fix this by changing gsm->count to gsm->len comparison from equal to less than. Also add upper limit checks against the constant MAX_MRU in gsm0_receive() and gsm1_receive() to harden against memory corruption of gsm->len and gsm->mru. All other checks remain as we still need to limit the data according to the user configuration and actual payload size. CVE-2024-36016 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36016.html CVE-2024-36016 https://bugzilla.suse.com/1225642 SUSE Bug 1225642 In the Linux kernel, the following vulnerability has been resolved: rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation Each attribute inside a nested IFLA_VF_VLAN_LIST is assumed to be a struct ifla_vf_vlan_info so the size of such attribute needs to be at least of sizeof(struct ifla_vf_vlan_info) which is 14 bytes. The current size validation in do_setvfinfo is against NLA_HDRLEN (4 bytes) which is less than sizeof(struct ifla_vf_vlan_info) so this validation is not enough and a too small attribute might be cast to a struct ifla_vf_vlan_info, this might result in an out of bands read access when accessing the saved (casted) entry in ivvl. CVE-2024-36017 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36017.html CVE-2024-36017 https://bugzilla.suse.com/1225681 SUSE Bug 1225681 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix off by one in qla_edif_app_getstats() The app_reply->elem[] array is allocated earlier in this function and it has app_req.num_ports elements. Thus this > comparison needs to be >= to prevent memory corruption. CVE-2024-36025 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36025.html CVE-2024-36025 https://bugzilla.suse.com/1225704 SUSE Bug 1225704 In the Linux kernel, the following vulnerability has been resolved: fpga: bridge: add owner module and take its refcount The current implementation of the fpga bridge assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the bridge if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_bridge struct and use it to take the module's refcount. Modify the function for registering a bridge to take an additional owner module parameter and rename it to avoid conflicts. Use the old function name for a helper macro that automatically sets the module that registers the bridge as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a bridge without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga bridge. Other changes: opportunistically move put_device() from __fpga_bridge_get() to fpga_bridge_get() and of_fpga_bridge_get() to improve code clarity since the bridge device is taken in these functions. CVE-2024-36479 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36479.html CVE-2024-36479 https://bugzilla.suse.com/1226949 SUSE Bug 1226949 ** 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-36592 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36592.html CVE-2024-36592 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: add missing firmware sanity checks Add the missing sanity checks when parsing the firmware files before downloading them to avoid accessing and corrupting memory beyond the vmalloced buffer. CVE-2024-36880 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36880.html CVE-2024-36880 https://bugzilla.suse.com/1225722 SUSE Bug 1225722 In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete FFS based applications can utilize the aio_cancel() callback to dequeue pending USB requests submitted to the UDC. There is a scenario where the FFS application issues an AIO cancel call, while the UDC is handling a soft disconnect. For a DWC3 based implementation, the callstack looks like the following: DWC3 Gadget FFS Application dwc3_gadget_soft_disconnect() ... --> dwc3_stop_active_transfers() --> dwc3_gadget_giveback(-ESHUTDOWN) --> ffs_epfile_async_io_complete() ffs_aio_cancel() --> usb_ep_free_request() --> usb_ep_dequeue() There is currently no locking implemented between the AIO completion handler and AIO cancel, so the issue occurs if the completion routine is running in parallel to an AIO cancel call coming from the FFS application. As the completion call frees the USB request (io_data->req) the FFS application is also referencing it for the usb_ep_dequeue() call. This can lead to accessing a stale/hanging pointer. commit b566d38857fc ("usb: gadget: f_fs: use io_data->status consistently") relocated the usb_ep_free_request() into ffs_epfile_async_io_complete(). However, in order to properly implement locking to mitigate this issue, the spinlock can't be added to ffs_epfile_async_io_complete(), as usb_ep_dequeue() (if successfully dequeuing a USB request) will call the function driver's completion handler in the same context. Hence, leading into a deadlock. Fix this issue by moving the usb_ep_free_request() back to ffs_user_copy_worker(), and ensuring that it explicitly sets io_data->req to NULL after freeing it within the ffs->eps_lock. This resolves the race condition above, as the ffs_aio_cancel() routine will not continue attempting to dequeue a request that has already been freed, or the ffs_user_copy_work() not freeing the USB request until the AIO cancel is done referencing it. This fix depends on commit b566d38857fc ("usb: gadget: f_fs: use io_data->status consistently") CVE-2024-36894 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36894.html CVE-2024-36894 https://bugzilla.suse.com/1225749 SUSE Bug 1225749 https://bugzilla.suse.com/1226139 SUSE Bug 1226139 In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: fix nfc_llcp_setsockopt() unsafe copies syzbot reported unsafe calls to copy_from_sockptr() [1] Use copy_safe_from_sockptr() instead. [1] BUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset include/linux/sockptr.h:49 [inline] BUG: KASAN: slab-out-of-bounds in copy_from_sockptr include/linux/sockptr.h:55 [inline] BUG: KASAN: slab-out-of-bounds in nfc_llcp_setsockopt+0x6c2/0x850 net/nfc/llcp_sock.c:255 Read of size 4 at addr ffff88801caa1ec3 by task syz-executor459/5078 CPU: 0 PID: 5078 Comm: syz-executor459 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 copy_from_sockptr_offset include/linux/sockptr.h:49 [inline] copy_from_sockptr include/linux/sockptr.h:55 [inline] nfc_llcp_setsockopt+0x6c2/0x850 net/nfc/llcp_sock.c:255 do_sock_setsockopt+0x3b1/0x720 net/socket.c:2311 __sys_setsockopt+0x1ae/0x250 net/socket.c:2334 __do_sys_setsockopt net/socket.c:2343 [inline] __se_sys_setsockopt net/socket.c:2340 [inline] __x64_sys_setsockopt+0xb5/0xd0 net/socket.c:2340 do_syscall_64+0xfd/0x240 entry_SYSCALL_64_after_hwframe+0x6d/0x75 RIP: 0033:0x7f7fac07fd89 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 91 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff660eb788 EFLAGS: 00000246 ORIG_RAX: 0000000000000036 RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f7fac07fd89 RDX: 0000000000000000 RSI: 0000000000000118 RDI: 0000000000000004 RBP: 0000000000000000 R08: 0000000000000002 R09: 0000000000000000 R10: 0000000020000a80 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 CVE-2024-36915 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36915.html CVE-2024-36915 https://bugzilla.suse.com/1225758 SUSE Bug 1225758 In the Linux kernel, the following vulnerability has been resolved: block: fix overflow in blk_ioctl_discard() There is no check for overflow of 'start + len' in blk_ioctl_discard(). Hung task occurs if submit an discard ioctl with the following param: start = 0x80000000000ff000, len = 0x8000000000fff000; Add the overflow validation now. CVE-2024-36917 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36917.html CVE-2024-36917 https://bugzilla.suse.com/1225770 SUSE Bug 1225770 In the Linux kernel, the following vulnerability has been resolved: scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload The session resources are used by FW and driver when session is offloaded, once session is uploaded these resources are not used. The lock is not required as these fields won't be used any longer. The offload and upload calls are sequential, hence lock is not required. This will suppress following BUG_ON(): [ 449.843143] ------------[ cut here ]------------ [ 449.848302] kernel BUG at mm/vmalloc.c:2727! [ 449.853072] invalid opcode: 0000 [#1] PREEMPT SMP PTI [ 449.858712] CPU: 5 PID: 1996 Comm: kworker/u24:2 Not tainted 5.14.0-118.el9.x86_64 #1 Rebooting. [ 449.867454] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.3.4 11/08/2016 [ 449.876966] Workqueue: fc_rport_eq fc_rport_work [libfc] [ 449.882910] RIP: 0010:vunmap+0x2e/0x30 [ 449.887098] Code: 00 65 8b 05 14 a2 f0 4a a9 00 ff ff 00 75 1b 55 48 89 fd e8 34 36 79 00 48 85 ed 74 0b 48 89 ef 31 f6 5d e9 14 fc ff ff 5d c3 <0f> 0b 0f 1f 44 00 00 41 57 41 56 49 89 ce 41 55 49 89 fd 41 54 41 [ 449.908054] RSP: 0018:ffffb83d878b3d68 EFLAGS: 00010206 [ 449.913887] RAX: 0000000080000201 RBX: ffff8f4355133550 RCX: 000000000d400005 [ 449.921843] RDX: 0000000000000001 RSI: 0000000000001000 RDI: ffffb83da53f5000 [ 449.929808] RBP: ffff8f4ac6675800 R08: ffffb83d878b3d30 R09: 00000000000efbdf [ 449.937774] R10: 0000000000000003 R11: ffff8f434573e000 R12: 0000000000001000 [ 449.945736] R13: 0000000000001000 R14: ffffb83da53f5000 R15: ffff8f43d4ea3ae0 [ 449.953701] FS: 0000000000000000(0000) GS:ffff8f529fc80000(0000) knlGS:0000000000000000 [ 449.962732] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 449.969138] CR2: 00007f8cf993e150 CR3: 0000000efbe10003 CR4: 00000000003706e0 [ 449.977102] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 449.985065] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 449.993028] Call Trace: [ 449.995756] __iommu_dma_free+0x96/0x100 [ 450.000139] bnx2fc_free_session_resc+0x67/0x240 [bnx2fc] [ 450.006171] bnx2fc_upload_session+0xce/0x100 [bnx2fc] [ 450.011910] bnx2fc_rport_event_handler+0x9f/0x240 [bnx2fc] [ 450.018136] fc_rport_work+0x103/0x5b0 [libfc] [ 450.023103] process_one_work+0x1e8/0x3c0 [ 450.027581] worker_thread+0x50/0x3b0 [ 450.031669] ? rescuer_thread+0x370/0x370 [ 450.036143] kthread+0x149/0x170 [ 450.039744] ? set_kthread_struct+0x40/0x40 [ 450.044411] ret_from_fork+0x22/0x30 [ 450.048404] Modules linked in: vfat msdos fat xfs nfs_layout_nfsv41_files rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver dm_service_time qedf qed crc8 bnx2fc libfcoe libfc scsi_transport_fc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp dcdbas rapl intel_cstate intel_uncore mei_me pcspkr mei ipmi_ssif lpc_ich ipmi_si fuse zram ext4 mbcache jbd2 loop nfsv3 nfs_acl nfs lockd grace fscache netfs irdma ice sd_mod t10_pi sg ib_uverbs ib_core 8021q garp mrp stp llc mgag200 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt mxm_wmi fb_sys_fops cec crct10dif_pclmul ahci crc32_pclmul bnx2x drm ghash_clmulni_intel libahci rfkill i40e libata megaraid_sas mdio wmi sunrpc lrw dm_crypt dm_round_robin dm_multipath dm_snapshot dm_bufio dm_mirror dm_region_hash dm_log dm_zero dm_mod linear raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid6_pq libcrc32c crc32c_intel raid1 raid0 iscsi_ibft squashfs be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls [ 450.048497] libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi edd ipmi_devintf ipmi_msghandler [ 450.159753] ---[ end trace 712de2c57c64abc8 ]--- CVE-2024-36919 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36919.html CVE-2024-36919 https://bugzilla.suse.com/1225767 SUSE Bug 1225767 In the Linux kernel, the following vulnerability has been resolved: fs/9p: fix uninitialized values during inode evict If an iget fails due to not being able to retrieve information from the server then the inode structure is only partially initialized. When the inode gets evicted, references to uninitialized structures (like fscache cookies) were being made. This patch checks for a bad_inode before doing anything other than clearing the inode from the cache. Since the inode is bad, it shouldn't have any state associated with it that needs to be written back (and there really isn't a way to complete those anyways). CVE-2024-36923 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36923.html CVE-2024-36923 https://bugzilla.suse.com/1225815 SUSE Bug 1225815 In the Linux kernel, the following vulnerability has been resolved: bna: ensure the copied buf is NUL terminated Currently, we allocate a nbytes-sized kernel buffer and copy nbytes from userspace to that buffer. Later, we use sscanf on this buffer but we don't ensure that the string is terminated inside the buffer, this can lead to OOB read when using sscanf. Fix this issue by using memdup_user_nul instead of memdup_user. CVE-2024-36934 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36934.html CVE-2024-36934 https://bugzilla.suse.com/1225760 SUSE Bug 1225760 In the Linux kernel, the following vulnerability has been resolved: bpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue Fix NULL pointer data-races in sk_psock_skb_ingress_enqueue() which syzbot reported [1]. [1] BUG: KCSAN: data-race in sk_psock_drop / sk_psock_skb_ingress_enqueue write to 0xffff88814b3278b8 of 8 bytes by task 10724 on cpu 1: sk_psock_stop_verdict net/core/skmsg.c:1257 [inline] sk_psock_drop+0x13e/0x1f0 net/core/skmsg.c:843 sk_psock_put include/linux/skmsg.h:459 [inline] sock_map_close+0x1a7/0x260 net/core/sock_map.c:1648 unix_release+0x4b/0x80 net/unix/af_unix.c:1048 __sock_release net/socket.c:659 [inline] sock_close+0x68/0x150 net/socket.c:1421 __fput+0x2c1/0x660 fs/file_table.c:422 __fput_sync+0x44/0x60 fs/file_table.c:507 __do_sys_close fs/open.c:1556 [inline] __se_sys_close+0x101/0x1b0 fs/open.c:1541 __x64_sys_close+0x1f/0x30 fs/open.c:1541 do_syscall_64+0xd3/0x1d0 entry_SYSCALL_64_after_hwframe+0x6d/0x75 read to 0xffff88814b3278b8 of 8 bytes by task 10713 on cpu 0: sk_psock_data_ready include/linux/skmsg.h:464 [inline] sk_psock_skb_ingress_enqueue+0x32d/0x390 net/core/skmsg.c:555 sk_psock_skb_ingress_self+0x185/0x1e0 net/core/skmsg.c:606 sk_psock_verdict_apply net/core/skmsg.c:1008 [inline] sk_psock_verdict_recv+0x3e4/0x4a0 net/core/skmsg.c:1202 unix_read_skb net/unix/af_unix.c:2546 [inline] unix_stream_read_skb+0x9e/0xf0 net/unix/af_unix.c:2682 sk_psock_verdict_data_ready+0x77/0x220 net/core/skmsg.c:1223 unix_stream_sendmsg+0x527/0x860 net/unix/af_unix.c:2339 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg+0x140/0x180 net/socket.c:745 ____sys_sendmsg+0x312/0x410 net/socket.c:2584 ___sys_sendmsg net/socket.c:2638 [inline] __sys_sendmsg+0x1e9/0x280 net/socket.c:2667 __do_sys_sendmsg net/socket.c:2676 [inline] __se_sys_sendmsg net/socket.c:2674 [inline] __x64_sys_sendmsg+0x46/0x50 net/socket.c:2674 do_syscall_64+0xd3/0x1d0 entry_SYSCALL_64_after_hwframe+0x6d/0x75 value changed: 0xffffffff83d7feb0 -> 0x0000000000000000 Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 10713 Comm: syz-executor.4 Tainted: G W 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024 Prior to this, commit 4cd12c6065df ("bpf, sockmap: Fix NULL pointer dereference in sk_psock_verdict_data_ready()") fixed one NULL pointer similarly due to no protection of saved_data_ready. Here is another different caller causing the same issue because of the same reason. So we should protect it with sk_callback_lock read lock because the writer side in the sk_psock_drop() uses "write_lock_bh(&sk->sk_callback_lock);". To avoid errors that could happen in future, I move those two pairs of lock into the sk_psock_data_ready(), which is suggested by John Fastabend. CVE-2024-36938 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36938.html CVE-2024-36938 https://bugzilla.suse.com/1225761 SUSE Bug 1225761 In the Linux kernel, the following vulnerability has been resolved: pinctrl: core: delete incorrect free in pinctrl_enable() The "pctldev" struct is allocated in devm_pinctrl_register_and_init(). It's a devm_ managed pointer that is freed by devm_pinctrl_dev_release(), so freeing it in pinctrl_enable() will lead to a double free. The devm_pinctrl_dev_release() function frees the pindescs and destroys the mutex as well. CVE-2024-36940 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36940.html CVE-2024-36940 https://bugzilla.suse.com/1225840 SUSE Bug 1225840 https://bugzilla.suse.com/1225841 SUSE Bug 1225841 In the Linux kernel, the following vulnerability has been resolved: amd/amdkfd: sync all devices to wait all processes being evicted If there are more than one device doing reset in parallel, the first device will call kfd_suspend_all_processes() to evict all processes on all devices, this call takes time to finish. other device will start reset and recover without waiting. if the process has not been evicted before doing recover, it will be restored, then caused page fault. CVE-2024-36949 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36949.html CVE-2024-36949 https://bugzilla.suse.com/1225894 SUSE Bug 1225894 In the Linux kernel, the following vulnerability has been resolved: firewire: ohci: mask bus reset interrupts between ISR and bottom half In the FireWire OHCI interrupt handler, if a bus reset interrupt has occurred, mask bus reset interrupts until bus_reset_work has serviced and cleared the interrupt. Normally, we always leave bus reset interrupts masked. We infer the bus reset from the self-ID interrupt that happens shortly thereafter. A scenario where we unmask bus reset interrupts was introduced in 2008 in a007bb857e0b26f5d8b73c2ff90782d9c0972620: If OHCI_PARAM_DEBUG_BUSRESETS (8) is set in the debug parameter bitmask, we will unmask bus reset interrupts so we can log them. irq_handler logs the bus reset interrupt. However, we can't clear the bus reset event flag in irq_handler, because we won't service the event until later. irq_handler exits with the event flag still set. If the corresponding interrupt is still unmasked, the first bus reset will usually freeze the system due to irq_handler being called again each time it exits. This freeze can be reproduced by loading firewire_ohci with "modprobe firewire_ohci debug=-1" (to enable all debugging output). Apparently there are also some cases where bus_reset_work will get called soon enough to clear the event, and operation will continue normally. This freeze was first reported a few months after a007bb85 was committed, but until now it was never fixed. The debug level could safely be set to -1 through sysfs after the module was loaded, but this would be ineffectual in logging bus reset interrupts since they were only unmasked during initialization. irq_handler will now leave the event flag set but mask bus reset interrupts, so irq_handler won't be called again and there will be no freeze. If OHCI_PARAM_DEBUG_BUSRESETS is enabled, bus_reset_work will unmask the interrupt after servicing the event, so future interrupts will be caught as desired. As a side effect to this change, OHCI_PARAM_DEBUG_BUSRESETS can now be enabled through sysfs in addition to during initial module loading. However, when enabled through sysfs, logging of bus reset interrupts will be effective only starting with the second bus reset, after bus_reset_work has executed. CVE-2024-36950 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36950.html CVE-2024-36950 https://bugzilla.suse.com/1225895 SUSE Bug 1225895 In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Fix invalid reads in fence signaled events Correctly set the length of the drm_event to the size of the structure that's actually used. The length of the drm_event was set to the parent structure instead of to the drm_vmw_event_fence which is supposed to be read. drm_read uses the length parameter to copy the event to the user space thus resuling in oob reads. CVE-2024-36960 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36960.html CVE-2024-36960 https://bugzilla.suse.com/1225872 SUSE Bug 1225872 In the Linux kernel, the following vulnerability has been resolved: fs/9p: only translate RWX permissions for plain 9P2000 Garbage in plain 9P2000's perm bits is allowed through, which causes it to be able to set (among others) the suid bit. This was presumably not the intent since the unix extended bits are handled explicitly and conditionally on .u. CVE-2024-36964 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-36964.html CVE-2024-36964 https://bugzilla.suse.com/1225866 SUSE Bug 1225866 https://bugzilla.suse.com/1226325 SUSE Bug 1226325 In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga manager. Other changes: opportunistically move put_device() from __fpga_mgr_get() to fpga_mgr_get() and of_fpga_mgr_get() to improve code clarity since the manager device is taken in these functions. CVE-2024-37021 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-37021.html CVE-2024-37021 https://bugzilla.suse.com/1226950 SUSE Bug 1226950 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix crash on racing fsync and size-extending write into prealloc We have been seeing crashes on duplicate keys in btrfs_set_item_key_safe(): BTRFS critical (device vdb): slot 4 key (450 108 8192) new key (450 108 8192) ------------[ cut here ]------------ kernel BUG at fs/btrfs/ctree.c:2620! invalid opcode: 0000 [#1] PREEMPT SMP PTI CPU: 0 PID: 3139 Comm: xfs_io Kdump: loaded Not tainted 6.9.0 #6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014 RIP: 0010:btrfs_set_item_key_safe+0x11f/0x290 [btrfs] With the following stack trace: #0 btrfs_set_item_key_safe (fs/btrfs/ctree.c:2620:4) #1 btrfs_drop_extents (fs/btrfs/file.c:411:4) #2 log_one_extent (fs/btrfs/tree-log.c:4732:9) #3 btrfs_log_changed_extents (fs/btrfs/tree-log.c:4955:9) #4 btrfs_log_inode (fs/btrfs/tree-log.c:6626:9) #5 btrfs_log_inode_parent (fs/btrfs/tree-log.c:7070:8) #6 btrfs_log_dentry_safe (fs/btrfs/tree-log.c:7171:8) #7 btrfs_sync_file (fs/btrfs/file.c:1933:8) #8 vfs_fsync_range (fs/sync.c:188:9) #9 vfs_fsync (fs/sync.c:202:9) #10 do_fsync (fs/sync.c:212:9) #11 __do_sys_fdatasync (fs/sync.c:225:9) #12 __se_sys_fdatasync (fs/sync.c:223:1) #13 __x64_sys_fdatasync (fs/sync.c:223:1) #14 do_syscall_x64 (arch/x86/entry/common.c:52:14) #15 do_syscall_64 (arch/x86/entry/common.c:83:7) #16 entry_SYSCALL_64+0xaf/0x14c (arch/x86/entry/entry_64.S:121) So we're logging a changed extent from fsync, which is splitting an extent in the log tree. But this split part already exists in the tree, triggering the BUG(). This is the state of the log tree at the time of the crash, dumped with drgn (https://github.com/osandov/drgn/blob/main/contrib/btrfs_tree.py) to get more details than btrfs_print_leaf() gives us: >>> print_extent_buffer(prog.crashed_thread().stack_trace()[0]["eb"]) leaf 33439744 level 0 items 72 generation 9 owner 18446744073709551610 leaf 33439744 flags 0x100000000000000 fs uuid e5bd3946-400c-4223-8923-190ef1f18677 chunk uuid d58cb17e-6d02-494a-829a-18b7d8a399da item 0 key (450 INODE_ITEM 0) itemoff 16123 itemsize 160 generation 7 transid 9 size 8192 nbytes 8473563889606862198 block group 0 mode 100600 links 1 uid 0 gid 0 rdev 0 sequence 204 flags 0x10(PREALLOC) atime 1716417703.220000000 (2024-05-22 15:41:43) ctime 1716417704.983333333 (2024-05-22 15:41:44) mtime 1716417704.983333333 (2024-05-22 15:41:44) otime 17592186044416.000000000 (559444-03-08 01:40:16) item 1 key (450 INODE_REF 256) itemoff 16110 itemsize 13 index 195 namelen 3 name: 193 item 2 key (450 XATTR_ITEM 1640047104) itemoff 16073 itemsize 37 location key (0 UNKNOWN.0 0) type XATTR transid 7 data_len 1 name_len 6 name: user.a data a item 3 key (450 EXTENT_DATA 0) itemoff 16020 itemsize 53 generation 9 type 1 (regular) extent data disk byte 303144960 nr 12288 extent data offset 0 nr 4096 ram 12288 extent compression 0 (none) item 4 key (450 EXTENT_DATA 4096) itemoff 15967 itemsize 53 generation 9 type 2 (prealloc) prealloc data disk byte 303144960 nr 12288 prealloc data offset 4096 nr 8192 item 5 key (450 EXTENT_DATA 8192) itemoff 15914 itemsize 53 generation 9 type 2 (prealloc) prealloc data disk byte 303144960 nr 12288 prealloc data offset 8192 nr 4096 ... So the real problem happened earlier: notice that items 4 (4k-12k) and 5 (8k-12k) overlap. Both are prealloc extents. Item 4 straddles i_size and item 5 starts at i_size. Here is the state of ---truncated--- CVE-2024-37354 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-37354.html CVE-2024-37354 https://bugzilla.suse.com/1227101 SUSE Bug 1227101 In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix seg fault in rxe_comp_queue_pkt In rxe_comp_queue_pkt() an incoming response packet skb is enqueued to the resp_pkts queue and then a decision is made whether to run the completer task inline or schedule it. Finally the skb is dereferenced to bump a 'hw' performance counter. This is wrong because if the completer task is already running in a separate thread it may have already processed the skb and freed it which can cause a seg fault. This has been observed infrequently in testing at high scale. This patch fixes this by changing the order of enqueuing the packet until after the counter is accessed. CVE-2024-38544 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38544.html CVE-2024-38544 https://bugzilla.suse.com/1226597 SUSE Bug 1226597 In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix UAF for cq async event The refcount of CQ is not protected by locks. When CQ asynchronous events and CQ destruction are concurrent, CQ may have been released, which will cause UAF. Use the xa_lock() to protect the CQ refcount. CVE-2024-38545 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38545.html CVE-2024-38545 https://bugzilla.suse.com/1226595 SUSE Bug 1226595 In the Linux kernel, the following vulnerability has been resolved: drm: vc4: Fix possible null pointer dereference In vc4_hdmi_audio_init() of_get_address() may return NULL which is later dereferenced. Fix this bug by adding NULL check. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2024-38546 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38546.html CVE-2024-38546 https://bugzilla.suse.com/1226593 SUSE Bug 1226593 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Add 0 size check to mtk_drm_gem_obj Add a check to mtk_drm_gem_init if we attempt to allocate a GEM object of 0 bytes. Currently, no such check exists and the kernel will panic if a userspace application attempts to allocate a 0x0 GBM buffer. Tested by attempting to allocate a 0x0 GBM buffer on an MT8188 and verifying that we now return EINVAL. CVE-2024-38549 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38549.html CVE-2024-38549 https://bugzilla.suse.com/1226735 SUSE Bug 1226735 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix potential index out of bounds in color transformation function Fixes index out of bounds issue in the color transformation function. The issue could occur when the index 'i' exceeds the number of transfer function points (TRANSFER_FUNC_POINTS). The fix adds a check to ensure 'i' is within bounds before accessing the transfer function points. If 'i' is out of bounds, an error message is logged and the function returns false to indicate an error. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:405 cm_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.red' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:406 cm_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.green' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:407 cm_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.blue' 1025 <= s32max CVE-2024-38552 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38552.html CVE-2024-38552 https://bugzilla.suse.com/1226767 SUSE Bug 1226767 In the Linux kernel, the following vulnerability has been resolved: net: fec: remove .ndo_poll_controller to avoid deadlocks There is a deadlock issue found in sungem driver, please refer to the commit ac0a230f719b ("eth: sungem: remove .ndo_poll_controller to avoid deadlocks"). The root cause of the issue is that netpoll is in atomic context and disable_irq() is called by .ndo_poll_controller interface of sungem driver, however, disable_irq() might sleep. After analyzing the implementation of fec_poll_controller(), the fec driver should have the same issue. Due to the fec driver uses NAPI for TX completions, the .ndo_poll_controller is unnecessary to be implemented in the fec driver, so fec_poll_controller() can be safely removed. CVE-2024-38553 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38553.html CVE-2024-38553 https://bugzilla.suse.com/1226744 SUSE Bug 1226744 In the Linux kernel, the following vulnerability has been resolved: wifi: ar5523: enable proper endpoint verification Syzkaller reports [1] hitting a warning about an endpoint in use not having an expected type to it. Fix the issue by checking for the existence of all proper endpoints with their according types intact. Sadly, this patch has not been tested on real hardware. [1] Syzkaller report: ------------[ cut here ]------------ usb 1-1: BOGUS urb xfer, pipe 3 != type 1 WARNING: CPU: 0 PID: 3643 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 ... Call Trace: <TASK> ar5523_cmd+0x41b/0x780 drivers/net/wireless/ath/ar5523/ar5523.c:275 ar5523_cmd_read drivers/net/wireless/ath/ar5523/ar5523.c:302 [inline] ar5523_host_available drivers/net/wireless/ath/ar5523/ar5523.c:1376 [inline] ar5523_probe+0x14b0/0x1d10 drivers/net/wireless/ath/ar5523/ar5523.c:1655 usb_probe_interface+0x30f/0x7f0 drivers/usb/core/driver.c:396 call_driver_probe drivers/base/dd.c:560 [inline] really_probe+0x249/0xb90 drivers/base/dd.c:639 __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:778 driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:808 __device_attach_driver+0x1d4/0x2e0 drivers/base/dd.c:936 bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:427 __device_attach+0x1e4/0x530 drivers/base/dd.c:1008 bus_probe_device+0x1e8/0x2a0 drivers/base/bus.c:487 device_add+0xbd9/0x1e90 drivers/base/core.c:3517 usb_set_configuration+0x101d/0x1900 drivers/usb/core/message.c:2170 usb_generic_driver_probe+0xbe/0x100 drivers/usb/core/generic.c:238 usb_probe_device+0xd8/0x2c0 drivers/usb/core/driver.c:293 call_driver_probe drivers/base/dd.c:560 [inline] really_probe+0x249/0xb90 drivers/base/dd.c:639 __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:778 driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:808 __device_attach_driver+0x1d4/0x2e0 drivers/base/dd.c:936 bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:427 __device_attach+0x1e4/0x530 drivers/base/dd.c:1008 bus_probe_device+0x1e8/0x2a0 drivers/base/bus.c:487 device_add+0xbd9/0x1e90 drivers/base/core.c:3517 usb_new_device.cold+0x685/0x10ad drivers/usb/core/hub.c:2573 hub_port_connect drivers/usb/core/hub.c:5353 [inline] hub_port_connect_change drivers/usb/core/hub.c:5497 [inline] port_event drivers/usb/core/hub.c:5653 [inline] hub_event+0x26cb/0x45d0 drivers/usb/core/hub.c:5735 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289 worker_thread+0x669/0x1090 kernel/workqueue.c:2436 kthread+0x2e8/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 </TASK> CVE-2024-38565 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38565.html CVE-2024-38565 https://bugzilla.suse.com/1226747 SUSE Bug 1226747 In the Linux kernel, the following vulnerability has been resolved: wifi: carl9170: add a proper sanity check for endpoints Syzkaller reports [1] hitting a warning which is caused by presence of a wrong endpoint type at the URB sumbitting stage. While there was a check for a specific 4th endpoint, since it can switch types between bulk and interrupt, other endpoints are trusted implicitly. Similar warning is triggered in a couple of other syzbot issues [2]. Fix the issue by doing a comprehensive check of all endpoints taking into account difference between high- and full-speed configuration. [1] Syzkaller report: ... WARNING: CPU: 0 PID: 4721 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 ... Call Trace: <TASK> carl9170_usb_send_rx_irq_urb+0x273/0x340 drivers/net/wireless/ath/carl9170/usb.c:504 carl9170_usb_init_device drivers/net/wireless/ath/carl9170/usb.c:939 [inline] carl9170_usb_firmware_finish drivers/net/wireless/ath/carl9170/usb.c:999 [inline] carl9170_usb_firmware_step2+0x175/0x240 drivers/net/wireless/ath/carl9170/usb.c:1028 request_firmware_work_func+0x130/0x240 drivers/base/firmware_loader/main.c:1107 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289 worker_thread+0x669/0x1090 kernel/workqueue.c:2436 kthread+0x2e8/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 </TASK> [2] Related syzkaller crashes: CVE-2024-38567 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38567.html CVE-2024-38567 https://bugzilla.suse.com/1226769 SUSE Bug 1226769 In the Linux kernel, the following vulnerability has been resolved: ecryptfs: Fix buffer size for tag 66 packet The 'TAG 66 Packet Format' description is missing the cipher code and checksum fields that are packed into the message packet. As a result, the buffer allocated for the packet is 3 bytes too small and write_tag_66_packet() will write up to 3 bytes past the end of the buffer. Fix this by increasing the size of the allocation so the whole packet will always fit in the buffer. This fixes the below kasan slab-out-of-bounds bug: BUG: KASAN: slab-out-of-bounds in ecryptfs_generate_key_packet_set+0x7d6/0xde0 Write of size 1 at addr ffff88800afbb2a5 by task touch/181 CPU: 0 PID: 181 Comm: touch Not tainted 6.6.13-gnu #1 4c9534092be820851bb687b82d1f92a426598dc6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2/GNU Guix 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x4c/0x70 print_report+0xc5/0x610 ? ecryptfs_generate_key_packet_set+0x7d6/0xde0 ? kasan_complete_mode_report_info+0x44/0x210 ? ecryptfs_generate_key_packet_set+0x7d6/0xde0 kasan_report+0xc2/0x110 ? ecryptfs_generate_key_packet_set+0x7d6/0xde0 __asan_store1+0x62/0x80 ecryptfs_generate_key_packet_set+0x7d6/0xde0 ? __pfx_ecryptfs_generate_key_packet_set+0x10/0x10 ? __alloc_pages+0x2e2/0x540 ? __pfx_ovl_open+0x10/0x10 [overlay 30837f11141636a8e1793533a02e6e2e885dad1d] ? dentry_open+0x8f/0xd0 ecryptfs_write_metadata+0x30a/0x550 ? __pfx_ecryptfs_write_metadata+0x10/0x10 ? ecryptfs_get_lower_file+0x6b/0x190 ecryptfs_initialize_file+0x77/0x150 ecryptfs_create+0x1c2/0x2f0 path_openat+0x17cf/0x1ba0 ? __pfx_path_openat+0x10/0x10 do_filp_open+0x15e/0x290 ? __pfx_do_filp_open+0x10/0x10 ? __kasan_check_write+0x18/0x30 ? _raw_spin_lock+0x86/0xf0 ? __pfx__raw_spin_lock+0x10/0x10 ? __kasan_check_write+0x18/0x30 ? alloc_fd+0xf4/0x330 do_sys_openat2+0x122/0x160 ? __pfx_do_sys_openat2+0x10/0x10 __x64_sys_openat+0xef/0x170 ? __pfx___x64_sys_openat+0x10/0x10 do_syscall_64+0x60/0xd0 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 RIP: 0033:0x7f00a703fd67 Code: 25 00 00 41 00 3d 00 00 41 00 74 37 64 8b 04 25 18 00 00 00 85 c0 75 5b 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 85 00 00 00 48 83 c4 68 5d 41 5c c3 0f 1f RSP: 002b:00007ffc088e30b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007ffc088e3368 RCX: 00007f00a703fd67 RDX: 0000000000000941 RSI: 00007ffc088e48d7 RDI: 00000000ffffff9c RBP: 00007ffc088e48d7 R08: 0000000000000001 R09: 0000000000000000 R10: 00000000000001b6 R11: 0000000000000246 R12: 0000000000000941 R13: 0000000000000000 R14: 00007ffc088e48d7 R15: 00007f00a7180040 </TASK> Allocated by task 181: kasan_save_stack+0x2f/0x60 kasan_set_track+0x29/0x40 kasan_save_alloc_info+0x25/0x40 __kasan_kmalloc+0xc5/0xd0 __kmalloc+0x66/0x160 ecryptfs_generate_key_packet_set+0x6d2/0xde0 ecryptfs_write_metadata+0x30a/0x550 ecryptfs_initialize_file+0x77/0x150 ecryptfs_create+0x1c2/0x2f0 path_openat+0x17cf/0x1ba0 do_filp_open+0x15e/0x290 do_sys_openat2+0x122/0x160 __x64_sys_openat+0xef/0x170 do_syscall_64+0x60/0xd0 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 CVE-2024-38578 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38578.html CVE-2024-38578 https://bugzilla.suse.com/1226634 SUSE Bug 1226634 In the Linux kernel, the following vulnerability has been resolved: crypto: bcm - Fix pointer arithmetic In spu2_dump_omd() value of ptr is increased by ciph_key_len instead of hash_iv_len which could lead to going beyond the buffer boundaries. Fix this bug by changing ciph_key_len to hash_iv_len. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2024-38579 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38579.html CVE-2024-38579 https://bugzilla.suse.com/1226637 SUSE Bug 1226637 In the Linux kernel, the following vulnerability has been resolved: epoll: be better about file lifetimes epoll can call out to vfs_poll() with a file pointer that may race with the last 'fput()'. That would make f_count go down to zero, and while the ep->mtx locking means that the resulting file pointer tear-down will be blocked until the poll returns, it means that f_count is already dead, and any use of it won't actually get a reference to the file any more: it's dead regardless. Make sure we have a valid ref on the file pointer before we call down to vfs_poll() from the epoll routines. CVE-2024-38580 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38580.html CVE-2024-38580 https://bugzilla.suse.com/1226610 SUSE Bug 1226610 In the Linux kernel, the following vulnerability has been resolved: eth: sungem: remove .ndo_poll_controller to avoid deadlocks Erhard reports netpoll warnings from sungem: netpoll_send_skb_on_dev(): eth0 enabled interrupts in poll (gem_start_xmit+0x0/0x398) WARNING: CPU: 1 PID: 1 at net/core/netpoll.c:370 netpoll_send_skb+0x1fc/0x20c gem_poll_controller() disables interrupts, which may sleep. We can't sleep in netpoll, it has interrupts disabled completely. Strangely, gem_poll_controller() doesn't even poll the completions, and instead acts as if an interrupt has fired so it just schedules NAPI and exits. None of this has been necessary for years, since netpoll invokes NAPI directly. CVE-2024-38597 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38597.html CVE-2024-38597 https://bugzilla.suse.com/1226749 SUSE Bug 1226749 In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix a race between readers and resize checks The reader code in rb_get_reader_page() swaps a new reader page into the ring buffer by doing cmpxchg on old->list.prev->next to point it to the new page. Following that, if the operation is successful, old->list.next->prev gets updated too. This means the underlying doubly-linked list is temporarily inconsistent, page->prev->next or page->next->prev might not be equal back to page for some page in the ring buffer. The resize operation in ring_buffer_resize() can be invoked in parallel. It calls rb_check_pages() which can detect the described inconsistency and stop further tracing: [ 190.271762] ------------[ cut here ]------------ [ 190.271771] WARNING: CPU: 1 PID: 6186 at kernel/trace/ring_buffer.c:1467 rb_check_pages.isra.0+0x6a/0xa0 [ 190.271789] Modules linked in: [...] [ 190.271991] Unloaded tainted modules: intel_uncore_frequency(E):1 skx_edac(E):1 [ 190.272002] CPU: 1 PID: 6186 Comm: cmd.sh Kdump: loaded Tainted: G E 6.9.0-rc6-default #5 158d3e1e6d0b091c34c3b96bfd99a1c58306d79f [ 190.272011] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552c-rebuilt.opensuse.org 04/01/2014 [ 190.272015] RIP: 0010:rb_check_pages.isra.0+0x6a/0xa0 [ 190.272023] Code: [...] [ 190.272028] RSP: 0018:ffff9c37463abb70 EFLAGS: 00010206 [ 190.272034] RAX: ffff8eba04b6cb80 RBX: 0000000000000007 RCX: ffff8eba01f13d80 [ 190.272038] RDX: ffff8eba01f130c0 RSI: ffff8eba04b6cd00 RDI: ffff8eba0004c700 [ 190.272042] RBP: ffff8eba0004c700 R08: 0000000000010002 R09: 0000000000000000 [ 190.272045] R10: 00000000ffff7f52 R11: ffff8eba7f600000 R12: ffff8eba0004c720 [ 190.272049] R13: ffff8eba00223a00 R14: 0000000000000008 R15: ffff8eba067a8000 [ 190.272053] FS: 00007f1bd64752c0(0000) GS:ffff8eba7f680000(0000) knlGS:0000000000000000 [ 190.272057] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 190.272061] CR2: 00007f1bd6662590 CR3: 000000010291e001 CR4: 0000000000370ef0 [ 190.272070] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 190.272073] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 190.272077] Call Trace: [ 190.272098] <TASK> [ 190.272189] ring_buffer_resize+0x2ab/0x460 [ 190.272199] __tracing_resize_ring_buffer.part.0+0x23/0xa0 [ 190.272206] tracing_resize_ring_buffer+0x65/0x90 [ 190.272216] tracing_entries_write+0x74/0xc0 [ 190.272225] vfs_write+0xf5/0x420 [ 190.272248] ksys_write+0x67/0xe0 [ 190.272256] do_syscall_64+0x82/0x170 [ 190.272363] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 190.272373] RIP: 0033:0x7f1bd657d263 [ 190.272381] Code: [...] [ 190.272385] RSP: 002b:00007ffe72b643f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 190.272391] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f1bd657d263 [ 190.272395] RDX: 0000000000000002 RSI: 0000555a6eb538e0 RDI: 0000000000000001 [ 190.272398] RBP: 0000555a6eb538e0 R08: 000000000000000a R09: 0000000000000000 [ 190.272401] R10: 0000555a6eb55190 R11: 0000000000000246 R12: 00007f1bd6662500 [ 190.272404] R13: 0000000000000002 R14: 00007f1bd6667c00 R15: 0000000000000002 [ 190.272412] </TASK> [ 190.272414] ---[ end trace 0000000000000000 ]--- Note that ring_buffer_resize() calls rb_check_pages() only if the parent trace_buffer has recording disabled. Recent commit d78ab792705c ("tracing: Stop current tracer when resizing buffer") causes that it is now always the case which makes it more likely to experience this issue. The window to hit this race is nonetheless very small. To help reproducing it, one can add a delay loop in rb_get_reader_page(): ret = rb_head_page_replace(reader, cpu_buffer->reader_page); if (!ret) goto spin; for (unsigned i = 0; i < 1U << 26; i++) /* inserted delay loop */ __asm__ __volatile__ ("" : : : "memory"); rb_list_head(reader->list.next)->prev = &cpu_buffer->reader_page->list; .. ---truncated--- CVE-2024-38601 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38601.html CVE-2024-38601 https://bugzilla.suse.com/1226876 SUSE Bug 1226876 In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix netif state handling mlx5e_suspend cleans resources only if netif_device_present() returns true. However, mlx5e_resume changes the state of netif, via mlx5e_nic_enable, only if reg_state == NETREG_REGISTERED. In the below case, the above leads to NULL-ptr Oops[1] and memory leaks: mlx5e_probe _mlx5e_resume mlx5e_attach_netdev mlx5e_nic_enable <-- netdev not reg, not calling netif_device_attach() register_netdev <-- failed for some reason. ERROR_FLOW: _mlx5e_suspend <-- netif_device_present return false, resources aren't freed :( Hence, clean resources in this case as well. [1] BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0010 [#1] SMP CPU: 2 PID: 9345 Comm: test-ovs-ct-gen Not tainted 6.5.0_for_upstream_min_debug_2023_09_05_16_01 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:0x0 Code: Unable to access opcode bytes at0xffffffffffffffd6. RSP: 0018:ffff888178aaf758 EFLAGS: 00010246 Call Trace: <TASK> ? __die+0x20/0x60 ? page_fault_oops+0x14c/0x3c0 ? exc_page_fault+0x75/0x140 ? asm_exc_page_fault+0x22/0x30 notifier_call_chain+0x35/0xb0 blocking_notifier_call_chain+0x3d/0x60 mlx5_blocking_notifier_call_chain+0x22/0x30 [mlx5_core] mlx5_core_uplink_netdev_event_replay+0x3e/0x60 [mlx5_core] mlx5_mdev_netdev_track+0x53/0x60 [mlx5_ib] mlx5_ib_roce_init+0xc3/0x340 [mlx5_ib] __mlx5_ib_add+0x34/0xd0 [mlx5_ib] mlx5r_probe+0xe1/0x210 [mlx5_ib] ? auxiliary_match_id+0x6a/0x90 auxiliary_bus_probe+0x38/0x80 ? driver_sysfs_add+0x51/0x80 really_probe+0xc9/0x3e0 ? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 bus_probe_device+0x86/0xa0 device_add+0x637/0x840 __auxiliary_device_add+0x3b/0xa0 add_adev+0xc9/0x140 [mlx5_core] mlx5_rescan_drivers_locked+0x22a/0x310 [mlx5_core] mlx5_register_device+0x53/0xa0 [mlx5_core] mlx5_init_one_devl_locked+0x5c4/0x9c0 [mlx5_core] mlx5_init_one+0x3b/0x60 [mlx5_core] probe_one+0x44c/0x730 [mlx5_core] local_pci_probe+0x3e/0x90 pci_device_probe+0xbf/0x210 ? kernfs_create_link+0x5d/0xa0 ? sysfs_do_create_link_sd+0x60/0xc0 really_probe+0xc9/0x3e0 ? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 pci_bus_add_device+0x54/0x80 pci_iov_add_virtfn+0x2e6/0x320 sriov_enable+0x208/0x420 mlx5_core_sriov_configure+0x9e/0x200 [mlx5_core] sriov_numvfs_store+0xae/0x1a0 kernfs_fop_write_iter+0x10c/0x1a0 vfs_write+0x291/0x3c0 ksys_write+0x5f/0xe0 do_syscall_64+0x3d/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 CR2: 0000000000000000 ---[ end trace 0000000000000000 ]--- CVE-2024-38608 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38608.html CVE-2024-38608 https://bugzilla.suse.com/1226746 SUSE Bug 1226746 In the Linux kernel, the following vulnerability has been resolved: ALSA: timer: Set lower bound of start tick time Currently ALSA timer doesn't have the lower limit of the start tick time, and it allows a very small size, e.g. 1 tick with 1ns resolution for hrtimer. Such a situation may lead to an unexpected RCU stall, where the callback repeatedly queuing the expire update, as reported by fuzzer. This patch introduces a sanity check of the timer start tick time, so that the system returns an error when a too small start size is set. As of this patch, the lower limit is hard-coded to 100us, which is small enough but can still work somehow. CVE-2024-38618 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38618.html CVE-2024-38618 https://bugzilla.suse.com/1226754 SUSE Bug 1226754 In the Linux kernel, the following vulnerability has been resolved: media: stk1160: fix bounds checking in stk1160_copy_video() The subtract in this condition is reversed. The ->length is the length of the buffer. The ->bytesused is how many bytes we have copied thus far. When the condition is reversed that means the result of the subtraction is always negative but since it's unsigned then the result is a very high positive value. That means the overflow check is never true. Additionally, the ->bytesused doesn't actually work for this purpose because we're not writing to "buf->mem + buf->bytesused". Instead, the math to calculate the destination where we are writing is a bit involved. You calculate the number of full lines already written, multiply by two, skip a line if necessary so that we start on an odd numbered line, and add the offset into the line. To fix this buffer overflow, just take the actual destination where we are writing, if the offset is already out of bounds print an error and return. Otherwise, write up to buf->length bytes. CVE-2024-38621 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38621.html CVE-2024-38621 https://bugzilla.suse.com/1226895 SUSE Bug 1226895 In the Linux kernel, the following vulnerability has been resolved: stm class: Fix a double free in stm_register_device() The put_device(&stm->dev) call will trigger stm_device_release() which frees "stm" so the vfree(stm) on the next line is a double free. CVE-2024-38627 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38627.html CVE-2024-38627 https://bugzilla.suse.com/1226857 SUSE Bug 1226857 In the Linux kernel, the following vulnerability has been resolved: enic: Validate length of nl attributes in enic_set_vf_port enic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE is of length PORT_PROFILE_MAX and that the nl attributes IFLA_PORT_INSTANCE_UUID, IFLA_PORT_HOST_UUID are of length PORT_UUID_MAX. These attributes are validated (in the function do_setlink in rtnetlink.c) using the nla_policy ifla_port_policy. The policy defines IFLA_PORT_PROFILE as NLA_STRING, IFLA_PORT_INSTANCE_UUID as NLA_BINARY and IFLA_PORT_HOST_UUID as NLA_STRING. That means that the length validation using the policy is for the max size of the attributes and not on exact size so the length of these attributes might be less than the sizes that enic_set_vf_port expects. This might cause an out of bands read access in the memcpys of the data of these attributes in enic_set_vf_port. CVE-2024-38659 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38659.html CVE-2024-38659 https://bugzilla.suse.com/1226883 SUSE Bug 1226883 In the Linux kernel, the following vulnerability has been resolved: s390/ap: Fix crash in AP internal function modify_bitmap() A system crash like this Failing address: 200000cb7df6f000 TEID: 200000cb7df6f403 Fault in home space mode while using kernel ASCE. AS:00000002d71bc007 R3:00000003fe5b8007 S:000000011a446000 P:000000015660c13d Oops: 0038 ilc:3 [#1] PREEMPT SMP Modules linked in: mlx5_ib ... CPU: 8 PID: 7556 Comm: bash Not tainted 6.9.0-rc7 #8 Hardware name: IBM 3931 A01 704 (LPAR) Krnl PSW : 0704e00180000000 0000014b75e7b606 (ap_parse_bitmap_str+0x10e/0x1f8) R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 Krnl GPRS: 0000000000000001 ffffffffffffffc0 0000000000000001 00000048f96b75d3 000000cb00000100 ffffffffffffffff ffffffffffffffff 000000cb7df6fce0 000000cb7df6fce0 00000000ffffffff 000000000000002b 00000048ffffffff 000003ff9b2dbc80 200000cb7df6fcd8 0000014bffffffc0 000000cb7df6fbc8 Krnl Code: 0000014b75e7b5fc: a7840047 brc 8,0000014b75e7b68a 0000014b75e7b600: 18b2 lr %r11,%r2 #0000014b75e7b602: a7f4000a brc 15,0000014b75e7b616 >0000014b75e7b606: eb22d00000e6 laog %r2,%r2,0(%r13) 0000014b75e7b60c: a7680001 lhi %r6,1 0000014b75e7b610: 187b lr %r7,%r11 0000014b75e7b612: 84960021 brxh %r9,%r6,0000014b75e7b654 0000014b75e7b616: 18e9 lr %r14,%r9 Call Trace: [<0000014b75e7b606>] ap_parse_bitmap_str+0x10e/0x1f8 ([<0000014b75e7b5dc>] ap_parse_bitmap_str+0xe4/0x1f8) [<0000014b75e7b758>] apmask_store+0x68/0x140 [<0000014b75679196>] kernfs_fop_write_iter+0x14e/0x1e8 [<0000014b75598524>] vfs_write+0x1b4/0x448 [<0000014b7559894c>] ksys_write+0x74/0x100 [<0000014b7618a440>] __do_syscall+0x268/0x328 [<0000014b761a3558>] system_call+0x70/0x98 INFO: lockdep is turned off. Last Breaking-Event-Address: [<0000014b75e7b636>] ap_parse_bitmap_str+0x13e/0x1f8 Kernel panic - not syncing: Fatal exception: panic_on_oops occured when /sys/bus/ap/a[pq]mask was updated with a relative mask value (like +0x10-0x12,+60,-90) with one of the numeric values exceeding INT_MAX. The fix is simple: use unsigned long values for the internal variables. The correct checks are already in place in the function but a simple int for the internal variables was used with the possibility to overflow. CVE-2024-38661 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38661.html CVE-2024-38661 https://bugzilla.suse.com/1226996 SUSE Bug 1226996 In the Linux kernel, the following vulnerability has been resolved: dma-buf/sw-sync: don't enable IRQ from sync_print_obj() Since commit a6aa8fca4d79 ("dma-buf/sw-sync: Reduce irqsave/irqrestore from known context") by error replaced spin_unlock_irqrestore() with spin_unlock_irq() for both sync_debugfs_show() and sync_print_obj() despite sync_print_obj() is called from sync_debugfs_show(), lockdep complains inconsistent lock state warning. Use plain spin_{lock,unlock}() for sync_print_obj(), for sync_debugfs_show() is already using spin_{lock,unlock}_irq(). CVE-2024-38780 SUSE Linux Enterprise Real Time 12 SP5:cluster-md-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:dlm-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:gfs2-kmp-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-devel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-base-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-rt_debug-devel-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-source-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:kernel-syms-rt-4.12.14-10.191.1 SUSE Linux Enterprise Real Time 12 SP5:ocfs2-kmp-rt-4.12.14-10.191.1 moderate 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/2024/suse-su-20242381-1/ https://www.suse.com/security/cve/CVE-2024-38780.html CVE-2024-38780 https://bugzilla.suse.com/1226886 SUSE Bug 1226886