Security update for the Linux Kernel SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2025:4141-1 Final 1 1 2025-11-19T14:06:18Z current 2025-11-19T14:06:18Z 2025-11-19T14:06:18Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for the Linux Kernel The SUSE Linux Enterprise 15 SP7 RT kernel was updated to fix various security issues The following security issues were fixed: - CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling (bsc#1244939). - CVE-2025-38539: trace/fgraph: Fix the warning caused by missing unregister notifier (bsc#1248211). - CVE-2025-38552: mptcp: plug races between subflow fail and subflow creation (bsc#1248230). - CVE-2025-38653: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al (bsc#1248630). - CVE-2025-38699: scsi: bfa: Double-free fix (bsc#1249224). - CVE-2025-38700: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated (bsc#1249182). - CVE-2025-38718: sctp: linearize cloned gso packets in sctp_rcv (bsc#1249161). - CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324). - CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288). - CVE-2025-39673: ppp: fix race conditions in ppp_fill_forward_path (bsc#1249320). - CVE-2025-39676: scsi: qla4xxx: Prevent a potential error pointer dereference (bsc#1249302). - CVE-2025-39683: tracing: Limit access to parser->buffer when trace_get_user failed (bsc#1249286). - CVE-2025-39697: nfs: remove dead code for the old swap over NFS implementation (bsc#1249319). - CVE-2025-39702: ipv6: sr: Fix MAC comparison to be constant-time (bsc#1249317). - CVE-2025-39756: fs: Prevent file descriptor table allocations exceeding INT_MAX (bsc#1249512). - CVE-2025-39794: ARM: tegra: Use I/O memcpy to write to IRAM (bsc#1249595). - CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975). - CVE-2025-39812: sctp: initialize more fields in sctp_v6_from_sk() (bsc#1250202). - CVE-2025-39813: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump (bsc#1250032). - CVE-2025-39828: atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control() (bsc#1250205). - CVE-2025-39832: net/mlx5: Add sync reset drop mode support (bsc#1249901). - CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292). - CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276). - CVE-2025-39851: vxlan: Fix NPD when refreshing an FDB entry with a nexthop object (bsc#1250296). - CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275). - CVE-2025-39854: ice: fix NULL access of tx->in_use in ice_ll_ts_intr (bsc#1250297). - CVE-2025-39866: fs: writeback: fix use-after-free in __mark_inode_dirty() (bsc#1250455). - CVE-2025-39876: net: fec: Fix possible NPD in fec_enet_phy_reset_after_clk_enable() (bsc#1250400). - CVE-2025-39881: kernfs: Fix UAF in polling when open file is released (bsc#1250379). - CVE-2025-39895: sched: Fix sched_numa_find_nth_cpu() if mask offline (bsc#1250721). - CVE-2025-39900: net_sched: gen_estimator: fix est_timer() vs CONFIG_PREEMPT_RT=y (bsc#1250758). - CVE-2025-39902: mm/slub: avoid accessing metadata when pointer is invalid in object_err() (bsc#1250702). - CVE-2025-39911: i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path (bsc#1250704). - CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230). - CVE-2025-39946: tls: make sure to abort the stream if headers are bogus (bsc#1251114). - CVE-2025-39947: net/mlx5e: Harden uplink netdev access against device unbind (bsc#1251232). - CVE-2025-39948: ice: fix Rx page leak on multi-buffer frames (bsc#1251233). - CVE-2025-39949: qed: Don't collect too many protection override GRC elements (bsc#1251177). - CVE-2025-39955: tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect() (bsc#1251804). - CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047). - CVE-2025-39969: i40e: fix validation of VF state in get resources (bsc#1252044). - CVE-2025-39970: i40e: fix input validation logic for action_meta (bsc#1252051). - CVE-2025-39971: i40e: fix idx validation in config queues msg (bsc#1252052). - CVE-2025-39972: i40e: fix idx validation in i40e_validate_queue_map (bsc#1252039). - CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035). - CVE-2025-39978: octeontx2-pf: Fix potential use after free in otx2_tc_add_flow() (bsc#1252069). - CVE-2025-39984: net: tun: Update napi->skb after XDP process (bsc#1252081). - CVE-2025-40000: wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait() (bsc#1252062). - CVE-2025-40005: spi: cadence-quadspi: Implement refcount to handle unbind during busy (bsc#1252349). - CVE-2025-40012: net/smc: fix warning in smc_rx_splice() when calling get_page() (bsc#1252330). - CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688). - CVE-2025-40051: vhost: vringh: Modify the return value check (bsc#1252858). - CVE-2025-40056: vhost: vringh: Fix copy_to_iter return value check (bsc#1252826). - CVE-2025-40060: coresight: trbe: Return NULL pointer for allocation failures (bsc#1252848). - CVE-2025-40078: bpf: Explicitly check accesses to bpf_sock_addr (bsc#1252789). - CVE-2025-40100: btrfs: do not assert we found block group item when creating free space tree (bsc#1252918). The following non security issues were fixed: - ACPI/processor_idle: Add FFH state handling (jsc#PED-13815). - ACPI/processor_idle: Export acpi_processor_ffh_play_dead() (jsc#PED-13815). - ACPI: battery: Add synchronization between interface updates (git-fixes). - ACPI: processor: Rescan 'dead' SMT siblings during initialization (jsc#PED-13815). - KVM: PPC: Fix misleading interrupts comment in kvmppc_prepare_to_enter() (bsc#1215199). - KVM: x86: Plumb in the vCPU to kvm_x86_ops.hwapic_isr_update() (git-fixes). - KVM: x86: Process 'guest stopped request' once per guest time update (git-fixes). - PM: hibernate: Add pm_hibernation_mode_is_suspend() (bsc#1243112). - PM: hibernate: Add stub for pm_hibernate_is_recovering() (bsc#1243112). - PM: hibernate: Fix pm_hibernation_mode_is_suspend() build breakage (bsc#1243112). - PM: hibernate: add new api pm_hibernate_is_recovering() (bsc#1243112). - Reapply 'x86/smp: Eliminate mwait_play_dead_cpuid_hint()' (jsc#PED-13815). - bpf: Allow helper bpf_get_[ns_]current_pid_tgid() for all prog types (bsc#1252364). - cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() (stable-fixes git-fixes). - cpuidle: Do not return from cpuidle_play_dead() on callback failures (jsc#PED-13815). - dpll: Make ZL3073X invisible (bsc#1252253). - dpll: zl3073x: Add firmware loading functionality (bsc#1252253). - dpll: zl3073x: Add functions to access hardware registers (bsc#1252253). - dpll: zl3073x: Add low-level flash functions (bsc#1252253). - dpll: zl3073x: Add support to get fractional frequency offset (bsc#1252253). - dpll: zl3073x: Add support to get phase offset on connected input pin (bsc#1252253). - dpll: zl3073x: Add support to get/set esync on pins (bsc#1252253). - dpll: zl3073x: Fix build failure (bsc#1252253). - dpll: zl3073x: Fix double free in zl3073x_devlink_flash_update() (bsc#1252253). - dpll: zl3073x: Handle missing or corrupted flash configuration (bsc#1252253). - dpll: zl3073x: Implement devlink flash callback (bsc#1252253). - dpll: zl3073x: Increase maximum size of flash utility (bsc#1252253). - dpll: zl3073x: Refactor DPLL initialization (bsc#1252253). - dpll: zl3073x: ZL3073X_I2C and ZL3073X_SPI should depend on NET (bsc#1252253). - drm/amd : Update MES API header file for v11 & v12 (stable-fixes). - drm/amd/amdgpu: Implement MES suspend/resume gang functionality for v12 (bsc#1243112). - drm/amd/display: Add NULL check for stream before dereference in 'dm_vupdate_high_irq' (bsc#1243112). - drm/amd/display: Enable Dynamic DTBCLK Switch (bsc#1243112). - drm/amd/display: Fix vupdate_offload_work doc (bsc#1243112). - drm/amd/display: fix dmub access race condition (bsc#1243112). - drm/amd/display: more liberal vmin/vmax update for freesync (bsc#1243112). - drm/amd/include : MES v11 and v12 API header update (stable-fixes). - drm/amd/include : Update MES v12 API for fence update (stable-fixes). - drm/amd/pm: fix smu table id bound check issue in smu_cmn_update_table() (git-fixes). - drm/amd: Avoid evicting resources at S5 (bsc#1243112). - drm/amd: Check whether secure display TA loaded successfully (bsc#1243112). - drm/amd: Fix hybrid sleep (bsc#1243112). - drm/amd: Only restore cached manual clock settings in restore if OD enabled (bsc#1243112). - drm/amd: Restore cached manual clock settings during resume (bsc#1243112). - drm/amdgpu/mes11: implement detect and reset callback (bsc#1243112). - drm/amdgpu/mes12: implement detect and reset callback (bsc#1243112). - drm/amdgpu/mes: add front end for detect and reset hung queue (bsc#1243112). - drm/amdgpu/vpe: cancel delayed work in hw_fini (bsc#1243112). - drm/amdgpu: Avoid rma causes GPU duplicate reset (bsc#1243112). - drm/amdgpu: Fix for GPU reset being blocked by KIQ I/O (bsc#1243112). - drm/amdgpu: Report individual reset error (bsc#1243112). - drm/amdgpu: do not resume device in thaw for normal hibernation (bsc#1243112). - drm/amdgpu: fix link error for !PM_SLEEP (bsc#1243112). - drm/amdkfd: Fix mmap write lock not release (bsc#1243112). - drm/xe/guc: Prepare GuC register list and update ADS size for error capture (stable-fixes). - ext4: fix checks for orphan inodes (bsc#1250119). - hfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat() (git-fixes). - intel_idle: Provide the default enter_dead() handler (jsc#PED-13815). - intel_idle: Rescan 'dead' SMT siblings during initialization (jsc#PED-13815). - intel_idle: Use subsys_initcall_sync() for initialization (jsc#PED-13815). - ixgbe: handle IXGBE_VF_FEATURES_NEGOTIATE mbox cmd (bsc#1247222). - ixgbe: handle IXGBE_VF_GET_PF_LINK_STATE mailbox operation (bsc#1247222). - ixgbevf: fix getting link speed data for E610 devices (bsc#1247222). - ixgbevf: fix mailbox API compatibility by negotiating supported features (bsc#1247222). - kdb: Replace deprecated strcpy() with memmove() in vkdb_printf() (bsc#1252939). - module: Prevent silent truncation of module name in delete_module(2) (git-fixes). - net: mana: Use page pool fragments for RX buffers instead of full pages to improve memory efficiency (bsc#1248754). - netfilter: nft_objref: validate objref and objrefmap expressions (bsc#1250237). - nvme-auth: update bi_directional flag (git-fixes bsc#1249735). - nvme-auth: update sc_c in host response (git-fixes bsc#1249397). - nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500). - nvme-tcp: send only permitted commands for secure concat (git-fixes bsc#1247683). - nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500). - nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500). - nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500). - perf/x86/intel: Allow to update user space GPRs from PEBS records (git-fixes). - perf/x86/intel: Fix crash in icl_update_topdown_event() (git-fixes). - phy: cadence: cdns-dphy: Update calibration wait time for startup state machine (git-fixes). - platform/x86/amd/pmc: Add 1Ah family series to STB support list (bsc#1243112). - platform/x86/amd/pmc: Add MECHREVO Yilong15Pro to spurious_8042 list (bsc#1243112). - platform/x86/amd/pmc: Add Stellaris Slim Gen6 AMD to spurious 8042 quirks list (bsc#1243112). - platform/x86/amd/pmc: Add VPE information for AMDI000A platform (bsc#1243112). - platform/x86/amd/pmc: Add idlemask support for 1Ah family (bsc#1243112). - platform/x86/amd/pmc: Extend support for PMC features on new AMD platform (bsc#1243112). - platform/x86/amd/pmc: Fix SMU command submission path on new AMD platform (bsc#1243112). - platform/x86/amd/pmc: Modify SMU message port for latest AMD platform (bsc#1243112). - platform/x86/amd/pmc: Notify user when platform does not support s0ix transition (bsc#1243112). - platform/x86/amd/pmc: Remove unnecessary line breaks (bsc#1243112). - platform/x86/amd/pmc: Send OS_HINT command for AMDI000A platform (bsc#1243112). - platform/x86/amd/pmc: Send OS_HINT command for new AMD platform (bsc#1243112). - platform/x86/amd/pmc: Update IP information structure for newer SoCs (bsc#1243112). - platform/x86/amd/pmc: Use ARRAY_SIZE() to fill num_ips information (bsc#1243112). - platform/x86/amd/pmc: call amd_pmc_get_ip_info() during driver probe (bsc#1243112). - platform/x86/amd: pmc: Add new ACPI ID AMDI000B (bsc#1243112). - platform/x86/amd: pmc: Drop SMU F/W match for Cezanne (bsc#1243112). - platform/x86/amd: pmc: Use guard(mutex) (bsc#1243112). - powerpc/boot: Fix build with gcc 15 (bsc#1215199). - powerpc/fadump: skip parameter area allocation when fadump is disabled (jsc#PED-9891 git-fixes). - powerpc/kvm: Fix ifdef to remove build warning (bsc#1215199). - powerpc/powernv/pci: Fix underflow and leak issue (bsc#1215199). - powerpc/pseries/msi: Fix potential underflow and leak issue (bsc#1215199). - powerpc: floppy: Add missing checks after DMA map (bsc#1215199). - proc: fix missing pde_set_flags() for net proc files (bsc#1248630) - proc: fix type confusion in pde_set_flags() (bsc#1248630) - sched/idle: Conditionally handle tick broadcast in default_idle_call() (bsc#1248517). - scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519). - scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519). - scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519). - scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519). - scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519). - scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519). - scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519). - scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519). - scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519). - scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519). - scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519). - scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519). - scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519). - scsi: lpfc: Use int type to store negative error codes (bsc#1250519). - scsi: lpfc: use min() to improve code (bsc#1250519). - serial: sc16is7xx: rename Kconfig CONFIG_SERIAL_SC16IS7XX_CORE (bsc#1252469) - skmsg: Return copied bytes in sk_msg_memcopy_from_iter (bsc#1250650). - smb: client: fix crypto buffers in non-linear memory (bsc#1250491, bsc#1239206). - smb: client: fix potential cfid UAF in smb2_query_info_compound (bsc#1248886). - tcp_bpf: Fix copied value in tcp_bpf_sendmsg (bsc#1250650). - tracing: Remove unneeded goto out logic (bsc#1249286). - x86/idle: Sanitize X86_BUG_AMD_E400 handling (bsc#1248517). - x86/resctrl: Fix miscount of bandwidth event when reactivating previously unavailable RMID (bsc#1252734). - x86/resctrl: Refactor resctrl_arch_rmid_read() (bsc#1252734). - x86/smp: Allow calling mwait_play_dead with an arbitrary hint (jsc#PED-13815). - x86/smp: Fix mwait_play_dead() and acpi_processor_ffh_play_dead() noreturn behavior (jsc#PED-13815). - x86/smp: PM/hibernate: Split arch_resume_nosmt() (jsc#PED-13815). - x86/topology: Implement topology_is_core_online() to address SMT regression (jsc#PED-13815). The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-2025-4141,SUSE-SLE-Module-Live-Patching-15-SP7-2025-4141,SUSE-SLE-Module-RT-15-SP7-2025-4141 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ Link for SUSE-SU-2025:4141-1 https://lists.suse.com/pipermail/sle-security-updates/2025-November/023304.html E-Mail link for SUSE-SU-2025:4141-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1012628 SUSE Bug 1012628 https://bugzilla.suse.com/1194869 SUSE Bug 1194869 https://bugzilla.suse.com/1213061 SUSE Bug 1213061 https://bugzilla.suse.com/1213666 SUSE Bug 1213666 https://bugzilla.suse.com/1214073 SUSE Bug 1214073 https://bugzilla.suse.com/1214928 SUSE Bug 1214928 https://bugzilla.suse.com/1214953 SUSE Bug 1214953 https://bugzilla.suse.com/1214954 SUSE Bug 1214954 https://bugzilla.suse.com/1215143 SUSE Bug 1215143 https://bugzilla.suse.com/1215150 SUSE Bug 1215150 https://bugzilla.suse.com/1215199 SUSE Bug 1215199 https://bugzilla.suse.com/1215696 SUSE Bug 1215696 https://bugzilla.suse.com/1216396 SUSE Bug 1216396 https://bugzilla.suse.com/1216436 SUSE Bug 1216436 https://bugzilla.suse.com/1216976 SUSE Bug 1216976 https://bugzilla.suse.com/1220186 SUSE Bug 1220186 https://bugzilla.suse.com/1220419 SUSE Bug 1220419 https://bugzilla.suse.com/1229165 SUSE Bug 1229165 https://bugzilla.suse.com/1239206 SUSE Bug 1239206 https://bugzilla.suse.com/1243100 SUSE Bug 1243100 https://bugzilla.suse.com/1243112 SUSE Bug 1243112 https://bugzilla.suse.com/1244939 SUSE Bug 1244939 https://bugzilla.suse.com/1245193 SUSE Bug 1245193 https://bugzilla.suse.com/1245260 SUSE Bug 1245260 https://bugzilla.suse.com/1246125 SUSE Bug 1246125 https://bugzilla.suse.com/1247118 SUSE Bug 1247118 https://bugzilla.suse.com/1247222 SUSE Bug 1247222 https://bugzilla.suse.com/1247500 SUSE Bug 1247500 https://bugzilla.suse.com/1247683 SUSE Bug 1247683 https://bugzilla.suse.com/1248111 SUSE Bug 1248111 https://bugzilla.suse.com/1248211 SUSE Bug 1248211 https://bugzilla.suse.com/1248230 SUSE Bug 1248230 https://bugzilla.suse.com/1248517 SUSE Bug 1248517 https://bugzilla.suse.com/1248630 SUSE Bug 1248630 https://bugzilla.suse.com/1248735 SUSE Bug 1248735 https://bugzilla.suse.com/1248754 SUSE Bug 1248754 https://bugzilla.suse.com/1248847 SUSE Bug 1248847 https://bugzilla.suse.com/1248886 SUSE Bug 1248886 https://bugzilla.suse.com/1249123 SUSE Bug 1249123 https://bugzilla.suse.com/1249159 SUSE Bug 1249159 https://bugzilla.suse.com/1249161 SUSE Bug 1249161 https://bugzilla.suse.com/1249164 SUSE Bug 1249164 https://bugzilla.suse.com/1249166 SUSE Bug 1249166 https://bugzilla.suse.com/1249169 SUSE Bug 1249169 https://bugzilla.suse.com/1249170 SUSE Bug 1249170 https://bugzilla.suse.com/1249177 SUSE Bug 1249177 https://bugzilla.suse.com/1249182 SUSE Bug 1249182 https://bugzilla.suse.com/1249190 SUSE Bug 1249190 https://bugzilla.suse.com/1249194 SUSE Bug 1249194 https://bugzilla.suse.com/1249195 SUSE Bug 1249195 https://bugzilla.suse.com/1249196 SUSE Bug 1249196 https://bugzilla.suse.com/1249200 SUSE Bug 1249200 https://bugzilla.suse.com/1249203 SUSE Bug 1249203 https://bugzilla.suse.com/1249204 SUSE Bug 1249204 https://bugzilla.suse.com/1249215 SUSE Bug 1249215 https://bugzilla.suse.com/1249220 SUSE Bug 1249220 https://bugzilla.suse.com/1249221 SUSE Bug 1249221 https://bugzilla.suse.com/1249224 SUSE Bug 1249224 https://bugzilla.suse.com/1249254 SUSE Bug 1249254 https://bugzilla.suse.com/1249255 SUSE Bug 1249255 https://bugzilla.suse.com/1249257 SUSE Bug 1249257 https://bugzilla.suse.com/1249260 SUSE Bug 1249260 https://bugzilla.suse.com/1249263 SUSE Bug 1249263 https://bugzilla.suse.com/1249265 SUSE Bug 1249265 https://bugzilla.suse.com/1249266 SUSE Bug 1249266 https://bugzilla.suse.com/1249271 SUSE Bug 1249271 https://bugzilla.suse.com/1249272 SUSE Bug 1249272 https://bugzilla.suse.com/1249273 SUSE Bug 1249273 https://bugzilla.suse.com/1249278 SUSE Bug 1249278 https://bugzilla.suse.com/1249279 SUSE Bug 1249279 https://bugzilla.suse.com/1249281 SUSE Bug 1249281 https://bugzilla.suse.com/1249282 SUSE Bug 1249282 https://bugzilla.suse.com/1249285 SUSE Bug 1249285 https://bugzilla.suse.com/1249286 SUSE Bug 1249286 https://bugzilla.suse.com/1249288 SUSE Bug 1249288 https://bugzilla.suse.com/1249292 SUSE Bug 1249292 https://bugzilla.suse.com/1249296 SUSE Bug 1249296 https://bugzilla.suse.com/1249299 SUSE Bug 1249299 https://bugzilla.suse.com/1249302 SUSE Bug 1249302 https://bugzilla.suse.com/1249304 SUSE Bug 1249304 https://bugzilla.suse.com/1249308 SUSE Bug 1249308 https://bugzilla.suse.com/1249312 SUSE Bug 1249312 https://bugzilla.suse.com/1249317 SUSE Bug 1249317 https://bugzilla.suse.com/1249318 SUSE Bug 1249318 https://bugzilla.suse.com/1249319 SUSE Bug 1249319 https://bugzilla.suse.com/1249320 SUSE Bug 1249320 https://bugzilla.suse.com/1249321 SUSE Bug 1249321 https://bugzilla.suse.com/1249323 SUSE Bug 1249323 https://bugzilla.suse.com/1249324 SUSE Bug 1249324 https://bugzilla.suse.com/1249338 SUSE Bug 1249338 https://bugzilla.suse.com/1249397 SUSE Bug 1249397 https://bugzilla.suse.com/1249413 SUSE Bug 1249413 https://bugzilla.suse.com/1249479 SUSE Bug 1249479 https://bugzilla.suse.com/1249486 SUSE Bug 1249486 https://bugzilla.suse.com/1249489 SUSE Bug 1249489 https://bugzilla.suse.com/1249490 SUSE Bug 1249490 https://bugzilla.suse.com/1249506 SUSE Bug 1249506 https://bugzilla.suse.com/1249512 SUSE Bug 1249512 https://bugzilla.suse.com/1249515 SUSE Bug 1249515 https://bugzilla.suse.com/1249522 SUSE Bug 1249522 https://bugzilla.suse.com/1249523 SUSE Bug 1249523 https://bugzilla.suse.com/1249538 SUSE Bug 1249538 https://bugzilla.suse.com/1249542 SUSE Bug 1249542 https://bugzilla.suse.com/1249548 SUSE Bug 1249548 https://bugzilla.suse.com/1249554 SUSE Bug 1249554 https://bugzilla.suse.com/1249595 SUSE Bug 1249595 https://bugzilla.suse.com/1249598 SUSE Bug 1249598 https://bugzilla.suse.com/1249608 SUSE Bug 1249608 https://bugzilla.suse.com/1249615 SUSE Bug 1249615 https://bugzilla.suse.com/1249640 SUSE Bug 1249640 https://bugzilla.suse.com/1249641 SUSE Bug 1249641 https://bugzilla.suse.com/1249642 SUSE Bug 1249642 https://bugzilla.suse.com/1249658 SUSE Bug 1249658 https://bugzilla.suse.com/1249662 SUSE Bug 1249662 https://bugzilla.suse.com/1249672 SUSE Bug 1249672 https://bugzilla.suse.com/1249673 SUSE Bug 1249673 https://bugzilla.suse.com/1249677 SUSE Bug 1249677 https://bugzilla.suse.com/1249678 SUSE Bug 1249678 https://bugzilla.suse.com/1249679 SUSE Bug 1249679 https://bugzilla.suse.com/1249682 SUSE Bug 1249682 https://bugzilla.suse.com/1249687 SUSE Bug 1249687 https://bugzilla.suse.com/1249698 SUSE Bug 1249698 https://bugzilla.suse.com/1249707 SUSE Bug 1249707 https://bugzilla.suse.com/1249712 SUSE Bug 1249712 https://bugzilla.suse.com/1249730 SUSE Bug 1249730 https://bugzilla.suse.com/1249735 SUSE Bug 1249735 https://bugzilla.suse.com/1249756 SUSE Bug 1249756 https://bugzilla.suse.com/1249758 SUSE Bug 1249758 https://bugzilla.suse.com/1249761 SUSE Bug 1249761 https://bugzilla.suse.com/1249762 SUSE Bug 1249762 https://bugzilla.suse.com/1249768 SUSE Bug 1249768 https://bugzilla.suse.com/1249774 SUSE Bug 1249774 https://bugzilla.suse.com/1249779 SUSE Bug 1249779 https://bugzilla.suse.com/1249780 SUSE Bug 1249780 https://bugzilla.suse.com/1249785 SUSE Bug 1249785 https://bugzilla.suse.com/1249787 SUSE Bug 1249787 https://bugzilla.suse.com/1249795 SUSE Bug 1249795 https://bugzilla.suse.com/1249815 SUSE Bug 1249815 https://bugzilla.suse.com/1249820 SUSE Bug 1249820 https://bugzilla.suse.com/1249823 SUSE Bug 1249823 https://bugzilla.suse.com/1249824 SUSE Bug 1249824 https://bugzilla.suse.com/1249825 SUSE Bug 1249825 https://bugzilla.suse.com/1249826 SUSE Bug 1249826 https://bugzilla.suse.com/1249833 SUSE Bug 1249833 https://bugzilla.suse.com/1249842 SUSE Bug 1249842 https://bugzilla.suse.com/1249845 SUSE Bug 1249845 https://bugzilla.suse.com/1249849 SUSE Bug 1249849 https://bugzilla.suse.com/1249850 SUSE Bug 1249850 https://bugzilla.suse.com/1249853 SUSE Bug 1249853 https://bugzilla.suse.com/1249856 SUSE Bug 1249856 https://bugzilla.suse.com/1249861 SUSE Bug 1249861 https://bugzilla.suse.com/1249863 SUSE Bug 1249863 https://bugzilla.suse.com/1249864 SUSE Bug 1249864 https://bugzilla.suse.com/1249865 SUSE Bug 1249865 https://bugzilla.suse.com/1249866 SUSE Bug 1249866 https://bugzilla.suse.com/1249869 SUSE Bug 1249869 https://bugzilla.suse.com/1249870 SUSE Bug 1249870 https://bugzilla.suse.com/1249880 SUSE Bug 1249880 https://bugzilla.suse.com/1249883 SUSE Bug 1249883 https://bugzilla.suse.com/1249888 SUSE Bug 1249888 https://bugzilla.suse.com/1249894 SUSE Bug 1249894 https://bugzilla.suse.com/1249896 SUSE Bug 1249896 https://bugzilla.suse.com/1249897 SUSE Bug 1249897 https://bugzilla.suse.com/1249901 SUSE Bug 1249901 https://bugzilla.suse.com/1249911 SUSE Bug 1249911 https://bugzilla.suse.com/1249917 SUSE Bug 1249917 https://bugzilla.suse.com/1249919 SUSE Bug 1249919 https://bugzilla.suse.com/1249923 SUSE Bug 1249923 https://bugzilla.suse.com/1249926 SUSE Bug 1249926 https://bugzilla.suse.com/1249938 SUSE Bug 1249938 https://bugzilla.suse.com/1249949 SUSE Bug 1249949 https://bugzilla.suse.com/1249950 SUSE Bug 1249950 https://bugzilla.suse.com/1249952 SUSE Bug 1249952 https://bugzilla.suse.com/1249975 SUSE Bug 1249975 https://bugzilla.suse.com/1249979 SUSE Bug 1249979 https://bugzilla.suse.com/1249984 SUSE Bug 1249984 https://bugzilla.suse.com/1249988 SUSE Bug 1249988 https://bugzilla.suse.com/1249990 SUSE Bug 1249990 https://bugzilla.suse.com/1249993 SUSE Bug 1249993 https://bugzilla.suse.com/1249994 SUSE Bug 1249994 https://bugzilla.suse.com/1249997 SUSE Bug 1249997 https://bugzilla.suse.com/1250004 SUSE Bug 1250004 https://bugzilla.suse.com/1250006 SUSE Bug 1250006 https://bugzilla.suse.com/1250007 SUSE Bug 1250007 https://bugzilla.suse.com/1250012 SUSE Bug 1250012 https://bugzilla.suse.com/1250022 SUSE Bug 1250022 https://bugzilla.suse.com/1250024 SUSE Bug 1250024 https://bugzilla.suse.com/1250028 SUSE Bug 1250028 https://bugzilla.suse.com/1250029 SUSE Bug 1250029 https://bugzilla.suse.com/1250032 SUSE Bug 1250032 https://bugzilla.suse.com/1250035 SUSE Bug 1250035 https://bugzilla.suse.com/1250049 SUSE Bug 1250049 https://bugzilla.suse.com/1250055 SUSE Bug 1250055 https://bugzilla.suse.com/1250058 SUSE Bug 1250058 https://bugzilla.suse.com/1250062 SUSE Bug 1250062 https://bugzilla.suse.com/1250063 SUSE Bug 1250063 https://bugzilla.suse.com/1250065 SUSE Bug 1250065 https://bugzilla.suse.com/1250066 SUSE Bug 1250066 https://bugzilla.suse.com/1250067 SUSE Bug 1250067 https://bugzilla.suse.com/1250069 SUSE Bug 1250069 https://bugzilla.suse.com/1250070 SUSE Bug 1250070 https://bugzilla.suse.com/1250073 SUSE Bug 1250073 https://bugzilla.suse.com/1250074 SUSE Bug 1250074 https://bugzilla.suse.com/1250088 SUSE Bug 1250088 https://bugzilla.suse.com/1250089 SUSE Bug 1250089 https://bugzilla.suse.com/1250106 SUSE Bug 1250106 https://bugzilla.suse.com/1250112 SUSE Bug 1250112 https://bugzilla.suse.com/1250117 SUSE Bug 1250117 https://bugzilla.suse.com/1250119 SUSE Bug 1250119 https://bugzilla.suse.com/1250120 SUSE Bug 1250120 https://bugzilla.suse.com/1250125 SUSE Bug 1250125 https://bugzilla.suse.com/1250127 SUSE Bug 1250127 https://bugzilla.suse.com/1250128 SUSE Bug 1250128 https://bugzilla.suse.com/1250145 SUSE Bug 1250145 https://bugzilla.suse.com/1250150 SUSE Bug 1250150 https://bugzilla.suse.com/1250156 SUSE Bug 1250156 https://bugzilla.suse.com/1250157 SUSE Bug 1250157 https://bugzilla.suse.com/1250161 SUSE Bug 1250161 https://bugzilla.suse.com/1250163 SUSE Bug 1250163 https://bugzilla.suse.com/1250166 SUSE Bug 1250166 https://bugzilla.suse.com/1250167 SUSE Bug 1250167 https://bugzilla.suse.com/1250169 SUSE Bug 1250169 https://bugzilla.suse.com/1250171 SUSE Bug 1250171 https://bugzilla.suse.com/1250177 SUSE Bug 1250177 https://bugzilla.suse.com/1250180 SUSE Bug 1250180 https://bugzilla.suse.com/1250186 SUSE Bug 1250186 https://bugzilla.suse.com/1250196 SUSE Bug 1250196 https://bugzilla.suse.com/1250198 SUSE Bug 1250198 https://bugzilla.suse.com/1250199 SUSE Bug 1250199 https://bugzilla.suse.com/1250201 SUSE Bug 1250201 https://bugzilla.suse.com/1250202 SUSE Bug 1250202 https://bugzilla.suse.com/1250203 SUSE Bug 1250203 https://bugzilla.suse.com/1250204 SUSE Bug 1250204 https://bugzilla.suse.com/1250205 SUSE Bug 1250205 https://bugzilla.suse.com/1250206 SUSE Bug 1250206 https://bugzilla.suse.com/1250208 SUSE Bug 1250208 https://bugzilla.suse.com/1250237 SUSE Bug 1250237 https://bugzilla.suse.com/1250241 SUSE Bug 1250241 https://bugzilla.suse.com/1250242 SUSE Bug 1250242 https://bugzilla.suse.com/1250243 SUSE Bug 1250243 https://bugzilla.suse.com/1250247 SUSE Bug 1250247 https://bugzilla.suse.com/1250249 SUSE Bug 1250249 https://bugzilla.suse.com/1250262 SUSE Bug 1250262 https://bugzilla.suse.com/1250263 SUSE Bug 1250263 https://bugzilla.suse.com/1250266 SUSE Bug 1250266 https://bugzilla.suse.com/1250268 SUSE Bug 1250268 https://bugzilla.suse.com/1250274 SUSE Bug 1250274 https://bugzilla.suse.com/1250275 SUSE Bug 1250275 https://bugzilla.suse.com/1250276 SUSE Bug 1250276 https://bugzilla.suse.com/1250281 SUSE Bug 1250281 https://bugzilla.suse.com/1250290 SUSE Bug 1250290 https://bugzilla.suse.com/1250291 SUSE Bug 1250291 https://bugzilla.suse.com/1250292 SUSE Bug 1250292 https://bugzilla.suse.com/1250296 SUSE Bug 1250296 https://bugzilla.suse.com/1250297 SUSE Bug 1250297 https://bugzilla.suse.com/1250298 SUSE Bug 1250298 https://bugzilla.suse.com/1250313 SUSE Bug 1250313 https://bugzilla.suse.com/1250319 SUSE Bug 1250319 https://bugzilla.suse.com/1250323 SUSE Bug 1250323 https://bugzilla.suse.com/1250325 SUSE Bug 1250325 https://bugzilla.suse.com/1250329 SUSE Bug 1250329 https://bugzilla.suse.com/1250337 SUSE Bug 1250337 https://bugzilla.suse.com/1250358 SUSE Bug 1250358 https://bugzilla.suse.com/1250371 SUSE Bug 1250371 https://bugzilla.suse.com/1250377 SUSE Bug 1250377 https://bugzilla.suse.com/1250379 SUSE Bug 1250379 https://bugzilla.suse.com/1250384 SUSE Bug 1250384 https://bugzilla.suse.com/1250389 SUSE Bug 1250389 https://bugzilla.suse.com/1250395 SUSE Bug 1250395 https://bugzilla.suse.com/1250397 SUSE Bug 1250397 https://bugzilla.suse.com/1250400 SUSE Bug 1250400 https://bugzilla.suse.com/1250402 SUSE Bug 1250402 https://bugzilla.suse.com/1250406 SUSE Bug 1250406 https://bugzilla.suse.com/1250426 SUSE Bug 1250426 https://bugzilla.suse.com/1250450 SUSE Bug 1250450 https://bugzilla.suse.com/1250455 SUSE Bug 1250455 https://bugzilla.suse.com/1250459 SUSE Bug 1250459 https://bugzilla.suse.com/1250491 SUSE Bug 1250491 https://bugzilla.suse.com/1250519 SUSE Bug 1250519 https://bugzilla.suse.com/1250650 SUSE Bug 1250650 https://bugzilla.suse.com/1250702 SUSE Bug 1250702 https://bugzilla.suse.com/1250704 SUSE Bug 1250704 https://bugzilla.suse.com/1250712 SUSE Bug 1250712 https://bugzilla.suse.com/1250713 SUSE Bug 1250713 https://bugzilla.suse.com/1250721 SUSE Bug 1250721 https://bugzilla.suse.com/1250732 SUSE Bug 1250732 https://bugzilla.suse.com/1250736 SUSE Bug 1250736 https://bugzilla.suse.com/1250741 SUSE Bug 1250741 https://bugzilla.suse.com/1250742 SUSE Bug 1250742 https://bugzilla.suse.com/1250758 SUSE Bug 1250758 https://bugzilla.suse.com/1250759 SUSE Bug 1250759 https://bugzilla.suse.com/1250763 SUSE Bug 1250763 https://bugzilla.suse.com/1250765 SUSE Bug 1250765 https://bugzilla.suse.com/1250807 SUSE Bug 1250807 https://bugzilla.suse.com/1250808 SUSE Bug 1250808 https://bugzilla.suse.com/1250809 SUSE Bug 1250809 https://bugzilla.suse.com/1250812 SUSE Bug 1250812 https://bugzilla.suse.com/1250813 SUSE Bug 1250813 https://bugzilla.suse.com/1250815 SUSE Bug 1250815 https://bugzilla.suse.com/1250816 SUSE Bug 1250816 https://bugzilla.suse.com/1250820 SUSE Bug 1250820 https://bugzilla.suse.com/1250823 SUSE Bug 1250823 https://bugzilla.suse.com/1250825 SUSE Bug 1250825 https://bugzilla.suse.com/1250827 SUSE Bug 1250827 https://bugzilla.suse.com/1250830 SUSE Bug 1250830 https://bugzilla.suse.com/1250831 SUSE Bug 1250831 https://bugzilla.suse.com/1250837 SUSE Bug 1250837 https://bugzilla.suse.com/1250841 SUSE Bug 1250841 https://bugzilla.suse.com/1250861 SUSE Bug 1250861 https://bugzilla.suse.com/1250863 SUSE Bug 1250863 https://bugzilla.suse.com/1250867 SUSE Bug 1250867 https://bugzilla.suse.com/1250872 SUSE Bug 1250872 https://bugzilla.suse.com/1250873 SUSE Bug 1250873 https://bugzilla.suse.com/1250878 SUSE Bug 1250878 https://bugzilla.suse.com/1250905 SUSE Bug 1250905 https://bugzilla.suse.com/1250907 SUSE Bug 1250907 https://bugzilla.suse.com/1250917 SUSE Bug 1250917 https://bugzilla.suse.com/1250918 SUSE Bug 1250918 https://bugzilla.suse.com/1250923 SUSE Bug 1250923 https://bugzilla.suse.com/1250926 SUSE Bug 1250926 https://bugzilla.suse.com/1250928 SUSE Bug 1250928 https://bugzilla.suse.com/1250929 SUSE Bug 1250929 https://bugzilla.suse.com/1250930 SUSE Bug 1250930 https://bugzilla.suse.com/1250931 SUSE Bug 1250931 https://bugzilla.suse.com/1250941 SUSE Bug 1250941 https://bugzilla.suse.com/1250942 SUSE Bug 1250942 https://bugzilla.suse.com/1250946 SUSE Bug 1250946 https://bugzilla.suse.com/1250949 SUSE Bug 1250949 https://bugzilla.suse.com/1250957 SUSE Bug 1250957 https://bugzilla.suse.com/1250964 SUSE Bug 1250964 https://bugzilla.suse.com/1251024 SUSE Bug 1251024 https://bugzilla.suse.com/1251027 SUSE Bug 1251027 https://bugzilla.suse.com/1251028 SUSE Bug 1251028 https://bugzilla.suse.com/1251031 SUSE Bug 1251031 https://bugzilla.suse.com/1251035 SUSE Bug 1251035 https://bugzilla.suse.com/1251038 SUSE Bug 1251038 https://bugzilla.suse.com/1251043 SUSE Bug 1251043 https://bugzilla.suse.com/1251045 SUSE Bug 1251045 https://bugzilla.suse.com/1251052 SUSE Bug 1251052 https://bugzilla.suse.com/1251053 SUSE Bug 1251053 https://bugzilla.suse.com/1251054 SUSE Bug 1251054 https://bugzilla.suse.com/1251056 SUSE Bug 1251056 https://bugzilla.suse.com/1251057 SUSE Bug 1251057 https://bugzilla.suse.com/1251059 SUSE Bug 1251059 https://bugzilla.suse.com/1251060 SUSE Bug 1251060 https://bugzilla.suse.com/1251065 SUSE Bug 1251065 https://bugzilla.suse.com/1251066 SUSE Bug 1251066 https://bugzilla.suse.com/1251067 SUSE Bug 1251067 https://bugzilla.suse.com/1251068 SUSE Bug 1251068 https://bugzilla.suse.com/1251071 SUSE Bug 1251071 https://bugzilla.suse.com/1251076 SUSE Bug 1251076 https://bugzilla.suse.com/1251079 SUSE Bug 1251079 https://bugzilla.suse.com/1251081 SUSE Bug 1251081 https://bugzilla.suse.com/1251083 SUSE Bug 1251083 https://bugzilla.suse.com/1251084 SUSE Bug 1251084 https://bugzilla.suse.com/1251100 SUSE Bug 1251100 https://bugzilla.suse.com/1251105 SUSE Bug 1251105 https://bugzilla.suse.com/1251106 SUSE Bug 1251106 https://bugzilla.suse.com/1251108 SUSE Bug 1251108 https://bugzilla.suse.com/1251113 SUSE Bug 1251113 https://bugzilla.suse.com/1251114 SUSE Bug 1251114 https://bugzilla.suse.com/1251119 SUSE Bug 1251119 https://bugzilla.suse.com/1251123 SUSE Bug 1251123 https://bugzilla.suse.com/1251126 SUSE Bug 1251126 https://bugzilla.suse.com/1251132 SUSE Bug 1251132 https://bugzilla.suse.com/1251134 SUSE Bug 1251134 https://bugzilla.suse.com/1251143 SUSE Bug 1251143 https://bugzilla.suse.com/1251146 SUSE Bug 1251146 https://bugzilla.suse.com/1251150 SUSE Bug 1251150 https://bugzilla.suse.com/1251152 SUSE Bug 1251152 https://bugzilla.suse.com/1251153 SUSE Bug 1251153 https://bugzilla.suse.com/1251159 SUSE Bug 1251159 https://bugzilla.suse.com/1251161 SUSE Bug 1251161 https://bugzilla.suse.com/1251170 SUSE Bug 1251170 https://bugzilla.suse.com/1251177 SUSE Bug 1251177 https://bugzilla.suse.com/1251180 SUSE Bug 1251180 https://bugzilla.suse.com/1251206 SUSE Bug 1251206 https://bugzilla.suse.com/1251215 SUSE Bug 1251215 https://bugzilla.suse.com/1251216 SUSE Bug 1251216 https://bugzilla.suse.com/1251222 SUSE Bug 1251222 https://bugzilla.suse.com/1251230 SUSE Bug 1251230 https://bugzilla.suse.com/1251232 SUSE Bug 1251232 https://bugzilla.suse.com/1251233 SUSE Bug 1251233 https://bugzilla.suse.com/1251247 SUSE Bug 1251247 https://bugzilla.suse.com/1251268 SUSE Bug 1251268 https://bugzilla.suse.com/1251269 SUSE Bug 1251269 https://bugzilla.suse.com/1251270 SUSE Bug 1251270 https://bugzilla.suse.com/1251282 SUSE Bug 1251282 https://bugzilla.suse.com/1251283 SUSE Bug 1251283 https://bugzilla.suse.com/1251286 SUSE Bug 1251286 https://bugzilla.suse.com/1251290 SUSE Bug 1251290 https://bugzilla.suse.com/1251319 SUSE Bug 1251319 https://bugzilla.suse.com/1251321 SUSE Bug 1251321 https://bugzilla.suse.com/1251323 SUSE Bug 1251323 https://bugzilla.suse.com/1251328 SUSE Bug 1251328 https://bugzilla.suse.com/1251529 SUSE Bug 1251529 https://bugzilla.suse.com/1251721 SUSE Bug 1251721 https://bugzilla.suse.com/1251732 SUSE Bug 1251732 https://bugzilla.suse.com/1251742 SUSE Bug 1251742 https://bugzilla.suse.com/1251743 SUSE Bug 1251743 https://bugzilla.suse.com/1251746 SUSE Bug 1251746 https://bugzilla.suse.com/1251748 SUSE Bug 1251748 https://bugzilla.suse.com/1251749 SUSE Bug 1251749 https://bugzilla.suse.com/1251750 SUSE Bug 1251750 https://bugzilla.suse.com/1251754 SUSE Bug 1251754 https://bugzilla.suse.com/1251755 SUSE Bug 1251755 https://bugzilla.suse.com/1251756 SUSE Bug 1251756 https://bugzilla.suse.com/1251758 SUSE Bug 1251758 https://bugzilla.suse.com/1251759 SUSE Bug 1251759 https://bugzilla.suse.com/1251760 SUSE Bug 1251760 https://bugzilla.suse.com/1251762 SUSE Bug 1251762 https://bugzilla.suse.com/1251763 SUSE Bug 1251763 https://bugzilla.suse.com/1251764 SUSE Bug 1251764 https://bugzilla.suse.com/1251769 SUSE Bug 1251769 https://bugzilla.suse.com/1251771 SUSE Bug 1251771 https://bugzilla.suse.com/1251772 SUSE Bug 1251772 https://bugzilla.suse.com/1251777 SUSE Bug 1251777 https://bugzilla.suse.com/1251780 SUSE Bug 1251780 https://bugzilla.suse.com/1251804 SUSE Bug 1251804 https://bugzilla.suse.com/1251810 SUSE Bug 1251810 https://bugzilla.suse.com/1251930 SUSE Bug 1251930 https://bugzilla.suse.com/1251967 SUSE Bug 1251967 https://bugzilla.suse.com/1252033 SUSE Bug 1252033 https://bugzilla.suse.com/1252035 SUSE Bug 1252035 https://bugzilla.suse.com/1252039 SUSE Bug 1252039 https://bugzilla.suse.com/1252044 SUSE Bug 1252044 https://bugzilla.suse.com/1252047 SUSE Bug 1252047 https://bugzilla.suse.com/1252051 SUSE Bug 1252051 https://bugzilla.suse.com/1252052 SUSE Bug 1252052 https://bugzilla.suse.com/1252056 SUSE Bug 1252056 https://bugzilla.suse.com/1252060 SUSE Bug 1252060 https://bugzilla.suse.com/1252062 SUSE Bug 1252062 https://bugzilla.suse.com/1252064 SUSE Bug 1252064 https://bugzilla.suse.com/1252065 SUSE Bug 1252065 https://bugzilla.suse.com/1252069 SUSE Bug 1252069 https://bugzilla.suse.com/1252070 SUSE Bug 1252070 https://bugzilla.suse.com/1252072 SUSE Bug 1252072 https://bugzilla.suse.com/1252074 SUSE Bug 1252074 https://bugzilla.suse.com/1252075 SUSE Bug 1252075 https://bugzilla.suse.com/1252078 SUSE Bug 1252078 https://bugzilla.suse.com/1252079 SUSE Bug 1252079 https://bugzilla.suse.com/1252081 SUSE Bug 1252081 https://bugzilla.suse.com/1252082 SUSE Bug 1252082 https://bugzilla.suse.com/1252083 SUSE Bug 1252083 https://bugzilla.suse.com/1252236 SUSE Bug 1252236 https://bugzilla.suse.com/1252253 SUSE Bug 1252253 https://bugzilla.suse.com/1252265 SUSE Bug 1252265 https://bugzilla.suse.com/1252330 SUSE Bug 1252330 https://bugzilla.suse.com/1252332 SUSE Bug 1252332 https://bugzilla.suse.com/1252336 SUSE Bug 1252336 https://bugzilla.suse.com/1252346 SUSE Bug 1252346 https://bugzilla.suse.com/1252348 SUSE Bug 1252348 https://bugzilla.suse.com/1252349 SUSE Bug 1252349 https://bugzilla.suse.com/1252364 SUSE Bug 1252364 https://bugzilla.suse.com/1252469 SUSE Bug 1252469 https://bugzilla.suse.com/1252479 SUSE Bug 1252479 https://bugzilla.suse.com/1252481 SUSE Bug 1252481 https://bugzilla.suse.com/1252489 SUSE Bug 1252489 https://bugzilla.suse.com/1252490 SUSE Bug 1252490 https://bugzilla.suse.com/1252492 SUSE Bug 1252492 https://bugzilla.suse.com/1252495 SUSE Bug 1252495 https://bugzilla.suse.com/1252496 SUSE Bug 1252496 https://bugzilla.suse.com/1252499 SUSE Bug 1252499 https://bugzilla.suse.com/1252534 SUSE Bug 1252534 https://bugzilla.suse.com/1252536 SUSE Bug 1252536 https://bugzilla.suse.com/1252537 SUSE Bug 1252537 https://bugzilla.suse.com/1252550 SUSE Bug 1252550 https://bugzilla.suse.com/1252553 SUSE Bug 1252553 https://bugzilla.suse.com/1252559 SUSE Bug 1252559 https://bugzilla.suse.com/1252561 SUSE Bug 1252561 https://bugzilla.suse.com/1252564 SUSE Bug 1252564 https://bugzilla.suse.com/1252565 SUSE Bug 1252565 https://bugzilla.suse.com/1252566 SUSE Bug 1252566 https://bugzilla.suse.com/1252632 SUSE Bug 1252632 https://bugzilla.suse.com/1252668 SUSE Bug 1252668 https://bugzilla.suse.com/1252678 SUSE Bug 1252678 https://bugzilla.suse.com/1252679 SUSE Bug 1252679 https://bugzilla.suse.com/1252685 SUSE Bug 1252685 https://bugzilla.suse.com/1252688 SUSE Bug 1252688 https://bugzilla.suse.com/1252734 SUSE Bug 1252734 https://bugzilla.suse.com/1252735 SUSE Bug 1252735 https://bugzilla.suse.com/1252772 SUSE Bug 1252772 https://bugzilla.suse.com/1252775 SUSE Bug 1252775 https://bugzilla.suse.com/1252785 SUSE Bug 1252785 https://bugzilla.suse.com/1252787 SUSE Bug 1252787 https://bugzilla.suse.com/1252789 SUSE Bug 1252789 https://bugzilla.suse.com/1252797 SUSE Bug 1252797 https://bugzilla.suse.com/1252819 SUSE Bug 1252819 https://bugzilla.suse.com/1252822 SUSE Bug 1252822 https://bugzilla.suse.com/1252826 SUSE Bug 1252826 https://bugzilla.suse.com/1252841 SUSE Bug 1252841 https://bugzilla.suse.com/1252848 SUSE Bug 1252848 https://bugzilla.suse.com/1252849 SUSE Bug 1252849 https://bugzilla.suse.com/1252850 SUSE Bug 1252850 https://bugzilla.suse.com/1252851 SUSE Bug 1252851 https://bugzilla.suse.com/1252854 SUSE Bug 1252854 https://bugzilla.suse.com/1252858 SUSE Bug 1252858 https://bugzilla.suse.com/1252865 SUSE Bug 1252865 https://bugzilla.suse.com/1252866 SUSE Bug 1252866 https://bugzilla.suse.com/1252873 SUSE Bug 1252873 https://bugzilla.suse.com/1252902 SUSE Bug 1252902 https://bugzilla.suse.com/1252904 SUSE Bug 1252904 https://bugzilla.suse.com/1252909 SUSE Bug 1252909 https://bugzilla.suse.com/1252915 SUSE Bug 1252915 https://bugzilla.suse.com/1252918 SUSE Bug 1252918 https://bugzilla.suse.com/1252921 SUSE Bug 1252921 https://bugzilla.suse.com/1252939 SUSE Bug 1252939 https://www.suse.com/security/cve/CVE-2023-31248/ SUSE CVE CVE-2023-31248 page https://www.suse.com/security/cve/CVE-2023-3772/ SUSE CVE CVE-2023-3772 page https://www.suse.com/security/cve/CVE-2023-39197/ SUSE CVE CVE-2023-39197 page https://www.suse.com/security/cve/CVE-2023-42753/ SUSE CVE CVE-2023-42753 page https://www.suse.com/security/cve/CVE-2023-53147/ SUSE CVE CVE-2023-53147 page https://www.suse.com/security/cve/CVE-2023-53148/ SUSE CVE CVE-2023-53148 page https://www.suse.com/security/cve/CVE-2023-53150/ SUSE CVE CVE-2023-53150 page https://www.suse.com/security/cve/CVE-2023-53151/ SUSE CVE CVE-2023-53151 page https://www.suse.com/security/cve/CVE-2023-53152/ SUSE CVE CVE-2023-53152 page https://www.suse.com/security/cve/CVE-2023-53165/ SUSE CVE CVE-2023-53165 page https://www.suse.com/security/cve/CVE-2023-53167/ SUSE CVE CVE-2023-53167 page https://www.suse.com/security/cve/CVE-2023-53170/ SUSE CVE CVE-2023-53170 page https://www.suse.com/security/cve/CVE-2023-53174/ SUSE CVE CVE-2023-53174 page https://www.suse.com/security/cve/CVE-2023-53175/ SUSE CVE CVE-2023-53175 page https://www.suse.com/security/cve/CVE-2023-53177/ SUSE CVE CVE-2023-53177 page https://www.suse.com/security/cve/CVE-2023-53179/ SUSE CVE CVE-2023-53179 page https://www.suse.com/security/cve/CVE-2023-53180/ SUSE CVE CVE-2023-53180 page https://www.suse.com/security/cve/CVE-2023-53181/ SUSE CVE CVE-2023-53181 page https://www.suse.com/security/cve/CVE-2023-53183/ SUSE CVE CVE-2023-53183 page https://www.suse.com/security/cve/CVE-2023-53184/ SUSE CVE CVE-2023-53184 page https://www.suse.com/security/cve/CVE-2023-53185/ SUSE CVE CVE-2023-53185 page https://www.suse.com/security/cve/CVE-2023-53187/ SUSE CVE CVE-2023-53187 page https://www.suse.com/security/cve/CVE-2023-53189/ SUSE CVE CVE-2023-53189 page https://www.suse.com/security/cve/CVE-2023-53192/ SUSE CVE CVE-2023-53192 page https://www.suse.com/security/cve/CVE-2023-53195/ SUSE CVE CVE-2023-53195 page https://www.suse.com/security/cve/CVE-2023-53196/ SUSE CVE CVE-2023-53196 page https://www.suse.com/security/cve/CVE-2023-53201/ SUSE CVE CVE-2023-53201 page https://www.suse.com/security/cve/CVE-2023-53204/ SUSE CVE CVE-2023-53204 page https://www.suse.com/security/cve/CVE-2023-53205/ SUSE CVE CVE-2023-53205 page https://www.suse.com/security/cve/CVE-2023-53206/ SUSE CVE CVE-2023-53206 page https://www.suse.com/security/cve/CVE-2023-53207/ SUSE CVE CVE-2023-53207 page https://www.suse.com/security/cve/CVE-2023-53208/ SUSE CVE CVE-2023-53208 page https://www.suse.com/security/cve/CVE-2023-53209/ SUSE CVE CVE-2023-53209 page https://www.suse.com/security/cve/CVE-2023-53210/ SUSE CVE CVE-2023-53210 page https://www.suse.com/security/cve/CVE-2023-53215/ SUSE CVE CVE-2023-53215 page https://www.suse.com/security/cve/CVE-2023-53217/ SUSE CVE CVE-2023-53217 page https://www.suse.com/security/cve/CVE-2023-53220/ SUSE CVE CVE-2023-53220 page https://www.suse.com/security/cve/CVE-2023-53221/ SUSE CVE CVE-2023-53221 page https://www.suse.com/security/cve/CVE-2023-53222/ SUSE CVE CVE-2023-53222 page https://www.suse.com/security/cve/CVE-2023-53226/ SUSE CVE CVE-2023-53226 page https://www.suse.com/security/cve/CVE-2023-53230/ SUSE CVE CVE-2023-53230 page https://www.suse.com/security/cve/CVE-2023-53231/ SUSE CVE CVE-2023-53231 page https://www.suse.com/security/cve/CVE-2023-53235/ SUSE CVE CVE-2023-53235 page https://www.suse.com/security/cve/CVE-2023-53238/ SUSE CVE CVE-2023-53238 page https://www.suse.com/security/cve/CVE-2023-53243/ SUSE CVE CVE-2023-53243 page https://www.suse.com/security/cve/CVE-2023-53245/ SUSE CVE CVE-2023-53245 page https://www.suse.com/security/cve/CVE-2023-53247/ SUSE CVE CVE-2023-53247 page https://www.suse.com/security/cve/CVE-2023-53248/ SUSE CVE CVE-2023-53248 page https://www.suse.com/security/cve/CVE-2023-53249/ SUSE CVE CVE-2023-53249 page https://www.suse.com/security/cve/CVE-2023-53251/ SUSE CVE CVE-2023-53251 page https://www.suse.com/security/cve/CVE-2023-53252/ SUSE CVE CVE-2023-53252 page https://www.suse.com/security/cve/CVE-2023-53255/ SUSE CVE CVE-2023-53255 page https://www.suse.com/security/cve/CVE-2023-53257/ SUSE CVE CVE-2023-53257 page https://www.suse.com/security/cve/CVE-2023-53258/ SUSE CVE CVE-2023-53258 page https://www.suse.com/security/cve/CVE-2023-53260/ SUSE CVE CVE-2023-53260 page https://www.suse.com/security/cve/CVE-2023-53263/ SUSE CVE CVE-2023-53263 page https://www.suse.com/security/cve/CVE-2023-53264/ SUSE CVE CVE-2023-53264 page https://www.suse.com/security/cve/CVE-2023-53272/ SUSE CVE CVE-2023-53272 page https://www.suse.com/security/cve/CVE-2023-53274/ SUSE CVE CVE-2023-53274 page https://www.suse.com/security/cve/CVE-2023-53275/ SUSE CVE CVE-2023-53275 page https://www.suse.com/security/cve/CVE-2023-53280/ SUSE CVE CVE-2023-53280 page https://www.suse.com/security/cve/CVE-2023-53286/ SUSE CVE CVE-2023-53286 page https://www.suse.com/security/cve/CVE-2023-53287/ SUSE CVE CVE-2023-53287 page https://www.suse.com/security/cve/CVE-2023-53288/ SUSE CVE CVE-2023-53288 page https://www.suse.com/security/cve/CVE-2023-53291/ SUSE CVE CVE-2023-53291 page https://www.suse.com/security/cve/CVE-2023-53292/ SUSE CVE CVE-2023-53292 page https://www.suse.com/security/cve/CVE-2023-53303/ SUSE CVE CVE-2023-53303 page https://www.suse.com/security/cve/CVE-2023-53304/ SUSE CVE CVE-2023-53304 page https://www.suse.com/security/cve/CVE-2023-53305/ SUSE CVE CVE-2023-53305 page https://www.suse.com/security/cve/CVE-2023-53309/ SUSE CVE CVE-2023-53309 page https://www.suse.com/security/cve/CVE-2023-53311/ SUSE CVE CVE-2023-53311 page https://www.suse.com/security/cve/CVE-2023-53312/ SUSE CVE CVE-2023-53312 page https://www.suse.com/security/cve/CVE-2023-53313/ SUSE CVE CVE-2023-53313 page https://www.suse.com/security/cve/CVE-2023-53314/ SUSE CVE CVE-2023-53314 page https://www.suse.com/security/cve/CVE-2023-53316/ SUSE CVE CVE-2023-53316 page https://www.suse.com/security/cve/CVE-2023-53319/ SUSE CVE CVE-2023-53319 page https://www.suse.com/security/cve/CVE-2023-53321/ SUSE CVE CVE-2023-53321 page https://www.suse.com/security/cve/CVE-2023-53322/ SUSE CVE CVE-2023-53322 page https://www.suse.com/security/cve/CVE-2023-53323/ SUSE CVE CVE-2023-53323 page https://www.suse.com/security/cve/CVE-2023-53324/ SUSE CVE CVE-2023-53324 page https://www.suse.com/security/cve/CVE-2023-53325/ SUSE CVE CVE-2023-53325 page https://www.suse.com/security/cve/CVE-2023-53328/ SUSE CVE CVE-2023-53328 page https://www.suse.com/security/cve/CVE-2023-53331/ SUSE CVE CVE-2023-53331 page https://www.suse.com/security/cve/CVE-2023-53333/ SUSE CVE CVE-2023-53333 page https://www.suse.com/security/cve/CVE-2023-53336/ SUSE CVE CVE-2023-53336 page https://www.suse.com/security/cve/CVE-2023-53338/ SUSE CVE CVE-2023-53338 page https://www.suse.com/security/cve/CVE-2023-53339/ SUSE CVE CVE-2023-53339 page https://www.suse.com/security/cve/CVE-2023-53342/ SUSE CVE CVE-2023-53342 page https://www.suse.com/security/cve/CVE-2023-53343/ SUSE CVE CVE-2023-53343 page https://www.suse.com/security/cve/CVE-2023-53350/ SUSE CVE CVE-2023-53350 page https://www.suse.com/security/cve/CVE-2023-53352/ SUSE CVE CVE-2023-53352 page https://www.suse.com/security/cve/CVE-2023-53354/ SUSE CVE CVE-2023-53354 page https://www.suse.com/security/cve/CVE-2023-53356/ SUSE CVE CVE-2023-53356 page https://www.suse.com/security/cve/CVE-2023-53357/ SUSE CVE CVE-2023-53357 page https://www.suse.com/security/cve/CVE-2023-53360/ SUSE CVE CVE-2023-53360 page https://www.suse.com/security/cve/CVE-2023-53362/ SUSE CVE CVE-2023-53362 page https://www.suse.com/security/cve/CVE-2023-53364/ SUSE CVE CVE-2023-53364 page https://www.suse.com/security/cve/CVE-2023-53365/ SUSE CVE CVE-2023-53365 page https://www.suse.com/security/cve/CVE-2023-53367/ SUSE CVE CVE-2023-53367 page https://www.suse.com/security/cve/CVE-2023-53368/ SUSE CVE CVE-2023-53368 page https://www.suse.com/security/cve/CVE-2023-53369/ SUSE CVE CVE-2023-53369 page https://www.suse.com/security/cve/CVE-2023-53370/ SUSE CVE CVE-2023-53370 page https://www.suse.com/security/cve/CVE-2023-53371/ SUSE CVE CVE-2023-53371 page https://www.suse.com/security/cve/CVE-2023-53374/ SUSE CVE CVE-2023-53374 page https://www.suse.com/security/cve/CVE-2023-53377/ SUSE CVE CVE-2023-53377 page https://www.suse.com/security/cve/CVE-2023-53379/ SUSE CVE CVE-2023-53379 page https://www.suse.com/security/cve/CVE-2023-53380/ SUSE CVE CVE-2023-53380 page https://www.suse.com/security/cve/CVE-2023-53384/ SUSE CVE CVE-2023-53384 page https://www.suse.com/security/cve/CVE-2023-53385/ SUSE CVE CVE-2023-53385 page https://www.suse.com/security/cve/CVE-2023-53386/ SUSE CVE CVE-2023-53386 page https://www.suse.com/security/cve/CVE-2023-53391/ SUSE CVE CVE-2023-53391 page https://www.suse.com/security/cve/CVE-2023-53394/ SUSE CVE CVE-2023-53394 page https://www.suse.com/security/cve/CVE-2023-53395/ SUSE CVE CVE-2023-53395 page https://www.suse.com/security/cve/CVE-2023-53397/ SUSE CVE CVE-2023-53397 page https://www.suse.com/security/cve/CVE-2023-53401/ SUSE CVE CVE-2023-53401 page https://www.suse.com/security/cve/CVE-2023-53420/ SUSE CVE CVE-2023-53420 page https://www.suse.com/security/cve/CVE-2023-53421/ SUSE CVE CVE-2023-53421 page https://www.suse.com/security/cve/CVE-2023-53424/ SUSE CVE CVE-2023-53424 page https://www.suse.com/security/cve/CVE-2023-53425/ SUSE CVE CVE-2023-53425 page https://www.suse.com/security/cve/CVE-2023-53426/ SUSE CVE CVE-2023-53426 page https://www.suse.com/security/cve/CVE-2023-53428/ SUSE CVE CVE-2023-53428 page https://www.suse.com/security/cve/CVE-2023-53429/ SUSE CVE CVE-2023-53429 page https://www.suse.com/security/cve/CVE-2023-53432/ SUSE CVE CVE-2023-53432 page https://www.suse.com/security/cve/CVE-2023-53436/ SUSE CVE CVE-2023-53436 page https://www.suse.com/security/cve/CVE-2023-53438/ SUSE CVE CVE-2023-53438 page https://www.suse.com/security/cve/CVE-2023-53441/ SUSE CVE CVE-2023-53441 page https://www.suse.com/security/cve/CVE-2023-53442/ SUSE CVE CVE-2023-53442 page https://www.suse.com/security/cve/CVE-2023-53444/ SUSE CVE CVE-2023-53444 page https://www.suse.com/security/cve/CVE-2023-53446/ SUSE CVE CVE-2023-53446 page https://www.suse.com/security/cve/CVE-2023-53447/ SUSE CVE CVE-2023-53447 page https://www.suse.com/security/cve/CVE-2023-53448/ SUSE CVE CVE-2023-53448 page https://www.suse.com/security/cve/CVE-2023-53451/ SUSE CVE CVE-2023-53451 page https://www.suse.com/security/cve/CVE-2023-53454/ SUSE CVE CVE-2023-53454 page https://www.suse.com/security/cve/CVE-2023-53456/ SUSE CVE CVE-2023-53456 page https://www.suse.com/security/cve/CVE-2023-53457/ SUSE CVE CVE-2023-53457 page https://www.suse.com/security/cve/CVE-2023-53461/ SUSE CVE CVE-2023-53461 page https://www.suse.com/security/cve/CVE-2023-53462/ SUSE CVE CVE-2023-53462 page https://www.suse.com/security/cve/CVE-2023-53463/ SUSE CVE CVE-2023-53463 page https://www.suse.com/security/cve/CVE-2023-53465/ SUSE CVE CVE-2023-53465 page https://www.suse.com/security/cve/CVE-2023-53472/ SUSE CVE CVE-2023-53472 page https://www.suse.com/security/cve/CVE-2023-53479/ SUSE CVE CVE-2023-53479 page https://www.suse.com/security/cve/CVE-2023-53480/ SUSE CVE CVE-2023-53480 page https://www.suse.com/security/cve/CVE-2023-53485/ SUSE CVE CVE-2023-53485 page https://www.suse.com/security/cve/CVE-2023-53487/ SUSE CVE CVE-2023-53487 page https://www.suse.com/security/cve/CVE-2023-53488/ SUSE CVE CVE-2023-53488 page https://www.suse.com/security/cve/CVE-2023-53490/ SUSE CVE CVE-2023-53490 page https://www.suse.com/security/cve/CVE-2023-53491/ SUSE CVE CVE-2023-53491 page https://www.suse.com/security/cve/CVE-2023-53492/ SUSE CVE CVE-2023-53492 page https://www.suse.com/security/cve/CVE-2023-53493/ SUSE CVE CVE-2023-53493 page https://www.suse.com/security/cve/CVE-2023-53495/ SUSE CVE CVE-2023-53495 page https://www.suse.com/security/cve/CVE-2023-53496/ SUSE CVE CVE-2023-53496 page https://www.suse.com/security/cve/CVE-2023-53500/ SUSE CVE CVE-2023-53500 page https://www.suse.com/security/cve/CVE-2023-53501/ SUSE CVE CVE-2023-53501 page https://www.suse.com/security/cve/CVE-2023-53504/ SUSE CVE CVE-2023-53504 page https://www.suse.com/security/cve/CVE-2023-53505/ SUSE CVE CVE-2023-53505 page https://www.suse.com/security/cve/CVE-2023-53507/ SUSE CVE CVE-2023-53507 page https://www.suse.com/security/cve/CVE-2023-53508/ SUSE CVE CVE-2023-53508 page https://www.suse.com/security/cve/CVE-2023-53510/ SUSE CVE CVE-2023-53510 page https://www.suse.com/security/cve/CVE-2023-53515/ SUSE CVE CVE-2023-53515 page https://www.suse.com/security/cve/CVE-2023-53516/ SUSE CVE CVE-2023-53516 page https://www.suse.com/security/cve/CVE-2023-53518/ SUSE CVE CVE-2023-53518 page https://www.suse.com/security/cve/CVE-2023-53519/ SUSE CVE CVE-2023-53519 page https://www.suse.com/security/cve/CVE-2023-53520/ SUSE CVE CVE-2023-53520 page https://www.suse.com/security/cve/CVE-2023-53523/ SUSE CVE CVE-2023-53523 page https://www.suse.com/security/cve/CVE-2023-53526/ SUSE CVE CVE-2023-53526 page https://www.suse.com/security/cve/CVE-2023-53527/ SUSE CVE CVE-2023-53527 page https://www.suse.com/security/cve/CVE-2023-53528/ SUSE CVE CVE-2023-53528 page https://www.suse.com/security/cve/CVE-2023-53530/ SUSE CVE CVE-2023-53530 page https://www.suse.com/security/cve/CVE-2023-53531/ SUSE CVE CVE-2023-53531 page https://www.suse.com/security/cve/CVE-2023-53538/ SUSE CVE CVE-2023-53538 page https://www.suse.com/security/cve/CVE-2023-53539/ SUSE CVE CVE-2023-53539 page https://www.suse.com/security/cve/CVE-2023-53540/ SUSE CVE CVE-2023-53540 page https://www.suse.com/security/cve/CVE-2023-53541/ SUSE CVE CVE-2023-53541 page https://www.suse.com/security/cve/CVE-2023-53543/ SUSE CVE CVE-2023-53543 page https://www.suse.com/security/cve/CVE-2023-53545/ SUSE CVE CVE-2023-53545 page https://www.suse.com/security/cve/CVE-2023-53546/ SUSE CVE CVE-2023-53546 page https://www.suse.com/security/cve/CVE-2023-53548/ SUSE CVE CVE-2023-53548 page https://www.suse.com/security/cve/CVE-2023-53550/ SUSE CVE CVE-2023-53550 page https://www.suse.com/security/cve/CVE-2023-53552/ SUSE CVE CVE-2023-53552 page https://www.suse.com/security/cve/CVE-2023-53553/ SUSE CVE CVE-2023-53553 page https://www.suse.com/security/cve/CVE-2023-53554/ SUSE CVE CVE-2023-53554 page https://www.suse.com/security/cve/CVE-2023-53555/ SUSE CVE CVE-2023-53555 page https://www.suse.com/security/cve/CVE-2023-53556/ SUSE CVE CVE-2023-53556 page https://www.suse.com/security/cve/CVE-2023-53557/ SUSE CVE CVE-2023-53557 page https://www.suse.com/security/cve/CVE-2023-53558/ SUSE CVE CVE-2023-53558 page https://www.suse.com/security/cve/CVE-2023-53559/ SUSE CVE CVE-2023-53559 page https://www.suse.com/security/cve/CVE-2023-53560/ SUSE CVE CVE-2023-53560 page https://www.suse.com/security/cve/CVE-2023-53563/ SUSE CVE CVE-2023-53563 page https://www.suse.com/security/cve/CVE-2023-53568/ SUSE CVE CVE-2023-53568 page https://www.suse.com/security/cve/CVE-2023-53570/ SUSE CVE CVE-2023-53570 page https://www.suse.com/security/cve/CVE-2023-53572/ SUSE CVE CVE-2023-53572 page https://www.suse.com/security/cve/CVE-2023-53574/ SUSE CVE CVE-2023-53574 page https://www.suse.com/security/cve/CVE-2023-53575/ SUSE CVE CVE-2023-53575 page https://www.suse.com/security/cve/CVE-2023-53577/ SUSE CVE CVE-2023-53577 page https://www.suse.com/security/cve/CVE-2023-53579/ SUSE CVE CVE-2023-53579 page https://www.suse.com/security/cve/CVE-2023-53580/ SUSE CVE CVE-2023-53580 page https://www.suse.com/security/cve/CVE-2023-53581/ SUSE CVE CVE-2023-53581 page https://www.suse.com/security/cve/CVE-2023-53583/ SUSE CVE CVE-2023-53583 page https://www.suse.com/security/cve/CVE-2023-53585/ SUSE CVE CVE-2023-53585 page https://www.suse.com/security/cve/CVE-2023-53588/ SUSE CVE CVE-2023-53588 page https://www.suse.com/security/cve/CVE-2023-53593/ SUSE CVE CVE-2023-53593 page https://www.suse.com/security/cve/CVE-2023-53596/ SUSE CVE CVE-2023-53596 page https://www.suse.com/security/cve/CVE-2023-53597/ SUSE CVE CVE-2023-53597 page https://www.suse.com/security/cve/CVE-2023-53599/ SUSE CVE CVE-2023-53599 page https://www.suse.com/security/cve/CVE-2023-53600/ SUSE CVE CVE-2023-53600 page https://www.suse.com/security/cve/CVE-2023-53601/ SUSE CVE CVE-2023-53601 page https://www.suse.com/security/cve/CVE-2023-53602/ SUSE CVE CVE-2023-53602 page https://www.suse.com/security/cve/CVE-2023-53603/ SUSE CVE CVE-2023-53603 page https://www.suse.com/security/cve/CVE-2023-53611/ SUSE CVE CVE-2023-53611 page https://www.suse.com/security/cve/CVE-2023-53613/ SUSE CVE CVE-2023-53613 page https://www.suse.com/security/cve/CVE-2023-53615/ SUSE CVE CVE-2023-53615 page https://www.suse.com/security/cve/CVE-2023-53616/ SUSE CVE CVE-2023-53616 page https://www.suse.com/security/cve/CVE-2023-53617/ SUSE CVE CVE-2023-53617 page https://www.suse.com/security/cve/CVE-2023-53618/ SUSE CVE CVE-2023-53618 page https://www.suse.com/security/cve/CVE-2023-53619/ SUSE CVE CVE-2023-53619 page https://www.suse.com/security/cve/CVE-2023-53621/ SUSE CVE CVE-2023-53621 page https://www.suse.com/security/cve/CVE-2023-53622/ SUSE CVE CVE-2023-53622 page https://www.suse.com/security/cve/CVE-2023-53631/ SUSE CVE CVE-2023-53631 page https://www.suse.com/security/cve/CVE-2023-53632/ SUSE CVE CVE-2023-53632 page https://www.suse.com/security/cve/CVE-2023-53633/ SUSE CVE CVE-2023-53633 page https://www.suse.com/security/cve/CVE-2023-53638/ SUSE CVE CVE-2023-53638 page https://www.suse.com/security/cve/CVE-2023-53645/ SUSE CVE CVE-2023-53645 page https://www.suse.com/security/cve/CVE-2023-53646/ SUSE CVE CVE-2023-53646 page https://www.suse.com/security/cve/CVE-2023-53647/ SUSE CVE CVE-2023-53647 page https://www.suse.com/security/cve/CVE-2023-53648/ SUSE CVE CVE-2023-53648 page https://www.suse.com/security/cve/CVE-2023-53649/ SUSE CVE CVE-2023-53649 page https://www.suse.com/security/cve/CVE-2023-53650/ SUSE CVE CVE-2023-53650 page https://www.suse.com/security/cve/CVE-2023-53652/ SUSE CVE CVE-2023-53652 page https://www.suse.com/security/cve/CVE-2023-53653/ SUSE CVE CVE-2023-53653 page https://www.suse.com/security/cve/CVE-2023-53654/ SUSE CVE CVE-2023-53654 page https://www.suse.com/security/cve/CVE-2023-53656/ SUSE CVE CVE-2023-53656 page https://www.suse.com/security/cve/CVE-2023-53657/ SUSE CVE CVE-2023-53657 page https://www.suse.com/security/cve/CVE-2023-53658/ SUSE CVE CVE-2023-53658 page https://www.suse.com/security/cve/CVE-2023-53659/ SUSE CVE CVE-2023-53659 page https://www.suse.com/security/cve/CVE-2023-53660/ SUSE CVE CVE-2023-53660 page https://www.suse.com/security/cve/CVE-2023-53662/ SUSE CVE CVE-2023-53662 page https://www.suse.com/security/cve/CVE-2023-53663/ SUSE CVE CVE-2023-53663 page https://www.suse.com/security/cve/CVE-2023-53665/ SUSE CVE CVE-2023-53665 page https://www.suse.com/security/cve/CVE-2023-53666/ SUSE CVE CVE-2023-53666 page https://www.suse.com/security/cve/CVE-2023-53668/ SUSE CVE CVE-2023-53668 page https://www.suse.com/security/cve/CVE-2023-53670/ SUSE CVE CVE-2023-53670 page https://www.suse.com/security/cve/CVE-2023-53672/ SUSE CVE CVE-2023-53672 page https://www.suse.com/security/cve/CVE-2023-53673/ SUSE CVE CVE-2023-53673 page https://www.suse.com/security/cve/CVE-2023-53674/ SUSE CVE CVE-2023-53674 page https://www.suse.com/security/cve/CVE-2023-53681/ SUSE CVE CVE-2023-53681 page https://www.suse.com/security/cve/CVE-2023-53686/ SUSE CVE CVE-2023-53686 page https://www.suse.com/security/cve/CVE-2023-53687/ SUSE CVE CVE-2023-53687 page https://www.suse.com/security/cve/CVE-2023-53693/ SUSE CVE CVE-2023-53693 page https://www.suse.com/security/cve/CVE-2023-53697/ SUSE CVE CVE-2023-53697 page https://www.suse.com/security/cve/CVE-2023-53698/ SUSE CVE CVE-2023-53698 page https://www.suse.com/security/cve/CVE-2023-53699/ SUSE CVE CVE-2023-53699 page https://www.suse.com/security/cve/CVE-2023-53703/ SUSE CVE CVE-2023-53703 page https://www.suse.com/security/cve/CVE-2023-53704/ SUSE CVE CVE-2023-53704 page https://www.suse.com/security/cve/CVE-2023-53707/ SUSE CVE CVE-2023-53707 page https://www.suse.com/security/cve/CVE-2023-53708/ SUSE CVE CVE-2023-53708 page https://www.suse.com/security/cve/CVE-2023-53711/ SUSE CVE CVE-2023-53711 page https://www.suse.com/security/cve/CVE-2023-53713/ SUSE CVE CVE-2023-53713 page https://www.suse.com/security/cve/CVE-2023-53718/ SUSE CVE CVE-2023-53718 page https://www.suse.com/security/cve/CVE-2023-53721/ SUSE CVE CVE-2023-53721 page https://www.suse.com/security/cve/CVE-2023-53722/ SUSE CVE CVE-2023-53722 page https://www.suse.com/security/cve/CVE-2023-53725/ SUSE CVE CVE-2023-53725 page https://www.suse.com/security/cve/CVE-2023-53726/ SUSE CVE CVE-2023-53726 page https://www.suse.com/security/cve/CVE-2023-53727/ SUSE CVE CVE-2023-53727 page https://www.suse.com/security/cve/CVE-2023-53728/ SUSE CVE CVE-2023-53728 page https://www.suse.com/security/cve/CVE-2023-53729/ SUSE CVE CVE-2023-53729 page https://www.suse.com/security/cve/CVE-2023-53730/ SUSE CVE CVE-2023-53730 page https://www.suse.com/security/cve/CVE-2023-53731/ SUSE CVE CVE-2023-53731 page https://www.suse.com/security/cve/CVE-2023-53733/ SUSE CVE CVE-2023-53733 page https://www.suse.com/security/cve/CVE-2024-26584/ SUSE CVE CVE-2024-26584 page https://www.suse.com/security/cve/CVE-2024-58240/ SUSE CVE CVE-2024-58240 page https://www.suse.com/security/cve/CVE-2025-38008/ SUSE CVE CVE-2025-38008 page https://www.suse.com/security/cve/CVE-2025-38465/ SUSE CVE CVE-2025-38465 page https://www.suse.com/security/cve/CVE-2025-38539/ SUSE CVE CVE-2025-38539 page https://www.suse.com/security/cve/CVE-2025-38552/ SUSE CVE CVE-2025-38552 page https://www.suse.com/security/cve/CVE-2025-38653/ SUSE CVE CVE-2025-38653 page https://www.suse.com/security/cve/CVE-2025-38680/ SUSE CVE CVE-2025-38680 page https://www.suse.com/security/cve/CVE-2025-38681/ SUSE CVE CVE-2025-38681 page https://www.suse.com/security/cve/CVE-2025-38683/ SUSE CVE CVE-2025-38683 page https://www.suse.com/security/cve/CVE-2025-38685/ SUSE CVE CVE-2025-38685 page https://www.suse.com/security/cve/CVE-2025-38687/ SUSE CVE CVE-2025-38687 page https://www.suse.com/security/cve/CVE-2025-38691/ SUSE CVE CVE-2025-38691 page https://www.suse.com/security/cve/CVE-2025-38692/ SUSE CVE CVE-2025-38692 page https://www.suse.com/security/cve/CVE-2025-38693/ SUSE CVE CVE-2025-38693 page https://www.suse.com/security/cve/CVE-2025-38694/ SUSE CVE CVE-2025-38694 page https://www.suse.com/security/cve/CVE-2025-38695/ SUSE CVE CVE-2025-38695 page https://www.suse.com/security/cve/CVE-2025-38697/ SUSE CVE CVE-2025-38697 page https://www.suse.com/security/cve/CVE-2025-38698/ SUSE CVE CVE-2025-38698 page https://www.suse.com/security/cve/CVE-2025-38699/ SUSE CVE CVE-2025-38699 page https://www.suse.com/security/cve/CVE-2025-38700/ SUSE CVE CVE-2025-38700 page https://www.suse.com/security/cve/CVE-2025-38702/ SUSE CVE CVE-2025-38702 page https://www.suse.com/security/cve/CVE-2025-38706/ SUSE CVE CVE-2025-38706 page https://www.suse.com/security/cve/CVE-2025-38712/ SUSE CVE CVE-2025-38712 page https://www.suse.com/security/cve/CVE-2025-38713/ SUSE CVE CVE-2025-38713 page https://www.suse.com/security/cve/CVE-2025-38714/ SUSE CVE CVE-2025-38714 page https://www.suse.com/security/cve/CVE-2025-38715/ SUSE CVE CVE-2025-38715 page https://www.suse.com/security/cve/CVE-2025-38718/ SUSE CVE CVE-2025-38718 page https://www.suse.com/security/cve/CVE-2025-38724/ SUSE CVE CVE-2025-38724 page https://www.suse.com/security/cve/CVE-2025-38725/ SUSE CVE CVE-2025-38725 page https://www.suse.com/security/cve/CVE-2025-38727/ SUSE CVE CVE-2025-38727 page https://www.suse.com/security/cve/CVE-2025-38729/ SUSE CVE CVE-2025-38729 page https://www.suse.com/security/cve/CVE-2025-38734/ SUSE CVE CVE-2025-38734 page https://www.suse.com/security/cve/CVE-2025-38735/ SUSE CVE CVE-2025-38735 page https://www.suse.com/security/cve/CVE-2025-38736/ SUSE CVE CVE-2025-38736 page https://www.suse.com/security/cve/CVE-2025-39673/ SUSE CVE CVE-2025-39673 page https://www.suse.com/security/cve/CVE-2025-39675/ SUSE CVE CVE-2025-39675 page https://www.suse.com/security/cve/CVE-2025-39676/ SUSE CVE CVE-2025-39676 page https://www.suse.com/security/cve/CVE-2025-39679/ SUSE CVE CVE-2025-39679 page https://www.suse.com/security/cve/CVE-2025-39683/ SUSE CVE CVE-2025-39683 page https://www.suse.com/security/cve/CVE-2025-39684/ SUSE CVE CVE-2025-39684 page https://www.suse.com/security/cve/CVE-2025-39685/ SUSE CVE CVE-2025-39685 page https://www.suse.com/security/cve/CVE-2025-39686/ SUSE CVE CVE-2025-39686 page https://www.suse.com/security/cve/CVE-2025-39693/ SUSE CVE CVE-2025-39693 page https://www.suse.com/security/cve/CVE-2025-39694/ SUSE CVE CVE-2025-39694 page https://www.suse.com/security/cve/CVE-2025-39697/ SUSE CVE CVE-2025-39697 page https://www.suse.com/security/cve/CVE-2025-39701/ SUSE CVE CVE-2025-39701 page https://www.suse.com/security/cve/CVE-2025-39702/ SUSE CVE CVE-2025-39702 page https://www.suse.com/security/cve/CVE-2025-39706/ SUSE CVE CVE-2025-39706 page https://www.suse.com/security/cve/CVE-2025-39709/ SUSE CVE CVE-2025-39709 page https://www.suse.com/security/cve/CVE-2025-39710/ SUSE CVE CVE-2025-39710 page https://www.suse.com/security/cve/CVE-2025-39713/ SUSE CVE CVE-2025-39713 page https://www.suse.com/security/cve/CVE-2025-39714/ SUSE CVE CVE-2025-39714 page https://www.suse.com/security/cve/CVE-2025-39719/ SUSE CVE CVE-2025-39719 page https://www.suse.com/security/cve/CVE-2025-39721/ SUSE CVE CVE-2025-39721 page https://www.suse.com/security/cve/CVE-2025-39724/ SUSE CVE CVE-2025-39724 page https://www.suse.com/security/cve/CVE-2025-39726/ SUSE CVE CVE-2025-39726 page https://www.suse.com/security/cve/CVE-2025-39730/ SUSE CVE CVE-2025-39730 page https://www.suse.com/security/cve/CVE-2025-39732/ SUSE CVE CVE-2025-39732 page https://www.suse.com/security/cve/CVE-2025-39739/ SUSE CVE CVE-2025-39739 page https://www.suse.com/security/cve/CVE-2025-39742/ SUSE CVE CVE-2025-39742 page https://www.suse.com/security/cve/CVE-2025-39743/ SUSE CVE CVE-2025-39743 page https://www.suse.com/security/cve/CVE-2025-39750/ SUSE CVE CVE-2025-39750 page https://www.suse.com/security/cve/CVE-2025-39751/ SUSE CVE CVE-2025-39751 page https://www.suse.com/security/cve/CVE-2025-39756/ SUSE CVE CVE-2025-39756 page https://www.suse.com/security/cve/CVE-2025-39757/ SUSE CVE CVE-2025-39757 page https://www.suse.com/security/cve/CVE-2025-39758/ SUSE CVE CVE-2025-39758 page https://www.suse.com/security/cve/CVE-2025-39759/ SUSE CVE CVE-2025-39759 page https://www.suse.com/security/cve/CVE-2025-39760/ SUSE CVE CVE-2025-39760 page https://www.suse.com/security/cve/CVE-2025-39761/ SUSE CVE CVE-2025-39761 page https://www.suse.com/security/cve/CVE-2025-39763/ SUSE CVE CVE-2025-39763 page https://www.suse.com/security/cve/CVE-2025-39772/ SUSE CVE CVE-2025-39772 page https://www.suse.com/security/cve/CVE-2025-39783/ SUSE CVE CVE-2025-39783 page https://www.suse.com/security/cve/CVE-2025-39790/ SUSE CVE CVE-2025-39790 page https://www.suse.com/security/cve/CVE-2025-39794/ SUSE CVE CVE-2025-39794 page https://www.suse.com/security/cve/CVE-2025-39797/ SUSE CVE CVE-2025-39797 page https://www.suse.com/security/cve/CVE-2025-39798/ SUSE CVE CVE-2025-39798 page https://www.suse.com/security/cve/CVE-2025-39800/ SUSE CVE CVE-2025-39800 page https://www.suse.com/security/cve/CVE-2025-39801/ SUSE CVE CVE-2025-39801 page https://www.suse.com/security/cve/CVE-2025-39806/ SUSE CVE CVE-2025-39806 page https://www.suse.com/security/cve/CVE-2025-39808/ SUSE CVE CVE-2025-39808 page https://www.suse.com/security/cve/CVE-2025-39810/ SUSE CVE CVE-2025-39810 page https://www.suse.com/security/cve/CVE-2025-39812/ SUSE CVE CVE-2025-39812 page https://www.suse.com/security/cve/CVE-2025-39813/ SUSE CVE CVE-2025-39813 page https://www.suse.com/security/cve/CVE-2025-39824/ SUSE CVE CVE-2025-39824 page https://www.suse.com/security/cve/CVE-2025-39826/ SUSE CVE CVE-2025-39826 page https://www.suse.com/security/cve/CVE-2025-39827/ SUSE CVE CVE-2025-39827 page https://www.suse.com/security/cve/CVE-2025-39828/ SUSE CVE CVE-2025-39828 page https://www.suse.com/security/cve/CVE-2025-39832/ SUSE CVE CVE-2025-39832 page https://www.suse.com/security/cve/CVE-2025-39833/ SUSE CVE CVE-2025-39833 page https://www.suse.com/security/cve/CVE-2025-39839/ SUSE CVE CVE-2025-39839 page https://www.suse.com/security/cve/CVE-2025-39841/ SUSE CVE CVE-2025-39841 page https://www.suse.com/security/cve/CVE-2025-39844/ SUSE CVE CVE-2025-39844 page https://www.suse.com/security/cve/CVE-2025-39845/ SUSE CVE CVE-2025-39845 page https://www.suse.com/security/cve/CVE-2025-39846/ SUSE CVE CVE-2025-39846 page https://www.suse.com/security/cve/CVE-2025-39847/ SUSE CVE CVE-2025-39847 page https://www.suse.com/security/cve/CVE-2025-39848/ SUSE CVE CVE-2025-39848 page https://www.suse.com/security/cve/CVE-2025-39849/ SUSE CVE CVE-2025-39849 page https://www.suse.com/security/cve/CVE-2025-39850/ SUSE CVE CVE-2025-39850 page https://www.suse.com/security/cve/CVE-2025-39851/ SUSE CVE CVE-2025-39851 page https://www.suse.com/security/cve/CVE-2025-39853/ SUSE CVE CVE-2025-39853 page https://www.suse.com/security/cve/CVE-2025-39854/ SUSE CVE CVE-2025-39854 page https://www.suse.com/security/cve/CVE-2025-39860/ SUSE CVE CVE-2025-39860 page https://www.suse.com/security/cve/CVE-2025-39861/ SUSE CVE CVE-2025-39861 page https://www.suse.com/security/cve/CVE-2025-39863/ SUSE CVE CVE-2025-39863 page https://www.suse.com/security/cve/CVE-2025-39864/ SUSE CVE CVE-2025-39864 page https://www.suse.com/security/cve/CVE-2025-39866/ SUSE CVE CVE-2025-39866 page https://www.suse.com/security/cve/CVE-2025-39869/ SUSE CVE CVE-2025-39869 page https://www.suse.com/security/cve/CVE-2025-39870/ SUSE CVE CVE-2025-39870 page https://www.suse.com/security/cve/CVE-2025-39871/ SUSE CVE CVE-2025-39871 page https://www.suse.com/security/cve/CVE-2025-39873/ SUSE CVE CVE-2025-39873 page https://www.suse.com/security/cve/CVE-2025-39876/ SUSE CVE CVE-2025-39876 page https://www.suse.com/security/cve/CVE-2025-39881/ SUSE CVE CVE-2025-39881 page https://www.suse.com/security/cve/CVE-2025-39882/ SUSE CVE CVE-2025-39882 page https://www.suse.com/security/cve/CVE-2025-39889/ SUSE CVE CVE-2025-39889 page https://www.suse.com/security/cve/CVE-2025-39891/ SUSE CVE CVE-2025-39891 page https://www.suse.com/security/cve/CVE-2025-39895/ SUSE CVE CVE-2025-39895 page https://www.suse.com/security/cve/CVE-2025-39900/ SUSE CVE CVE-2025-39900 page https://www.suse.com/security/cve/CVE-2025-39902/ SUSE CVE CVE-2025-39902 page https://www.suse.com/security/cve/CVE-2025-39907/ SUSE CVE CVE-2025-39907 page https://www.suse.com/security/cve/CVE-2025-39911/ SUSE CVE CVE-2025-39911 page https://www.suse.com/security/cve/CVE-2025-39920/ SUSE CVE CVE-2025-39920 page https://www.suse.com/security/cve/CVE-2025-39923/ SUSE CVE CVE-2025-39923 page https://www.suse.com/security/cve/CVE-2025-39925/ SUSE CVE CVE-2025-39925 page https://www.suse.com/security/cve/CVE-2025-39931/ SUSE CVE CVE-2025-39931 page https://www.suse.com/security/cve/CVE-2025-39934/ SUSE CVE CVE-2025-39934 page https://www.suse.com/security/cve/CVE-2025-39937/ SUSE CVE CVE-2025-39937 page https://www.suse.com/security/cve/CVE-2025-39938/ SUSE CVE CVE-2025-39938 page https://www.suse.com/security/cve/CVE-2025-39945/ SUSE CVE CVE-2025-39945 page https://www.suse.com/security/cve/CVE-2025-39946/ SUSE CVE CVE-2025-39946 page https://www.suse.com/security/cve/CVE-2025-39947/ SUSE CVE CVE-2025-39947 page https://www.suse.com/security/cve/CVE-2025-39948/ SUSE CVE CVE-2025-39948 page https://www.suse.com/security/cve/CVE-2025-39949/ SUSE CVE CVE-2025-39949 page https://www.suse.com/security/cve/CVE-2025-39952/ SUSE CVE CVE-2025-39952 page https://www.suse.com/security/cve/CVE-2025-39955/ SUSE CVE CVE-2025-39955 page https://www.suse.com/security/cve/CVE-2025-39957/ SUSE CVE CVE-2025-39957 page https://www.suse.com/security/cve/CVE-2025-39965/ SUSE CVE CVE-2025-39965 page https://www.suse.com/security/cve/CVE-2025-39967/ SUSE CVE CVE-2025-39967 page https://www.suse.com/security/cve/CVE-2025-39968/ SUSE CVE CVE-2025-39968 page https://www.suse.com/security/cve/CVE-2025-39969/ SUSE CVE CVE-2025-39969 page https://www.suse.com/security/cve/CVE-2025-39970/ SUSE CVE CVE-2025-39970 page https://www.suse.com/security/cve/CVE-2025-39971/ SUSE CVE CVE-2025-39971 page https://www.suse.com/security/cve/CVE-2025-39972/ SUSE CVE CVE-2025-39972 page https://www.suse.com/security/cve/CVE-2025-39973/ SUSE CVE CVE-2025-39973 page https://www.suse.com/security/cve/CVE-2025-39978/ SUSE CVE CVE-2025-39978 page https://www.suse.com/security/cve/CVE-2025-39981/ SUSE CVE CVE-2025-39981 page https://www.suse.com/security/cve/CVE-2025-39982/ SUSE CVE CVE-2025-39982 page https://www.suse.com/security/cve/CVE-2025-39984/ SUSE CVE CVE-2025-39984 page https://www.suse.com/security/cve/CVE-2025-39985/ SUSE CVE CVE-2025-39985 page https://www.suse.com/security/cve/CVE-2025-39986/ SUSE CVE CVE-2025-39986 page https://www.suse.com/security/cve/CVE-2025-39987/ SUSE CVE CVE-2025-39987 page https://www.suse.com/security/cve/CVE-2025-39988/ SUSE CVE CVE-2025-39988 page https://www.suse.com/security/cve/CVE-2025-39991/ SUSE CVE CVE-2025-39991 page https://www.suse.com/security/cve/CVE-2025-39993/ SUSE CVE CVE-2025-39993 page https://www.suse.com/security/cve/CVE-2025-39994/ SUSE CVE CVE-2025-39994 page https://www.suse.com/security/cve/CVE-2025-39995/ SUSE CVE CVE-2025-39995 page https://www.suse.com/security/cve/CVE-2025-39996/ SUSE CVE CVE-2025-39996 page https://www.suse.com/security/cve/CVE-2025-39997/ SUSE CVE CVE-2025-39997 page https://www.suse.com/security/cve/CVE-2025-40000/ SUSE CVE CVE-2025-40000 page https://www.suse.com/security/cve/CVE-2025-40005/ SUSE CVE CVE-2025-40005 page https://www.suse.com/security/cve/CVE-2025-40010/ SUSE CVE CVE-2025-40010 page https://www.suse.com/security/cve/CVE-2025-40011/ SUSE CVE CVE-2025-40011 page https://www.suse.com/security/cve/CVE-2025-40012/ SUSE CVE CVE-2025-40012 page https://www.suse.com/security/cve/CVE-2025-40013/ SUSE CVE CVE-2025-40013 page https://www.suse.com/security/cve/CVE-2025-40016/ SUSE CVE CVE-2025-40016 page https://www.suse.com/security/cve/CVE-2025-40018/ SUSE CVE CVE-2025-40018 page https://www.suse.com/security/cve/CVE-2025-40019/ SUSE CVE CVE-2025-40019 page https://www.suse.com/security/cve/CVE-2025-40020/ SUSE CVE CVE-2025-40020 page https://www.suse.com/security/cve/CVE-2025-40029/ SUSE CVE CVE-2025-40029 page https://www.suse.com/security/cve/CVE-2025-40032/ SUSE CVE CVE-2025-40032 page https://www.suse.com/security/cve/CVE-2025-40035/ SUSE CVE CVE-2025-40035 page https://www.suse.com/security/cve/CVE-2025-40036/ SUSE CVE CVE-2025-40036 page https://www.suse.com/security/cve/CVE-2025-40037/ SUSE CVE CVE-2025-40037 page https://www.suse.com/security/cve/CVE-2025-40043/ SUSE CVE CVE-2025-40043 page https://www.suse.com/security/cve/CVE-2025-40044/ SUSE CVE CVE-2025-40044 page https://www.suse.com/security/cve/CVE-2025-40049/ SUSE CVE CVE-2025-40049 page https://www.suse.com/security/cve/CVE-2025-40051/ SUSE CVE CVE-2025-40051 page https://www.suse.com/security/cve/CVE-2025-40052/ SUSE CVE CVE-2025-40052 page https://www.suse.com/security/cve/CVE-2025-40056/ SUSE CVE CVE-2025-40056 page https://www.suse.com/security/cve/CVE-2025-40058/ SUSE CVE CVE-2025-40058 page https://www.suse.com/security/cve/CVE-2025-40060/ SUSE CVE CVE-2025-40060 page https://www.suse.com/security/cve/CVE-2025-40061/ SUSE CVE CVE-2025-40061 page https://www.suse.com/security/cve/CVE-2025-40062/ SUSE CVE CVE-2025-40062 page https://www.suse.com/security/cve/CVE-2025-40071/ SUSE CVE CVE-2025-40071 page https://www.suse.com/security/cve/CVE-2025-40078/ SUSE CVE CVE-2025-40078 page https://www.suse.com/security/cve/CVE-2025-40082/ SUSE CVE CVE-2025-40082 page https://www.suse.com/security/cve/CVE-2025-40085/ SUSE CVE CVE-2025-40085 page https://www.suse.com/security/cve/CVE-2025-40087/ SUSE CVE CVE-2025-40087 page https://www.suse.com/security/cve/CVE-2025-40088/ SUSE CVE CVE-2025-40088 page https://www.suse.com/security/cve/CVE-2025-40091/ SUSE CVE CVE-2025-40091 page https://www.suse.com/security/cve/CVE-2025-40096/ SUSE CVE CVE-2025-40096 page https://www.suse.com/security/cve/CVE-2025-40100/ SUSE CVE CVE-2025-40100 page https://www.suse.com/security/cve/CVE-2025-40104/ SUSE CVE CVE-2025-40104 page SUSE Linux Enterprise Live Patching 15 SP7 SUSE Real Time Module 15 SP7 cluster-md-kmp-rt-6.4.0-150700.7.22.1 dlm-kmp-rt-6.4.0-150700.7.22.1 gfs2-kmp-rt-6.4.0-150700.7.22.1 kernel-devel-rt-6.4.0-150700.7.22.1 kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 kernel-rt-6.4.0-150700.7.22.1 kernel-rt-devel-6.4.0-150700.7.22.1 kernel-rt-extra-6.4.0-150700.7.22.1 kernel-rt-livepatch-6.4.0-150700.7.22.1 kernel-rt-livepatch-devel-6.4.0-150700.7.22.1 kernel-rt-optional-6.4.0-150700.7.22.1 kernel-rt-vdso-6.4.0-150700.7.22.1 kernel-source-rt-6.4.0-150700.7.22.1 kernel-syms-rt-6.4.0-150700.7.22.1 kselftests-kmp-rt-6.4.0-150700.7.22.1 ocfs2-kmp-rt-6.4.0-150700.7.22.1 reiserfs-kmp-rt-6.4.0-150700.7.22.1 kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 as a component of SUSE Linux Enterprise Live Patching 15 SP7 cluster-md-kmp-rt-6.4.0-150700.7.22.1 as a component of SUSE Real Time Module 15 SP7 dlm-kmp-rt-6.4.0-150700.7.22.1 as a component of SUSE Real Time Module 15 SP7 gfs2-kmp-rt-6.4.0-150700.7.22.1 as a component of SUSE Real Time Module 15 SP7 kernel-devel-rt-6.4.0-150700.7.22.1 as a component of SUSE Real Time Module 15 SP7 kernel-rt-6.4.0-150700.7.22.1 as a component of SUSE Real Time Module 15 SP7 kernel-rt-devel-6.4.0-150700.7.22.1 as a component of SUSE Real Time Module 15 SP7 kernel-source-rt-6.4.0-150700.7.22.1 as a component of SUSE Real Time Module 15 SP7 kernel-syms-rt-6.4.0-150700.7.22.1 as a component of SUSE Real Time Module 15 SP7 ocfs2-kmp-rt-6.4.0-150700.7.22.1 as a component of SUSE Real Time Module 15 SP7 Linux Kernel nftables Use-After-Free Local Privilege Escalation Vulnerability; `nft_chain_lookup_byid()` failed to check whether a chain was active and CAP_NET_ADMIN is in any user or network namespace CVE-2023-31248 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-31248.html CVE-2023-31248 https://bugzilla.suse.com/1213061 SUSE Bug 1213061 https://bugzilla.suse.com/1213064 SUSE Bug 1213064 A flaw was found in the Linux kernel's IP framework for transforming packets (XFRM subsystem). This issue may allow a malicious user with CAP_NET_ADMIN privileges to directly dereference a NULL pointer in xfrm_update_ae_params(), leading to a possible kernel crash and denial of service. CVE-2023-3772 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-3772.html CVE-2023-3772 https://bugzilla.suse.com/1213666 SUSE Bug 1213666 An out-of-bounds read vulnerability was found in Netfilter Connection Tracking (conntrack) in the Linux kernel. This flaw allows a remote user to disclose sensitive information via the DCCP protocol. CVE-2023-39197 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-39197.html CVE-2023-39197 https://bugzilla.suse.com/1216976 SUSE Bug 1216976 https://bugzilla.suse.com/1220015 SUSE Bug 1220015 An array indexing vulnerability was found in the netfilter subsystem of the Linux kernel. A missing macro could lead to a miscalculation of the `h->nets` array offset, providing attackers with the primitive to arbitrarily increment/decrement a memory buffer out-of-bound. This issue may allow a local user to crash the system or potentially escalate their privileges on the system. CVE-2023-42753 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-42753.html CVE-2023-42753 https://bugzilla.suse.com/1215150 SUSE Bug 1215150 https://bugzilla.suse.com/1218613 SUSE Bug 1218613 In the Linux kernel, the following vulnerability has been resolved: xfrm: add NULL check in xfrm_update_ae_params Normally, x->replay_esn and x->preplay_esn should be allocated at xfrm_alloc_replay_state_esn(...) in xfrm_state_construct(...), hence the xfrm_update_ae_params(...) is okay to update them. However, the current implementation of xfrm_new_ae(...) allows a malicious user to directly dereference a NULL pointer and crash the kernel like below. BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 8253067 P4D 8253067 PUD 8e0e067 PMD 0 Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 PID: 98 Comm: poc.npd Not tainted 6.4.0-rc7-00072-gdad9774deaf1 #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.o4 RIP: 0010:memcpy_orig+0xad/0x140 Code: e8 4c 89 5f e0 48 8d 7f e0 73 d2 83 c2 20 48 29 d6 48 29 d7 83 fa 10 72 34 4c 8b 06 4c 8b 4e 08 c RSP: 0018:ffff888008f57658 EFLAGS: 00000202 RAX: 0000000000000000 RBX: ffff888008bd0000 RCX: ffffffff8238e571 RDX: 0000000000000018 RSI: ffff888007f64844 RDI: 0000000000000000 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff888008f57818 R13: ffff888007f64aa4 R14: 0000000000000000 R15: 0000000000000000 FS: 00000000014013c0(0000) GS:ffff88806d600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000054d8000 CR4: 00000000000006f0 Call Trace: <TASK> ? __die+0x1f/0x70 ? page_fault_oops+0x1e8/0x500 ? __pfx_is_prefetch.constprop.0+0x10/0x10 ? __pfx_page_fault_oops+0x10/0x10 ? _raw_spin_unlock_irqrestore+0x11/0x40 ? fixup_exception+0x36/0x460 ? _raw_spin_unlock_irqrestore+0x11/0x40 ? exc_page_fault+0x5e/0xc0 ? asm_exc_page_fault+0x26/0x30 ? xfrm_update_ae_params+0xd1/0x260 ? memcpy_orig+0xad/0x140 ? __pfx__raw_spin_lock_bh+0x10/0x10 xfrm_update_ae_params+0xe7/0x260 xfrm_new_ae+0x298/0x4e0 ? __pfx_xfrm_new_ae+0x10/0x10 ? __pfx_xfrm_new_ae+0x10/0x10 xfrm_user_rcv_msg+0x25a/0x410 ? __pfx_xfrm_user_rcv_msg+0x10/0x10 ? __alloc_skb+0xcf/0x210 ? stack_trace_save+0x90/0xd0 ? filter_irq_stacks+0x1c/0x70 ? __stack_depot_save+0x39/0x4e0 ? __kasan_slab_free+0x10a/0x190 ? kmem_cache_free+0x9c/0x340 ? netlink_recvmsg+0x23c/0x660 ? sock_recvmsg+0xeb/0xf0 ? __sys_recvfrom+0x13c/0x1f0 ? __x64_sys_recvfrom+0x71/0x90 ? do_syscall_64+0x3f/0x90 ? entry_SYSCALL_64_after_hwframe+0x72/0xdc ? copyout+0x3e/0x50 netlink_rcv_skb+0xd6/0x210 ? __pfx_xfrm_user_rcv_msg+0x10/0x10 ? __pfx_netlink_rcv_skb+0x10/0x10 ? __pfx_sock_has_perm+0x10/0x10 ? mutex_lock+0x8d/0xe0 ? __pfx_mutex_lock+0x10/0x10 xfrm_netlink_rcv+0x44/0x50 netlink_unicast+0x36f/0x4c0 ? __pfx_netlink_unicast+0x10/0x10 ? netlink_recvmsg+0x500/0x660 netlink_sendmsg+0x3b7/0x700 This Null-ptr-deref bug is assigned CVE-2023-3772. And this commit adds additional NULL check in xfrm_update_ae_params to fix the NPD. CVE-2023-53147 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53147.html CVE-2023-53147 https://bugzilla.suse.com/1249880 SUSE Bug 1249880 In the Linux kernel, the following vulnerability has been resolved: igb: Fix igb_down hung on surprise removal In a setup where a Thunderbolt hub connects to Ethernet and a display through USB Type-C, users may experience a hung task timeout when they remove the cable between the PC and the Thunderbolt hub. This is because the igb_down function is called multiple times when the Thunderbolt hub is unplugged. For example, the igb_io_error_detected triggers the first call, and the igb_remove triggers the second call. The second call to igb_down will block at napi_synchronize. Here's the call trace: __schedule+0x3b0/0xddb ? __mod_timer+0x164/0x5d3 schedule+0x44/0xa8 schedule_timeout+0xb2/0x2a4 ? run_local_timers+0x4e/0x4e msleep+0x31/0x38 igb_down+0x12c/0x22a [igb 6615058754948bfde0bf01429257eb59f13030d4] __igb_close+0x6f/0x9c [igb 6615058754948bfde0bf01429257eb59f13030d4] igb_close+0x23/0x2b [igb 6615058754948bfde0bf01429257eb59f13030d4] __dev_close_many+0x95/0xec dev_close_many+0x6e/0x103 unregister_netdevice_many+0x105/0x5b1 unregister_netdevice_queue+0xc2/0x10d unregister_netdev+0x1c/0x23 igb_remove+0xa7/0x11c [igb 6615058754948bfde0bf01429257eb59f13030d4] pci_device_remove+0x3f/0x9c device_release_driver_internal+0xfe/0x1b4 pci_stop_bus_device+0x5b/0x7f pci_stop_bus_device+0x30/0x7f pci_stop_bus_device+0x30/0x7f pci_stop_and_remove_bus_device+0x12/0x19 pciehp_unconfigure_device+0x76/0xe9 pciehp_disable_slot+0x6e/0x131 pciehp_handle_presence_or_link_change+0x7a/0x3f7 pciehp_ist+0xbe/0x194 irq_thread_fn+0x22/0x4d ? irq_thread+0x1fd/0x1fd irq_thread+0x17b/0x1fd ? irq_forced_thread_fn+0x5f/0x5f kthread+0x142/0x153 ? __irq_get_irqchip_state+0x46/0x46 ? kthread_associate_blkcg+0x71/0x71 ret_from_fork+0x1f/0x30 In this case, igb_io_error_detected detaches the network interface and requests a PCIE slot reset, however, the PCIE reset callback is not being invoked and thus the Ethernet connection breaks down. As the PCIE error in this case is a non-fatal one, requesting a slot reset can be avoided. This patch fixes the task hung issue and preserves Ethernet connection by ignoring non-fatal PCIE errors. CVE-2023-53148 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53148.html CVE-2023-53148 https://bugzilla.suse.com/1249842 SUSE Bug 1249842 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Pointer may be dereferenced Klocwork tool reported pointer 'rport' returned from call to function fc_bsg_to_rport() may be NULL and will be dereferenced. Add a fix to validate rport before dereferencing. CVE-2023-53150 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53150.html CVE-2023-53150 https://bugzilla.suse.com/1249853 SUSE Bug 1249853 In the Linux kernel, the following vulnerability has been resolved: md/raid10: prevent soft lockup while flush writes Currently, there is no limit for raid1/raid10 plugged bio. While flushing writes, raid1 has cond_resched() while raid10 doesn't, and too many writes can cause soft lockup. Follow up soft lockup can be triggered easily with writeback test for raid10 with ramdisks: watchdog: BUG: soft lockup - CPU#10 stuck for 27s! [md0_raid10:1293] Call Trace: <TASK> call_rcu+0x16/0x20 put_object+0x41/0x80 __delete_object+0x50/0x90 delete_object_full+0x2b/0x40 kmemleak_free+0x46/0xa0 slab_free_freelist_hook.constprop.0+0xed/0x1a0 kmem_cache_free+0xfd/0x300 mempool_free_slab+0x1f/0x30 mempool_free+0x3a/0x100 bio_free+0x59/0x80 bio_put+0xcf/0x2c0 free_r10bio+0xbf/0xf0 raid_end_bio_io+0x78/0xb0 one_write_done+0x8a/0xa0 raid10_end_write_request+0x1b4/0x430 bio_endio+0x175/0x320 brd_submit_bio+0x3b9/0x9b7 [brd] __submit_bio+0x69/0xe0 submit_bio_noacct_nocheck+0x1e6/0x5a0 submit_bio_noacct+0x38c/0x7e0 flush_pending_writes+0xf0/0x240 raid10d+0xac/0x1ed0 Fix the problem by adding cond_resched() to raid10 like what raid1 did. Note that unlimited plugged bio still need to be optimized, for example, in the case of lots of dirty pages writeback, this will take lots of memory and io will spend a long time in plug, hence io latency is bad. CVE-2023-53151 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53151.html CVE-2023-53151 https://bugzilla.suse.com/1249865 SUSE Bug 1249865 In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix calltrace warning in amddrm_buddy_fini The following call trace is observed when removing the amdgpu driver, which is caused by that BOs allocated for psp are not freed until removing. [61811.450562] RIP: 0010:amddrm_buddy_fini.cold+0x29/0x47 [amddrm_buddy] [61811.450577] Call Trace: [61811.450577] <TASK> [61811.450579] amdgpu_vram_mgr_fini+0x135/0x1c0 [amdgpu] [61811.450728] amdgpu_ttm_fini+0x207/0x290 [amdgpu] [61811.450870] amdgpu_bo_fini+0x27/0xa0 [amdgpu] [61811.451012] gmc_v9_0_sw_fini+0x4a/0x60 [amdgpu] [61811.451166] amdgpu_device_fini_sw+0x117/0x520 [amdgpu] [61811.451306] amdgpu_driver_release_kms+0x16/0x30 [amdgpu] [61811.451447] devm_drm_dev_init_release+0x4d/0x80 [drm] [61811.451466] devm_action_release+0x15/0x20 [61811.451469] release_nodes+0x40/0xb0 [61811.451471] devres_release_all+0x9b/0xd0 [61811.451473] __device_release_driver+0x1bb/0x2a0 [61811.451476] driver_detach+0xf3/0x140 [61811.451479] bus_remove_driver+0x6c/0xf0 [61811.451481] driver_unregister+0x31/0x60 [61811.451483] pci_unregister_driver+0x40/0x90 [61811.451486] amdgpu_exit+0x15/0x447 [amdgpu] For smu v13_0_2, if the GPU supports xgmi, refer to commit f5c7e7797060 ("drm/amdgpu: Adjust removal control flow for smu v13_0_2"), it will run gpu recover in AMDGPU_RESET_FOR_DEVICE_REMOVE mode when removing, which makes all devices in hive list have hw reset but no resume except the basic ip blocks, then other ip blocks will not call .hw_fini according to ip_block.status.hw. Since psp_free_shared_bufs just includes some software operations, so move it to psp_sw_fini. CVE-2023-53152 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53152.html CVE-2023-53152 https://bugzilla.suse.com/1249883 SUSE Bug 1249883 In the Linux kernel, the following vulnerability has been resolved: udf: Fix uninitialized array access for some pathnames For filenames that begin with . and are between 2 and 5 characters long, UDF charset conversion code would read uninitialized memory in the output buffer. The only practical impact is that the name may be prepended a "unification hash" when it is not actually needed but still it is good to fix this. CVE-2023-53165 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53165.html CVE-2023-53165 https://bugzilla.suse.com/1250395 SUSE Bug 1250395 In the Linux kernel, the following vulnerability has been resolved: tracing: Fix null pointer dereference in tracing_err_log_open() Fix an issue in function 'tracing_err_log_open'. The function doesn't call 'seq_open' if the file is opened only with write permissions, which results in 'file->private_data' being left as null. If we then use 'lseek' on that opened file, 'seq_lseek' dereferences 'file->private_data' in 'mutex_lock(&m->lock)', resulting in a kernel panic. Writing to this node requires root privileges, therefore this bug has very little security impact. Tracefs node: /sys/kernel/tracing/error_log Example Kernel panic: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000038 Call trace: mutex_lock+0x30/0x110 seq_lseek+0x34/0xb8 __arm64_sys_lseek+0x6c/0xb8 invoke_syscall+0x58/0x13c el0_svc_common+0xc4/0x10c do_el0_svc+0x24/0x98 el0_svc+0x24/0x88 el0t_64_sync_handler+0x84/0xe4 el0t_64_sync+0x1b4/0x1b8 Code: d503201f aa0803e0 aa1f03e1 aa0103e9 (c8e97d02) ---[ end trace 561d1b49c12cf8a5 ]--- Kernel panic - not syncing: Oops: Fatal exception CVE-2023-53167 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53167.html CVE-2023-53167 https://bugzilla.suse.com/1249712 SUSE Bug 1249712 In the Linux kernel, the following vulnerability has been resolved: net: dsa: Removed unneeded of_node_put in felix_parse_ports_node Remove unnecessary of_node_put from the continue path to prevent child node from being released twice, which could avoid resource leak or other unexpected issues. CVE-2023-53170 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53170.html CVE-2023-53170 https://bugzilla.suse.com/1249850 SUSE Bug 1249850 In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix possible memory leak if device_add() fails If device_add() returns error, the name allocated by dev_set_name() needs be freed. As the comment of device_add() says, put_device() should be used to decrease the reference count in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanp(). CVE-2023-53174 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53174.html CVE-2023-53174 https://bugzilla.suse.com/1250024 SUSE Bug 1250024 In the Linux kernel, the following vulnerability has been resolved: PCI: hv: Fix a crash in hv_pci_restore_msi_msg() during hibernation When a Linux VM with an assigned PCI device runs on Hyper-V, if the PCI device driver is not loaded yet (i.e. MSI-X/MSI is not enabled on the device yet), doing a VM hibernation triggers a panic in hv_pci_restore_msi_msg() -> msi_lock_descs(&pdev->dev), because pdev->dev.msi.data is still NULL. Avoid the panic by checking if MSI-X/MSI is enabled. CVE-2023-53175 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53175.html CVE-2023-53175 https://bugzilla.suse.com/1249845 SUSE Bug 1249845 In the Linux kernel, the following vulnerability has been resolved: media: hi846: fix usage of pm_runtime_get_if_in_use() pm_runtime_get_if_in_use() does not only return nonzero values when the device is in use, it can return a negative errno too. And especially during resuming from system suspend, when runtime pm is not yet up again, -EAGAIN is being returned, so the subsequent pm_runtime_put() call results in a refcount underflow. Fix system-resume by handling -EAGAIN of pm_runtime_get_if_in_use(). CVE-2023-53177 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53177.html CVE-2023-53177 https://bugzilla.suse.com/1249849 SUSE Bug 1249849 In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: add the missing IP_SET_HASH_WITH_NET0 macro for ip_set_hash_netportnet.c The missing IP_SET_HASH_WITH_NET0 macro in ip_set_hash_netportnet can lead to the use of wrong `CIDR_POS(c)` for calculating array offsets, which can lead to integer underflow. As a result, it leads to slab out-of-bound access. This patch adds back the IP_SET_HASH_WITH_NET0 macro to ip_set_hash_netportnet to address the issue. CVE-2023-53179 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53179.html CVE-2023-53179 https://bugzilla.suse.com/1249825 SUSE Bug 1249825 In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Avoid NULL pointer access during management transmit cleanup Currently 'ar' reference is not added in skb_cb. Though this is generally not used during transmit completion callbacks, on interface removal the remaining idr cleanup callback uses the ar pointer from skb_cb from management txmgmt_idr. Hence fill them during transmit call for proper usage to avoid NULL pointer dereference. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1 CVE-2023-53180 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53180.html CVE-2023-53180 https://bugzilla.suse.com/1249826 SUSE Bug 1249826 In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: Stop leaking on krealloc() failure Currently dma_resv_get_fences() will leak the previously allocated array if the fence iteration got restarted and the krealloc_array() fails. Free the old array by hand, and make sure we still clear the returned *fences so the caller won't end up accessing freed memory. Some (but not all) of the callers of dma_resv_get_fences() seem to still trawl through the array even when dma_resv_get_fences() failed. And let's zero out *num_fences as well for good measure. CVE-2023-53181 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53181.html CVE-2023-53181 https://bugzilla.suse.com/1249824 SUSE Bug 1249824 In the Linux kernel, the following vulnerability has been resolved: btrfs: exit gracefully if reloc roots don't match [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). [CAUSE] The root cause of the triggered ASSERT() is we can have a race between quota tree creation and relocation. This leads us to create a duplicated quota tree in the btrfs_read_fs_root() path, and since it's treated as fs tree, it would have ROOT_SHAREABLE flag, causing us to create a reloc tree for it. The bug itself is fixed by a dedicated patch for it, but this already taught us the ASSERT() is not something straightforward for developers. [ENHANCEMENT] Instead of using an ASSERT(), let's handle it gracefully and output extra info about the mismatch reloc roots to help debug. Also with the above ASSERT() removed, we can trigger ASSERT(0)s inside merge_reloc_roots() later. Also replace those ASSERT(0)s with WARN_ON()s. CVE-2023-53183 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53183.html CVE-2023-53183 https://bugzilla.suse.com/1249863 SUSE Bug 1249863 In the Linux kernel, the following vulnerability has been resolved: arm64/sme: Set new vector length before reallocating As part of fixing the allocation of the buffer for SVE state when changing SME vector length we introduced an immediate reallocation of the SVE state, this is also done when changing the SVE vector length for consistency. Unfortunately this reallocation is done prior to writing the new vector length to the task struct, meaning the allocation is done with the old vector length and can lead to memory corruption due to an undersized buffer being used. Move the update of the vector length before the allocation to ensure that the new vector length is taken into account. For some reason this isn't triggering any problems when running tests on the arm64 fixes branch (even after repeated tries) but is triggering issues very often after merge into mainline. CVE-2023-53184 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53184.html CVE-2023-53184 https://bugzilla.suse.com/1249823 SUSE Bug 1249823 In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: don't allow to overwrite ENDPOINT0 attributes A bad USB device is able to construct a service connection response message with target endpoint being ENDPOINT0 which is reserved for HTC_CTRL_RSVD_SVC and should not be modified to be used for any other services. Reject such service connection responses. Found by Linux Verification Center (linuxtesting.org) with Syzkaller. CVE-2023-53185 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53185.html CVE-2023-53185 https://bugzilla.suse.com/1249820 SUSE Bug 1249820 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix use-after-free of new block group that became unused If a task creates a new block group and that block group becomes unused before we finish its creation, at btrfs_create_pending_block_groups(), then when btrfs_mark_bg_unused() is called against the block group, we assume that the block group is currently in the list of block groups to reclaim, and we move it out of the list of new block groups and into the list of unused block groups. This has two consequences: 1) We move it out of the list of new block groups associated to the current transaction. So the block group creation is not finished and if we attempt to delete the bg because it's unused, we will not find the block group item in the extent tree (or the new block group tree), its device extent items in the device tree etc, resulting in the deletion to fail due to the missing items; 2) We don't increment the reference count on the block group when we move it to the list of unused block groups, because we assumed the block group was on the list of block groups to reclaim, and in that case it already has the correct reference count. However the block group was on the list of new block groups, in which case no extra reference was taken because it's local to the current task. This later results in doing an extra reference count decrement when removing the block group from the unused list, eventually leading the reference count to 0. This second case was caught when running generic/297 from fstests, which produced the following assertion failure and stack trace: [589.559] assertion failed: refcount_read(&block_group->refs) == 1, in fs/btrfs/block-group.c:4299 [589.559] ------------[ cut here ]------------ [589.559] kernel BUG at fs/btrfs/block-group.c:4299! [589.560] invalid opcode: 0000 [#1] PREEMPT SMP PTI [589.560] CPU: 8 PID: 2819134 Comm: umount Tainted: G W 6.4.0-rc6-btrfs-next-134+ #1 [589.560] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014 [589.560] RIP: 0010:btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.561] Code: 68 62 da c0 (...) [589.561] RSP: 0018:ffffa55a8c3b3d98 EFLAGS: 00010246 [589.561] RAX: 0000000000000058 RBX: ffff8f030d7f2000 RCX: 0000000000000000 [589.562] RDX: 0000000000000000 RSI: ffffffff953f0878 RDI: 00000000ffffffff [589.562] RBP: ffff8f030d7f2088 R08: 0000000000000000 R09: ffffa55a8c3b3c50 [589.562] R10: 0000000000000001 R11: 0000000000000001 R12: ffff8f05850b4c00 [589.562] R13: ffff8f030d7f2090 R14: ffff8f05850b4cd8 R15: dead000000000100 [589.563] FS: 00007f497fd2e840(0000) GS:ffff8f09dfc00000(0000) knlGS:0000000000000000 [589.563] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [589.563] CR2: 00007f497ff8ec10 CR3: 0000000271472006 CR4: 0000000000370ee0 [589.563] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [589.564] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [589.564] Call Trace: [589.564] <TASK> [589.565] ? __die_body+0x1b/0x60 [589.565] ? die+0x39/0x60 [589.565] ? do_trap+0xeb/0x110 [589.565] ? btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.566] ? do_error_trap+0x6a/0x90 [589.566] ? btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.566] ? exc_invalid_op+0x4e/0x70 [589.566] ? btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.567] ? asm_exc_invalid_op+0x16/0x20 [589.567] ? btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.567] ? btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.567] close_ctree+0x35d/0x560 [btrfs] [589.568] ? fsnotify_sb_delete+0x13e/0x1d0 [589.568] ? dispose_list+0x3a/0x50 [589.568] ? evict_inodes+0x151/0x1a0 [589.568] generic_shutdown_super+0x73/0x1a0 [589.569] kill_anon_super+0x14/0x30 [589.569] btrfs_kill_super+0x12/0x20 [btrfs] [589.569] deactivate_locked ---truncated--- CVE-2023-53187 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53187.html CVE-2023-53187 https://bugzilla.suse.com/1249815 SUSE Bug 1249815 In the Linux kernel, the following vulnerability has been resolved: ipv6/addrconf: fix a potential refcount underflow for idev Now in addrconf_mod_rs_timer(), reference idev depends on whether rs_timer is not pending. Then modify rs_timer timeout. There is a time gap in [1], during which if the pending rs_timer becomes not pending. It will miss to hold idev, but the rs_timer is activated. Thus rs_timer callback function addrconf_rs_timer() will be executed and put idev later without holding idev. A refcount underflow issue for idev can be caused by this. if (!timer_pending(&idev->rs_timer)) in6_dev_hold(idev); <--------------[1] mod_timer(&idev->rs_timer, jiffies + when); To fix the issue, hold idev if mod_timer() return 0. CVE-2023-53189 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53189.html CVE-2023-53189 https://bugzilla.suse.com/1249894 SUSE Bug 1249894 In the Linux kernel, the following vulnerability has been resolved: vxlan: Fix nexthop hash size The nexthop code expects a 31 bit hash, such as what is returned by fib_multipath_hash() and rt6_multipath_hash(). Passing the 32 bit hash returned by skb_get_hash() can lead to problems related to the fact that 'int hash' is a negative number when the MSB is set. In the case of hash threshold nexthop groups, nexthop_select_path_hthr() will disproportionately select the first nexthop group entry. In the case of resilient nexthop groups, nexthop_select_path_res() may do an out of bounds access in nh_buckets[], for example: hash = -912054133 num_nh_buckets = 2 bucket_index = 65535 which leads to the following panic: BUG: unable to handle page fault for address: ffffc900025910c8 PGD 100000067 P4D 100000067 PUD 10026b067 PMD 0 Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI CPU: 4 PID: 856 Comm: kworker/4:3 Not tainted 6.5.0-rc2+ #34 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Workqueue: ipv6_addrconf addrconf_dad_work RIP: 0010:nexthop_select_path+0x197/0xbf0 Code: c1 e4 05 be 08 00 00 00 4c 8b 35 a4 14 7e 01 4e 8d 6c 25 00 4a 8d 7c 25 08 48 01 dd e8 c2 25 15 ff 49 8d 7d 08 e8 39 13 15 ff <4d> 89 75 08 48 89 ef e8 7d 12 15 ff 48 8b 5d 00 e8 14 55 2f 00 85 RSP: 0018:ffff88810c36f260 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 00000000002000c0 RCX: ffffffffaf02dd77 RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffffc900025910c8 RBP: ffffc900025910c0 R08: 0000000000000001 R09: fffff520004b2219 R10: ffffc900025910cf R11: 31392d2068736168 R12: 00000000002000c0 R13: ffffc900025910c0 R14: 00000000fffef608 R15: ffff88811840e900 FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc900025910c8 CR3: 0000000129d00000 CR4: 0000000000750ee0 PKRU: 55555554 Call Trace: <TASK> ? __die+0x23/0x70 ? page_fault_oops+0x1ee/0x5c0 ? __pfx_is_prefetch.constprop.0+0x10/0x10 ? __pfx_page_fault_oops+0x10/0x10 ? search_bpf_extables+0xfe/0x1c0 ? fixup_exception+0x3b/0x470 ? exc_page_fault+0xf6/0x110 ? asm_exc_page_fault+0x26/0x30 ? nexthop_select_path+0x197/0xbf0 ? nexthop_select_path+0x197/0xbf0 ? lock_is_held_type+0xe7/0x140 vxlan_xmit+0x5b2/0x2340 ? __lock_acquire+0x92b/0x3370 ? __pfx_vxlan_xmit+0x10/0x10 ? __pfx___lock_acquire+0x10/0x10 ? __pfx_register_lock_class+0x10/0x10 ? skb_network_protocol+0xce/0x2d0 ? dev_hard_start_xmit+0xca/0x350 ? __pfx_vxlan_xmit+0x10/0x10 dev_hard_start_xmit+0xca/0x350 __dev_queue_xmit+0x513/0x1e20 ? __pfx___dev_queue_xmit+0x10/0x10 ? __pfx_lock_release+0x10/0x10 ? mark_held_locks+0x44/0x90 ? skb_push+0x4c/0x80 ? eth_header+0x81/0xe0 ? __pfx_eth_header+0x10/0x10 ? neigh_resolve_output+0x215/0x310 ? ip6_finish_output2+0x2ba/0xc90 ip6_finish_output2+0x2ba/0xc90 ? lock_release+0x236/0x3e0 ? ip6_mtu+0xbb/0x240 ? __pfx_ip6_finish_output2+0x10/0x10 ? find_held_lock+0x83/0xa0 ? lock_is_held_type+0xe7/0x140 ip6_finish_output+0x1ee/0x780 ip6_output+0x138/0x460 ? __pfx_ip6_output+0x10/0x10 ? __pfx___lock_acquire+0x10/0x10 ? __pfx_ip6_finish_output+0x10/0x10 NF_HOOK.constprop.0+0xc0/0x420 ? __pfx_NF_HOOK.constprop.0+0x10/0x10 ? ndisc_send_skb+0x2c0/0x960 ? __pfx_lock_release+0x10/0x10 ? __local_bh_enable_ip+0x93/0x110 ? lock_is_held_type+0xe7/0x140 ndisc_send_skb+0x4be/0x960 ? __pfx_ndisc_send_skb+0x10/0x10 ? mark_held_locks+0x65/0x90 ? find_held_lock+0x83/0xa0 ndisc_send_ns+0xb0/0x110 ? __pfx_ndisc_send_ns+0x10/0x10 addrconf_dad_work+0x631/0x8e0 ? lock_acquire+0x180/0x3f0 ? __pfx_addrconf_dad_work+0x10/0x10 ? mark_held_locks+0x24/0x90 process_one_work+0x582/0x9c0 ? __pfx_process_one_work+0x10/0x10 ? __pfx_do_raw_spin_lock+0x10/0x10 ? mark_held_locks+0x24/0x90 worker_thread+0x93/0x630 ? __kthread_parkme+0xdc/0x100 ? __pfx_worker_thread+0x10/0x10 kthread+0x1a5/0x1e0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x34/0x60 ---truncated--- CVE-2023-53192 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53192.html CVE-2023-53192 https://bugzilla.suse.com/1249897 SUSE Bug 1249897 In the Linux kernel, the following vulnerability has been resolved: mlxsw: minimal: fix potential memory leak in mlxsw_m_linecards_init The line cards array is not freed in the error path of mlxsw_m_linecards_init(), which can lead to a memory leak. Fix by freeing the array in the error path, thereby making the error path identical to mlxsw_m_linecards_fini(). CVE-2023-53195 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53195.html CVE-2023-53195 https://bugzilla.suse.com/1249761 SUSE Bug 1249761 In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: qcom: Fix potential memory leak Function dwc3_qcom_probe() allocates memory for resource structure which is pointed by parent_res pointer. This memory is not freed. This leads to memory leak. Use stack memory to prevent memory leak. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2023-53196 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53196.html CVE-2023-53196 https://bugzilla.suse.com/1249758 SUSE Bug 1249758 In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: wraparound mbox producer index Driver is not handling the wraparound of the mbox producer index correctly. Currently the wraparound happens once u32 max is reached. Bit 31 of the producer index register is special and should be set only once for the first command. Because the producer index overflow setting bit31 after a long time, FW goes to initialization sequence and this causes FW hang. Fix is to wraparound the mbox producer index once it reaches u16 max. CVE-2023-53201 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53201.html CVE-2023-53201 https://bugzilla.suse.com/1249687 SUSE Bug 1249687 In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix data-races around user->unix_inflight. user->unix_inflight is changed under spin_lock(unix_gc_lock), but too_many_unix_fds() reads it locklessly. Let's annotate the write/read accesses to user->unix_inflight. BUG: KCSAN: data-race in unix_attach_fds / unix_inflight write to 0xffffffff8546f2d0 of 8 bytes by task 44798 on cpu 1: unix_inflight+0x157/0x180 net/unix/scm.c:66 unix_attach_fds+0x147/0x1e0 net/unix/scm.c:123 unix_scm_to_skb net/unix/af_unix.c:1827 [inline] unix_dgram_sendmsg+0x46a/0x14f0 net/unix/af_unix.c:1950 unix_seqpacket_sendmsg net/unix/af_unix.c:2308 [inline] unix_seqpacket_sendmsg+0xba/0x130 net/unix/af_unix.c:2292 sock_sendmsg_nosec net/socket.c:725 [inline] sock_sendmsg+0x148/0x160 net/socket.c:748 ____sys_sendmsg+0x4e4/0x610 net/socket.c:2494 ___sys_sendmsg+0xc6/0x140 net/socket.c:2548 __sys_sendmsg+0x94/0x140 net/socket.c:2577 __do_sys_sendmsg net/socket.c:2586 [inline] __se_sys_sendmsg net/socket.c:2584 [inline] __x64_sys_sendmsg+0x45/0x50 net/socket.c:2584 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 read to 0xffffffff8546f2d0 of 8 bytes by task 44814 on cpu 0: too_many_unix_fds net/unix/scm.c:101 [inline] unix_attach_fds+0x54/0x1e0 net/unix/scm.c:110 unix_scm_to_skb net/unix/af_unix.c:1827 [inline] unix_dgram_sendmsg+0x46a/0x14f0 net/unix/af_unix.c:1950 unix_seqpacket_sendmsg net/unix/af_unix.c:2308 [inline] unix_seqpacket_sendmsg+0xba/0x130 net/unix/af_unix.c:2292 sock_sendmsg_nosec net/socket.c:725 [inline] sock_sendmsg+0x148/0x160 net/socket.c:748 ____sys_sendmsg+0x4e4/0x610 net/socket.c:2494 ___sys_sendmsg+0xc6/0x140 net/socket.c:2548 __sys_sendmsg+0x94/0x140 net/socket.c:2577 __do_sys_sendmsg net/socket.c:2586 [inline] __se_sys_sendmsg net/socket.c:2584 [inline] __x64_sys_sendmsg+0x45/0x50 net/socket.c:2584 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 value changed: 0x000000000000000c -> 0x000000000000000d Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 44814 Comm: systemd-coredum Not tainted 6.4.0-11989-g6843306689af #6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 CVE-2023-53204 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53204.html CVE-2023-53204 https://bugzilla.suse.com/1249682 SUSE Bug 1249682 In the Linux kernel, the following vulnerability has been resolved: KVM: s390/diag: fix racy access of physical cpu number in diag 9c handler We do check for target CPU == -1, but this might change at the time we are going to use it. Hold the physical target CPU in a local variable to avoid out-of-bound accesses to the cpu arrays. CVE-2023-53205 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53205.html CVE-2023-53205 https://bugzilla.suse.com/1249677 SUSE Bug 1249677 In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus_core) Fix NULL pointer dereference Pass i2c_client to _pmbus_is_enabled to drop the assumption that a regulator device is passed in. This will fix the issue of a NULL pointer dereference when called from _pmbus_get_flags. CVE-2023-53206 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53206.html CVE-2023-53206 https://bugzilla.suse.com/1249679 SUSE Bug 1249679 In the Linux kernel, the following vulnerability has been resolved: ublk: fail to recover device if queue setup is interrupted In ublk_ctrl_end_recovery(), if wait_for_completion_interruptible() is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLK_CMD_END_USER_RECOVERY, otherwise kernel oops can be triggered. CVE-2023-53207 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53207.html CVE-2023-53207 https://bugzilla.suse.com/1249678 SUSE Bug 1249678 In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Load L1's TSC multiplier based on L1 state, not L2 state When emulating nested VM-Exit, load L1's TSC multiplier if L1's desired ratio doesn't match the current ratio, not if the ratio L1 is using for L2 diverges from the default. Functionally, the end result is the same as KVM will run L2 with L1's multiplier if L2's multiplier is the default, i.e. checking that L1's multiplier is loaded is equivalent to checking if L2 has a non-default multiplier. However, the assertion that TSC scaling is exposed to L1 is flawed, as userspace can trigger the WARN at will by writing the MSR and then updating guest CPUID to hide the feature (modifying guest CPUID is allowed anytime before KVM_RUN). E.g. hacking KVM's state_test selftest to do vcpu_set_msr(vcpu, MSR_AMD64_TSC_RATIO, 0); vcpu_clear_cpuid_feature(vcpu, X86_FEATURE_TSCRATEMSR); after restoring state in a new VM+vCPU yields an endless supply of: ------------[ cut here ]------------ WARNING: CPU: 10 PID: 206939 at arch/x86/kvm/svm/nested.c:1105 nested_svm_vmexit+0x6af/0x720 [kvm_amd] Call Trace: nested_svm_exit_handled+0x102/0x1f0 [kvm_amd] svm_handle_exit+0xb9/0x180 [kvm_amd] kvm_arch_vcpu_ioctl_run+0x1eab/0x2570 [kvm] kvm_vcpu_ioctl+0x4c9/0x5b0 [kvm] ? trace_hardirqs_off+0x4d/0xa0 __se_sys_ioctl+0x7a/0xc0 __x64_sys_ioctl+0x21/0x30 do_syscall_64+0x41/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd Unlike the nested VMRUN path, hoisting the svm->tsc_scaling_enabled check into the if-statement is wrong as KVM needs to ensure L1's multiplier is loaded in the above scenario. Alternatively, the WARN_ON() could simply be deleted, but that would make KVM's behavior even more subtle, e.g. it's not immediately obvious why it's safe to write MSR_AMD64_TSC_RATIO when checking only tsc_ratio_msr. CVE-2023-53208 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53208.html CVE-2023-53208 https://bugzilla.suse.com/1249698 SUSE Bug 1249698 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211_hwsim: Fix possible NULL dereference In a call to mac80211_hwsim_select_tx_link() the sta pointer might be NULL, thus need to check that it is not NULL before accessing it. CVE-2023-53209 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53209.html CVE-2023-53209 https://bugzilla.suse.com/1249856 SUSE Bug 1249856 https://bugzilla.suse.com/1253191 SUSE Bug 1253191 In the Linux kernel, the following vulnerability has been resolved: md/raid5-cache: fix null-ptr-deref for r5l_flush_stripe_to_raid() r5l_flush_stripe_to_raid() will check if the list 'flushing_ios' is empty, and then submit 'flush_bio', however, r5l_log_flush_endio() is clearing the list first and then clear the bio, which will cause null-ptr-deref: T1: submit flush io raid5d handle_active_stripes r5l_flush_stripe_to_raid // list is empty // add 'io_end_ios' to the list bio_init submit_bio // io1 T2: io1 is done r5l_log_flush_endio list_splice_tail_init // clear the list T3: submit new flush io ... r5l_flush_stripe_to_raid // list is empty // add 'io_end_ios' to the list bio_init bio_uninit // clear bio->bi_blkg submit_bio // null-ptr-deref Fix this problem by clearing bio before clearing the list in r5l_log_flush_endio(). CVE-2023-53210 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53210.html CVE-2023-53210 https://bugzilla.suse.com/1249673 SUSE Bug 1249673 In the Linux kernel, the following vulnerability has been resolved: sched/fair: Don't balance task to its current running CPU We've run into the case that the balancer tries to balance a migration disabled task and trigger the warning in set_task_cpu() like below: ------------[ cut here ]------------ WARNING: CPU: 7 PID: 0 at kernel/sched/core.c:3115 set_task_cpu+0x188/0x240 Modules linked in: hclgevf xt_CHECKSUM ipt_REJECT nf_reject_ipv4 <...snip> CPU: 7 PID: 0 Comm: swapper/7 Kdump: loaded Tainted: G O 6.1.0-rc4+ #1 Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V5.B221.01 12/09/2021 pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : set_task_cpu+0x188/0x240 lr : load_balance+0x5d0/0xc60 sp : ffff80000803bc70 x29: ffff80000803bc70 x28: ffff004089e190e8 x27: ffff004089e19040 x26: ffff007effcabc38 x25: 0000000000000000 x24: 0000000000000001 x23: ffff80000803be84 x22: 000000000000000c x21: ffffb093e79e2a78 x20: 000000000000000c x19: ffff004089e19040 x18: 0000000000000000 x17: 0000000000001fad x16: 0000000000000030 x15: 0000000000000000 x14: 0000000000000003 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000001 x10: 0000000000000400 x9 : ffffb093e4cee530 x8 : 00000000fffffffe x7 : 0000000000ce168a x6 : 000000000000013e x5 : 00000000ffffffe1 x4 : 0000000000000001 x3 : 0000000000000b2a x2 : 0000000000000b2a x1 : ffffb093e6d6c510 x0 : 0000000000000001 Call trace: set_task_cpu+0x188/0x240 load_balance+0x5d0/0xc60 rebalance_domains+0x26c/0x380 _nohz_idle_balance.isra.0+0x1e0/0x370 run_rebalance_domains+0x6c/0x80 __do_softirq+0x128/0x3d8 ____do_softirq+0x18/0x24 call_on_irq_stack+0x2c/0x38 do_softirq_own_stack+0x24/0x3c __irq_exit_rcu+0xcc/0xf4 irq_exit_rcu+0x18/0x24 el1_interrupt+0x4c/0xe4 el1h_64_irq_handler+0x18/0x2c el1h_64_irq+0x74/0x78 arch_cpu_idle+0x18/0x4c default_idle_call+0x58/0x194 do_idle+0x244/0x2b0 cpu_startup_entry+0x30/0x3c secondary_start_kernel+0x14c/0x190 __secondary_switched+0xb0/0xb4 ---[ end trace 0000000000000000 ]--- Further investigation shows that the warning is superfluous, the migration disabled task is just going to be migrated to its current running CPU. This is because that on load balance if the dst_cpu is not allowed by the task, we'll re-select a new_dst_cpu as a candidate. If no task can be balanced to dst_cpu we'll try to balance the task to the new_dst_cpu instead. In this case when the migration disabled task is not on CPU it only allows to run on its current CPU, load balance will select its current CPU as new_dst_cpu and later triggers the warning above. The new_dst_cpu is chosen from the env->dst_grpmask. Currently it contains CPUs in sched_group_span() and if we have overlapped groups it's possible to run into this case. This patch makes env->dst_grpmask of group_balance_mask() which exclude any CPUs from the busiest group and solve the issue. For balancing in a domain with no overlapped groups the behaviour keeps same as before. CVE-2023-53215 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53215.html CVE-2023-53215 https://bugzilla.suse.com/1250397 SUSE Bug 1250397 In the Linux kernel, the following vulnerability has been resolved: nubus: Partially revert proc_create_single_data() conversion The conversion to proc_create_single_data() introduced a regression whereby reading a file in /proc/bus/nubus results in a seg fault: # grep -r . /proc/bus/nubus/e/ Data read fault at 0x00000020 in Super Data (pc=0x1074c2) BAD KERNEL BUSERR Oops: 00000000 Modules linked in: PC: [<001074c2>] PDE_DATA+0xc/0x16 SR: 2010 SP: 38284958 a2: 01152370 d0: 00000001 d1: 01013000 d2: 01002790 d3: 00000000 d4: 00000001 d5: 0008ce2e a0: 00000000 a1: 00222a40 Process grep (pid: 45, task=142f8727) Frame format=B ssw=074d isc=2008 isb=4e5e daddr=00000020 dobuf=01199e70 baddr=001074c8 dibuf=ffffffff ver=f Stack from 01199e48: 01199e70 00222a58 01002790 00000000 011a3000 01199eb0 015000c0 00000000 00000000 01199ec0 01199ec0 000d551a 011a3000 00000001 00000000 00018000 d003f000 00000003 00000001 0002800d 01052840 01199fa8 c01f8000 00000000 00000029 0b532b80 00000000 00000000 00000029 0b532b80 01199ee4 00103640 011198c0 d003f000 00018000 01199fa8 00000000 011198c0 00000000 01199f4c 000b3344 011198c0 d003f000 00018000 01199fa8 00000000 00018000 011198c0 Call Trace: [<00222a58>] nubus_proc_rsrc_show+0x18/0xa0 [<000d551a>] seq_read+0xc4/0x510 [<00018000>] fp_fcos+0x2/0x82 [<0002800d>] __sys_setreuid+0x115/0x1c6 [<00103640>] proc_reg_read+0x5c/0xb0 [<00018000>] fp_fcos+0x2/0x82 [<000b3344>] __vfs_read+0x2c/0x13c [<00018000>] fp_fcos+0x2/0x82 [<00018000>] fp_fcos+0x2/0x82 [<000b8aa2>] sys_statx+0x60/0x7e [<000b34b6>] vfs_read+0x62/0x12a [<00018000>] fp_fcos+0x2/0x82 [<00018000>] fp_fcos+0x2/0x82 [<000b39c2>] ksys_read+0x48/0xbe [<00018000>] fp_fcos+0x2/0x82 [<000b3a4e>] sys_read+0x16/0x1a [<00018000>] fp_fcos+0x2/0x82 [<00002b84>] syscall+0x8/0xc [<00018000>] fp_fcos+0x2/0x82 [<0000c016>] not_ext+0xa/0x18 Code: 4e5e 4e75 4e56 0000 206e 0008 2068 ffe8 <2068> 0020 2008 4e5e 4e75 4e56 0000 2f0b 206e 0008 2068 0004 2668 0020 206b ffe8 Disabling lock debugging due to kernel taint Segmentation fault The proc_create_single_data() conversion does not work because single_open(file, nubus_proc_rsrc_show, PDE_DATA(inode)) is not equivalent to the original code. CVE-2023-53217 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53217.html CVE-2023-53217 https://bugzilla.suse.com/1249672 SUSE Bug 1249672 In the Linux kernel, the following vulnerability has been resolved: media: az6007: Fix null-ptr-deref in az6007_i2c_xfer() In az6007_i2c_xfer, msg is controlled by user. When msg[i].buf is null and msg[i].len is zero, former checks on msg[i].buf would be passed. Malicious data finally reach az6007_i2c_xfer. If accessing msg[i].buf[0] without sanity check, null ptr deref would happen. We add check on msg[i].len to prevent crash. Similar commit: commit 0ed554fd769a ("media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()") CVE-2023-53220 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53220.html CVE-2023-53220 https://bugzilla.suse.com/1250337 SUSE Bug 1250337 In the Linux kernel, the following vulnerability has been resolved: bpf: Fix memleak due to fentry attach failure If it fails to attach fentry, the allocated bpf trampoline image will be left in the system. That can be verified by checking /proc/kallsyms. This meamleak can be verified by a simple bpf program as follows: SEC("fentry/trap_init") int fentry_run() { return 0; } It will fail to attach trap_init because this function is freed after kernel init, and then we can find the trampoline image is left in the system by checking /proc/kallsyms. $ tail /proc/kallsyms ffffffffc0613000 t bpf_trampoline_6442453466_1 [bpf] ffffffffc06c3000 t bpf_trampoline_6442453466_1 [bpf] $ bpftool btf dump file /sys/kernel/btf/vmlinux | grep "FUNC 'trap_init'" [2522] FUNC 'trap_init' type_id=119 linkage=static $ echo $((6442453466 & 0x7fffffff)) 2522 Note that there are two left bpf trampoline images, that is because the libbpf will fallback to raw tracepoint if -EINVAL is returned. CVE-2023-53221 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53221.html CVE-2023-53221 https://bugzilla.suse.com/1249662 SUSE Bug 1249662 In the Linux kernel, the following vulnerability has been resolved: jfs: jfs_dmap: Validate db_l2nbperpage while mounting In jfs_dmap.c at line 381, BLKTODMAP is used to get a logical block number inside dbFree(). db_l2nbperpage, which is the log2 number of blocks per page, is passed as an argument to BLKTODMAP which uses it for shifting. Syzbot reported a shift out-of-bounds crash because db_l2nbperpage is too big. This happens because the large value is set without any validation in dbMount() at line 181. Thus, make sure that db_l2nbperpage is correct while mounting. Max number of blocks per page = Page size / Min block size => log2(Max num_block per page) = log2(Page size / Min block size) = log2(Page size) - log2(Min block size) => Max db_l2nbperpage = L2PSIZE - L2MINBLOCKSIZE CVE-2023-53222 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53222.html CVE-2023-53222 https://bugzilla.suse.com/1249864 SUSE Bug 1249864 In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix OOB and integer underflow when rx packets Make sure mwifiex_process_mgmt_packet, mwifiex_process_sta_rx_packet and mwifiex_process_uap_rx_packet, mwifiex_uap_queue_bridged_pkt and mwifiex_process_rx_packet not out-of-bounds access the skb->data buffer. CVE-2023-53226 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53226.html CVE-2023-53226 https://bugzilla.suse.com/1249658 SUSE Bug 1249658 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix warning in cifs_smb3_do_mount() This fixes the following warning reported by kernel test robot fs/smb/client/cifsfs.c:982 cifs_smb3_do_mount() warn: possible memory leak of 'cifs_sb' CVE-2023-53230 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53230.html CVE-2023-53230 https://bugzilla.suse.com/1249866 SUSE Bug 1249866 In the Linux kernel, the following vulnerability has been resolved: erofs: Fix detection of atomic context Current check for atomic context is not sufficient as z_erofs_decompressqueue_endio can be called under rcu lock from blk_mq_flush_plug_list(). See the stacktrace [1] In such case we should hand off the decompression work for async processing rather than trying to do sync decompression in current context. Patch fixes the detection by checking for rcu_read_lock_any_held() and while at it use more appropriate !in_task() check than in_atomic(). Background: Historically erofs would always schedule a kworker for decompression which would incur the scheduling cost regardless of the context. But z_erofs_decompressqueue_endio() may not always be in atomic context and we could actually benefit from doing the decompression in z_erofs_decompressqueue_endio() if we are in thread context, for example when running with dm-verity. This optimization was later added in patch [2] which has shown improvement in performance benchmarks. ============================================== [1] Problem stacktrace [name:core&]BUG: sleeping function called from invalid context at kernel/locking/mutex.c:291 [name:core&]in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 1615, name: CpuMonitorServi [name:core&]preempt_count: 0, expected: 0 [name:core&]RCU nest depth: 1, expected: 0 CPU: 7 PID: 1615 Comm: CpuMonitorServi Tainted: G S W OE 6.1.25-android14-5-maybe-dirty-mainline #1 Hardware name: MT6897 (DT) Call trace: dump_backtrace+0x108/0x15c show_stack+0x20/0x30 dump_stack_lvl+0x6c/0x8c dump_stack+0x20/0x48 __might_resched+0x1fc/0x308 __might_sleep+0x50/0x88 mutex_lock+0x2c/0x110 z_erofs_decompress_queue+0x11c/0xc10 z_erofs_decompress_kickoff+0x110/0x1a4 z_erofs_decompressqueue_endio+0x154/0x180 bio_endio+0x1b0/0x1d8 __dm_io_complete+0x22c/0x280 clone_endio+0xe4/0x280 bio_endio+0x1b0/0x1d8 blk_update_request+0x138/0x3a4 blk_mq_plug_issue_direct+0xd4/0x19c blk_mq_flush_plug_list+0x2b0/0x354 __blk_flush_plug+0x110/0x160 blk_finish_plug+0x30/0x4c read_pages+0x2fc/0x370 page_cache_ra_unbounded+0xa4/0x23c page_cache_ra_order+0x290/0x320 do_sync_mmap_readahead+0x108/0x2c0 filemap_fault+0x19c/0x52c __do_fault+0xc4/0x114 handle_mm_fault+0x5b4/0x1168 do_page_fault+0x338/0x4b4 do_translation_fault+0x40/0x60 do_mem_abort+0x60/0xc8 el0_da+0x4c/0xe0 el0t_64_sync_handler+0xd4/0xfc el0t_64_sync+0x1a0/0x1a4 [2] Link: https://lore.kernel.org/all/20210317035448.13921-1-huangjianan@oppo.com/ CVE-2023-53231 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53231.html CVE-2023-53231 https://bugzilla.suse.com/1249787 SUSE Bug 1249787 In the Linux kernel, the following vulnerability has been resolved: drm/tests: helpers: Avoid a driver uaf when using __drm_kunit_helper_alloc_drm_device() the driver may be dereferenced by device-managed resources up until the device is freed, which is typically later than the kunit-managed resource code frees it. Fix this by simply make the driver device-managed as well. In short, the sequence leading to the UAF is as follows: INIT: Code allocates a struct device as a kunit-managed resource. Code allocates a drm driver as a kunit-managed resource. Code allocates a drm device as a device-managed resource. EXIT: Kunit resource cleanup frees the drm driver Kunit resource cleanup puts the struct device, which starts a device-managed resource cleanup device-managed cleanup calls drm_dev_put() drm_dev_put() dereferences the (now freed) drm driver -> Boom. Related KASAN message: [55272.551542] ================================================================== [55272.551551] BUG: KASAN: slab-use-after-free in drm_dev_put.part.0+0xd4/0xe0 [drm] [55272.551603] Read of size 8 at addr ffff888127502828 by task kunit_try_catch/10353 [55272.551612] CPU: 4 PID: 10353 Comm: kunit_try_catch Tainted: G U N 6.5.0-rc7+ #155 [55272.551620] Hardware name: ASUS System Product Name/PRIME B560M-A AC, BIOS 0403 01/26/2021 [55272.551626] Call Trace: [55272.551629] <TASK> [55272.551633] dump_stack_lvl+0x57/0x90 [55272.551639] print_report+0xcf/0x630 [55272.551645] ? _raw_spin_lock_irqsave+0x5f/0x70 [55272.551652] ? drm_dev_put.part.0+0xd4/0xe0 [drm] [55272.551694] kasan_report+0xd7/0x110 [55272.551699] ? drm_dev_put.part.0+0xd4/0xe0 [drm] [55272.551742] drm_dev_put.part.0+0xd4/0xe0 [drm] [55272.551783] devres_release_all+0x15d/0x1f0 [55272.551790] ? __pfx_devres_release_all+0x10/0x10 [55272.551797] device_unbind_cleanup+0x16/0x1a0 [55272.551802] device_release_driver_internal+0x3e5/0x540 [55272.551808] ? kobject_put+0x5d/0x4b0 [55272.551814] bus_remove_device+0x1f1/0x3f0 [55272.551819] device_del+0x342/0x910 [55272.551826] ? __pfx_device_del+0x10/0x10 [55272.551830] ? lock_release+0x339/0x5e0 [55272.551836] ? kunit_remove_resource+0x128/0x290 [kunit] [55272.551845] ? __pfx_lock_release+0x10/0x10 [55272.551851] platform_device_del.part.0+0x1f/0x1e0 [55272.551856] ? _raw_spin_unlock_irqrestore+0x30/0x60 [55272.551863] kunit_remove_resource+0x195/0x290 [kunit] [55272.551871] ? _raw_spin_unlock_irqrestore+0x30/0x60 [55272.551877] kunit_cleanup+0x78/0x120 [kunit] [55272.551885] ? __kthread_parkme+0xc1/0x1f0 [55272.551891] ? __pfx_kunit_try_run_case_cleanup+0x10/0x10 [kunit] [55272.551900] ? __pfx_kunit_generic_run_threadfn_adapter+0x10/0x10 [kunit] [55272.551909] kunit_generic_run_threadfn_adapter+0x4a/0x90 [kunit] [55272.551919] kthread+0x2e7/0x3c0 [55272.551924] ? __pfx_kthread+0x10/0x10 [55272.551929] ret_from_fork+0x2d/0x70 [55272.551935] ? __pfx_kthread+0x10/0x10 [55272.551940] ret_from_fork_asm+0x1b/0x30 [55272.551948] </TASK> [55272.551953] Allocated by task 10351: [55272.551956] kasan_save_stack+0x1c/0x40 [55272.551962] kasan_set_track+0x21/0x30 [55272.551966] __kasan_kmalloc+0x8b/0x90 [55272.551970] __kmalloc+0x5e/0x160 [55272.551976] kunit_kmalloc_array+0x1c/0x50 [kunit] [55272.551984] drm_exec_test_init+0xfa/0x2c0 [drm_exec_test] [55272.551991] kunit_try_run_case+0xdd/0x250 [kunit] [55272.551999] kunit_generic_run_threadfn_adapter+0x4a/0x90 [kunit] [55272.552008] kthread+0x2e7/0x3c0 [55272.552012] ret_from_fork+0x2d/0x70 [55272.552017] ret_from_fork_asm+0x1b/0x30 [55272.552024] Freed by task 10353: [55272.552027] kasan_save_stack+0x1c/0x40 [55272.552032] kasan_set_track+0x21/0x30 [55272.552036] kasan_save_free_info+0x27/0x40 [55272.552041] __kasan_slab_free+0x106/0x180 [55272.552046] slab_free_freelist_hook+0xb3/0x160 [55272.552051] __kmem_cache_free+0xb2/0x290 [55272.552056] kunit_remove_resource+0x195/0x290 [kunit] [55272.552064] kunit_cleanup+0x7 ---truncated--- CVE-2023-53235 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53235.html CVE-2023-53235 https://bugzilla.suse.com/1249785 SUSE Bug 1249785 In the Linux kernel, the following vulnerability has been resolved: phy: hisilicon: Fix an out of bounds check in hisi_inno_phy_probe() The size of array 'priv->ports[]' is INNO_PHY_PORT_NUM. In the for loop, 'i' is used as the index for array 'priv->ports[]' with a check (i > INNO_PHY_PORT_NUM) which indicates that INNO_PHY_PORT_NUM is allowed value for 'i' in the same loop. This > comparison needs to be changed to >=, otherwise it potentially leads to an out of bounds write on the next iteration through the loop CVE-2023-53238 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53238.html CVE-2023-53238 https://bugzilla.suse.com/1249707 SUSE Bug 1249707 In the Linux kernel, the following vulnerability has been resolved: btrfs: add handling for RAID1C23/DUP to btrfs_reduce_alloc_profile Callers of `btrfs_reduce_alloc_profile` expect it to return exactly one allocation profile flag, and failing to do so may ultimately result in a WARN_ON and remount-ro when allocating new blocks, like the below transaction abort on 6.1. `btrfs_reduce_alloc_profile` has two ways of determining the profile, first it checks if a conversion balance is currently running and uses the profile we're converting to. If no balance is currently running, it returns the max-redundancy profile which at least one block in the selected block group has. This works by simply checking each known allocation profile bit in redundancy order. However, `btrfs_reduce_alloc_profile` has not been updated as new flags have been added - first with the `DUP` profile and later with the RAID1C34 profiles. Because of the way it checks, if we have blocks with different profiles and at least one is known, that profile will be selected. However, if none are known we may return a flag set with multiple allocation profiles set. This is currently only possible when a balance from one of the three unhandled profiles to another of the unhandled profiles is canceled after allocating at least one block using the new profile. In that case, a transaction abort like the below will occur and the filesystem will need to be mounted with -o skip_balance to get it mounted rw again (but the balance cannot be resumed without a similar abort). [770.648] ------------[ cut here ]------------ [770.648] BTRFS: Transaction aborted (error -22) [770.648] WARNING: CPU: 43 PID: 1159593 at fs/btrfs/extent-tree.c:4122 find_free_extent+0x1d94/0x1e00 [btrfs] [770.648] CPU: 43 PID: 1159593 Comm: btrfs Tainted: G W 6.1.0-0.deb11.7-powerpc64le #1 Debian 6.1.20-2~bpo11+1a~test [770.648] Hardware name: T2P9D01 REV 1.00 POWER9 0x4e1202 opal:skiboot-bc106a0 PowerNV [770.648] NIP: c00800000f6784fc LR: c00800000f6784f8 CTR: c000000000d746c0 [770.648] REGS: c000200089afe9a0 TRAP: 0700 Tainted: G W (6.1.0-0.deb11.7-powerpc64le Debian 6.1.20-2~bpo11+1a~test) [770.648] MSR: 9000000002029033 <SF,HV,VEC,EE,ME,IR,DR,RI,LE> CR: 28848282 XER: 20040000 [770.648] CFAR: c000000000135110 IRQMASK: 0 GPR00: c00800000f6784f8 c000200089afec40 c00800000f7ea800 0000000000000026 GPR04: 00000001004820c2 c000200089afea00 c000200089afe9f8 0000000000000027 GPR08: c000200ffbfe7f98 c000000002127f90 ffffffffffffffd8 0000000026d6a6e8 GPR12: 0000000028848282 c000200fff7f3800 5deadbeef0000122 c00000002269d000 GPR16: c0002008c7797c40 c000200089afef17 0000000000000000 0000000000000000 GPR20: 0000000000000000 0000000000000001 c000200008bc5a98 0000000000000001 GPR24: 0000000000000000 c0000003c73088d0 c000200089afef17 c000000016d3a800 GPR28: c0000003c7308800 c00000002269d000 ffffffffffffffea 0000000000000001 [770.648] NIP [c00800000f6784fc] find_free_extent+0x1d94/0x1e00 [btrfs] [770.648] LR [c00800000f6784f8] find_free_extent+0x1d90/0x1e00 [btrfs] [770.648] Call Trace: [770.648] [c000200089afec40] [c00800000f6784f8] find_free_extent+0x1d90/0x1e00 [btrfs] (unreliable) [770.648] [c000200089afed30] [c00800000f681398] btrfs_reserve_extent+0x1a0/0x2f0 [btrfs] [770.648] [c000200089afeea0] [c00800000f681bf0] btrfs_alloc_tree_block+0x108/0x670 [btrfs] [770.648] [c000200089afeff0] [c00800000f66bd68] __btrfs_cow_block+0x170/0x850 [btrfs] [770.648] [c000200089aff100] [c00800000f66c58c] btrfs_cow_block+0x144/0x288 [btrfs] [770.648] [c000200089aff1b0] [c00800000f67113c] btrfs_search_slot+0x6b4/0xcb0 [btrfs] [770.648] [c000200089aff2a0] [c00800000f679f60] lookup_inline_extent_backref+0x128/0x7c0 [btrfs] [770.648] [c000200089aff3b0] [c00800000f67b338] lookup_extent_backref+0x70/0x190 [btrfs] [770.648] [c000200089aff470] [c00800000f67b54c] __btrfs_free_extent+0xf4/0x1490 [btrfs] [770.648] [ ---truncated--- CVE-2023-53243 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53243.html CVE-2023-53243 https://bugzilla.suse.com/1249640 SUSE Bug 1249640 In the Linux kernel, the following vulnerability has been resolved: scsi: storvsc: Fix handling of virtual Fibre Channel timeouts Hyper-V provides the ability to connect Fibre Channel LUNs to the host system and present them in a guest VM as a SCSI device. I/O to the vFC device is handled by the storvsc driver. The storvsc driver includes a partial integration with the FC transport implemented in the generic portion of the Linux SCSI subsystem so that FC attributes can be displayed in /sys. However, the partial integration means that some aspects of vFC don't work properly. Unfortunately, a full and correct integration isn't practical because of limitations in what Hyper-V provides to the guest. In particular, in the context of Hyper-V storvsc, the FC transport timeout function fc_eh_timed_out() causes a kernel panic because it can't find the rport and dereferences a NULL pointer. The original patch that added the call from storvsc_eh_timed_out() to fc_eh_timed_out() is faulty in this regard. In many cases a timeout is due to a transient condition, so the situation can be improved by just continuing to wait like with other I/O requests issued by storvsc, and avoiding the guaranteed panic. For a permanent failure, continuing to wait may result in a hung thread instead of a panic, which again may be better. So fix the panic by removing the storvsc call to fc_eh_timed_out(). This allows storvsc to keep waiting for a response. The change has been tested by users who experienced a panic in fc_eh_timed_out() due to transient timeouts, and it solves their problem. In the future we may want to deprecate the vFC functionality in storvsc since it can't be fully fixed. But it has current users for whom it is working well enough, so it should probably stay for a while longer. CVE-2023-53245 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53245.html CVE-2023-53245 https://bugzilla.suse.com/1249641 SUSE Bug 1249641 In the Linux kernel, the following vulnerability has been resolved: btrfs: set_page_extent_mapped after read_folio in btrfs_cont_expand While trying to get the subpage blocksize tests running, I hit the following panic on generic/476 assertion failed: PagePrivate(page) && page->private, in fs/btrfs/subpage.c:229 kernel BUG at fs/btrfs/subpage.c:229! Internal error: Oops - BUG: 00000000f2000800 [#1] SMP CPU: 1 PID: 1453 Comm: fsstress Not tainted 6.4.0-rc7+ #12 Hardware name: QEMU KVM Virtual Machine, BIOS edk2-20230301gitf80f052277c8-26.fc38 03/01/2023 pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) pc : btrfs_subpage_assert+0xbc/0xf0 lr : btrfs_subpage_assert+0xbc/0xf0 Call trace: btrfs_subpage_assert+0xbc/0xf0 btrfs_subpage_clear_checked+0x38/0xc0 btrfs_page_clear_checked+0x48/0x98 btrfs_truncate_block+0x5d0/0x6a8 btrfs_cont_expand+0x5c/0x528 btrfs_write_check.isra.0+0xf8/0x150 btrfs_buffered_write+0xb4/0x760 btrfs_do_write_iter+0x2f8/0x4b0 btrfs_file_write_iter+0x1c/0x30 do_iter_readv_writev+0xc8/0x158 do_iter_write+0x9c/0x210 vfs_iter_write+0x24/0x40 iter_file_splice_write+0x224/0x390 direct_splice_actor+0x38/0x68 splice_direct_to_actor+0x12c/0x260 do_splice_direct+0x90/0xe8 generic_copy_file_range+0x50/0x90 vfs_copy_file_range+0x29c/0x470 __arm64_sys_copy_file_range+0xcc/0x498 invoke_syscall.constprop.0+0x80/0xd8 do_el0_svc+0x6c/0x168 el0_svc+0x50/0x1b0 el0t_64_sync_handler+0x114/0x120 el0t_64_sync+0x194/0x198 This happens because during btrfs_cont_expand we'll get a page, set it as mapped, and if it's not Uptodate we'll read it. However between the read and re-locking the page we could have called release_folio() on the page, but left the page in the file mapping. release_folio() can clear the page private, and thus further down we blow up when we go to modify the subpage bits. Fix this by putting the set_page_extent_mapped() after the read. This is safe because read_folio() will call set_page_extent_mapped() before it does the read, and then if we clear page private but leave it on the mapping we're completely safe re-setting set_page_extent_mapped(). With this patch I can now run generic/476 without panicing. CVE-2023-53247 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53247.html CVE-2023-53247 https://bugzilla.suse.com/1249870 SUSE Bug 1249870 In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: install stub fence into potential unused fence pointers When using cpu to update page tables, vm update fences are unused. Install stub fence into these fence pointers instead of NULL to avoid NULL dereference when calling dma_fence_wait() on them. CVE-2023-53248 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53248.html CVE-2023-53248 https://bugzilla.suse.com/1249779 SUSE Bug 1249779 In the Linux kernel, the following vulnerability has been resolved: clk: imx: clk-imx8mn: fix memory leak in imx8mn_clocks_probe Use devm_of_iomap() instead of of_iomap() to automatically handle the unused ioremap region. If any error occurs, regions allocated by kzalloc() will leak, but using devm_kzalloc() instead will automatically free the memory using devm_kfree(). CVE-2023-53249 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53249.html CVE-2023-53249 https://bugzilla.suse.com/1249642 SUSE Bug 1249642 In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: pcie: fix NULL pointer dereference in iwl_pcie_irq_rx_msix_handler() rxq can be NULL only when trans_pcie->rxq is NULL and entry->entry is zero. For the case when entry->entry is not equal to 0, rxq won't be NULL even if trans_pcie->rxq is NULL. Modify checker to check for trans_pcie->rxq. CVE-2023-53251 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53251.html CVE-2023-53251 https://bugzilla.suse.com/1249730 SUSE Bug 1249730 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: use RCU for hci_conn_params and iterate safely in hci_sync hci_update_accept_list_sync iterates over hdev->pend_le_conns and hdev->pend_le_reports, and waits for controller events in the loop body, without holding hdev lock. Meanwhile, these lists and the items may be modified e.g. by le_scan_cleanup. This can invalidate the list cursor or any other item in the list, resulting to invalid behavior (eg use-after-free). Use RCU for the hci_conn_params action lists. Since the loop bodies in hci_sync block and we cannot use RCU or hdev->lock for the whole loop, copy list items first and then iterate on the copy. Only the flags field is written from elsewhere, so READ_ONCE/WRITE_ONCE should guarantee we read valid values. Free params everywhere with hci_conn_params_free so the cleanup is guaranteed to be done properly. This fixes the following, which can be triggered e.g. by BlueZ new mgmt-tester case "Add + Remove Device Nowait - Success", or by changing hci_le_set_cig_params to always return false, and running iso-tester: ================================================================== BUG: KASAN: slab-use-after-free in hci_update_passive_scan_sync (net/bluetooth/hci_sync.c:2536 net/bluetooth/hci_sync.c:2723 net/bluetooth/hci_sync.c:2841) Read of size 8 at addr ffff888001265018 by task kworker/u3:0/32 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-1.fc38 04/01/2014 Workqueue: hci0 hci_cmd_sync_work Call Trace: <TASK> dump_stack_lvl (./arch/x86/include/asm/irqflags.h:134 lib/dump_stack.c:107) print_report (mm/kasan/report.c:320 mm/kasan/report.c:430) ? __virt_addr_valid (./include/linux/mmzone.h:1915 ./include/linux/mmzone.h:2011 arch/x86/mm/physaddr.c:65) ? hci_update_passive_scan_sync (net/bluetooth/hci_sync.c:2536 net/bluetooth/hci_sync.c:2723 net/bluetooth/hci_sync.c:2841) kasan_report (mm/kasan/report.c:538) ? hci_update_passive_scan_sync (net/bluetooth/hci_sync.c:2536 net/bluetooth/hci_sync.c:2723 net/bluetooth/hci_sync.c:2841) hci_update_passive_scan_sync (net/bluetooth/hci_sync.c:2536 net/bluetooth/hci_sync.c:2723 net/bluetooth/hci_sync.c:2841) ? __pfx_hci_update_passive_scan_sync (net/bluetooth/hci_sync.c:2780) ? mutex_lock (kernel/locking/mutex.c:282) ? __pfx_mutex_lock (kernel/locking/mutex.c:282) ? __pfx_mutex_unlock (kernel/locking/mutex.c:538) ? __pfx_update_passive_scan_sync (net/bluetooth/hci_sync.c:2861) hci_cmd_sync_work (net/bluetooth/hci_sync.c:306) process_one_work (./arch/x86/include/asm/preempt.h:27 kernel/workqueue.c:2399) worker_thread (./include/linux/list.h:292 kernel/workqueue.c:2538) ? __pfx_worker_thread (kernel/workqueue.c:2480) kthread (kernel/kthread.c:376) ? __pfx_kthread (kernel/kthread.c:331) ret_from_fork (arch/x86/entry/entry_64.S:314) </TASK> Allocated by task 31: kasan_save_stack (mm/kasan/common.c:46) kasan_set_track (mm/kasan/common.c:52) __kasan_kmalloc (mm/kasan/common.c:374 mm/kasan/common.c:383) hci_conn_params_add (./include/linux/slab.h:580 ./include/linux/slab.h:720 net/bluetooth/hci_core.c:2277) hci_connect_le_scan (net/bluetooth/hci_conn.c:1419 net/bluetooth/hci_conn.c:1589) hci_connect_cis (net/bluetooth/hci_conn.c:2266) iso_connect_cis (net/bluetooth/iso.c:390) iso_sock_connect (net/bluetooth/iso.c:899) __sys_connect (net/socket.c:2003 net/socket.c:2020) __x64_sys_connect (net/socket.c:2027) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) Freed by task 15: kasan_save_stack (mm/kasan/common.c:46) kasan_set_track (mm/kasan/common.c:52) kasan_save_free_info (mm/kasan/generic.c:523) __kasan_slab_free (mm/kasan/common.c:238 mm/kasan/common.c:200 mm/kasan/common.c:244) __kmem_cache_free (mm/slub.c:1807 mm/slub.c:3787 mm/slub.c:3800) hci_conn_params_del (net/bluetooth/hci_core.c:2323) le_scan_cleanup (net/bluetooth/hci_conn.c:202) process_one_work (./arch/x86/include/asm/preempt. ---truncated--- CVE-2023-53252 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53252.html CVE-2023-53252 https://bugzilla.suse.com/1249756 SUSE Bug 1249756 In the Linux kernel, the following vulnerability has been resolved: firmware: stratix10-svc: Fix a potential resource leak in svc_create_memory_pool() svc_create_memory_pool() is only called from stratix10_svc_drv_probe(). Most of resources in the probe are managed, but not this memremap() call. There is also no memunmap() call in the file. So switch to devm_memremap() to avoid a resource leak. CVE-2023-53255 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53255.html CVE-2023-53255 https://bugzilla.suse.com/1249762 SUSE Bug 1249762 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: check S1G action frame size Before checking the action code, check that it even exists in the frame. CVE-2023-53257 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53257.html CVE-2023-53257 https://bugzilla.suse.com/1249869 SUSE Bug 1249869 https://bugzilla.suse.com/1250730 SUSE Bug 1250730 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix possible underflow for displays with large vblank [Why] Underflow observed when using a display with a large vblank region and low refresh rate [How] Simplify calculation of vblank_nom Increase value for VBlankNomDefaultUS to 800us CVE-2023-53258 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53258.html CVE-2023-53258 https://bugzilla.suse.com/1249780 SUSE Bug 1249780 In the Linux kernel, the following vulnerability has been resolved: ovl: fix null pointer dereference in ovl_permission() Following process: P1 P2 path_lookupat link_path_walk inode_permission ovl_permission ovl_i_path_real(inode, &realpath) path->dentry = ovl_i_dentry_upper(inode) drop_cache __dentry_kill(ovl_dentry) iput(ovl_inode) ovl_destroy_inode(ovl_inode) dput(oi->__upperdentry) dentry_kill(upperdentry) dentry_unlink_inode upperdentry->d_inode = NULL realinode = d_inode(realpath.dentry) // return NULL inode_permission(realinode) inode->i_sb // NULL pointer dereference , will trigger an null pointer dereference at realinode: [ 335.664979] BUG: kernel NULL pointer dereference, address: 0000000000000002 [ 335.668032] CPU: 0 PID: 2592 Comm: ls Not tainted 6.3.0 [ 335.669956] RIP: 0010:inode_permission+0x33/0x2c0 [ 335.678939] Call Trace: [ 335.679165] <TASK> [ 335.679371] ovl_permission+0xde/0x320 [ 335.679723] inode_permission+0x15e/0x2c0 [ 335.680090] link_path_walk+0x115/0x550 [ 335.680771] path_lookupat.isra.0+0xb2/0x200 [ 335.681170] filename_lookup+0xda/0x240 [ 335.681922] vfs_statx+0xa6/0x1f0 [ 335.682233] vfs_fstatat+0x7b/0xb0 Fetch a reproducer in [Link]. Use the helper ovl_i_path_realinode() to get realinode and then do non-nullptr checking. CVE-2023-53260 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53260.html CVE-2023-53260 https://bugzilla.suse.com/1249768 SUSE Bug 1249768 In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/disp: fix use-after-free in error handling of nouveau_connector_create We can't simply free the connector after calling drm_connector_init on it. We need to clean up the drm side first. It might not fix all regressions from commit 2b5d1c29f6c4 ("drm/nouveau/disp: PIOR DP uses GPIO for HPD, not PMGR AUX interrupts"), but at least it fixes a memory corruption in error handling related to that commit. CVE-2023-53263 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53263.html CVE-2023-53263 https://bugzilla.suse.com/1249861 SUSE Bug 1249861 https://bugzilla.suse.com/1253190 SUSE Bug 1253190 In the Linux kernel, the following vulnerability has been resolved: clk: imx: clk-imxrt1050: fix memory leak in imxrt1050_clocks_probe Use devm_of_iomap() instead of of_iomap() to automatically handle the unused ioremap region. If any error occurs, regions allocated by kzalloc() will leak, but using devm_kzalloc() instead will automatically free the memory using devm_kfree(). Also, fix error handling of hws by adding unregister_hws label, which unregisters remaining hws when iomap failed. CVE-2023-53264 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53264.html CVE-2023-53264 https://bugzilla.suse.com/1249795 SUSE Bug 1249795 In the Linux kernel, the following vulnerability has been resolved: net: ena: fix shift-out-of-bounds in exponential backoff The ENA adapters on our instances occasionally reset. Once recently logged a UBSAN failure to console in the process: UBSAN: shift-out-of-bounds in build/linux/drivers/net/ethernet/amazon/ena/ena_com.c:540:13 shift exponent 32 is too large for 32-bit type 'unsigned int' CPU: 28 PID: 70012 Comm: kworker/u72:2 Kdump: loaded not tainted 5.15.117 Hardware name: Amazon EC2 c5d.9xlarge/, BIOS 1.0 10/16/2017 Workqueue: ena ena_fw_reset_device [ena] Call Trace: <TASK> dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x36 __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e ? __const_udelay+0x43/0x50 ena_delay_exponential_backoff_us.cold+0x16/0x1e [ena] wait_for_reset_state+0x54/0xa0 [ena] ena_com_dev_reset+0xc8/0x110 [ena] ena_down+0x3fe/0x480 [ena] ena_destroy_device+0xeb/0xf0 [ena] ena_fw_reset_device+0x30/0x50 [ena] process_one_work+0x22b/0x3d0 worker_thread+0x4d/0x3f0 ? process_one_work+0x3d0/0x3d0 kthread+0x12a/0x150 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x22/0x30 </TASK> Apparently, the reset delays are getting so large they can trigger a UBSAN panic. Looking at the code, the current timeout is capped at 5000us. Using a base value of 100us, the current code will overflow after (1<<29). Even at values before 32, this function wraps around, perhaps unintentionally. Cap the value of the exponent used for this backoff at (1<<16) which is larger than currently necessary, but large enough to support bigger values in the future. CVE-2023-53272 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53272.html CVE-2023-53272 https://bugzilla.suse.com/1249917 SUSE Bug 1249917 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: mt8183: Add back SSPM related clocks This reverts commit 860690a93ef23b567f781c1b631623e27190f101. On the MT8183, the SSPM related clocks were removed claiming a lack of usage. This however causes some issues when the driver was converted to the new simple-probe mechanism. This mechanism allocates enough space for all the clocks defined in the clock driver, not the highest index in the DT binding. This leads to out-of-bound writes if their are holes in the DT binding or the driver (due to deprecated or unimplemented clocks). These errors can go unnoticed and cause memory corruption, leading to crashes in unrelated areas, or nothing at all. KASAN will detect them. Add the SSPM related clocks back to the MT8183 clock driver to fully implement the DT binding. The SSPM clocks are for the power management co-processor, and should never be turned off. They are marked as such. CVE-2023-53274 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53274.html CVE-2023-53274 https://bugzilla.suse.com/1249919 SUSE Bug 1249919 In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: fix a possible null-pointer dereference due to data race in snd_hdac_regmap_sync() The variable codec->regmap is often protected by the lock codec->regmap_lock when is accessed. However, it is accessed without holding the lock when is accessed in snd_hdac_regmap_sync(): if (codec->regmap) In my opinion, this may be a harmful race, because if codec->regmap is set to NULL right after the condition is checked, a null-pointer dereference can occur in the called function regcache_sync(): map->lock(map->lock_arg); --> Line 360 in drivers/base/regmap/regcache.c To fix this possible null-pointer dereference caused by data race, the mutex_lock coverage is extended to protect the if statement as well as the function call to regcache_sync(). [ Note: the lack of the regmap_lock itself is harmless for the current codec driver implementations, as snd_hdac_regmap_sync() is only for PM runtime resume that is prohibited during the codec probe. But the change makes the whole code more consistent, so it's merged as is -- tiwai ] CVE-2023-53275 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53275.html CVE-2023-53275 https://bugzilla.suse.com/1250459 SUSE Bug 1250459 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue System crash when qla2x00_start_sp(sp) returns error code EGAIN and wake_up gets called for uninitialized wait queue sp->nvme_ls_waitq. qla2xxx [0000:37:00.1]-2121:5: Returning existing qpair of ffff8ae2c0513400 for idx=0 qla2xxx [0000:37:00.1]-700e:5: qla2x00_start_sp failed = 11 BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 09/03/2021 Workqueue: nvme-wq nvme_fc_connect_ctrl_work [nvme_fc] RIP: 0010:__wake_up_common+0x4c/0x190 RSP: 0018:ffff95f3e0cb7cd0 EFLAGS: 00010086 RAX: 0000000000000000 RBX: ffff8b08d3b26328 RCX: 0000000000000000 RDX: 0000000000000001 RSI: 0000000000000003 RDI: ffff8b08d3b26320 RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffffffffffe8 R10: 0000000000000000 R11: ffff95f3e0cb7a60 R12: ffff95f3e0cb7d20 R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8b2fdf6c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000002f1e410002 CR4: 00000000007706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: __wake_up_common_lock+0x7c/0xc0 qla_nvme_ls_req+0x355/0x4c0 [qla2xxx] ? __nvme_fc_send_ls_req+0x260/0x380 [nvme_fc] ? nvme_fc_send_ls_req.constprop.42+0x1a/0x45 [nvme_fc] ? nvme_fc_connect_ctrl_work.cold.63+0x1e3/0xa7d [nvme_fc] Remove unused nvme_ls_waitq wait queue. nvme_ls_waitq logic was removed previously in the commits tagged Fixed: below. CVE-2023-53280 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53280.html CVE-2023-53280 https://bugzilla.suse.com/1249938 SUSE Bug 1249938 In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Return the firmware result upon destroying QP/RQ Previously when destroying a QP/RQ, the result of the firmware destruction function was ignored and upper layers weren't informed about the failure. Which in turn could lead to various problems since when upper layer isn't aware of the failure it continues its operation thinking that the related QP/RQ was successfully destroyed while it actually wasn't, which could lead to the below kernel WARN. Currently, we return the correct firmware destruction status to upper layers which in case of the RQ would be mlx5_ib_destroy_wq() which was already capable of handling RQ destruction failure or in case of a QP to destroy_qp_common(), which now would actually warn upon qp destruction failure. WARNING: CPU: 3 PID: 995 at drivers/infiniband/core/rdma_core.c:940 uverbs_destroy_ufile_hw+0xcb/0xe0 [ib_uverbs] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_umad ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core overlay mlx5_core fuse CPU: 3 PID: 995 Comm: python3 Not tainted 5.16.0-rc5+ #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:uverbs_destroy_ufile_hw+0xcb/0xe0 [ib_uverbs] Code: 41 5c 41 5d 41 5e e9 44 34 f0 e0 48 89 df e8 4c 77 ff ff 49 8b 86 10 01 00 00 48 85 c0 74 a1 4c 89 e7 ff d0 eb 9a 0f 0b eb c1 <0f> 0b be 04 00 00 00 48 89 df e8 b6 f6 ff ff e9 75 ff ff ff 90 0f RSP: 0018:ffff8881533e3e78 EFLAGS: 00010287 RAX: ffff88811b2cf3e0 RBX: ffff888106209700 RCX: 0000000000000000 RDX: ffff888106209780 RSI: ffff8881533e3d30 RDI: ffff888109b101a0 RBP: 0000000000000001 R08: ffff888127cb381c R09: 0de9890000000009 R10: ffff888127cb3800 R11: 0000000000000000 R12: ffff888106209780 R13: ffff888106209750 R14: ffff888100f20660 R15: 0000000000000000 FS: 00007f8be353b740(0000) GS:ffff88852c980000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8bd5b117c0 CR3: 000000012cd8a004 CR4: 0000000000370ea0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ib_uverbs_close+0x1a/0x90 [ib_uverbs] __fput+0x82/0x230 task_work_run+0x59/0x90 exit_to_user_mode_prepare+0x138/0x140 syscall_exit_to_user_mode+0x1d/0x50 ? __x64_sys_close+0xe/0x40 do_syscall_64+0x4a/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f8be3ae0abb Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 83 43 f9 ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 c1 43 f9 ff 8b 44 RSP: 002b:00007ffdb51909c0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 RAX: 0000000000000000 RBX: 0000557bb7f7c020 RCX: 00007f8be3ae0abb RDX: 0000557bb7c74010 RSI: 0000557bb7f14ca0 RDI: 0000000000000005 RBP: 0000557bb7fbd598 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000293 R12: 0000557bb7fbd5b8 R13: 0000557bb7fbd5a8 R14: 0000000000001000 R15: 0000557bb7f7c020 </TASK> CVE-2023-53286 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53286.html CVE-2023-53286 https://bugzilla.suse.com/1250325 SUSE Bug 1250325 In the Linux kernel, the following vulnerability has been resolved: usb: cdns3: Put the cdns set active part outside the spin lock The device may be scheduled during the resume process, so this cannot appear in atomic operations. Since pm_runtime_set_active will resume suppliers, put set active outside the spin lock, which is only used to protect the struct cdns data structure, otherwise the kernel will report the following warning: BUG: sleeping function called from invalid context at drivers/base/power/runtime.c:1163 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 651, name: sh preempt_count: 1, expected: 0 RCU nest depth: 0, expected: 0 CPU: 0 PID: 651 Comm: sh Tainted: G WC 6.1.20 #1 Hardware name: Freescale i.MX8QM MEK (DT) Call trace: dump_backtrace.part.0+0xe0/0xf0 show_stack+0x18/0x30 dump_stack_lvl+0x64/0x80 dump_stack+0x1c/0x38 __might_resched+0x1fc/0x240 __might_sleep+0x68/0xc0 __pm_runtime_resume+0x9c/0xe0 rpm_get_suppliers+0x68/0x1b0 __pm_runtime_set_status+0x298/0x560 cdns_resume+0xb0/0x1c0 cdns3_controller_resume.isra.0+0x1e0/0x250 cdns3_plat_resume+0x28/0x40 CVE-2023-53287 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53287.html CVE-2023-53287 https://bugzilla.suse.com/1250089 SUSE Bug 1250089 In the Linux kernel, the following vulnerability has been resolved: drm/client: Fix memory leak in drm_client_modeset_probe When a new mode is set to modeset->mode, the previous mode should be freed. This fixes the following kmemleak report: drm_mode_duplicate+0x45/0x220 [drm] drm_client_modeset_probe+0x944/0xf50 [drm] __drm_fb_helper_initial_config_and_unlock+0xb4/0x2c0 [drm_kms_helper] drm_fbdev_client_hotplug+0x2bc/0x4d0 [drm_kms_helper] drm_client_register+0x169/0x240 [drm] ast_pci_probe+0x142/0x190 [ast] local_pci_probe+0xdc/0x180 work_for_cpu_fn+0x4e/0xa0 process_one_work+0x8b7/0x1540 worker_thread+0x70a/0xed0 kthread+0x29f/0x340 ret_from_fork+0x1f/0x30 CVE-2023-53288 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53288.html CVE-2023-53288 https://bugzilla.suse.com/1250058 SUSE Bug 1250058 In the Linux kernel, the following vulnerability has been resolved: rcu/rcuscale: Stop kfree_scale_thread thread(s) after unloading rcuscale Running the 'kfree_rcu_test' test case [1] results in a splat [2]. The root cause is the kfree_scale_thread thread(s) continue running after unloading the rcuscale module. This commit fixes that isue by invoking kfree_scale_cleanup() from rcu_scale_cleanup() when removing the rcuscale module. [1] modprobe rcuscale kfree_rcu_test=1 // After some time rmmod rcuscale rmmod torture [2] BUG: unable to handle page fault for address: ffffffffc0601a87 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page PGD 11de4f067 P4D 11de4f067 PUD 11de51067 PMD 112f4d067 PTE 0 Oops: 0010 [#1] PREEMPT SMP NOPTI CPU: 1 PID: 1798 Comm: kfree_scale_thr Not tainted 6.3.0-rc1-rcu+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 RIP: 0010:0xffffffffc0601a87 Code: Unable to access opcode bytes at 0xffffffffc0601a5d. RSP: 0018:ffffb25bc2e57e18 EFLAGS: 00010297 RAX: 0000000000000000 RBX: ffffffffc061f0b6 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff962fd0de RDI: ffffffff962fd0de RBP: ffffb25bc2e57ea8 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000000 R13: 0000000000000000 R14: 000000000000000a R15: 00000000001c1dbe FS: 0000000000000000(0000) GS:ffff921fa2200000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffc0601a5d CR3: 000000011de4c006 CR4: 0000000000370ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? kvfree_call_rcu+0xf0/0x3a0 ? kthread+0xf3/0x120 ? kthread_complete_and_exit+0x20/0x20 ? ret_from_fork+0x1f/0x30 </TASK> Modules linked in: rfkill sunrpc ... [last unloaded: torture] CR2: ffffffffc0601a87 ---[ end trace 0000000000000000 ]--- CVE-2023-53291 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53291.html CVE-2023-53291 https://bugzilla.suse.com/1249926 SUSE Bug 1249926 In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix NULL dereference on q->elevator in blk_mq_elv_switch_none After grabbing q->sysfs_lock, q->elevator may become NULL because of elevator switch. Fix the NULL dereference on q->elevator by checking it with lock. CVE-2023-53292 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53292.html CVE-2023-53292 https://bugzilla.suse.com/1250163 SUSE Bug 1250163 In the Linux kernel, the following vulnerability has been resolved: net: microchip: vcap api: Fix possible memory leak for vcap_dup_rule() Inject fault When select CONFIG_VCAP_KUNIT_TEST, the below memory leak occurs. If kzalloc() for duprule succeeds, but the following kmemdup() fails, the duprule, ckf and caf memory will be leaked. So kfree them in the error path. unreferenced object 0xffff122744c50600 (size 192): comm "kunit_try_catch", pid 346, jiffies 4294896122 (age 911.812s) hex dump (first 32 bytes): 10 27 00 00 04 00 00 00 1e 00 00 00 2c 01 00 00 .'..........,... 00 00 00 00 00 00 00 00 18 06 c5 44 27 12 ff ff ...........D'... backtrace: [<00000000394b0db8>] __kmem_cache_alloc_node+0x274/0x2f8 [<0000000001bedc67>] kmalloc_trace+0x38/0x88 [<00000000b0612f98>] vcap_dup_rule+0x50/0x460 [<000000005d2d3aca>] vcap_add_rule+0x8cc/0x1038 [<00000000eef9d0f8>] test_vcap_xn_rule_creator.constprop.0.isra.0+0x238/0x494 [<00000000cbda607b>] vcap_api_rule_remove_in_front_test+0x1ac/0x698 [<00000000c8766299>] kunit_try_run_case+0xe0/0x20c [<00000000c4fe9186>] kunit_generic_run_threadfn_adapter+0x50/0x94 [<00000000f6864acf>] kthread+0x2e8/0x374 [<0000000022e639b3>] ret_from_fork+0x10/0x20 CVE-2023-53303 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53303.html CVE-2023-53303 https://bugzilla.suse.com/1249896 SUSE Bug 1249896 In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: fix overlap expiration walk The lazy gc on insert that should remove timed-out entries fails to release the other half of the interval, if any. Can be reproduced with tests/shell/testcases/sets/0044interval_overlap_0 in nftables.git and kmemleak enabled kernel. Second bug is the use of rbe_prev vs. prev pointer. If rbe_prev() returns NULL after at least one iteration, rbe_prev points to element that is not an end interval, hence it should not be removed. Lastly, check the genmask of the end interval if this is active in the current generation. CVE-2023-53304 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53304.html CVE-2023-53304 https://bugzilla.suse.com/1249923 SUSE Bug 1249923 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free Fix potential use-after-free in l2cap_le_command_rej. CVE-2023-53305 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53305.html CVE-2023-53305 https://bugzilla.suse.com/1250049 SUSE Bug 1250049 In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Fix integer overflow in radeon_cs_parser_init The type of size is unsigned, if size is 0x40000000, there will be an integer overflow, size will be zero after size *= sizeof(uint32_t), will cause uninitialized memory to be referenced later CVE-2023-53309 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53309.html CVE-2023-53309 https://bugzilla.suse.com/1250055 SUSE Bug 1250055 In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput During unmount process of nilfs2, nothing holds nilfs_root structure after nilfs2 detaches its writer in nilfs_detach_log_writer(). Previously, nilfs_evict_inode() could cause use-after-free read for nilfs_root if inodes are left in "garbage_list" and released by nilfs_dispose_list at the end of nilfs_detach_log_writer(), and this bug was fixed by commit 9b5a04ac3ad9 ("nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode()"). However, it turned out that there is another possibility of UAF in the call path where mark_inode_dirty_sync() is called from iput(): nilfs_detach_log_writer() nilfs_dispose_list() iput() mark_inode_dirty_sync() __mark_inode_dirty() nilfs_dirty_inode() __nilfs_mark_inode_dirty() nilfs_load_inode_block() --> causes UAF of nilfs_root struct This can happen after commit 0ae45f63d4ef ("vfs: add support for a lazytime mount option"), which changed iput() to call mark_inode_dirty_sync() on its final reference if i_state has I_DIRTY_TIME flag and i_nlink is non-zero. This issue appears after commit 28a65b49eb53 ("nilfs2: do not write dirty data after degenerating to read-only") when using the syzbot reproducer, but the issue has potentially existed before. Fix this issue by adding a "purging flag" to the nilfs structure, setting that flag while disposing the "garbage_list" and checking it in __nilfs_mark_inode_dirty(). Unlike commit 9b5a04ac3ad9 ("nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode()"), this patch does not rely on ns_writer to determine whether to skip operations, so as not to break recovery on mount. The nilfs_salvage_orphan_logs routine dirties the buffer of salvaged data before attaching the log writer, so changing __nilfs_mark_inode_dirty() to skip the operation when ns_writer is NULL will cause recovery write to fail. The purpose of using the cleanup-only flag is to allow for narrowing of such conditions. CVE-2023-53311 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53311.html CVE-2023-53311 https://bugzilla.suse.com/1250062 SUSE Bug 1250062 In the Linux kernel, the following vulnerability has been resolved: net: fix net_dev_start_xmit trace event vs skb_transport_offset() After blamed commit, we must be more careful about using skb_transport_offset(), as reminded us by syzbot: WARNING: CPU: 0 PID: 10 at include/linux/skbuff.h:2868 skb_transport_offset include/linux/skbuff.h:2977 [inline] WARNING: CPU: 0 PID: 10 at include/linux/skbuff.h:2868 perf_trace_net_dev_start_xmit+0x89a/0xce0 include/trace/events/net.h:14 Modules linked in: CPU: 0 PID: 10 Comm: kworker/u4:1 Not tainted 6.1.30-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Workqueue: bat_events batadv_iv_send_outstanding_bat_ogm_packet RIP: 0010:skb_transport_header include/linux/skbuff.h:2868 [inline] RIP: 0010:skb_transport_offset include/linux/skbuff.h:2977 [inline] RIP: 0010:perf_trace_net_dev_start_xmit+0x89a/0xce0 include/trace/events/net.h:14 Code: 8b 04 25 28 00 00 00 48 3b 84 24 c0 00 00 00 0f 85 4e 04 00 00 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc e8 56 22 01 fd <0f> 0b e9 f6 fc ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 86 f9 ff RSP: 0018:ffffc900002bf700 EFLAGS: 00010293 RAX: ffffffff8485d8ca RBX: 000000000000ffff RCX: ffff888100914280 RDX: 0000000000000000 RSI: 000000000000ffff RDI: 000000000000ffff RBP: ffffc900002bf818 R08: ffffffff8485d5b6 R09: fffffbfff0f8fb5e R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff110217d8f67 R13: ffff88810bec7b3a R14: dffffc0000000000 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff8881f6a00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f96cf6d52f0 CR3: 000000012224c000 CR4: 0000000000350ef0 Call Trace: <TASK> [<ffffffff84715e35>] trace_net_dev_start_xmit include/trace/events/net.h:14 [inline] [<ffffffff84715e35>] xmit_one net/core/dev.c:3643 [inline] [<ffffffff84715e35>] dev_hard_start_xmit+0x705/0x980 net/core/dev.c:3660 [<ffffffff8471a232>] __dev_queue_xmit+0x16b2/0x3370 net/core/dev.c:4324 [<ffffffff85416493>] dev_queue_xmit include/linux/netdevice.h:3030 [inline] [<ffffffff85416493>] batadv_send_skb_packet+0x3f3/0x680 net/batman-adv/send.c:108 [<ffffffff85416744>] batadv_send_broadcast_skb+0x24/0x30 net/batman-adv/send.c:127 [<ffffffff853bc52a>] batadv_iv_ogm_send_to_if net/batman-adv/bat_iv_ogm.c:393 [inline] [<ffffffff853bc52a>] batadv_iv_ogm_emit net/batman-adv/bat_iv_ogm.c:421 [inline] [<ffffffff853bc52a>] batadv_iv_send_outstanding_bat_ogm_packet+0x69a/0x840 net/batman-adv/bat_iv_ogm.c:1701 [<ffffffff8151023c>] process_one_work+0x8ac/0x1170 kernel/workqueue.c:2289 [<ffffffff81511938>] worker_thread+0xaa8/0x12d0 kernel/workqueue.c:2436 CVE-2023-53312 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53312.html CVE-2023-53312 https://bugzilla.suse.com/1250063 SUSE Bug 1250063 In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix wrong setting of max_corr_read_errors There is no input check when echo md/max_read_errors and overflow might occur. Add check of input number. CVE-2023-53313 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53313.html CVE-2023-53313 https://bugzilla.suse.com/1249911 SUSE Bug 1249911 In the Linux kernel, the following vulnerability has been resolved: fbdev/ep93xx-fb: Do not assign to struct fb_info.dev Do not assing the Linux device to struct fb_info.dev. The call to register_framebuffer() initializes the field to the fbdev device. Drivers should not override its value. Fixes a bug where the driver incorrectly decreases the hardware device's reference counter and leaks the fbdev device. v2: * add Fixes tag (Dan) CVE-2023-53314 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53314.html CVE-2023-53314 https://bugzilla.suse.com/1250065 SUSE Bug 1250065 In the Linux kernel, the following vulnerability has been resolved: drm/msm/dp: Free resources after unregistering them The DP component's unbind operation walks through the submodules to unregister and clean things up. But if the unbind happens because the DP controller itself is being removed, all the memory for those submodules has just been freed. Change the order of these operations to avoid the many use-after-free that otherwise happens in this code path. Patchwork: https://patchwork.freedesktop.org/patch/542166/ CVE-2023-53316 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53316.html CVE-2023-53316 https://bugzilla.suse.com/1250066 SUSE Bug 1250066 In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle kvm_arm_init failure correctly in finalize_pkvm Currently there is no synchronisation between finalize_pkvm() and kvm_arm_init() initcalls. The finalize_pkvm() proceeds happily even if kvm_arm_init() fails resulting in the following warning on all the CPUs and eventually a HYP panic: | kvm [1]: IPA Size Limit: 48 bits | kvm [1]: Failed to init hyp memory protection | kvm [1]: error initializing Hyp mode: -22 | | <snip> | | WARNING: CPU: 0 PID: 0 at arch/arm64/kvm/pkvm.c:226 _kvm_host_prot_finalize+0x30/0x50 | Modules linked in: | CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.4.0 #237 | Hardware name: FVP Base RevC (DT) | pstate: 634020c5 (nZCv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=--) | pc : _kvm_host_prot_finalize+0x30/0x50 | lr : __flush_smp_call_function_queue+0xd8/0x230 | | Call trace: | _kvm_host_prot_finalize+0x3c/0x50 | on_each_cpu_cond_mask+0x3c/0x6c | pkvm_drop_host_privileges+0x4c/0x78 | finalize_pkvm+0x3c/0x5c | do_one_initcall+0xcc/0x240 | do_initcall_level+0x8c/0xac | do_initcalls+0x54/0x94 | do_basic_setup+0x1c/0x28 | kernel_init_freeable+0x100/0x16c | kernel_init+0x20/0x1a0 | ret_from_fork+0x10/0x20 | Failed to finalize Hyp protection: -22 | dtb=fvp-base-revc.dtb | kvm [95]: nVHE hyp BUG at: arch/arm64/kvm/hyp/nvhe/mem_protect.c:540! | kvm [95]: nVHE call trace: | kvm [95]: [<ffff800081052984>] __kvm_nvhe_hyp_panic+0xac/0xf8 | kvm [95]: [<ffff800081059644>] __kvm_nvhe_handle_host_mem_abort+0x1a0/0x2ac | kvm [95]: [<ffff80008105511c>] __kvm_nvhe_handle_trap+0x4c/0x160 | kvm [95]: [<ffff8000810540fc>] __kvm_nvhe___skip_pauth_save+0x4/0x4 | kvm [95]: ---[ end nVHE call trace ]--- | kvm [95]: Hyp Offset: 0xfffe8db00ffa0000 | Kernel panic - not syncing: HYP panic: | PS:a34023c9 PC:0000f250710b973c ESR:00000000f2000800 | FAR:ffff000800cb00d0 HPFAR:000000000880cb00 PAR:0000000000000000 | VCPU:0000000000000000 | CPU: 3 PID: 95 Comm: kworker/u16:2 Tainted: G W 6.4.0 #237 | Hardware name: FVP Base RevC (DT) | Workqueue: rpciod rpc_async_schedule | Call trace: | dump_backtrace+0xec/0x108 | show_stack+0x18/0x2c | dump_stack_lvl+0x50/0x68 | dump_stack+0x18/0x24 | panic+0x138/0x33c | nvhe_hyp_panic_handler+0x100/0x184 | new_slab+0x23c/0x54c | ___slab_alloc+0x3e4/0x770 | kmem_cache_alloc_node+0x1f0/0x278 | __alloc_skb+0xdc/0x294 | tcp_stream_alloc_skb+0x2c/0xf0 | tcp_sendmsg_locked+0x3d0/0xda4 | tcp_sendmsg+0x38/0x5c | inet_sendmsg+0x44/0x60 | sock_sendmsg+0x1c/0x34 | xprt_sock_sendmsg+0xdc/0x274 | xs_tcp_send_request+0x1ac/0x28c | xprt_transmit+0xcc/0x300 | call_transmit+0x78/0x90 | __rpc_execute+0x114/0x3d8 | rpc_async_schedule+0x28/0x48 | process_one_work+0x1d8/0x314 | worker_thread+0x248/0x474 | kthread+0xfc/0x184 | ret_from_fork+0x10/0x20 | SMP: stopping secondary CPUs | Kernel Offset: 0x57c5cb460000 from 0xffff800080000000 | PHYS_OFFSET: 0x80000000 | CPU features: 0x00000000,1035b7a3,ccfe773f | Memory Limit: none | ---[ end Kernel panic - not syncing: HYP panic: | PS:a34023c9 PC:0000f250710b973c ESR:00000000f2000800 | FAR:ffff000800cb00d0 HPFAR:000000000880cb00 PAR:0000000000000000 | VCPU:0000000000000000 ]--- Fix it by checking for the successfull initialisation of kvm_arm_init() in finalize_pkvm() before proceeding any futher. CVE-2023-53319 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53319.html CVE-2023-53319 https://bugzilla.suse.com/1250067 SUSE Bug 1250067 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211_hwsim: drop short frames While technically some control frames like ACK are shorter and end after Address 1, such frames shouldn't be forwarded through wmediumd or similar userspace, so require the full 3-address header to avoid accessing invalid memory if shorter frames are passed in. CVE-2023-53321 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53321.html CVE-2023-53321 https://bugzilla.suse.com/1250313 SUSE Bug 1250313 https://bugzilla.suse.com/1250314 SUSE Bug 1250314 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Wait for io return on terminate rport System crash due to use after free. Current code allows terminate_rport_io to exit before making sure all IOs has returned. For FCP-2 device, IO's can hang on in HW because driver has not tear down the session in FW at first sign of cable pull. When dev_loss_tmo timer pops, terminate_rport_io is called and upper layer is about to free various resources. Terminate_rport_io trigger qla to do the final cleanup, but the cleanup might not be fast enough where it leave qla still holding on to the same resource. Wait for IO's to return to upper layer before resources are freed. CVE-2023-53322 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53322.html CVE-2023-53322 https://bugzilla.suse.com/1250323 SUSE Bug 1250323 In the Linux kernel, the following vulnerability has been resolved: ext2/dax: Fix ext2_setsize when len is page aligned PAGE_ALIGN(x) macro gives the next highest value which is multiple of pagesize. But if x is already page aligned then it simply returns x. So, if x passed is 0 in dax_zero_range() function, that means the length gets passed as 0 to ->iomap_begin(). In ext2 it then calls ext2_get_blocks -> max_blocks as 0 and hits bug_on here in ext2_get_blocks(). BUG_ON(maxblocks == 0); Instead we should be calling dax_truncate_page() here which takes care of it. i.e. it only calls dax_zero_range if the offset is not page/block aligned. This can be easily triggered with following on fsdax mounted pmem device. dd if=/dev/zero of=file count=1 bs=512 truncate -s 0 file [79.525838] EXT2-fs (pmem0): DAX enabled. Warning: EXPERIMENTAL, use at your own risk [79.529376] ext2 filesystem being mounted at /mnt1/test supports timestamps until 2038 (0x7fffffff) [93.793207] ------------[ cut here ]------------ [93.795102] kernel BUG at fs/ext2/inode.c:637! [93.796904] invalid opcode: 0000 [#1] PREEMPT SMP PTI [93.798659] CPU: 0 PID: 1192 Comm: truncate Not tainted 6.3.0-rc2-xfstests-00056-g131086faa369 #139 [93.806459] RIP: 0010:ext2_get_blocks.constprop.0+0x524/0x610 <...> [93.835298] Call Trace: [93.836253] <TASK> [93.837103] ? lock_acquire+0xf8/0x110 [93.838479] ? d_lookup+0x69/0xd0 [93.839779] ext2_iomap_begin+0xa7/0x1c0 [93.841154] iomap_iter+0xc7/0x150 [93.842425] dax_zero_range+0x6e/0xa0 [93.843813] ext2_setsize+0x176/0x1b0 [93.845164] ext2_setattr+0x151/0x200 [93.846467] notify_change+0x341/0x4e0 [93.847805] ? lock_acquire+0xf8/0x110 [93.849143] ? do_truncate+0x74/0xe0 [93.850452] ? do_truncate+0x84/0xe0 [93.851739] do_truncate+0x84/0xe0 [93.852974] do_sys_ftruncate+0x2b4/0x2f0 [93.854404] do_syscall_64+0x3f/0x90 [93.855789] entry_SYSCALL_64_after_hwframe+0x72/0xdc CVE-2023-53323 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53323.html CVE-2023-53323 https://bugzilla.suse.com/1250069 SUSE Bug 1250069 In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Don't leak some plane state Apparently no one noticed that mdp5 plane states leak like a sieve ever since we introduced plane_state->commit refcount a few years ago in 21a01abbe32a ("drm/atomic: Fix freeing connector/plane state too early by tracking commits, v3.") Fix it by using the right helpers. Patchwork: https://patchwork.freedesktop.org/patch/551236/ CVE-2023-53324 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53324.html CVE-2023-53324 https://bugzilla.suse.com/1250070 SUSE Bug 1250070 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: dp: Change logging to dev for mtk_dp_aux_transfer() Change logging from drm_{err,info}() to dev_{err,info}() in functions mtk_dp_aux_transfer() and mtk_dp_aux_do_transfer(): this will be essential to avoid getting NULL pointer kernel panics if any kind of error happens during AUX transfers happening before the bridge is attached. This may potentially start happening in a later commit implementing aux-bus support, as AUX transfers will be triggered from the panel driver (for EDID) before the mtk-dp bridge gets attached, and it's done in preparation for the same. CVE-2023-53325 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53325.html CVE-2023-53325 https://bugzilla.suse.com/1250035 SUSE Bug 1250035 In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Enhance sanity check while generating attr_list ni_create_attr_list uses WARN_ON to catch error cases while generating attribute list, which only prints out stack trace and may not be enough. This repalces them with more proper error handling flow. [ 59.666332] BUG: kernel NULL pointer dereference, address: 000000000000000e [ 59.673268] #PF: supervisor read access in kernel mode [ 59.678354] #PF: error_code(0x0000) - not-present page [ 59.682831] PGD 8000000005ff1067 P4D 8000000005ff1067 PUD 7dee067 PMD 0 [ 59.688556] Oops: 0000 [#1] PREEMPT SMP KASAN PTI [ 59.692642] CPU: 0 PID: 198 Comm: poc Tainted: G B W 6.2.0-rc1+ #4 [ 59.698868] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 [ 59.708795] RIP: 0010:ni_create_attr_list+0x505/0x860 [ 59.713657] Code: 7e 10 e8 5e d0 d0 ff 45 0f b7 76 10 48 8d 7b 16 e8 00 d1 d0 ff 66 44 89 73 16 4d 8d 75 0e 4c 89 f7 e8 3f d0 d0 ff 4c 8d8 [ 59.731559] RSP: 0018:ffff88800a56f1e0 EFLAGS: 00010282 [ 59.735691] RAX: 0000000000000001 RBX: ffff88800b7b5088 RCX: ffffffffb83079fe [ 59.741792] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffffbb7f9fc0 [ 59.748423] RBP: ffff88800a56f3a8 R08: ffff88800b7b50a0 R09: fffffbfff76ff3f9 [ 59.754654] R10: ffffffffbb7f9fc7 R11: fffffbfff76ff3f8 R12: ffff88800b756180 [ 59.761552] R13: 0000000000000000 R14: 000000000000000e R15: 0000000000000050 [ 59.768323] FS: 00007feaa8c96440(0000) GS:ffff88806d400000(0000) knlGS:0000000000000000 [ 59.776027] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 59.781395] CR2: 00007f3a2e0b1000 CR3: 000000000a5bc000 CR4: 00000000000006f0 [ 59.787607] Call Trace: [ 59.790271] <TASK> [ 59.792488] ? __pfx_ni_create_attr_list+0x10/0x10 [ 59.797235] ? kernel_text_address+0xd3/0xe0 [ 59.800856] ? unwind_get_return_address+0x3e/0x60 [ 59.805101] ? __kasan_check_write+0x18/0x20 [ 59.809296] ? preempt_count_sub+0x1c/0xd0 [ 59.813421] ni_ins_attr_ext+0x52c/0x5c0 [ 59.817034] ? __pfx_ni_ins_attr_ext+0x10/0x10 [ 59.821926] ? __vfs_setxattr+0x121/0x170 [ 59.825718] ? __vfs_setxattr_noperm+0x97/0x300 [ 59.829562] ? __vfs_setxattr_locked+0x145/0x170 [ 59.833987] ? vfs_setxattr+0x137/0x2a0 [ 59.836732] ? do_setxattr+0xce/0x150 [ 59.839807] ? setxattr+0x126/0x140 [ 59.842353] ? path_setxattr+0x164/0x180 [ 59.845275] ? __x64_sys_setxattr+0x71/0x90 [ 59.848838] ? do_syscall_64+0x3f/0x90 [ 59.851898] ? entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 59.857046] ? stack_depot_save+0x17/0x20 [ 59.860299] ni_insert_attr+0x1ba/0x420 [ 59.863104] ? __pfx_ni_insert_attr+0x10/0x10 [ 59.867069] ? preempt_count_sub+0x1c/0xd0 [ 59.869897] ? _raw_spin_unlock_irqrestore+0x2b/0x50 [ 59.874088] ? __create_object+0x3ae/0x5d0 [ 59.877865] ni_insert_resident+0xc4/0x1c0 [ 59.881430] ? __pfx_ni_insert_resident+0x10/0x10 [ 59.886355] ? kasan_save_alloc_info+0x1f/0x30 [ 59.891117] ? __kasan_kmalloc+0x8b/0xa0 [ 59.894383] ntfs_set_ea+0x90d/0xbf0 [ 59.897703] ? __pfx_ntfs_set_ea+0x10/0x10 [ 59.901011] ? kernel_text_address+0xd3/0xe0 [ 59.905308] ? __kernel_text_address+0x16/0x50 [ 59.909811] ? unwind_get_return_address+0x3e/0x60 [ 59.914898] ? __pfx_stack_trace_consume_entry+0x10/0x10 [ 59.920250] ? arch_stack_walk+0xa2/0x100 [ 59.924560] ? filter_irq_stacks+0x27/0x80 [ 59.928722] ntfs_setxattr+0x405/0x440 [ 59.932512] ? __pfx_ntfs_setxattr+0x10/0x10 [ 59.936634] ? kvmalloc_node+0x2d/0x120 [ 59.940378] ? kasan_save_stack+0x41/0x60 [ 59.943870] ? kasan_save_stack+0x2a/0x60 [ 59.947719] ? kasan_set_track+0x29/0x40 [ 59.951417] ? kasan_save_alloc_info+0x1f/0x30 [ 59.955733] ? __kasan_kmalloc+0x8b/0xa0 [ 59.959598] ? __kmalloc_node+0x68/0x150 [ 59.963163] ? kvmalloc_node+0x2d/0x120 [ 59.966490] ? vmemdup_user+0x2b/0xa0 ---truncated--- CVE-2023-53328 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53328.html CVE-2023-53328 https://bugzilla.suse.com/1249952 SUSE Bug 1249952 In the Linux kernel, the following vulnerability has been resolved: pstore/ram: Check start of empty przs during init After commit 30696378f68a ("pstore/ram: Do not treat empty buffers as valid"), initialization would assume a prz was valid after seeing that the buffer_size is zero (regardless of the buffer start position). This unchecked start value means it could be outside the bounds of the buffer, leading to future access panics when written to: sysdump_panic_event+0x3b4/0x5b8 atomic_notifier_call_chain+0x54/0x90 panic+0x1c8/0x42c die+0x29c/0x2a8 die_kernel_fault+0x68/0x78 __do_kernel_fault+0x1c4/0x1e0 do_bad_area+0x40/0x100 do_translation_fault+0x68/0x80 do_mem_abort+0x68/0xf8 el1_da+0x1c/0xc0 __raw_writeb+0x38/0x174 __memcpy_toio+0x40/0xac persistent_ram_update+0x44/0x12c persistent_ram_write+0x1a8/0x1b8 ramoops_pstore_write+0x198/0x1e8 pstore_console_write+0x94/0xe0 ... To avoid this, also check if the prz start is 0 during the initialization phase. If not, the next prz sanity check case will discover it (start > size) and zap the buffer back to a sane state. [kees: update commit log with backtrace and clarifications] CVE-2023-53331 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53331.html CVE-2023-53331 https://bugzilla.suse.com/1249950 SUSE Bug 1249950 In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: dccp: copy entire header to stack buffer, not just basic one Eric Dumazet says: nf_conntrack_dccp_packet() has an unique: dh = skb_header_pointer(skb, dataoff, sizeof(_dh), &_dh); And nothing more is 'pulled' from the packet, depending on the content. dh->dccph_doff, and/or dh->dccph_x ...) So dccp_ack_seq() is happily reading stuff past the _dh buffer. BUG: KASAN: stack-out-of-bounds in nf_conntrack_dccp_packet+0x1134/0x11c0 Read of size 4 at addr ffff000128f66e0c by task syz-executor.2/29371 [..] Fix this by increasing the stack buffer to also include room for the extra sequence numbers and all the known dccp packet type headers, then pull again after the initial validation of the basic header. While at it, mark packets invalid that lack 48bit sequence bit but where RFC says the type MUST use them. Compile tested only. v2: first skb_header_pointer() now needs to adjust the size to only pull the generic header. (Eric) Heads-up: I intend to remove dccp conntrack support later this year. CVE-2023-53333 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53333.html CVE-2023-53333 https://bugzilla.suse.com/1249949 SUSE Bug 1249949 In the Linux kernel, the following vulnerability has been resolved: media: ipu-bridge: Fix null pointer deref on SSDB/PLD parsing warnings When ipu_bridge_parse_rotation() and ipu_bridge_parse_orientation() run sensor->adev is not set yet. So if either of the dev_warn() calls about unknown values are hit this will lead to a NULL pointer deref. Set sensor->adev earlier, with a borrowed ref to avoid making unrolling on errors harder, to fix this. CVE-2023-53336 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53336.html CVE-2023-53336 https://bugzilla.suse.com/1250073 SUSE Bug 1250073 In the Linux kernel, the following vulnerability has been resolved: lwt: Fix return values of BPF xmit ops BPF encap ops can return different types of positive values, such like NET_RX_DROP, NET_XMIT_CN, NETDEV_TX_BUSY, and so on, from function skb_do_redirect and bpf_lwt_xmit_reroute. At the xmit hook, such return values would be treated implicitly as LWTUNNEL_XMIT_CONTINUE in ip(6)_finish_output2. When this happens, skbs that have been freed would continue to the neighbor subsystem, causing use-after-free bug and kernel crashes. To fix the incorrect behavior, skb_do_redirect return values can be simply discarded, the same as tc-egress behavior. On the other hand, bpf_lwt_xmit_reroute returns useful errors to local senders, e.g. PMTU information. Thus convert its return values to avoid the conflict with LWTUNNEL_XMIT_CONTINUE. CVE-2023-53338 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53338.html CVE-2023-53338 https://bugzilla.suse.com/1250074 SUSE Bug 1250074 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix BUG_ON condition in btrfs_cancel_balance Pausing and canceling balance can race to interrupt balance lead to BUG_ON panic in btrfs_cancel_balance. The BUG_ON condition in btrfs_cancel_balance does not take this race scenario into account. However, the race condition has no other side effects. We can fix that. Reproducing it with panic trace like this: kernel BUG at fs/btrfs/volumes.c:4618! RIP: 0010:btrfs_cancel_balance+0x5cf/0x6a0 Call Trace: <TASK> ? do_nanosleep+0x60/0x120 ? hrtimer_nanosleep+0xb7/0x1a0 ? sched_core_clone_cookie+0x70/0x70 btrfs_ioctl_balance_ctl+0x55/0x70 btrfs_ioctl+0xa46/0xd20 __x64_sys_ioctl+0x7d/0xa0 do_syscall_64+0x38/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd Race scenario as follows: > mutex_unlock(&fs_info->balance_mutex); > -------------------- > .......issue pause and cancel req in another thread > -------------------- > ret = __btrfs_balance(fs_info); > > mutex_lock(&fs_info->balance_mutex); > if (ret == -ECANCELED && atomic_read(&fs_info->balance_pause_req)) { > btrfs_info(fs_info, "balance: paused"); > btrfs_exclop_balance(fs_info, BTRFS_EXCLOP_BALANCE_PAUSED); > } CVE-2023-53339 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53339.html CVE-2023-53339 https://bugzilla.suse.com/1250329 SUSE Bug 1250329 In the Linux kernel, the following vulnerability has been resolved: net: marvell: prestera: fix handling IPv4 routes with nhid Fix handling IPv4 routes referencing a nexthop via its id by replacing calls to fib_info_nh() with fib_info_nhc(). Trying to add an IPv4 route referencing a nextop via nhid: $ ip link set up swp5 $ ip a a 10.0.0.1/24 dev swp5 $ ip nexthop add dev swp5 id 20 via 10.0.0.2 $ ip route add 10.0.1.0/24 nhid 20 triggers warnings when trying to handle the route: [ 528.805763] ------------[ cut here ]------------ [ 528.810437] WARNING: CPU: 3 PID: 53 at include/net/nexthop.h:468 __prestera_fi_is_direct+0x2c/0x68 [prestera] [ 528.820434] Modules linked in: prestera_pci act_gact act_police sch_ingress cls_u32 cls_flower prestera arm64_delta_tn48m_dn_led(O) arm64_delta_tn48m_dn_cpld(O) [last unloaded: prestera_pci] [ 528.837485] CPU: 3 PID: 53 Comm: kworker/u8:3 Tainted: G O 6.4.5 #1 [ 528.845178] Hardware name: delta,tn48m-dn (DT) [ 528.849641] Workqueue: prestera_ordered __prestera_router_fib_event_work [prestera] [ 528.857352] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 528.864347] pc : __prestera_fi_is_direct+0x2c/0x68 [prestera] [ 528.870135] lr : prestera_k_arb_fib_evt+0xb20/0xd50 [prestera] [ 528.876007] sp : ffff80000b20bc90 [ 528.879336] x29: ffff80000b20bc90 x28: 0000000000000000 x27: ffff0001374d3a48 [ 528.886510] x26: ffff000105604000 x25: ffff000134af8a28 x24: ffff0001374d3800 [ 528.893683] x23: ffff000101c89148 x22: ffff000101c89000 x21: ffff000101c89200 [ 528.900855] x20: ffff00013641fda0 x19: ffff800009d01088 x18: 0000000000000059 [ 528.908027] x17: 0000000000000277 x16: 0000000000000000 x15: 0000000000000000 [ 528.915198] x14: 0000000000000003 x13: 00000000000fe400 x12: 0000000000000000 [ 528.922371] x11: 0000000000000002 x10: 0000000000000aa0 x9 : ffff8000013d2020 [ 528.929543] x8 : 0000000000000018 x7 : 000000007b1703f8 x6 : 000000001ca72f86 [ 528.936715] x5 : 0000000033399ea7 x4 : 0000000000000000 x3 : ffff0001374d3acc [ 528.943886] x2 : 0000000000000000 x1 : ffff00010200de00 x0 : ffff000134ae3f80 [ 528.951058] Call trace: [ 528.953516] __prestera_fi_is_direct+0x2c/0x68 [prestera] [ 528.958952] __prestera_router_fib_event_work+0x100/0x158 [prestera] [ 528.965348] process_one_work+0x208/0x488 [ 528.969387] worker_thread+0x4c/0x430 [ 528.973068] kthread+0x120/0x138 [ 528.976313] ret_from_fork+0x10/0x20 [ 528.979909] ---[ end trace 0000000000000000 ]--- [ 528.984998] ------------[ cut here ]------------ [ 528.989645] WARNING: CPU: 3 PID: 53 at include/net/nexthop.h:468 __prestera_fi_is_direct+0x2c/0x68 [prestera] [ 528.999628] Modules linked in: prestera_pci act_gact act_police sch_ingress cls_u32 cls_flower prestera arm64_delta_tn48m_dn_led(O) arm64_delta_tn48m_dn_cpld(O) [last unloaded: prestera_pci] [ 529.016676] CPU: 3 PID: 53 Comm: kworker/u8:3 Tainted: G W O 6.4.5 #1 [ 529.024368] Hardware name: delta,tn48m-dn (DT) [ 529.028830] Workqueue: prestera_ordered __prestera_router_fib_event_work [prestera] [ 529.036539] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 529.043533] pc : __prestera_fi_is_direct+0x2c/0x68 [prestera] [ 529.049318] lr : __prestera_k_arb_fc_apply+0x280/0x2f8 [prestera] [ 529.055452] sp : ffff80000b20bc60 [ 529.058781] x29: ffff80000b20bc60 x28: 0000000000000000 x27: ffff0001374d3a48 [ 529.065953] x26: ffff000105604000 x25: ffff000134af8a28 x24: ffff0001374d3800 [ 529.073126] x23: ffff000101c89148 x22: ffff000101c89148 x21: ffff00013641fda0 [ 529.080299] x20: ffff000101c89000 x19: ffff000101c89020 x18: 0000000000000059 [ 529.087471] x17: 0000000000000277 x16: 0000000000000000 x15: 0000000000000000 [ 529.094642] x14: 0000000000000003 x13: 00000000000fe400 x12: 0000000000000000 [ 529.101814] x11: 0000000000000002 x10: 0000000000000aa0 x9 : ffff8000013cee80 [ 529.108985] x8 : 0000000000000018 x7 : 000000007b1703f8 x6 ---truncated--- CVE-2023-53342 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53342.html CVE-2023-53342 https://bugzilla.suse.com/1250029 SUSE Bug 1250029 In the Linux kernel, the following vulnerability has been resolved: icmp6: Fix null-ptr-deref of ip6_null_entry->rt6i_idev in icmp6_dev(). With some IPv6 Ext Hdr (RPL, SRv6, etc.), we can send a packet that has the link-local address as src and dst IP and will be forwarded to an external IP in the IPv6 Ext Hdr. For example, the script below generates a packet whose src IP is the link-local address and dst is updated to 11::. # for f in $(find /proc/sys/net/ -name *seg6_enabled*); do echo 1 > $f; done # python3 >>> from socket import * >>> from scapy.all import * >>> >>> SRC_ADDR = DST_ADDR = "fe80::5054:ff:fe12:3456" >>> >>> pkt = IPv6(src=SRC_ADDR, dst=DST_ADDR) >>> pkt /= IPv6ExtHdrSegmentRouting(type=4, addresses=["11::", "22::"], segleft=1) >>> >>> sk = socket(AF_INET6, SOCK_RAW, IPPROTO_RAW) >>> sk.sendto(bytes(pkt), (DST_ADDR, 0)) For such a packet, we call ip6_route_input() to look up a route for the next destination in these three functions depending on the header type. * ipv6_rthdr_rcv() * ipv6_rpl_srh_rcv() * ipv6_srh_rcv() If no route is found, ip6_null_entry is set to skb, and the following dst_input(skb) calls ip6_pkt_drop(). Finally, in icmp6_dev(), we dereference skb_rt6_info(skb)->rt6i_idev->dev as the input device is the loopback interface. Then, we have to check if skb_rt6_info(skb)->rt6i_idev is NULL or not to avoid NULL pointer deref for ip6_null_entry. BUG: kernel NULL pointer dereference, address: 0000000000000000 PF: supervisor read access in kernel mode PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 0 PID: 157 Comm: python3 Not tainted 6.4.0-11996-gb121d614371c #35 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:icmp6_send (net/ipv6/icmp.c:436 net/ipv6/icmp.c:503) Code: fe ff ff 48 c7 40 30 c0 86 5d 83 e8 c6 44 1c 00 e9 c8 fc ff ff 49 8b 46 58 48 83 e0 fe 0f 84 4a fb ff ff 48 8b 80 d0 00 00 00 <48> 8b 00 44 8b 88 e0 00 00 00 e9 34 fb ff ff 4d 85 ed 0f 85 69 01 RSP: 0018:ffffc90000003c70 EFLAGS: 00000286 RAX: 0000000000000000 RBX: 0000000000000001 RCX: 00000000000000e0 RDX: 0000000000000021 RSI: 0000000000000000 RDI: ffff888006d72a18 RBP: ffffc90000003d80 R08: 0000000000000000 R09: 0000000000000001 R10: ffffc90000003d98 R11: 0000000000000040 R12: ffff888006d72a10 R13: 0000000000000000 R14: ffff8880057fb800 R15: ffffffff835d86c0 FS: 00007f9dc72ee740(0000) GS:ffff88807dc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000057b2000 CR4: 00000000007506f0 PKRU: 55555554 Call Trace: <IRQ> ip6_pkt_drop (net/ipv6/route.c:4513) ipv6_rthdr_rcv (net/ipv6/exthdrs.c:640 net/ipv6/exthdrs.c:686) ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:437 (discriminator 5)) ip6_input_finish (./include/linux/rcupdate.h:781 net/ipv6/ip6_input.c:483) __netif_receive_skb_one_core (net/core/dev.c:5455) process_backlog (./include/linux/rcupdate.h:781 net/core/dev.c:5895) __napi_poll (net/core/dev.c:6460) net_rx_action (net/core/dev.c:6529 net/core/dev.c:6660) __do_softirq (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/irq.h:142 kernel/softirq.c:554) do_softirq (kernel/softirq.c:454 kernel/softirq.c:441) </IRQ> <TASK> __local_bh_enable_ip (kernel/softirq.c:381) __dev_queue_xmit (net/core/dev.c:4231) ip6_finish_output2 (./include/net/neighbour.h:544 net/ipv6/ip6_output.c:135) rawv6_sendmsg (./include/net/dst.h:458 ./include/linux/netfilter.h:303 net/ipv6/raw.c:656 net/ipv6/raw.c:914) sock_sendmsg (net/socket.c:725 net/socket.c:748) __sys_sendto (net/socket.c:2134) __x64_sys_sendto (net/socket.c:2146 net/socket.c:2142 net/socket.c:2142) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) RIP: 0033:0x7f9dc751baea Code: d8 64 89 02 48 c7 c0 ff f ---truncated--- CVE-2023-53343 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53343.html CVE-2023-53343 https://bugzilla.suse.com/1250022 SUSE Bug 1250022 In the Linux kernel, the following vulnerability has been resolved: accel/qaic: Fix slicing memory leak The temporary buffer storing slicing configuration data from user is only freed on error. This is a memory leak. Free the buffer unconditionally. CVE-2023-53350 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53350.html CVE-2023-53350 https://bugzilla.suse.com/1250012 SUSE Bug 1250012 In the Linux kernel, the following vulnerability has been resolved: drm/ttm: check null pointer before accessing when swapping Add a check to avoid null pointer dereference as below: [ 90.002283] general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI [ 90.002292] KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] [ 90.002346] ? exc_general_protection+0x159/0x240 [ 90.002352] ? asm_exc_general_protection+0x26/0x30 [ 90.002357] ? ttm_bo_evict_swapout_allowable+0x322/0x5e0 [ttm] [ 90.002365] ? ttm_bo_evict_swapout_allowable+0x42e/0x5e0 [ttm] [ 90.002373] ttm_bo_swapout+0x134/0x7f0 [ttm] [ 90.002383] ? __pfx_ttm_bo_swapout+0x10/0x10 [ttm] [ 90.002391] ? lock_acquire+0x44d/0x4f0 [ 90.002398] ? ttm_device_swapout+0xa5/0x260 [ttm] [ 90.002412] ? lock_acquired+0x355/0xa00 [ 90.002416] ? do_raw_spin_trylock+0xb6/0x190 [ 90.002421] ? __pfx_lock_acquired+0x10/0x10 [ 90.002426] ? ttm_global_swapout+0x25/0x210 [ttm] [ 90.002442] ttm_device_swapout+0x198/0x260 [ttm] [ 90.002456] ? __pfx_ttm_device_swapout+0x10/0x10 [ttm] [ 90.002472] ttm_global_swapout+0x75/0x210 [ttm] [ 90.002486] ttm_tt_populate+0x187/0x3f0 [ttm] [ 90.002501] ttm_bo_handle_move_mem+0x437/0x590 [ttm] [ 90.002517] ttm_bo_validate+0x275/0x430 [ttm] [ 90.002530] ? __pfx_ttm_bo_validate+0x10/0x10 [ttm] [ 90.002544] ? kasan_save_stack+0x33/0x60 [ 90.002550] ? kasan_set_track+0x25/0x30 [ 90.002554] ? __kasan_kmalloc+0x8f/0xa0 [ 90.002558] ? amdgpu_gtt_mgr_new+0x81/0x420 [amdgpu] [ 90.003023] ? ttm_resource_alloc+0xf6/0x220 [ttm] [ 90.003038] amdgpu_bo_pin_restricted+0x2dd/0x8b0 [amdgpu] [ 90.003210] ? __x64_sys_ioctl+0x131/0x1a0 [ 90.003210] ? do_syscall_64+0x60/0x90 CVE-2023-53352 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53352.html CVE-2023-53352 https://bugzilla.suse.com/1250006 SUSE Bug 1250006 In the Linux kernel, the following vulnerability has been resolved: skbuff: skb_segment, Call zero copy functions before using skbuff frags Commit bf5c25d60861 ("skbuff: in skb_segment, call zerocopy functions once per nskb") added the call to zero copy functions in skb_segment(). The change introduced a bug in skb_segment() because skb_orphan_frags() may possibly change the number of fragments or allocate new fragments altogether leaving nrfrags and frag to point to the old values. This can cause a panic with stacktrace like the one below. [ 193.894380] BUG: kernel NULL pointer dereference, address: 00000000000000bc [ 193.895273] CPU: 13 PID: 18164 Comm: vh-net-17428 Kdump: loaded Tainted: G O 5.15.123+ #26 [ 193.903919] RIP: 0010:skb_segment+0xb0e/0x12f0 [ 194.021892] Call Trace: [ 194.027422] <TASK> [ 194.072861] tcp_gso_segment+0x107/0x540 [ 194.082031] inet_gso_segment+0x15c/0x3d0 [ 194.090783] skb_mac_gso_segment+0x9f/0x110 [ 194.095016] __skb_gso_segment+0xc1/0x190 [ 194.103131] netem_enqueue+0x290/0xb10 [sch_netem] [ 194.107071] dev_qdisc_enqueue+0x16/0x70 [ 194.110884] __dev_queue_xmit+0x63b/0xb30 [ 194.121670] bond_start_xmit+0x159/0x380 [bonding] [ 194.128506] dev_hard_start_xmit+0xc3/0x1e0 [ 194.131787] __dev_queue_xmit+0x8a0/0xb30 [ 194.138225] macvlan_start_xmit+0x4f/0x100 [macvlan] [ 194.141477] dev_hard_start_xmit+0xc3/0x1e0 [ 194.144622] sch_direct_xmit+0xe3/0x280 [ 194.147748] __dev_queue_xmit+0x54a/0xb30 [ 194.154131] tap_get_user+0x2a8/0x9c0 [tap] [ 194.157358] tap_sendmsg+0x52/0x8e0 [tap] [ 194.167049] handle_tx_zerocopy+0x14e/0x4c0 [vhost_net] [ 194.173631] handle_tx+0xcd/0xe0 [vhost_net] [ 194.176959] vhost_worker+0x76/0xb0 [vhost] [ 194.183667] kthread+0x118/0x140 [ 194.190358] ret_from_fork+0x1f/0x30 [ 194.193670] </TASK> In this case calling skb_orphan_frags() updated nr_frags leaving nrfrags local variable in skb_segment() stale. This resulted in the code hitting i >= nrfrags prematurely and trying to move to next frag_skb using list_skb pointer, which was NULL, and caused kernel panic. Move the call to zero copy functions before using frags and nr_frags. CVE-2023-53354 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53354.html CVE-2023-53354 https://bugzilla.suse.com/1250004 SUSE Bug 1250004 In the Linux kernel, the following vulnerability has been resolved: usb: gadget: u_serial: Add null pointer check in gserial_suspend Consider a case where gserial_disconnect has already cleared gser->ioport. And if gserial_suspend gets called afterwards, it will lead to accessing of gser->ioport and thus causing null pointer dereference. Avoid this by adding a null pointer check. Added a static spinlock to prevent gser->ioport from becoming null after the newly added null pointer check. CVE-2023-53356 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53356.html CVE-2023-53356 https://bugzilla.suse.com/1249997 SUSE Bug 1249997 In the Linux kernel, the following vulnerability has been resolved: md/raid10: check slab-out-of-bounds in md_bitmap_get_counter If we write a large number to md/bitmap_set_bits, md_bitmap_checkpage() will return -EINVAL because 'page >= bitmap->pages', but the return value was not checked immediately in md_bitmap_get_counter() in order to set *blocks value and slab-out-of-bounds occurs. Move check of 'page >= bitmap->pages' to md_bitmap_get_counter() and return directly if true. CVE-2023-53357 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53357.html CVE-2023-53357 https://bugzilla.suse.com/1249994 SUSE Bug 1249994 In the Linux kernel, the following vulnerability has been resolved: NFSv4.2: Rework scratch handling for READ_PLUS (again) I found that the read code might send multiple requests using the same nfs_pgio_header, but nfs4_proc_read_setup() is only called once. This is how we ended up occasionally double-freeing the scratch buffer, but also means we set a NULL pointer but non-zero length to the xdr scratch buffer. This results in an oops the first time decoding needs to copy something to scratch, which frequently happens when decoding READ_PLUS hole segments. I fix this by moving scratch handling into the pageio read code. I provide a function to allocate scratch space for decoding read replies, and free the scratch buffer when the nfs_pgio_header is freed. CVE-2023-53360 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53360.html CVE-2023-53360 https://bugzilla.suse.com/1249990 SUSE Bug 1249990 In the Linux kernel, the following vulnerability has been resolved: bus: fsl-mc: don't assume child devices are all fsl-mc devices Changes in VFIO caused a pseudo-device to be created as child of fsl-mc devices causing a crash [1] when trying to bind a fsl-mc device to VFIO. Fix this by checking the device type when enumerating fsl-mc child devices. [1] Modules linked in: Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP CPU: 6 PID: 1289 Comm: sh Not tainted 6.2.0-rc5-00047-g7c46948a6e9c #2 Hardware name: NXP Layerscape LX2160ARDB (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : mc_send_command+0x24/0x1f0 lr : dprc_get_obj_region+0xfc/0x1c0 sp : ffff80000a88b900 x29: ffff80000a88b900 x28: ffff48a9429e1400 x27: 00000000000002b2 x26: ffff48a9429e1718 x25: 0000000000000000 x24: 0000000000000000 x23: ffffd59331ba3918 x22: ffffd59331ba3000 x21: 0000000000000000 x20: ffff80000a88b9b8 x19: 0000000000000000 x18: 0000000000000001 x17: 7270642f636d2d6c x16: 73662e3030303030 x15: ffffffffffffffff x14: ffffd59330f1d668 x13: ffff48a8727dc389 x12: ffff48a8727dc386 x11: 0000000000000002 x10: 00008ceaf02f35d4 x9 : 0000000000000012 x8 : 0000000000000000 x7 : 0000000000000006 x6 : ffff80000a88bab0 x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff80000a88b9e8 x2 : ffff80000a88b9e8 x1 : 0000000000000000 x0 : ffff48a945142b80 Call trace: mc_send_command+0x24/0x1f0 dprc_get_obj_region+0xfc/0x1c0 fsl_mc_device_add+0x340/0x590 fsl_mc_obj_device_add+0xd0/0xf8 dprc_scan_objects+0x1c4/0x340 dprc_scan_container+0x38/0x60 vfio_fsl_mc_probe+0x9c/0xf8 fsl_mc_driver_probe+0x24/0x70 really_probe+0xbc/0x2a8 __driver_probe_device+0x78/0xe0 device_driver_attach+0x30/0x68 bind_store+0xa8/0x130 drv_attr_store+0x24/0x38 sysfs_kf_write+0x44/0x60 kernfs_fop_write_iter+0x128/0x1b8 vfs_write+0x334/0x448 ksys_write+0x68/0xf0 __arm64_sys_write+0x1c/0x28 invoke_syscall+0x44/0x108 el0_svc_common.constprop.1+0x94/0xf8 do_el0_svc+0x38/0xb0 el0_svc+0x20/0x50 el0t_64_sync_handler+0x98/0xc0 el0t_64_sync+0x174/0x178 Code: aa0103f4 a9025bf5 d5384100 b9400801 (79401260) ---[ end trace 0000000000000000 ]--- CVE-2023-53362 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53362.html CVE-2023-53362 https://bugzilla.suse.com/1249993 SUSE Bug 1249993 In the Linux kernel, the following vulnerability has been resolved: regulator: da9063: better fix null deref with partial DT Two versions of the original patch were sent but V1 was merged instead of V2 due to a mistake. So update to V2. The advantage of V2 is that it completely avoids dereferencing the pointer, even just to take the address, which may fix problems with some compilers. Both versions work on my gcc 9.4 but use the safer one. CVE-2023-53364 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53364.html CVE-2023-53364 https://bugzilla.suse.com/1249984 SUSE Bug 1249984 In the Linux kernel, the following vulnerability has been resolved: ip6mr: Fix skb_under_panic in ip6mr_cache_report() skbuff: skb_under_panic: text:ffffffff88771f69 len:56 put:-4 head:ffff88805f86a800 data:ffff887f5f86a850 tail:0x88 end:0x2c0 dev:pim6reg ------------[ cut here ]------------ kernel BUG at net/core/skbuff.c:192! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 2 PID: 22968 Comm: kworker/2:11 Not tainted 6.5.0-rc3-00044-g0a8db05b571a #236 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: ipv6_addrconf addrconf_dad_work RIP: 0010:skb_panic+0x152/0x1d0 Call Trace: <TASK> skb_push+0xc4/0xe0 ip6mr_cache_report+0xd69/0x19b0 reg_vif_xmit+0x406/0x690 dev_hard_start_xmit+0x17e/0x6e0 __dev_queue_xmit+0x2d6a/0x3d20 vlan_dev_hard_start_xmit+0x3ab/0x5c0 dev_hard_start_xmit+0x17e/0x6e0 __dev_queue_xmit+0x2d6a/0x3d20 neigh_connected_output+0x3ed/0x570 ip6_finish_output2+0x5b5/0x1950 ip6_finish_output+0x693/0x11c0 ip6_output+0x24b/0x880 NF_HOOK.constprop.0+0xfd/0x530 ndisc_send_skb+0x9db/0x1400 ndisc_send_rs+0x12a/0x6c0 addrconf_dad_completed+0x3c9/0xea0 addrconf_dad_work+0x849/0x1420 process_one_work+0xa22/0x16e0 worker_thread+0x679/0x10c0 ret_from_fork+0x28/0x60 ret_from_fork_asm+0x11/0x20 When setup a vlan device on dev pim6reg, DAD ns packet may sent on reg_vif_xmit(). reg_vif_xmit() ip6mr_cache_report() skb_push(skb, -skb_network_offset(pkt));//skb_network_offset(pkt) is 4 And skb_push declared as: void *skb_push(struct sk_buff *skb, unsigned int len); skb->data -= len; //0xffff88805f86a84c - 0xfffffffc = 0xffff887f5f86a850 skb->data is set to 0xffff887f5f86a850, which is invalid mem addr, lead to skb_push() fails. CVE-2023-53365 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53365.html CVE-2023-53365 https://bugzilla.suse.com/1249988 SUSE Bug 1249988 In the Linux kernel, the following vulnerability has been resolved: accel/habanalabs: fix mem leak in capture user mappings This commit fixes a memory leak caused when clearing the user_mappings info when a new context is opened immediately after user_mapping is captured and a hard reset is performed. CVE-2023-53367 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53367.html CVE-2023-53367 https://bugzilla.suse.com/1250243 SUSE Bug 1250243 In the Linux kernel, the following vulnerability has been resolved: tracing: Fix race issue between cpu buffer write and swap Warning happened in rb_end_commit() at code: if (RB_WARN_ON(cpu_buffer, !local_read(&cpu_buffer->committing))) WARNING: CPU: 0 PID: 139 at kernel/trace/ring_buffer.c:3142 rb_commit+0x402/0x4a0 Call Trace: ring_buffer_unlock_commit+0x42/0x250 trace_buffer_unlock_commit_regs+0x3b/0x250 trace_event_buffer_commit+0xe5/0x440 trace_event_buffer_reserve+0x11c/0x150 trace_event_raw_event_sched_switch+0x23c/0x2c0 __traceiter_sched_switch+0x59/0x80 __schedule+0x72b/0x1580 schedule+0x92/0x120 worker_thread+0xa0/0x6f0 It is because the race between writing event into cpu buffer and swapping cpu buffer through file per_cpu/cpu0/snapshot: Write on CPU 0 Swap buffer by per_cpu/cpu0/snapshot on CPU 1 -------- -------- tracing_snapshot_write() [...] ring_buffer_lock_reserve() cpu_buffer = buffer->buffers[cpu]; // 1. Suppose find 'cpu_buffer_a'; [...] rb_reserve_next_event() [...] ring_buffer_swap_cpu() if (local_read(&cpu_buffer_a->committing)) goto out_dec; if (local_read(&cpu_buffer_b->committing)) goto out_dec; buffer_a->buffers[cpu] = cpu_buffer_b; buffer_b->buffers[cpu] = cpu_buffer_a; // 2. cpu_buffer has swapped here. rb_start_commit(cpu_buffer); if (unlikely(READ_ONCE(cpu_buffer->buffer) != buffer)) { // 3. This check passed due to 'cpu_buffer->buffer' [...] // has not changed here. return NULL; } cpu_buffer_b->buffer = buffer_a; cpu_buffer_a->buffer = buffer_b; [...] // 4. Reserve event from 'cpu_buffer_a'. ring_buffer_unlock_commit() [...] cpu_buffer = buffer->buffers[cpu]; // 5. Now find 'cpu_buffer_b' !!! rb_commit(cpu_buffer) rb_end_commit() // 6. WARN for the wrong 'committing' state !!! Based on above analysis, we can easily reproduce by following testcase: ``` bash #!/bin/bash dmesg -n 7 sysctl -w kernel.panic_on_warn=1 TR=/sys/kernel/tracing echo 7 > ${TR}/buffer_size_kb echo "sched:sched_switch" > ${TR}/set_event while [ true ]; do echo 1 > ${TR}/per_cpu/cpu0/snapshot done & while [ true ]; do echo 1 > ${TR}/per_cpu/cpu0/snapshot done & while [ true ]; do echo 1 > ${TR}/per_cpu/cpu0/snapshot done & ``` To fix it, IIUC, we can use smp_call_function_single() to do the swap on the target cpu where the buffer is located, so that above race would be avoided. CVE-2023-53368 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53368.html CVE-2023-53368 https://bugzilla.suse.com/1249979 SUSE Bug 1249979 In the Linux kernel, the following vulnerability has been resolved: net: dcb: choose correct policy to parse DCB_ATTR_BCN The dcbnl_bcn_setcfg uses erroneous policy to parse tb[DCB_ATTR_BCN], which is introduced in commit 859ee3c43812 ("DCB: Add support for DCB BCN"). Please see the comment in below code static int dcbnl_bcn_setcfg(...) { ... ret = nla_parse_nested_deprecated(..., dcbnl_pfc_up_nest, .. ) // !!! dcbnl_pfc_up_nest for attributes // DCB_PFC_UP_ATTR_0 to DCB_PFC_UP_ATTR_ALL in enum dcbnl_pfc_up_attrs ... for (i = DCB_BCN_ATTR_RP_0; i <= DCB_BCN_ATTR_RP_7; i++) { // !!! DCB_BCN_ATTR_RP_0 to DCB_BCN_ATTR_RP_7 in enum dcbnl_bcn_attrs ... value_byte = nla_get_u8(data[i]); ... } ... for (i = DCB_BCN_ATTR_BCNA_0; i <= DCB_BCN_ATTR_RI; i++) { // !!! DCB_BCN_ATTR_BCNA_0 to DCB_BCN_ATTR_RI in enum dcbnl_bcn_attrs ... value_int = nla_get_u32(data[i]); ... } ... } That is, the nla_parse_nested_deprecated uses dcbnl_pfc_up_nest attributes to parse nlattr defined in dcbnl_pfc_up_attrs. But the following access code fetch each nlattr as dcbnl_bcn_attrs attributes. By looking up the associated nla_policy for dcbnl_bcn_attrs. We can find the beginning part of these two policies are "same". static const struct nla_policy dcbnl_pfc_up_nest[...] = { [DCB_PFC_UP_ATTR_0] = {.type = NLA_U8}, [DCB_PFC_UP_ATTR_1] = {.type = NLA_U8}, [DCB_PFC_UP_ATTR_2] = {.type = NLA_U8}, [DCB_PFC_UP_ATTR_3] = {.type = NLA_U8}, [DCB_PFC_UP_ATTR_4] = {.type = NLA_U8}, [DCB_PFC_UP_ATTR_5] = {.type = NLA_U8}, [DCB_PFC_UP_ATTR_6] = {.type = NLA_U8}, [DCB_PFC_UP_ATTR_7] = {.type = NLA_U8}, [DCB_PFC_UP_ATTR_ALL] = {.type = NLA_FLAG}, }; static const struct nla_policy dcbnl_bcn_nest[...] = { [DCB_BCN_ATTR_RP_0] = {.type = NLA_U8}, [DCB_BCN_ATTR_RP_1] = {.type = NLA_U8}, [DCB_BCN_ATTR_RP_2] = {.type = NLA_U8}, [DCB_BCN_ATTR_RP_3] = {.type = NLA_U8}, [DCB_BCN_ATTR_RP_4] = {.type = NLA_U8}, [DCB_BCN_ATTR_RP_5] = {.type = NLA_U8}, [DCB_BCN_ATTR_RP_6] = {.type = NLA_U8}, [DCB_BCN_ATTR_RP_7] = {.type = NLA_U8}, [DCB_BCN_ATTR_RP_ALL] = {.type = NLA_FLAG}, // from here is somewhat different [DCB_BCN_ATTR_BCNA_0] = {.type = NLA_U32}, ... [DCB_BCN_ATTR_ALL] = {.type = NLA_FLAG}, }; Therefore, the current code is buggy and this nla_parse_nested_deprecated could overflow the dcbnl_pfc_up_nest and use the adjacent nla_policy to parse attributes from DCB_BCN_ATTR_BCNA_0. Hence use the correct policy dcbnl_bcn_nest to parse the nested tb[DCB_ATTR_BCN] TLV. CVE-2023-53369 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53369.html CVE-2023-53369 https://bugzilla.suse.com/1250206 SUSE Bug 1250206 In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix memory leak in mes self test The fences associated with mes queue have to be freed up during amdgpu_ring_fini. CVE-2023-53370 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53370.html CVE-2023-53370 https://bugzilla.suse.com/1250208 SUSE Bug 1250208 In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: fix memory leak in mlx5e_fs_tt_redirect_any_create The memory pointed to by the fs->any pointer is not freed in the error path of mlx5e_fs_tt_redirect_any_create, which can lead to a memory leak. Fix by freeing the memory in the error path, thereby making the error path identical to mlx5e_fs_tt_redirect_any_destroy(). CVE-2023-53371 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53371.html CVE-2023-53371 https://bugzilla.suse.com/1250112 SUSE Bug 1250112 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: fail SCO/ISO via hci_conn_failed if ACL gone early Not calling hci_(dis)connect_cfm before deleting conn referred to by a socket generally results to use-after-free. When cleaning up SCO connections when the parent ACL is deleted too early, use hci_conn_failed to do the connection cleanup properly. We also need to clean up ISO connections in a similar situation when connecting has started but LE Create CIS is not yet sent, so do it too here. CVE-2023-53374 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53374.html CVE-2023-53374 https://bugzilla.suse.com/1250196 SUSE Bug 1250196 In the Linux kernel, the following vulnerability has been resolved: cifs: prevent use-after-free by freeing the cfile later In smb2_compound_op we have a possible use-after-free which can cause hard to debug problems later on. This was revealed during stress testing with KASAN enabled kernel. Fixing it by moving the cfile free call to a few lines below, after the usage. CVE-2023-53377 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53377.html CVE-2023-53377 https://bugzilla.suse.com/1250161 SUSE Bug 1250161 In the Linux kernel, the following vulnerability has been resolved: usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe() Smatch reports: drivers/usb/phy/phy-tahvo.c: tahvo_usb_probe() warn: missing unwind goto? After geting irq, if ret < 0, it will return without error handling to free memory. Just add error handling to fix this problem. CVE-2023-53379 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53379.html CVE-2023-53379 https://bugzilla.suse.com/1250128 SUSE Bug 1250128 In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request There are two check of 'mreplace' in raid10_sync_request(). In the first check, 'need_replace' will be set and 'mreplace' will be used later if no-Faulty 'mreplace' exists, In the second check, 'mreplace' will be set to NULL if it is Faulty, but 'need_replace' will not be changed accordingly. null-ptr-deref occurs if Faulty is set between two check. Fix it by merging two checks into one. And replace 'need_replace' with 'mreplace' because their values are always the same. CVE-2023-53380 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53380.html CVE-2023-53380 https://bugzilla.suse.com/1250198 SUSE Bug 1250198 In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: avoid possible NULL skb pointer dereference In 'mwifiex_handle_uap_rx_forward()', always check the value returned by 'skb_copy()' to avoid potential NULL pointer dereference in 'mwifiex_uap_queue_bridged_pkt()', and drop original skb in case of copying failure. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2023-53384 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53384.html CVE-2023-53384 https://bugzilla.suse.com/1250127 SUSE Bug 1250127 In the Linux kernel, the following vulnerability has been resolved: media: mdp3: Fix resource leaks in of_find_device_by_node Use put_device to release the object get through of_find_device_by_node, avoiding resource leaks. CVE-2023-53385 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53385.html CVE-2023-53385 https://bugzilla.suse.com/1250319 SUSE Bug 1250319 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix potential use-after-free when clear keys Similar to commit c5d2b6fa26b5 ("Bluetooth: Fix use-after-free in hci_remove_ltk/hci_remove_irk"). We can not access k after kfree_rcu() call. CVE-2023-53386 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53386.html CVE-2023-53386 https://bugzilla.suse.com/1250106 SUSE Bug 1250106 In the Linux kernel, the following vulnerability has been resolved: shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs As the ramfs-based tmpfs uses ramfs_init_fs_context() for the init_fs_context method, which allocates fc->s_fs_info, use ramfs_kill_sb() to free it and avoid a memory leak. CVE-2023-53391 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53391.html CVE-2023-53391 https://bugzilla.suse.com/1250117 SUSE Bug 1250117 In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: xsk: Fix crash on regular rq reactivation When the regular rq is reactivated after the XSK socket is closed it could be reading stale cqes which eventually corrupts the rq. This leads to no more traffic being received on the regular rq and a crash on the next close or deactivation of the rq. Kal Cuttler Conely reported this issue as a crash on the release path when the xdpsock sample program is stopped (killed) and restarted in sequence while traffic is running. This patch flushes all cqes when during the rq flush. The cqe flushing is done in the reset state of the rq. mlx5e_rq_to_ready code is moved into the flush function to allow for this. CVE-2023-53394 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53394.html CVE-2023-53394 https://bugzilla.suse.com/1250199 SUSE Bug 1250199 In the Linux kernel, the following vulnerability has been resolved: ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer ACPICA commit 90310989a0790032f5a0140741ff09b545af4bc5 According to the ACPI specification 19.6.134, no argument is required to be passed for ASL Timer instruction. For taking care of no argument, AML_NO_OPERAND_RESOLVE flag is added to ASL Timer instruction opcode. When ASL timer instruction interpreted by ACPI interpreter, getting error. After adding AML_NO_OPERAND_RESOLVE flag to ASL Timer instruction opcode, issue is not observed. ============================================================= UBSAN: array-index-out-of-bounds in acpica/dswexec.c:401:12 index -1 is out of range for type 'union acpi_operand_object *[9]' CPU: 37 PID: 1678 Comm: cat Not tainted 6.0.0-dev-th500-6.0.y-1+bcf8c46459e407-generic-64k HW name: NVIDIA BIOS v1.1.1-d7acbfc-dirty 12/19/2022 Call trace: dump_backtrace+0xe0/0x130 show_stack+0x20/0x60 dump_stack_lvl+0x68/0x84 dump_stack+0x18/0x34 ubsan_epilogue+0x10/0x50 __ubsan_handle_out_of_bounds+0x80/0x90 acpi_ds_exec_end_op+0x1bc/0x6d8 acpi_ps_parse_loop+0x57c/0x618 acpi_ps_parse_aml+0x1e0/0x4b4 acpi_ps_execute_method+0x24c/0x2b8 acpi_ns_evaluate+0x3a8/0x4bc acpi_evaluate_object+0x15c/0x37c acpi_evaluate_integer+0x54/0x15c show_power+0x8c/0x12c [acpi_power_meter] CVE-2023-53395 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53395.html CVE-2023-53395 https://bugzilla.suse.com/1247374 SUSE Bug 1247374 https://bugzilla.suse.com/1250358 SUSE Bug 1250358 https://bugzilla.suse.com/1250359 SUSE Bug 1250359 In the Linux kernel, the following vulnerability has been resolved: modpost: fix off by one in is_executable_section() The > comparison should be >= to prevent an out of bounds array access. CVE-2023-53397 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53397.html CVE-2023-53397 https://bugzilla.suse.com/1250125 SUSE Bug 1250125 In the Linux kernel, the following vulnerability has been resolved: mm: kmem: fix a NULL pointer dereference in obj_stock_flush_required() KCSAN found an issue in obj_stock_flush_required(): stock->cached_objcg can be reset between the check and dereference: ================================================================== BUG: KCSAN: data-race in drain_all_stock / drain_obj_stock write to 0xffff888237c2a2f8 of 8 bytes by task 19625 on cpu 0: drain_obj_stock+0x408/0x4e0 mm/memcontrol.c:3306 refill_obj_stock+0x9c/0x1e0 mm/memcontrol.c:3340 obj_cgroup_uncharge+0xe/0x10 mm/memcontrol.c:3408 memcg_slab_free_hook mm/slab.h:587 [inline] __cache_free mm/slab.c:3373 [inline] __do_kmem_cache_free mm/slab.c:3577 [inline] kmem_cache_free+0x105/0x280 mm/slab.c:3602 __d_free fs/dcache.c:298 [inline] dentry_free fs/dcache.c:375 [inline] __dentry_kill+0x422/0x4a0 fs/dcache.c:621 dentry_kill+0x8d/0x1e0 dput+0x118/0x1f0 fs/dcache.c:913 __fput+0x3bf/0x570 fs/file_table.c:329 ____fput+0x15/0x20 fs/file_table.c:349 task_work_run+0x123/0x160 kernel/task_work.c:179 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] exit_to_user_mode_loop+0xcf/0xe0 kernel/entry/common.c:171 exit_to_user_mode_prepare+0x6a/0xa0 kernel/entry/common.c:203 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] syscall_exit_to_user_mode+0x26/0x140 kernel/entry/common.c:296 do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd read to 0xffff888237c2a2f8 of 8 bytes by task 19632 on cpu 1: obj_stock_flush_required mm/memcontrol.c:3319 [inline] drain_all_stock+0x174/0x2a0 mm/memcontrol.c:2361 try_charge_memcg+0x6d0/0xd10 mm/memcontrol.c:2703 try_charge mm/memcontrol.c:2837 [inline] mem_cgroup_charge_skmem+0x51/0x140 mm/memcontrol.c:7290 sock_reserve_memory+0xb1/0x390 net/core/sock.c:1025 sk_setsockopt+0x800/0x1e70 net/core/sock.c:1525 udp_lib_setsockopt+0x99/0x6c0 net/ipv4/udp.c:2692 udp_setsockopt+0x73/0xa0 net/ipv4/udp.c:2817 sock_common_setsockopt+0x61/0x70 net/core/sock.c:3668 __sys_setsockopt+0x1c3/0x230 net/socket.c:2271 __do_sys_setsockopt net/socket.c:2282 [inline] __se_sys_setsockopt net/socket.c:2279 [inline] __x64_sys_setsockopt+0x66/0x80 net/socket.c:2279 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 value changed: 0xffff8881382d52c0 -> 0xffff888138893740 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 19632 Comm: syz-executor.0 Not tainted 6.3.0-rc2-syzkaller-00387-g534293368afa #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023 Fix it by using READ_ONCE()/WRITE_ONCE() for all accesses to stock->cached_objcg. CVE-2023-53401 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53401.html CVE-2023-53401 https://bugzilla.suse.com/1250120 SUSE Bug 1250120 In the Linux kernel, the following vulnerability has been resolved: ntfs: Fix panic about slab-out-of-bounds caused by ntfs_listxattr() Here is a BUG report from syzbot: BUG: KASAN: slab-out-of-bounds in ntfs_list_ea fs/ntfs3/xattr.c:191 [inline] BUG: KASAN: slab-out-of-bounds in ntfs_listxattr+0x401/0x570 fs/ntfs3/xattr.c:710 Read of size 1 at addr ffff888021acaf3d by task syz-executor128/3632 Call Trace: ntfs_list_ea fs/ntfs3/xattr.c:191 [inline] ntfs_listxattr+0x401/0x570 fs/ntfs3/xattr.c:710 vfs_listxattr fs/xattr.c:457 [inline] listxattr+0x293/0x2d0 fs/xattr.c:804 Fix the logic of ea_all iteration. When the ea->name_len is 0, return immediately, or Add2Ptr() would visit invalid memory in the next loop. [almaz.alexandrovich@paragon-software.com: lines of the patch have changed] CVE-2023-53420 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53420.html CVE-2023-53420 https://bugzilla.suse.com/1250186 SUSE Bug 1250186 In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats() When blkg_alloc() is called to allocate a blkcg_gq structure with the associated blkg_iostat_set's, there are 2 fields within blkg_iostat_set that requires proper initialization - blkg & sync. The former field was introduced by commit 3b8cc6298724 ("blk-cgroup: Optimize blkcg_rstat_flush()") while the later one was introduced by commit f73316482977 ("blk-cgroup: reimplement basic IO stats using cgroup rstat"). Unfortunately those fields in the blkg_iostat_set's are not properly re-initialized when they are cleared in v1's blkcg_reset_stats(). This can lead to a kernel panic due to NULL pointer access of the blkg pointer. The missing initialization of sync is less problematic and can be a problem in a debug kernel due to missing lockdep initialization. Fix these problems by re-initializing them after memory clearing. CVE-2023-53421 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53421.html CVE-2023-53421 https://bugzilla.suse.com/1250171 SUSE Bug 1250171 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: fix of_iomap memory leak Smatch reports: drivers/clk/mediatek/clk-mtk.c:583 mtk_clk_simple_probe() warn: 'base' from of_iomap() not released on lines: 496. This problem was also found in linux-next. In mtk_clk_simple_probe(), base is not released when handling errors if clk_data is not existed, which may cause a leak. So free_base should be added here to release base. CVE-2023-53424 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53424.html CVE-2023-53424 https://bugzilla.suse.com/1250169 SUSE Bug 1250169 In the Linux kernel, the following vulnerability has been resolved: media: platform: mediatek: vpu: fix NULL ptr dereference If pdev is NULL, then it is still dereferenced. This fixes this smatch warning: drivers/media/platform/mediatek/vpu/mtk_vpu.c:570 vpu_load_firmware() warn: address of NULL pointer 'pdev' CVE-2023-53425 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53425.html CVE-2023-53425 https://bugzilla.suse.com/1250290 SUSE Bug 1250290 In the Linux kernel, the following vulnerability has been resolved: xsk: Fix xsk_diag use-after-free error during socket cleanup Fix a use-after-free error that is possible if the xsk_diag interface is used after the socket has been unbound from the device. This can happen either due to the socket being closed or the device disappearing. In the early days of AF_XDP, the way we tested that a socket was not bound to a device was to simply check if the netdevice pointer in the xsk socket structure was NULL. Later, a better system was introduced by having an explicit state variable in the xsk socket struct. For example, the state of a socket that is on the way to being closed and has been unbound from the device is XSK_UNBOUND. The commit in the Fixes tag below deleted the old way of signalling that a socket is unbound, setting dev to NULL. This in the belief that all code using the old way had been exterminated. That was unfortunately not true as the xsk diagnostics code was still using the old way and thus does not work as intended when a socket is going down. Fix this by introducing a test against the state variable. If the socket is in the state XSK_UNBOUND, simply abort the diagnostic's netlink operation. CVE-2023-53426 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53426.html CVE-2023-53426 https://bugzilla.suse.com/1250166 SUSE Bug 1250166 In the Linux kernel, the following vulnerability has been resolved: powercap: arm_scmi: Remove recursion while parsing zones Powercap zones can be defined as arranged in a hierarchy of trees and when registering a zone with powercap_register_zone(), the kernel powercap subsystem expects this to happen starting from the root zones down to the leaves; on the other side, de-registration by powercap_deregister_zone() must begin from the leaf zones. Available SCMI powercap zones are retrieved dynamically from the platform at probe time and, while any defined hierarchy between the zones is described properly in the zones descriptor, the platform returns the availables zones with no particular well-defined order: as a consequence, the trees possibly composing the hierarchy of zones have to be somehow walked properly to register the retrieved zones from the root. Currently the ARM SCMI Powercap driver walks the zones using a recursive algorithm; this approach, even though correct and tested can lead to kernel stack overflow when processing a returned hierarchy of zones composed by particularly high trees. Avoid possible kernel stack overflow by substituting the recursive approach with an iterative one supported by a dynamically allocated stack-like data structure. CVE-2023-53428 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53428.html CVE-2023-53428 https://bugzilla.suse.com/1250167 SUSE Bug 1250167 In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. This also fundamentally solves the long problem documented in a comment in __extent_writepage by never leaking the error bit into the submission context. CVE-2023-53429 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53429.html CVE-2023-53429 https://bugzilla.suse.com/1250384 SUSE Bug 1250384 In the Linux kernel, the following vulnerability has been resolved: firewire: net: fix use after free in fwnet_finish_incoming_packet() The netif_rx() function frees the skb so we can't dereference it to save the skb->len. CVE-2023-53432 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53432.html CVE-2023-53432 https://bugzilla.suse.com/1250426 SUSE Bug 1250426 In the Linux kernel, the following vulnerability has been resolved: scsi: snic: Fix possible memory leak if device_add() fails If device_add() returns error, the name allocated by dev_set_name() needs be freed. As the comment of device_add() says, put_device() should be used to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanp(). CVE-2023-53436 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53436.html CVE-2023-53436 https://bugzilla.suse.com/1250156 SUSE Bug 1250156 In the Linux kernel, the following vulnerability has been resolved: x86/MCE: Always save CS register on AMD Zen IF Poison errors The Instruction Fetch (IF) units on current AMD Zen-based systems do not guarantee a synchronous #MC is delivered for poison consumption errors. Therefore, MCG_STATUS[EIPV|RIPV] will not be set. However, the microarchitecture does guarantee that the exception is delivered within the same context. In other words, the exact rIP is not known, but the context is known to not have changed. There is no architecturally-defined method to determine this behavior. The Code Segment (CS) register is always valid on such IF unit poison errors regardless of the value of MCG_STATUS[EIPV|RIPV]. Add a quirk to save the CS register for poison consumption from the IF unit banks. This is needed to properly determine the context of the error. Otherwise, the severity grading function will assume the context is IN_KERNEL due to the m->cs value being 0 (the initialized value). This leads to unnecessary kernel panics on data poison errors due to the kernel believing the poison consumption occurred in kernel context. CVE-2023-53438 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53438.html CVE-2023-53438 https://bugzilla.suse.com/1250180 SUSE Bug 1250180 https://bugzilla.suse.com/1250708 SUSE Bug 1250708 In the Linux kernel, the following vulnerability has been resolved: bpf: cpumap: Fix memory leak in cpu_map_update_elem Syzkaller reported a memory leak as follows: BUG: memory leak unreferenced object 0xff110001198ef748 (size 192): comm "syz-executor.3", pid 17672, jiffies 4298118891 (age 9.906s) hex dump (first 32 bytes): 00 00 00 00 4a 19 00 00 80 ad e3 e4 fe ff c0 00 ....J........... 00 b2 d3 0c 01 00 11 ff 28 f5 8e 19 01 00 11 ff ........(....... backtrace: [<ffffffffadd28087>] __cpu_map_entry_alloc+0xf7/0xb00 [<ffffffffadd28d8e>] cpu_map_update_elem+0x2fe/0x3d0 [<ffffffffadc6d0fd>] bpf_map_update_value.isra.0+0x2bd/0x520 [<ffffffffadc7349b>] map_update_elem+0x4cb/0x720 [<ffffffffadc7d983>] __se_sys_bpf+0x8c3/0xb90 [<ffffffffb029cc80>] do_syscall_64+0x30/0x40 [<ffffffffb0400099>] entry_SYSCALL_64_after_hwframe+0x61/0xc6 BUG: memory leak unreferenced object 0xff110001198ef528 (size 192): comm "syz-executor.3", pid 17672, jiffies 4298118891 (age 9.906s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffffadd281f0>] __cpu_map_entry_alloc+0x260/0xb00 [<ffffffffadd28d8e>] cpu_map_update_elem+0x2fe/0x3d0 [<ffffffffadc6d0fd>] bpf_map_update_value.isra.0+0x2bd/0x520 [<ffffffffadc7349b>] map_update_elem+0x4cb/0x720 [<ffffffffadc7d983>] __se_sys_bpf+0x8c3/0xb90 [<ffffffffb029cc80>] do_syscall_64+0x30/0x40 [<ffffffffb0400099>] entry_SYSCALL_64_after_hwframe+0x61/0xc6 BUG: memory leak unreferenced object 0xff1100010fd93d68 (size 8): comm "syz-executor.3", pid 17672, jiffies 4298118891 (age 9.906s) hex dump (first 8 bytes): 00 00 00 00 00 00 00 00 ........ backtrace: [<ffffffffade5db3e>] kvmalloc_node+0x11e/0x170 [<ffffffffadd28280>] __cpu_map_entry_alloc+0x2f0/0xb00 [<ffffffffadd28d8e>] cpu_map_update_elem+0x2fe/0x3d0 [<ffffffffadc6d0fd>] bpf_map_update_value.isra.0+0x2bd/0x520 [<ffffffffadc7349b>] map_update_elem+0x4cb/0x720 [<ffffffffadc7d983>] __se_sys_bpf+0x8c3/0xb90 [<ffffffffb029cc80>] do_syscall_64+0x30/0x40 [<ffffffffb0400099>] entry_SYSCALL_64_after_hwframe+0x61/0xc6 In the cpu_map_update_elem flow, when kthread_stop is called before calling the threadfn of rcpu->kthread, since the KTHREAD_SHOULD_STOP bit of kthread has been set by kthread_stop, the threadfn of rcpu->kthread will never be executed, and rcpu->refcnt will never be 0, which will lead to the allocated rcpu, rcpu->queue and rcpu->queue->queue cannot be released. Calling kthread_stop before executing kthread's threadfn will return -EINTR. We can complete the release of memory resources in this state. CVE-2023-53441 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53441.html CVE-2023-53441 https://bugzilla.suse.com/1250150 SUSE Bug 1250150 In the Linux kernel, the following vulnerability has been resolved: ice: Block switchdev mode when ADQ is active and vice versa ADQ and switchdev are not supported simultaneously. Enabling both at the same time can result in nullptr dereference. To prevent this, check if ADQ is active when changing devlink mode to switchdev mode, and check if switchdev is active when enabling ADQ. CVE-2023-53442 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53442.html CVE-2023-53442 https://bugzilla.suse.com/1250201 SUSE Bug 1250201 In the Linux kernel, the following vulnerability has been resolved: drm/ttm: fix bulk_move corruption when adding a entry When the resource is the first in the bulk_move range, adding it again (thus moving it to the tail) will corrupt the list since the first pointer is not moved. This eventually lead to null pointer deref in ttm_lru_bulk_move_del() CVE-2023-53444 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53444.html CVE-2023-53444 https://bugzilla.suse.com/1250157 SUSE Bug 1250157 In the Linux kernel, the following vulnerability has been resolved: PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free Struct pcie_link_state->downstream is a pointer to the pci_dev of function 0. Previously we retained that pointer when removing function 0, and subsequent ASPM policy changes dereferenced it, resulting in a use-after-free warning from KASAN, e.g.: # echo 1 > /sys/bus/pci/devices/0000:03:00.0/remove # echo powersave > /sys/module/pcie_aspm/parameters/policy BUG: KASAN: slab-use-after-free in pcie_config_aspm_link+0x42d/0x500 Call Trace: kasan_report+0xae/0xe0 pcie_config_aspm_link+0x42d/0x500 pcie_aspm_set_policy+0x8e/0x1a0 param_attr_store+0x162/0x2c0 module_attr_store+0x3e/0x80 PCIe spec r6.0, sec 7.5.3.7, recommends that software program the same ASPM Control value in all functions of multi-function devices. Disable ASPM and free the pcie_link_state when any child function is removed so we can discard the dangling pcie_link_state->downstream pointer and maintain the same ASPM Control configuration for all functions. [bhelgaas: commit log and comment] CVE-2023-53446 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53446.html CVE-2023-53446 https://bugzilla.suse.com/1250145 SUSE Bug 1250145 In the Linux kernel, the following vulnerability has been resolved: f2fs: don't reset unchangable mount option in f2fs_remount() syzbot reports a bug as below: general protection fault, probably for non-canonical address 0xdffffc0000000009: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:__lock_acquire+0x69/0x2000 kernel/locking/lockdep.c:4942 Call Trace: lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5691 __raw_write_lock include/linux/rwlock_api_smp.h:209 [inline] _raw_write_lock+0x2e/0x40 kernel/locking/spinlock.c:300 __drop_extent_tree+0x3ac/0x660 fs/f2fs/extent_cache.c:1100 f2fs_drop_extent_tree+0x17/0x30 fs/f2fs/extent_cache.c:1116 f2fs_insert_range+0x2d5/0x3c0 fs/f2fs/file.c:1664 f2fs_fallocate+0x4e4/0x6d0 fs/f2fs/file.c:1838 vfs_fallocate+0x54b/0x6b0 fs/open.c:324 ksys_fallocate fs/open.c:347 [inline] __do_sys_fallocate fs/open.c:355 [inline] __se_sys_fallocate fs/open.c:353 [inline] __x64_sys_fallocate+0xbd/0x100 fs/open.c:353 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 The root cause is race condition as below: - since it tries to remount rw filesystem, so that do_remount won't call sb_prepare_remount_readonly to block fallocate, there may be race condition in between remount and fallocate. - in f2fs_remount(), default_options() will reset mount option to default one, and then update it based on result of parse_options(), so there is a hole which race condition can happen. Thread A Thread B - f2fs_fill_super - parse_options - clear_opt(READ_EXTENT_CACHE) - f2fs_remount - default_options - set_opt(READ_EXTENT_CACHE) - f2fs_fallocate - f2fs_insert_range - f2fs_drop_extent_tree - __drop_extent_tree - __may_extent_tree - test_opt(READ_EXTENT_CACHE) return true - write_lock(&et->lock) access NULL pointer - parse_options - clear_opt(READ_EXTENT_CACHE) CVE-2023-53447 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53447.html CVE-2023-53447 https://bugzilla.suse.com/1250241 SUSE Bug 1250241 In the Linux kernel, the following vulnerability has been resolved: fbdev: imxfb: Removed unneeded release_mem_region Remove unnecessary release_mem_region from the error path to prevent mem region from being released twice, which could avoid resource leak or other unexpected issues. CVE-2023-53448 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53448.html CVE-2023-53448 https://bugzilla.suse.com/1250873 SUSE Bug 1250873 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix potential NULL pointer dereference Klocwork tool reported 'cur_dsd' may be dereferenced. Add fix to validate pointer before dereferencing the pointer. CVE-2023-53451 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53451.html CVE-2023-53451 https://bugzilla.suse.com/1250831 SUSE Bug 1250831 In the Linux kernel, the following vulnerability has been resolved: HID: multitouch: Correct devm device reference for hidinput input_dev name Reference the HID device rather than the input device for the devm allocation of the input_dev name. Referencing the input_dev would lead to a use-after-free when the input_dev was unregistered and subsequently fires a uevent that depends on the name. At the point of firing the uevent, the name would be freed by devres management. Use devm_kasprintf to simplify the logic for allocating memory and formatting the input_dev name string. CVE-2023-53454 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53454.html CVE-2023-53454 https://bugzilla.suse.com/1250759 SUSE Bug 1250759 In the Linux kernel, the following vulnerability has been resolved: scsi: qla4xxx: Add length check when parsing nlattrs There are three places that qla4xxx parses nlattrs: - qla4xxx_set_chap_entry() - qla4xxx_iface_set_param() - qla4xxx_sysfs_ddb_set_param() and each of them directly converts the nlattr to specific pointer of structure without length checking. This could be dangerous as those attributes are not validated and a malformed nlattr (e.g., length 0) could result in an OOB read that leaks heap dirty data. Add the nla_len check before accessing the nlattr data and return EINVAL if the length check fails. CVE-2023-53456 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53456.html CVE-2023-53456 https://bugzilla.suse.com/1250765 SUSE Bug 1250765 In the Linux kernel, the following vulnerability has been resolved: FS: JFS: Fix null-ptr-deref Read in txBegin Syzkaller reported an issue where txBegin may be called on a superblock in a read-only mounted filesystem which leads to NULL pointer deref. This could be solved by checking if the filesystem is read-only before calling txBegin, and returning with appropiate error code. CVE-2023-53457 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53457.html CVE-2023-53457 https://bugzilla.suse.com/1250763 SUSE Bug 1250763 In the Linux kernel, the following vulnerability has been resolved: io_uring: wait interruptibly for request completions on exit WHen the ring exits, cleanup is done and the final cancelation and waiting on completions is done by io_ring_exit_work. That function is invoked by kworker, which doesn't take any signals. Because of that, it doesn't really matter if we wait for completions in TASK_INTERRUPTIBLE or TASK_UNINTERRUPTIBLE state. However, it does matter to the hung task detection checker! Normally we expect cancelations and completions to happen rather quickly. Some test cases, however, will exit the ring and park the owning task stopped (eg via SIGSTOP). If the owning task needs to run task_work to complete requests, then io_ring_exit_work won't make any progress until the task is runnable again. Hence io_ring_exit_work can trigger the hung task detection, which is particularly problematic if panic-on-hung-task is enabled. As the ring exit doesn't take signals to begin with, have it wait interruptibly rather than uninterruptibly. io_uring has a separate stuck-exit warning that triggers independently anyway, so we're not really missing anything by making this switch. CVE-2023-53461 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53461.html CVE-2023-53461 https://bugzilla.suse.com/1250941 SUSE Bug 1250941 In the Linux kernel, the following vulnerability has been resolved: hsr: Fix uninit-value access in fill_frame_info() Syzbot reports the following uninit-value access problem. ===================================================== BUG: KMSAN: uninit-value in fill_frame_info net/hsr/hsr_forward.c:601 [inline] BUG: KMSAN: uninit-value in hsr_forward_skb+0x9bd/0x30f0 net/hsr/hsr_forward.c:616 fill_frame_info net/hsr/hsr_forward.c:601 [inline] hsr_forward_skb+0x9bd/0x30f0 net/hsr/hsr_forward.c:616 hsr_dev_xmit+0x192/0x330 net/hsr/hsr_device.c:223 __netdev_start_xmit include/linux/netdevice.h:4889 [inline] netdev_start_xmit include/linux/netdevice.h:4903 [inline] xmit_one net/core/dev.c:3544 [inline] dev_hard_start_xmit+0x247/0xa10 net/core/dev.c:3560 __dev_queue_xmit+0x34d0/0x52a0 net/core/dev.c:4340 dev_queue_xmit include/linux/netdevice.h:3082 [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:753 [inline] __sys_sendto+0x781/0xa30 net/socket.c:2176 __do_sys_sendto net/socket.c:2188 [inline] __se_sys_sendto net/socket.c:2184 [inline] __ia32_sys_sendto+0x11f/0x1c0 net/socket.c:2184 do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline] __do_fast_syscall_32+0xa2/0x100 arch/x86/entry/common.c:178 do_fast_syscall_32+0x37/0x80 arch/x86/entry/common.c:203 do_SYSENTER_32+0x1f/0x30 arch/x86/entry/common.c:246 entry_SYSENTER_compat_after_hwframe+0x70/0x82 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+0x148/0x470 net/core/skbuff.c:559 __alloc_skb+0x318/0x740 net/core/skbuff.c:644 alloc_skb include/linux/skbuff.h:1286 [inline] alloc_skb_with_frags+0xc8/0xbd0 net/core/skbuff.c:6299 sock_alloc_send_pskb+0xa80/0xbf0 net/core/sock.c:2794 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:753 [inline] __sys_sendto+0x781/0xa30 net/socket.c:2176 __do_sys_sendto net/socket.c:2188 [inline] __se_sys_sendto net/socket.c:2184 [inline] __ia32_sys_sendto+0x11f/0x1c0 net/socket.c:2184 do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline] __do_fast_syscall_32+0xa2/0x100 arch/x86/entry/common.c:178 do_fast_syscall_32+0x37/0x80 arch/x86/entry/common.c:203 do_SYSENTER_32+0x1f/0x30 arch/x86/entry/common.c:246 entry_SYSENTER_compat_after_hwframe+0x70/0x82 It is because VLAN not yet supported in hsr driver. Return error when protocol is ETH_P_8021Q in fill_frame_info() now to fix it. CVE-2023-53462 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53462.html CVE-2023-53462 https://bugzilla.suse.com/1250878 SUSE Bug 1250878 In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Do not reset dql stats on NON_FATAL err All ibmvnic resets, make a call to netdev_tx_reset_queue() when re-opening the device. netdev_tx_reset_queue() resets the num_queued and num_completed byte counters. These stats are used in Byte Queue Limit (BQL) algorithms. The difference between these two stats tracks the number of bytes currently sitting on the physical NIC. ibmvnic increases the number of queued bytes though calls to netdev_tx_sent_queue() in the drivers xmit function. When, VIOS reports that it is done transmitting bytes, the ibmvnic device increases the number of completed bytes through calls to netdev_tx_completed_queue(). It is important to note that the driver batches its transmit calls and num_queued is increased every time that an skb is added to the next batch, not necessarily when the batch is sent to VIOS for transmission. Unlike other reset types, a NON FATAL reset will not flush the sub crq tx buffers. Therefore, it is possible for the batched skb array to be partially full. So if there is call to netdev_tx_reset_queue() when re-opening the device, the value of num_queued (0) would not account for the skb's that are currently batched. Eventually, when the batch is sent to VIOS, the call to netdev_tx_completed_queue() would increase num_completed to a value greater than the num_queued. This causes a BUG_ON crash: ibmvnic 30000002: Firmware reports error, cause: adapter problem. Starting recovery... ibmvnic 30000002: tx error 600 ibmvnic 30000002: tx error 600 ibmvnic 30000002: tx error 600 ibmvnic 30000002: tx error 600 ------------[ cut here ]------------ kernel BUG at lib/dynamic_queue_limits.c:27! Oops: Exception in kernel mode, sig: 5 [....] NIP dql_completed+0x28/0x1c0 LR ibmvnic_complete_tx.isra.0+0x23c/0x420 [ibmvnic] Call Trace: ibmvnic_complete_tx.isra.0+0x3f8/0x420 [ibmvnic] (unreliable) ibmvnic_interrupt_tx+0x40/0x70 [ibmvnic] __handle_irq_event_percpu+0x98/0x270 ---[ end trace ]--- Therefore, do not reset the dql stats when performing a NON_FATAL reset. CVE-2023-53463 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53463.html CVE-2023-53463 https://bugzilla.suse.com/1250867 SUSE Bug 1250867 In the Linux kernel, the following vulnerability has been resolved: soundwire: qcom: fix storing port config out-of-bounds The 'qcom_swrm_ctrl->pconfig' has size of QCOM_SDW_MAX_PORTS (14), however we index it starting from 1, not 0, to match real port numbers. This can lead to writing port config past 'pconfig' bounds and overwriting next member of 'qcom_swrm_ctrl' struct. Reported also by smatch: drivers/soundwire/qcom.c:1269 qcom_swrm_get_port_config() error: buffer overflow 'ctrl->pconfig' 14 <= 14 CVE-2023-53465 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53465.html CVE-2023-53465 https://bugzilla.suse.com/1250863 SUSE Bug 1250863 In the Linux kernel, the following vulnerability has been resolved: pwm: lpc32xx: Remove handling of PWM channels Because LPC32xx PWM controllers have only a single output which is registered as the only PWM device/channel per controller, it is known in advance that pwm->hwpwm value is always 0. On basis of this fact simplify the code by removing operations with pwm->hwpwm, there is no controls which require channel number as input. Even though I wasn't aware at the time when I forward ported that patch, this fixes a null pointer dereference as lpc32xx->chip.pwms is NULL before devm_pwmchip_add() is called. CVE-2023-53472 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53472.html CVE-2023-53472 https://bugzilla.suse.com/1250841 SUSE Bug 1250841 In the Linux kernel, the following vulnerability has been resolved: cxl/acpi: Fix a use-after-free in cxl_parse_cfmws() KASAN and KFENCE detected an user-after-free in the CXL driver. This happens in the cxl_decoder_add() fail path. KASAN prints the following error: BUG: KASAN: slab-use-after-free in cxl_parse_cfmws (drivers/cxl/acpi.c:299) This happens in cxl_parse_cfmws(), where put_device() is called, releasing cxld, which is accessed later. Use the local variables in the dev_err() instead of pointing to the released memory. Since the dev_err() is printing a resource, change the open coded print format to use the %pr format specifier. CVE-2023-53479 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53479.html CVE-2023-53479 https://bugzilla.suse.com/1250837 SUSE Bug 1250837 In the Linux kernel, the following vulnerability has been resolved: kobject: Add sanity check for kset->kobj.ktype in kset_register() When I register a kset in the following way: static struct kset my_kset; kobject_set_name(&my_kset.kobj, "my_kset"); ret = kset_register(&my_kset); A null pointer dereference exception is occurred: [ 4453.568337] Unable to handle kernel NULL pointer dereference at \ virtual address 0000000000000028 ... ... [ 4453.810361] Call trace: [ 4453.813062] kobject_get_ownership+0xc/0x34 [ 4453.817493] kobject_add_internal+0x98/0x274 [ 4453.822005] kset_register+0x5c/0xb4 [ 4453.825820] my_kobj_init+0x44/0x1000 [my_kset] ... ... Because I didn't initialize my_kset.kobj.ktype. According to the description in Documentation/core-api/kobject.rst: - A ktype is the type of object that embeds a kobject. Every structure that embeds a kobject needs a corresponding ktype. So add sanity check to make sure kset->kobj.ktype is not NULL. CVE-2023-53480 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53480.html CVE-2023-53480 https://bugzilla.suse.com/1250861 SUSE Bug 1250861 In the Linux kernel, the following vulnerability has been resolved: fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev Syzkaller reported the following issue: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:1965:6 index -84 is out of range for type 's8[341]' (aka 'signed char[341]') CPU: 1 PID: 4995 Comm: syz-executor146 Not tainted 6.4.0-rc6-syzkaller-00037-gb6dad5178cea #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:217 [inline] __ubsan_handle_out_of_bounds+0x11c/0x150 lib/ubsan.c:348 dbAllocDmapLev+0x3e5/0x430 fs/jfs/jfs_dmap.c:1965 dbAllocCtl+0x113/0x920 fs/jfs/jfs_dmap.c:1809 dbAllocAG+0x28f/0x10b0 fs/jfs/jfs_dmap.c:1350 dbAlloc+0x658/0xca0 fs/jfs/jfs_dmap.c:874 dtSplitUp fs/jfs/jfs_dtree.c:974 [inline] dtInsert+0xda7/0x6b00 fs/jfs/jfs_dtree.c:863 jfs_create+0x7b6/0xbb0 fs/jfs/namei.c:137 lookup_open fs/namei.c:3492 [inline] open_last_lookups fs/namei.c:3560 [inline] path_openat+0x13df/0x3170 fs/namei.c:3788 do_filp_open+0x234/0x490 fs/namei.c:3818 do_sys_openat2+0x13f/0x500 fs/open.c:1356 do_sys_open fs/open.c:1372 [inline] __do_sys_openat fs/open.c:1388 [inline] __se_sys_openat fs/open.c:1383 [inline] __x64_sys_openat+0x247/0x290 fs/open.c:1383 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 RIP: 0033:0x7f1f4e33f7e9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 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 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffc21129578 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1f4e33f7e9 RDX: 000000000000275a RSI: 0000000020000040 RDI: 00000000ffffff9c RBP: 00007f1f4e2ff080 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f1f4e2ff110 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> The bug occurs when the dbAllocDmapLev()function attempts to access dp->tree.stree[leafidx + LEAFIND] while the leafidx value is negative. To rectify this, the patch introduces a safeguard within the dbAllocDmapLev() function. A check has been added to verify if leafidx is negative. If it is, the function immediately returns an I/O error, preventing any further execution that could potentially cause harm. Tested via syzbot. CVE-2023-53485 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53485.html CVE-2023-53485 https://bugzilla.suse.com/1250872 SUSE Bug 1250872 In the Linux kernel, the following vulnerability has been resolved: powerpc/rtas_flash: allow user copy to flash block cache objects With hardened usercopy enabled (CONFIG_HARDENED_USERCOPY=y), using the /proc/powerpc/rtas/firmware_update interface to prepare a system firmware update yields a BUG(): kernel BUG at mm/usercopy.c:102! Oops: Exception in kernel mode, sig: 5 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries Modules linked in: CPU: 0 PID: 2232 Comm: dd Not tainted 6.5.0-rc3+ #2 Hardware name: IBM,8408-E8E POWER8E (raw) 0x4b0201 0xf000004 of:IBM,FW860.50 (SV860_146) hv:phyp pSeries NIP: c0000000005991d0 LR: c0000000005991cc CTR: 0000000000000000 REGS: c0000000148c76a0 TRAP: 0700 Not tainted (6.5.0-rc3+) MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24002242 XER: 0000000c CFAR: c0000000001fbd34 IRQMASK: 0 [ ... GPRs omitted ... ] NIP usercopy_abort+0xa0/0xb0 LR usercopy_abort+0x9c/0xb0 Call Trace: usercopy_abort+0x9c/0xb0 (unreliable) __check_heap_object+0x1b4/0x1d0 __check_object_size+0x2d0/0x380 rtas_flash_write+0xe4/0x250 proc_reg_write+0xfc/0x160 vfs_write+0xfc/0x4e0 ksys_write+0x90/0x160 system_call_exception+0x178/0x320 system_call_common+0x160/0x2c4 The blocks of the firmware image are copied directly from user memory to objects allocated from flash_block_cache, so flash_block_cache must be created using kmem_cache_create_usercopy() to mark it safe for user access. [mpe: Trim and indent oops] CVE-2023-53487 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53487.html CVE-2023-53487 https://bugzilla.suse.com/1250830 SUSE Bug 1250830 In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix possible panic during hotplug remove During hotplug remove it is possible that the update counters work might be pending, and may run after memory has been freed. Cancel the update counters work before freeing memory. CVE-2023-53488 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53488.html CVE-2023-53488 https://bugzilla.suse.com/1250825 SUSE Bug 1250825 In the Linux kernel, the following vulnerability has been resolved: mptcp: fix disconnect vs accept race Despite commit 0ad529d9fd2b ("mptcp: fix possible divide by zero in recvmsg()"), the mptcp protocol is still prone to a race between disconnect() (or shutdown) and accept. The root cause is that the mentioned commit checks the msk-level flag, but mptcp_stream_accept() does acquire the msk-level lock, as it can rely directly on the first subflow lock. As reported by Christoph than can lead to a race where an msk socket is accepted after that mptcp_subflow_queue_clean() releases the listener socket lock and just before it takes destructive actions leading to the following splat: BUG: kernel NULL pointer dereference, address: 0000000000000012 PGD 5a4ca067 P4D 5a4ca067 PUD 37d4c067 PMD 0 Oops: 0000 [#1] PREEMPT SMP CPU: 2 PID: 10955 Comm: syz-executor.5 Not tainted 6.5.0-rc1-gdc7b257ee5dd #37 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-2.el7 04/01/2014 RIP: 0010:mptcp_stream_accept+0x1ee/0x2f0 include/net/inet_sock.h:330 Code: 0a 09 00 48 8b 1b 4c 39 e3 74 07 e8 bc 7c 7f fe eb a1 e8 b5 7c 7f fe 4c 8b 6c 24 08 eb 05 e8 a9 7c 7f fe 49 8b 85 d8 09 00 00 <0f> b6 40 12 88 44 24 07 0f b6 6c 24 07 bf 07 00 00 00 89 ee e8 89 RSP: 0018:ffffc90000d07dc0 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff888037e8d020 RCX: ffff88803b093300 RDX: 0000000000000000 RSI: ffffffff833822c5 RDI: ffffffff8333896a RBP: 0000607f82031520 R08: ffff88803b093300 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000003e83 R12: ffff888037e8d020 R13: ffff888037e8c680 R14: ffff888009af7900 R15: ffff888009af6880 FS: 00007fc26d708640(0000) GS:ffff88807dd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000012 CR3: 0000000066bc5001 CR4: 0000000000370ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> do_accept+0x1ae/0x260 net/socket.c:1872 __sys_accept4+0x9b/0x110 net/socket.c:1913 __do_sys_accept4 net/socket.c:1954 [inline] __se_sys_accept4 net/socket.c:1951 [inline] __x64_sys_accept4+0x20/0x30 net/socket.c:1951 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x47/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Address the issue by temporary removing the pending request socket from the accept queue, so that racing accept() can't touch them. After depleting the msk - the ssk still exists, as plain TCP sockets, re-insert them into the accept queue, so that later inet_csk_listen_stop() will complete the tcp socket disposal. CVE-2023-53490 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53490.html CVE-2023-53490 https://bugzilla.suse.com/1250827 SUSE Bug 1250827 In the Linux kernel, the following vulnerability has been resolved: start_kernel: Add __no_stack_protector function attribute Back during the discussion of commit a9a3ed1eff36 ("x86: Fix early boot crash on gcc-10, third try") we discussed the need for a function attribute to control the omission of stack protectors on a per-function basis; at the time Clang had support for no_stack_protector but GCC did not. This was fixed in gcc-11. Now that the function attribute is available, let's start using it. Callers of boot_init_stack_canary need to use this function attribute unless they're compiled with -fno-stack-protector, otherwise the canary stored in the stack slot of the caller will differ upon the call to boot_init_stack_canary. This will lead to a call to __stack_chk_fail() then panic. CVE-2023-53491 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53491.html CVE-2023-53491 https://bugzilla.suse.com/1250942 SUSE Bug 1250942 In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: do not ignore genmask when looking up chain by id When adding a rule to a chain referring to its ID, if that chain had been deleted on the same batch, the rule might end up referring to a deleted chain. This will lead to a WARNING like following: [ 33.098431] ------------[ cut here ]------------ [ 33.098678] WARNING: CPU: 5 PID: 69 at net/netfilter/nf_tables_api.c:2037 nf_tables_chain_destroy+0x23d/0x260 [ 33.099217] Modules linked in: [ 33.099388] CPU: 5 PID: 69 Comm: kworker/5:1 Not tainted 6.4.0+ #409 [ 33.099726] Workqueue: events nf_tables_trans_destroy_work [ 33.100018] RIP: 0010:nf_tables_chain_destroy+0x23d/0x260 [ 33.100306] Code: 8b 7c 24 68 e8 64 9c ed fe 4c 89 e7 e8 5c 9c ed fe 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d 31 c0 89 c6 89 c7 c3 cc cc cc cc <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d 31 c0 89 c6 89 c7 [ 33.101271] RSP: 0018:ffffc900004ffc48 EFLAGS: 00010202 [ 33.101546] RAX: 0000000000000001 RBX: ffff888006fc0a28 RCX: 0000000000000000 [ 33.101920] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 33.102649] RBP: ffffc900004ffc78 R08: 0000000000000000 R09: 0000000000000000 [ 33.103018] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880135ef500 [ 33.103385] R13: 0000000000000000 R14: dead000000000122 R15: ffff888006fc0a10 [ 33.103762] FS: 0000000000000000(0000) GS:ffff888024c80000(0000) knlGS:0000000000000000 [ 33.104184] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 33.104493] CR2: 00007fe863b56a50 CR3: 00000000124b0001 CR4: 0000000000770ee0 [ 33.104872] PKRU: 55555554 [ 33.104999] Call Trace: [ 33.105113] <TASK> [ 33.105214] ? show_regs+0x72/0x90 [ 33.105371] ? __warn+0xa5/0x210 [ 33.105520] ? nf_tables_chain_destroy+0x23d/0x260 [ 33.105732] ? report_bug+0x1f2/0x200 [ 33.105902] ? handle_bug+0x46/0x90 [ 33.106546] ? exc_invalid_op+0x19/0x50 [ 33.106762] ? asm_exc_invalid_op+0x1b/0x20 [ 33.106995] ? nf_tables_chain_destroy+0x23d/0x260 [ 33.107249] ? nf_tables_chain_destroy+0x30/0x260 [ 33.107506] nf_tables_trans_destroy_work+0x669/0x680 [ 33.107782] ? mark_held_locks+0x28/0xa0 [ 33.107996] ? __pfx_nf_tables_trans_destroy_work+0x10/0x10 [ 33.108294] ? _raw_spin_unlock_irq+0x28/0x70 [ 33.108538] process_one_work+0x68c/0xb70 [ 33.108755] ? lock_acquire+0x17f/0x420 [ 33.108977] ? __pfx_process_one_work+0x10/0x10 [ 33.109218] ? do_raw_spin_lock+0x128/0x1d0 [ 33.109435] ? _raw_spin_lock_irq+0x71/0x80 [ 33.109634] worker_thread+0x2bd/0x700 [ 33.109817] ? __pfx_worker_thread+0x10/0x10 [ 33.110254] kthread+0x18b/0x1d0 [ 33.110410] ? __pfx_kthread+0x10/0x10 [ 33.110581] ret_from_fork+0x29/0x50 [ 33.110757] </TASK> [ 33.110866] irq event stamp: 1651 [ 33.111017] hardirqs last enabled at (1659): [<ffffffffa206a209>] __up_console_sem+0x79/0xa0 [ 33.111379] hardirqs last disabled at (1666): [<ffffffffa206a1ee>] __up_console_sem+0x5e/0xa0 [ 33.111740] softirqs last enabled at (1616): [<ffffffffa1f5d40e>] __irq_exit_rcu+0x9e/0xe0 [ 33.112094] softirqs last disabled at (1367): [<ffffffffa1f5d40e>] __irq_exit_rcu+0x9e/0xe0 [ 33.112453] ---[ end trace 0000000000000000 ]--- This is due to the nft_chain_lookup_byid ignoring the genmask. After this change, adding the new rule will fail as it will not find the chain. CVE-2023-53492 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53492.html CVE-2023-53492 https://bugzilla.suse.com/1250823 SUSE Bug 1250823 In the Linux kernel, the following vulnerability has been resolved: accel/qaic: tighten bounds checking in decode_message() Copy the bounds checking from encode_message() to decode_message(). This patch addresses the following concerns. Ensure that there is enough space for at least one header so that we don't have a negative size later. if (msg_hdr_len < sizeof(*trans_hdr)) Ensure that we have enough space to read the next header from the msg->data. if (msg_len > msg_hdr_len - sizeof(*trans_hdr)) return -EINVAL; Check that the trans_hdr->len is not below the minimum size: if (hdr_len < sizeof(*trans_hdr)) This minimum check ensures that we don't corrupt memory in decode_passthrough() when we do. memcpy(out_trans->data, in_trans->data, len - sizeof(in_trans->hdr)); And finally, use size_add() to prevent an integer overflow: if (size_add(msg_len, hdr_len) > msg_hdr_len) CVE-2023-53493 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53493.html CVE-2023-53493 https://bugzilla.suse.com/1250820 SUSE Bug 1250820 In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mvpp2_main: fix possible OOB write in mvpp2_ethtool_get_rxnfc() rules is allocated in ethtool_get_rxnfc and the size is determined by rule_cnt from user space. So rule_cnt needs to be check before using rules to avoid OOB writing or NULL pointer dereference. CVE-2023-53495 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53495.html CVE-2023-53495 https://bugzilla.suse.com/1250907 SUSE Bug 1250907 In the Linux kernel, the following vulnerability has been resolved: x86/platform/uv: Use alternate source for socket to node data The UV code attempts to build a set of tables to allow it to do bidirectional socket<=>node lookups. But when nr_cpus is set to a smaller number than actually present, the cpu_to_node() mapping information for unused CPUs is not available to build_socket_tables(). This results in skipping some nodes or sockets when creating the tables and leaving some -1's for later code to trip. over, causing oopses. The problem is that the socket<=>node lookups are created by doing a loop over all CPUs, then looking up the CPU's APICID and socket. But if a CPU is not present, there is no way to start this lookup. Instead of looping over all CPUs, take CPUs out of the equation entirely. Loop over all APICIDs which are mapped to a valid NUMA node. Then just extract the socket-id from the APICID. This avoid tripping over disabled CPUs. CVE-2023-53496 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53496.html CVE-2023-53496 https://bugzilla.suse.com/1250905 SUSE Bug 1250905 In the Linux kernel, the following vulnerability has been resolved: xfrm: fix slab-use-after-free in decode_session6 When the xfrm device is set to the qdisc of the sfb type, the cb field of the sent skb may be modified during enqueuing. Then, slab-use-after-free may occur when the xfrm device sends IPv6 packets. The stack information is as follows: BUG: KASAN: slab-use-after-free in decode_session6+0x103f/0x1890 Read of size 1 at addr ffff8881111458ef by task swapper/3/0 CPU: 3 PID: 0 Comm: swapper/3 Not tainted 6.4.0-next-20230707 #409 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <IRQ> dump_stack_lvl+0xd9/0x150 print_address_description.constprop.0+0x2c/0x3c0 kasan_report+0x11d/0x130 decode_session6+0x103f/0x1890 __xfrm_decode_session+0x54/0xb0 xfrmi_xmit+0x173/0x1ca0 dev_hard_start_xmit+0x187/0x700 sch_direct_xmit+0x1a3/0xc30 __qdisc_run+0x510/0x17a0 __dev_queue_xmit+0x2215/0x3b10 neigh_connected_output+0x3c2/0x550 ip6_finish_output2+0x55a/0x1550 ip6_finish_output+0x6b9/0x1270 ip6_output+0x1f1/0x540 ndisc_send_skb+0xa63/0x1890 ndisc_send_rs+0x132/0x6f0 addrconf_rs_timer+0x3f1/0x870 call_timer_fn+0x1a0/0x580 expire_timers+0x29b/0x4b0 run_timer_softirq+0x326/0x910 __do_softirq+0x1d4/0x905 irq_exit_rcu+0xb7/0x120 sysvec_apic_timer_interrupt+0x97/0xc0 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1a/0x20 RIP: 0010:intel_idle_hlt+0x23/0x30 Code: 1f 84 00 00 00 00 00 f3 0f 1e fa 41 54 41 89 d4 0f 1f 44 00 00 66 90 0f 1f 44 00 00 0f 00 2d c4 9f ab 00 0f 1f 44 00 00 fb f4 <fa> 44 89 e0 41 5c c3 66 0f 1f 44 00 00 f3 0f 1e fa 41 54 41 89 d4 RSP: 0018:ffffc90000197d78 EFLAGS: 00000246 RAX: 00000000000a83c3 RBX: ffffe8ffffd09c50 RCX: ffffffff8a22d8e5 RDX: 0000000000000001 RSI: ffffffff8d3f8080 RDI: ffffe8ffffd09c50 RBP: ffffffff8d3f8080 R08: 0000000000000001 R09: ffffed1026ba6d9d R10: ffff888135d36ceb R11: 0000000000000001 R12: 0000000000000001 R13: ffffffff8d3f8100 R14: 0000000000000001 R15: 0000000000000000 cpuidle_enter_state+0xd3/0x6f0 cpuidle_enter+0x4e/0xa0 do_idle+0x2fe/0x3c0 cpu_startup_entry+0x18/0x20 start_secondary+0x200/0x290 secondary_startup_64_no_verify+0x167/0x16b </TASK> Allocated by task 939: kasan_save_stack+0x22/0x40 kasan_set_track+0x25/0x30 __kasan_slab_alloc+0x7f/0x90 kmem_cache_alloc_node+0x1cd/0x410 kmalloc_reserve+0x165/0x270 __alloc_skb+0x129/0x330 inet6_ifa_notify+0x118/0x230 __ipv6_ifa_notify+0x177/0xbe0 addrconf_dad_completed+0x133/0xe00 addrconf_dad_work+0x764/0x1390 process_one_work+0xa32/0x16f0 worker_thread+0x67d/0x10c0 kthread+0x344/0x440 ret_from_fork+0x1f/0x30 The buggy address belongs to the object at ffff888111145800 which belongs to the cache skbuff_small_head of size 640 The buggy address is located 239 bytes inside of freed 640-byte region [ffff888111145800, ffff888111145a80) As commit f855691975bb ("xfrm6: Fix the nexthdr offset in _decode_session6.") showed, xfrm_decode_session was originally intended only for the receive path. IP6CB(skb)->nhoff is not set during transmission. Therefore, set the cb field in the skb to 0 before sending packets. CVE-2023-53500 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53500.html CVE-2023-53500 https://bugzilla.suse.com/1250816 SUSE Bug 1250816 In the Linux kernel, the following vulnerability has been resolved: iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind When unbinding pasid - a race condition exists vs outstanding page faults. To prevent this, the pasid_state object contains a refcount. * set to 1 on pasid bind * incremented on each ppr notification start * decremented on each ppr notification done * decremented on pasid unbind Since refcount_dec assumes that refcount will never reach 0: the current implementation causes the following to be invoked on pasid unbind: REFCOUNT_WARN("decrement hit 0; leaking memory") Fix this issue by changing refcount_dec to refcount_dec_and_test to explicitly handle refcount=1. CVE-2023-53501 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53501.html CVE-2023-53501 https://bugzilla.suse.com/1250815 SUSE Bug 1250815 In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Properly order ib_device_unalloc() to avoid UAF ib_dealloc_device() should be called only after device cleanup. Fix the dealloc sequence. CVE-2023-53504 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53504.html CVE-2023-53504 https://bugzilla.suse.com/1250813 SUSE Bug 1250813 In the Linux kernel, the following vulnerability has been resolved: clk: tegra: tegra124-emc: Fix potential memory leak The tegra and tegra needs to be freed in the error handling path, otherwise it will be leaked. CVE-2023-53505 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53505.html CVE-2023-53505 https://bugzilla.suse.com/1250807 SUSE Bug 1250807 In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Unregister devlink params in case interface is down Currently, in case an interface is down, mlx5 driver doesn't unregister its devlink params, which leads to this WARN[1]. Fix it by unregistering devlink params in that case as well. [1] [ 295.244769 ] WARNING: CPU: 15 PID: 1 at net/core/devlink.c:9042 devlink_free+0x174/0x1fc [ 295.488379 ] CPU: 15 PID: 1 Comm: shutdown Tainted: G S OE 5.15.0-1017.19.3.g0677e61-bluefield #g0677e61 [ 295.509330 ] Hardware name: https://www.mellanox.com BlueField SoC/BlueField SoC, BIOS 4.2.0.12761 Jun 6 2023 [ 295.543096 ] pc : devlink_free+0x174/0x1fc [ 295.551104 ] lr : mlx5_devlink_free+0x18/0x2c [mlx5_core] [ 295.561816 ] sp : ffff80000809b850 [ 295.711155 ] Call trace: [ 295.716030 ] devlink_free+0x174/0x1fc [ 295.723346 ] mlx5_devlink_free+0x18/0x2c [mlx5_core] [ 295.733351 ] mlx5_sf_dev_remove+0x98/0xb0 [mlx5_core] [ 295.743534 ] auxiliary_bus_remove+0x2c/0x50 [ 295.751893 ] __device_release_driver+0x19c/0x280 [ 295.761120 ] device_release_driver+0x34/0x50 [ 295.769649 ] bus_remove_device+0xdc/0x170 [ 295.777656 ] device_del+0x17c/0x3a4 [ 295.784620 ] mlx5_sf_dev_remove+0x28/0xf0 [mlx5_core] [ 295.794800 ] mlx5_sf_dev_table_destroy+0x98/0x110 [mlx5_core] [ 295.806375 ] mlx5_unload+0x34/0xd0 [mlx5_core] [ 295.815339 ] mlx5_unload_one+0x70/0xe4 [mlx5_core] [ 295.824998 ] shutdown+0xb0/0xd8 [mlx5_core] [ 295.833439 ] pci_device_shutdown+0x3c/0xa0 [ 295.841651 ] device_shutdown+0x170/0x340 [ 295.849486 ] __do_sys_reboot+0x1f4/0x2a0 [ 295.857322 ] __arm64_sys_reboot+0x2c/0x40 [ 295.865329 ] invoke_syscall+0x78/0x100 [ 295.872817 ] el0_svc_common.constprop.0+0x54/0x184 [ 295.882392 ] do_el0_svc+0x30/0xac [ 295.889008 ] el0_svc+0x48/0x160 [ 295.895278 ] el0t_64_sync_handler+0xa4/0x130 [ 295.903807 ] el0t_64_sync+0x1a4/0x1a8 [ 295.911120 ] ---[ end trace 4f1d2381d00d9dce ]--- CVE-2023-53507 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53507.html CVE-2023-53507 https://bugzilla.suse.com/1250808 SUSE Bug 1250808 In the Linux kernel, the following vulnerability has been resolved: ublk: fail to start device if queue setup is interrupted In ublk_ctrl_start_dev(), if wait_for_completion_interruptible() is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLK_CMD_START_DEV, otherwise kernel oops can be triggered. Reported by German when working on qemu-storage-deamon which requires single thread ublk daemon. CVE-2023-53508 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53508.html CVE-2023-53508 https://bugzilla.suse.com/1250809 SUSE Bug 1250809 In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix handling of lrbp->cmd ufshcd_queuecommand() may be called two times in a row for a SCSI command before it is completed. Hence make the following changes: - In the functions that submit a command, do not check the old value of lrbp->cmd nor clear lrbp->cmd in error paths. - In ufshcd_release_scsi_cmd(), do not clear lrbp->cmd. See also scsi_send_eh_cmnd(). This commit prevents that the following appears if a command times out: WARNING: at drivers/ufs/core/ufshcd.c:2965 ufshcd_queuecommand+0x6f8/0x9a8 Call trace: ufshcd_queuecommand+0x6f8/0x9a8 scsi_send_eh_cmnd+0x2c0/0x960 scsi_eh_test_devices+0x100/0x314 scsi_eh_ready_devs+0xd90/0x114c scsi_error_handler+0x2b4/0xb70 kthread+0x16c/0x1e0 CVE-2023-53510 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53510.html CVE-2023-53510 https://bugzilla.suse.com/1250812 SUSE Bug 1250812 In the Linux kernel, the following vulnerability has been resolved: virtio-mmio: don't break lifecycle of vm_dev vm_dev has a separate lifecycle because it has a 'struct device' embedded. Thus, having a release callback for it is correct. Allocating the vm_dev struct with devres totally breaks this protection, though. Instead of waiting for the vm_dev release callback, the memory is freed when the platform_device is removed. Resulting in a use-after-free when finally the callback is to be called. To easily see the problem, compile the kernel with CONFIG_DEBUG_KOBJECT_RELEASE and unbind with sysfs. The fix is easy, don't use devres in this case. Found during my research about object lifetime problems. CVE-2023-53515 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53515.html CVE-2023-53515 https://bugzilla.suse.com/1250917 SUSE Bug 1250917 In the Linux kernel, the following vulnerability has been resolved: macvlan: add forgotten nla_policy for IFLA_MACVLAN_BC_CUTOFF The previous commit 954d1fa1ac93 ("macvlan: Add netlink attribute for broadcast cutoff") added one additional attribute named IFLA_MACVLAN_BC_CUTOFF to allow broadcast cutfoff. However, it forgot to describe the nla_policy at macvlan_policy (drivers/net/macvlan.c). Hence, this suppose NLA_S32 (4 bytes) integer can be faked as empty (0 bytes) by a malicious user, which could leads to OOB in heap just like CVE-2023-3773. To fix it, this commit just completes the nla_policy description for IFLA_MACVLAN_BC_CUTOFF. This enforces the length check and avoids the potential OOB read. CVE-2023-53516 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53516.html CVE-2023-53516 https://bugzilla.suse.com/1250918 SUSE Bug 1250918 In the Linux kernel, the following vulnerability has been resolved: PM / devfreq: Fix leak in devfreq_dev_release() srcu_init_notifier_head() allocates resources that need to be released with a srcu_cleanup_notifier_head() call. Reported by kmemleak. CVE-2023-53518 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53518.html CVE-2023-53518 https://bugzilla.suse.com/1250923 SUSE Bug 1250923 In the Linux kernel, the following vulnerability has been resolved: media: v4l2-mem2mem: add lock to protect parameter num_rdy Getting below error when using KCSAN to check the driver. Adding lock to protect parameter num_rdy when getting the value with function: v4l2_m2m_num_src_bufs_ready/v4l2_m2m_num_dst_bufs_ready. kworker/u16:3: [name:report&]BUG: KCSAN: data-race in v4l2_m2m_buf_queue kworker/u16:3: [name:report&] kworker/u16:3: [name:report&]read-write to 0xffffff8105f35b94 of 1 bytes by task 20865 on cpu 7: kworker/u16:3: v4l2_m2m_buf_queue+0xd8/0x10c CVE-2023-53519 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53519.html CVE-2023-53519 https://bugzilla.suse.com/1250964 SUSE Bug 1250964 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix hci_suspend_sync crash If hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier may still be accessing it, it can cause the program to crash. Here's the call trace: <4>[102152.653246] Call Trace: <4>[102152.653254] hci_suspend_sync+0x109/0x301 [bluetooth] <4>[102152.653259] hci_suspend_dev+0x78/0xcd [bluetooth] <4>[102152.653263] hci_suspend_notifier+0x42/0x7a [bluetooth] <4>[102152.653268] notifier_call_chain+0x43/0x6b <4>[102152.653271] __blocking_notifier_call_chain+0x48/0x69 <4>[102152.653273] __pm_notifier_call_chain+0x22/0x39 <4>[102152.653276] pm_suspend+0x287/0x57c <4>[102152.653278] state_store+0xae/0xe5 <4>[102152.653281] kernfs_fop_write+0x109/0x173 <4>[102152.653284] __vfs_write+0x16f/0x1a2 <4>[102152.653287] ? selinux_file_permission+0xca/0x16f <4>[102152.653289] ? security_file_permission+0x36/0x109 <4>[102152.653291] vfs_write+0x114/0x21d <4>[102152.653293] __x64_sys_write+0x7b/0xdb <4>[102152.653296] do_syscall_64+0x59/0x194 <4>[102152.653299] entry_SYSCALL_64_after_hwframe+0x5c/0xc1 This patch holds the reference count of the hci_dev object while processing it in hci_suspend_notifier to avoid potential crash caused by the race condition. CVE-2023-53520 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53520.html CVE-2023-53520 https://bugzilla.suse.com/1250957 SUSE Bug 1250957 https://bugzilla.suse.com/1250958 SUSE Bug 1250958 In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: fix time stamp counter initialization If the gs_usb device driver is unloaded (or unbound) before the interface is shut down, the USB stack first calls the struct usb_driver::disconnect and then the struct net_device_ops::ndo_stop callback. In gs_usb_disconnect() all pending bulk URBs are killed, i.e. no more RX'ed CAN frames are send from the USB device to the host. Later in gs_can_close() a reset control message is send to each CAN channel to remove the controller from the CAN bus. In this race window the USB device can still receive CAN frames from the bus and internally queue them to be send to the host. At least in the current version of the candlelight firmware, the queue of received CAN frames is not emptied during the reset command. After loading (or binding) the gs_usb driver, new URBs are submitted during the struct net_device_ops::ndo_open callback and the candlelight firmware starts sending its already queued CAN frames to the host. However, this scenario was not considered when implementing the hardware timestamp function. The cycle counter/time counter infrastructure is set up (gs_usb_timestamp_init()) after the USBs are submitted, resulting in a NULL pointer dereference if timecounter_cyc2time() (via the call chain: gs_usb_receive_bulk_callback() -> gs_usb_set_timestamp() -> gs_usb_skb_set_timestamp()) is called too early. Move the gs_usb_timestamp_init() function before the URBs are submitted to fix this problem. For a comprehensive solution, we need to consider gs_usb devices with more than 1 channel. The cycle counter/time counter infrastructure is setup per channel, but the RX URBs are per device. Once gs_can_open() of _a_ channel has been called, and URBs have been submitted, the gs_usb_receive_bulk_callback() can be called for _all_ available channels, even for channels that are not running, yet. As cycle counter/time counter has not set up, this will again lead to a NULL pointer dereference. Convert the cycle counter/time counter from a "per channel" to a "per device" functionality. Also set it up, before submitting any URBs to the device. Further in gs_usb_receive_bulk_callback(), don't process any URBs for not started CAN channels, only resubmit the URB. CVE-2023-53523 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53523.html CVE-2023-53523 https://bugzilla.suse.com/1250926 SUSE Bug 1250926 In the Linux kernel, the following vulnerability has been resolved: jbd2: check 'jh->b_transaction' before removing it from checkpoint Following process will corrupt ext4 image: Step 1: jbd2_journal_commit_transaction __jbd2_journal_insert_checkpoint(jh, commit_transaction) // Put jh into trans1->t_checkpoint_list journal->j_checkpoint_transactions = commit_transaction // Put trans1 into journal->j_checkpoint_transactions Step 2: do_get_write_access test_clear_buffer_dirty(bh) // clear buffer dirty，set jbd dirty __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2 Step 3: drop_cache journal_shrink_one_cp_list jbd2_journal_try_remove_checkpoint if (!trylock_buffer(bh)) // lock bh, true if (buffer_dirty(bh)) // buffer is not dirty __jbd2_journal_remove_checkpoint(jh) // remove jh from trans1->t_checkpoint_list Step 4: jbd2_log_do_checkpoint trans1 = journal->j_checkpoint_transactions // jh is not in trans1->t_checkpoint_list jbd2_cleanup_journal_tail(journal) // trans1 is done Step 5: Power cut, trans2 is not committed, jh is lost in next mounting. Fix it by checking 'jh->b_transaction' before remove it from checkpoint. CVE-2023-53526 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53526.html CVE-2023-53526 https://bugzilla.suse.com/1250928 SUSE Bug 1250928 In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Fix memory leak in tb_handle_dp_bandwidth_request() The memory allocated in tb_queue_dp_bandwidth_request() needs to be released once the request is handled to avoid leaking it. CVE-2023-53527 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53527.html CVE-2023-53527 https://bugzilla.suse.com/1250929 SUSE Bug 1250929 In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix unsafe drain work queue code If create_qp does not fully succeed it is possible for qp cleanup code to attempt to drain the send or recv work queues before the queues have been created causing a seg fault. This patch checks to see if the queues exist before attempting to drain them. CVE-2023-53528 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53528.html CVE-2023-53528 https://bugzilla.suse.com/1250930 SUSE Bug 1250930 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id() The following call trace was observed: localhost kernel: nvme nvme0: NVME-FC{0}: controller connect complete localhost kernel: BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u129:4/75092 localhost kernel: nvme nvme0: NVME-FC{0}: new ctrl: NQN "nqn.1992-08.com.netapp:sn.b42d198afb4d11ecad6d00a098d6abfa:subsystem.PR_Channel2022_RH84_subsystem_291" localhost kernel: caller is qla_nvme_post_cmd+0x216/0x1380 [qla2xxx] localhost kernel: CPU: 6 PID: 75092 Comm: kworker/u129:4 Kdump: loaded Tainted: G B W OE --------- --- 5.14.0-70.22.1.el9_0.x86_64+debug #1 localhost kernel: Hardware name: HPE ProLiant XL420 Gen10/ProLiant XL420 Gen10, BIOS U39 01/13/2022 localhost kernel: Workqueue: nvme-wq nvme_async_event_work [nvme_core] localhost kernel: Call Trace: localhost kernel: dump_stack_lvl+0x57/0x7d localhost kernel: check_preemption_disabled+0xc8/0xd0 localhost kernel: qla_nvme_post_cmd+0x216/0x1380 [qla2xxx] Use raw_smp_processor_id() instead of smp_processor_id(). Also use queue_work() across the driver instead of queue_work_on() thus avoiding usage of smp_processor_id() when CONFIG_DEBUG_PREEMPT is enabled. CVE-2023-53530 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53530.html CVE-2023-53530 https://bugzilla.suse.com/1250949 SUSE Bug 1250949 In the Linux kernel, the following vulnerability has been resolved: null_blk: fix poll request timeout handling When doing io_uring benchmark on /dev/nullb0, it's easy to crash the kernel if poll requests timeout triggered, as reported by David. [1] BUG: kernel NULL pointer dereference, address: 0000000000000008 Workqueue: kblockd blk_mq_timeout_work RIP: 0010:null_timeout_rq+0x4e/0x91 Call Trace: ? null_timeout_rq+0x4e/0x91 blk_mq_handle_expired+0x31/0x4b bt_iter+0x68/0x84 ? bt_tags_iter+0x81/0x81 __sbitmap_for_each_set.constprop.0+0xb0/0xf2 ? __blk_mq_complete_request_remote+0xf/0xf bt_for_each+0x46/0x64 ? __blk_mq_complete_request_remote+0xf/0xf ? percpu_ref_get_many+0xc/0x2a blk_mq_queue_tag_busy_iter+0x14d/0x18e blk_mq_timeout_work+0x95/0x127 process_one_work+0x185/0x263 worker_thread+0x1b5/0x227 This is indeed a race problem between null_timeout_rq() and null_poll(). null_poll() null_timeout_rq() spin_lock(&nq->poll_lock) list_splice_init(&nq->poll_list, &list) spin_unlock(&nq->poll_lock) while (!list_empty(&list)) req = list_first_entry() list_del_init() ... blk_mq_add_to_batch() // req->rq_next = NULL spin_lock(&nq->poll_lock) // rq->queuelist->next == NULL list_del_init(&rq->queuelist) spin_unlock(&nq->poll_lock) Fix these problems by setting requests state to MQ_RQ_COMPLETE under nq->poll_lock protection, in which null_timeout_rq() can safely detect this race and early return. Note this patch just fix the kernel panic when request timeout happen. [1] https://lore.kernel.org/all/3893581.1691785261@warthog.procyon.org.uk/ CVE-2023-53531 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53531.html CVE-2023-53531 https://bugzilla.suse.com/1250931 SUSE Bug 1250931 In the Linux kernel, the following vulnerability has been resolved: btrfs: insert tree mod log move in push_node_left There is a fairly unlikely race condition in tree mod log rewind that can result in a kernel panic which has the following trace: [530.569] BTRFS critical (device sda3): unable to find logical 0 length 4096 [530.585] BTRFS critical (device sda3): unable to find logical 0 length 4096 [530.602] BUG: kernel NULL pointer dereference, address: 0000000000000002 [530.618] #PF: supervisor read access in kernel mode [530.629] #PF: error_code(0x0000) - not-present page [530.641] PGD 0 P4D 0 [530.647] Oops: 0000 [#1] SMP [530.654] CPU: 30 PID: 398973 Comm: below Kdump: loaded Tainted: G S O K 5.12.0-0_fbk13_clang_7455_gb24de3bdb045 #1 [530.680] Hardware name: Quanta Mono Lake-M.2 SATA 1HY9U9Z001G/Mono Lake-M.2 SATA, BIOS F20_3A15 08/16/2017 [530.703] RIP: 0010:__btrfs_map_block+0xaa/0xd00 [530.755] RSP: 0018:ffffc9002c2f7600 EFLAGS: 00010246 [530.767] RAX: ffffffffffffffea RBX: ffff888292e41000 RCX: f2702d8b8be15100 [530.784] RDX: ffff88885fda6fb8 RSI: ffff88885fd973c8 RDI: ffff88885fd973c8 [530.800] RBP: ffff888292e410d0 R08: ffffffff82fd7fd0 R09: 00000000fffeffff [530.816] R10: ffffffff82e57fd0 R11: ffffffff82e57d70 R12: 0000000000000000 [530.832] R13: 0000000000001000 R14: 0000000000001000 R15: ffffc9002c2f76f0 [530.848] FS: 00007f38d64af000(0000) GS:ffff88885fd80000(0000) knlGS:0000000000000000 [530.866] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [530.880] CR2: 0000000000000002 CR3: 00000002b6770004 CR4: 00000000003706e0 [530.896] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [530.912] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [530.928] Call Trace: [530.934] ? btrfs_printk+0x13b/0x18c [530.943] ? btrfs_bio_counter_inc_blocked+0x3d/0x130 [530.955] btrfs_map_bio+0x75/0x330 [530.963] ? kmem_cache_alloc+0x12a/0x2d0 [530.973] ? btrfs_submit_metadata_bio+0x63/0x100 [530.984] btrfs_submit_metadata_bio+0xa4/0x100 [530.995] submit_extent_page+0x30f/0x360 [531.004] read_extent_buffer_pages+0x49e/0x6d0 [531.015] ? submit_extent_page+0x360/0x360 [531.025] btree_read_extent_buffer_pages+0x5f/0x150 [531.037] read_tree_block+0x37/0x60 [531.046] read_block_for_search+0x18b/0x410 [531.056] btrfs_search_old_slot+0x198/0x2f0 [531.066] resolve_indirect_ref+0xfe/0x6f0 [531.076] ? ulist_alloc+0x31/0x60 [531.084] ? kmem_cache_alloc_trace+0x12e/0x2b0 [531.095] find_parent_nodes+0x720/0x1830 [531.105] ? ulist_alloc+0x10/0x60 [531.113] iterate_extent_inodes+0xea/0x370 [531.123] ? btrfs_previous_extent_item+0x8f/0x110 [531.134] ? btrfs_search_path_in_tree+0x240/0x240 [531.146] iterate_inodes_from_logical+0x98/0xd0 [531.157] ? btrfs_search_path_in_tree+0x240/0x240 [531.168] btrfs_ioctl_logical_to_ino+0xd9/0x180 [531.179] btrfs_ioctl+0xe2/0x2eb0 This occurs when logical inode resolution takes a tree mod log sequence number, and then while backref walking hits a rewind on a busy node which has the following sequence of tree mod log operations (numbers filled in from a specific example, but they are somewhat arbitrary) REMOVE_WHILE_FREEING slot 532 REMOVE_WHILE_FREEING slot 531 REMOVE_WHILE_FREEING slot 530 ... REMOVE_WHILE_FREEING slot 0 REMOVE slot 455 REMOVE slot 454 REMOVE slot 453 ... REMOVE slot 0 ADD slot 455 ADD slot 454 ADD slot 453 ... ADD slot 0 MOVE src slot 0 -> dst slot 456 nritems 533 REMOVE slot 455 REMOVE slot 454 REMOVE slot 453 ... REMOVE slot 0 When this sequence gets applied via btrfs_tree_mod_log_rewind, it allocates a fresh rewind eb, and first inserts the correct key info for the 533 elements, then overwrites the first 456 of them, then decrements the count by 456 via the add ops, then rewinds the move by doing a memmove from 456:988->0:532. We have never written anything past 532, ---truncated--- CVE-2023-53538 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53538.html CVE-2023-53538 https://bugzilla.suse.com/1251024 SUSE Bug 1251024 In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix incomplete state save in rxe_requester If a send packet is dropped by the IP layer in rxe_requester() the call to rxe_xmit_packet() can fail with err == -EAGAIN. To recover, the state of the wqe is restored to the state before the packet was sent so it can be resent. However, the routines that save and restore the state miss a significnt part of the variable state in the wqe, the dma struct which is used to process through the sge table. And, the state is not saved before the packet is built which modifies the dma struct. Under heavy stress testing with many QPs on a fast node sending large messages to a slow node dropped packets are observed and the resent packets are corrupted because the dma struct was not restored. This patch fixes this behavior and allows the test cases to succeed. CVE-2023-53539 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53539.html CVE-2023-53539 https://bugzilla.suse.com/1251060 SUSE Bug 1251060 In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: reject auth/assoc to AP with our address If the AP uses our own address as its MLD address or BSSID, then clearly something's wrong. Reject such connections so we don't try and fail later. CVE-2023-53540 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53540.html CVE-2023-53540 https://bugzilla.suse.com/1251053 SUSE Bug 1251053 In the Linux kernel, the following vulnerability has been resolved: mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write When the oob buffer length is not in multiple of words, the oob write function does out-of-bounds read on the oob source buffer at the last iteration. Fix that by always checking length limit on the oob buffer read and fill with 0xff when reaching the end of the buffer to the oob registers. CVE-2023-53541 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53541.html CVE-2023-53541 https://bugzilla.suse.com/1251043 SUSE Bug 1251043 In the Linux kernel, the following vulnerability has been resolved: vdpa: Add max vqp attr to vdpa_nl_policy for nlattr length check The vdpa_nl_policy structure is used to validate the nlattr when parsing the incoming nlmsg. It will ensure the attribute being described produces a valid nlattr pointer in info->attrs before entering into each handler in vdpa_nl_ops. That is to say, the missing part in vdpa_nl_policy may lead to illegal nlattr after parsing, which could lead to OOB read just like CVE-2023-3773. This patch adds the missing nla_policy for vdpa max vqp attr to avoid such bugs. CVE-2023-53543 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53543.html CVE-2023-53543 https://bugzilla.suse.com/1251083 SUSE Bug 1251083 In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: unmap and remove csa_va properly Root PD BO should be reserved before unmap and remove a bo_va from VM otherwise lockdep will complain. v2: check fpriv->csa_va is not NULL instead of amdgpu_mcbp (christian) [14616.936827] WARNING: CPU: 6 PID: 1711 at drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:1762 amdgpu_vm_bo_del+0x399/0x3f0 [amdgpu] [14616.937096] Call Trace: [14616.937097] <TASK> [14616.937102] amdgpu_driver_postclose_kms+0x249/0x2f0 [amdgpu] [14616.937187] drm_file_free+0x1d6/0x300 [drm] [14616.937207] drm_close_helper.isra.0+0x62/0x70 [drm] [14616.937220] drm_release+0x5e/0x100 [drm] [14616.937234] __fput+0x9f/0x280 [14616.937239] ____fput+0xe/0x20 [14616.937241] task_work_run+0x61/0x90 [14616.937246] exit_to_user_mode_prepare+0x215/0x220 [14616.937251] syscall_exit_to_user_mode+0x2a/0x60 [14616.937254] do_syscall_64+0x48/0x90 [14616.937257] entry_SYSCALL_64_after_hwframe+0x63/0xcd CVE-2023-53545 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53545.html CVE-2023-53545 https://bugzilla.suse.com/1251084 SUSE Bug 1251084 In the Linux kernel, the following vulnerability has been resolved: net/mlx5: DR, fix memory leak in mlx5dr_cmd_create_reformat_ctx when mlx5_cmd_exec failed in mlx5dr_cmd_create_reformat_ctx, the memory pointed by 'in' is not released, which will cause memory leak. Move memory release after mlx5_cmd_exec. CVE-2023-53546 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53546.html CVE-2023-53546 https://bugzilla.suse.com/1251079 SUSE Bug 1251079 In the Linux kernel, the following vulnerability has been resolved: net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb The syzbot fuzzer identified a problem in the usbnet driver: usb 1-1: BOGUS urb xfer, pipe 3 != type 1 WARNING: CPU: 0 PID: 754 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 Modules linked in: CPU: 0 PID: 754 Comm: kworker/0:2 Not tainted 6.4.0-rc7-syzkaller-00014-g692b7dc87ca6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Workqueue: mld mld_ifc_work RIP: 0010:usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 Code: 7c 24 18 e8 2c b4 5b fb 48 8b 7c 24 18 e8 42 07 f0 fe 41 89 d8 44 89 e1 4c 89 ea 48 89 c6 48 c7 c7 a0 c9 fc 8a e8 5a 6f 23 fb <0f> 0b e9 58 f8 ff ff e8 fe b3 5b fb 48 81 c5 c0 05 00 00 e9 84 f7 RSP: 0018:ffffc9000463f568 EFLAGS: 00010086 RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000 RDX: ffff88801eb28000 RSI: ffffffff814c03b7 RDI: 0000000000000001 RBP: ffff8881443b7190 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000003 R13: ffff88802a77cb18 R14: 0000000000000003 R15: ffff888018262500 FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000556a99c15a18 CR3: 0000000028c71000 CR4: 0000000000350ef0 Call Trace: <TASK> usbnet_start_xmit+0xfe5/0x2190 drivers/net/usb/usbnet.c:1453 __netdev_start_xmit include/linux/netdevice.h:4918 [inline] netdev_start_xmit include/linux/netdevice.h:4932 [inline] xmit_one net/core/dev.c:3578 [inline] dev_hard_start_xmit+0x187/0x700 net/core/dev.c:3594 ... This bug is caused by the fact that usbnet trusts the bulk endpoint addresses its probe routine receives in the driver_info structure, and it does not check to see that these endpoints actually exist and have the expected type and directions. The fix is simply to add such a check. CVE-2023-53548 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53548.html CVE-2023-53548 https://bugzilla.suse.com/1251066 SUSE Bug 1251066 In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: fix global sysfs attribute type In commit 3666062b87ec ("cpufreq: amd-pstate: move to use bus_get_dev_root()") the "amd_pstate" attributes where moved from a dedicated kobject to the cpu root kobject. While the dedicated kobject expects to contain kobj_attributes the root kobject needs device_attributes. As the changed arguments are not used by the callbacks it works most of the time. However CFI will detect this issue: [ 4947.849350] CFI failure at dev_attr_show+0x24/0x60 (target: show_status+0x0/0x70; expected type: 0x8651b1de) ... [ 4947.849409] Call Trace: [ 4947.849410] <TASK> [ 4947.849411] ? __warn+0xcf/0x1c0 [ 4947.849414] ? dev_attr_show+0x24/0x60 [ 4947.849415] ? report_cfi_failure+0x4e/0x60 [ 4947.849417] ? handle_cfi_failure+0x14c/0x1d0 [ 4947.849419] ? __cfi_show_status+0x10/0x10 [ 4947.849420] ? handle_bug+0x4f/0x90 [ 4947.849421] ? exc_invalid_op+0x1a/0x60 [ 4947.849422] ? asm_exc_invalid_op+0x1a/0x20 [ 4947.849424] ? __cfi_show_status+0x10/0x10 [ 4947.849425] ? dev_attr_show+0x24/0x60 [ 4947.849426] sysfs_kf_seq_show+0xa6/0x110 [ 4947.849433] seq_read_iter+0x16c/0x4b0 [ 4947.849436] vfs_read+0x272/0x2d0 [ 4947.849438] ksys_read+0x72/0xe0 [ 4947.849439] do_syscall_64+0x76/0xb0 [ 4947.849440] ? do_user_addr_fault+0x252/0x650 [ 4947.849442] ? exc_page_fault+0x7a/0x1b0 [ 4947.849443] entry_SYSCALL_64_after_hwframe+0x72/0xdc CVE-2023-53550 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53550.html CVE-2023-53550 https://bugzilla.suse.com/1251071 SUSE Bug 1251071 In the Linux kernel, the following vulnerability has been resolved: drm/i915: mark requests for GuC virtual engines to avoid use-after-free References to i915_requests may be trapped by userspace inside a sync_file or dmabuf (dma-resv) and held indefinitely across different proceses. To counter-act the memory leaks, we try to not to keep references from the request past their completion. On the other side on fence release we need to know if rq->engine is valid and points to hw engine (true for non-virtual requests). To make it possible extra bit has been added to rq->execution_mask, for marking virtual engines. (cherry picked from commit 280410677af763f3871b93e794a199cfcf6fb580) CVE-2023-53552 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53552.html CVE-2023-53552 https://bugzilla.suse.com/1251065 SUSE Bug 1251065 In the Linux kernel, the following vulnerability has been resolved: HID: hyperv: avoid struct memcpy overrun warning A previous patch addressed the fortified memcpy warning for most builds, but I still see this one with gcc-9: In file included from include/linux/string.h:254, from drivers/hid/hid-hyperv.c:8: In function 'fortify_memcpy_chk', inlined from 'mousevsc_on_receive' at drivers/hid/hid-hyperv.c:272:3: include/linux/fortify-string.h:583:4: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning] 583 | __write_overflow_field(p_size_field, size); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ My guess is that the WARN_ON() itself is what confuses gcc, so it no longer sees that there is a correct range check. Rework the code in a way that helps readability and avoids the warning. CVE-2023-53553 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53553.html CVE-2023-53553 https://bugzilla.suse.com/1251068 SUSE Bug 1251068 In the Linux kernel, the following vulnerability has been resolved: staging: ks7010: potential buffer overflow in ks_wlan_set_encode_ext() The "exc->key_len" is a u16 that comes from the user. If it's over IW_ENCODING_TOKEN_MAX (64) that could lead to memory corruption. CVE-2023-53554 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53554.html CVE-2023-53554 https://bugzilla.suse.com/1251057 SUSE Bug 1251057 In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: initialize damo_filter->list from damos_new_filter() damos_new_filter() is not initializing the list field of newly allocated filter object. However, DAMON sysfs interface and DAMON_RECLAIM are not initializing it after calling damos_new_filter(). As a result, accessing uninitialized memory is possible. Actually, adding multiple DAMOS filters via DAMON sysfs interface caused NULL pointer dereferencing. Initialize the field just after the allocation from damos_new_filter(). CVE-2023-53555 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53555.html CVE-2023-53555 https://bugzilla.suse.com/1251056 SUSE Bug 1251056 In the Linux kernel, the following vulnerability has been resolved: iavf: Fix use-after-free in free_netdev We do netif_napi_add() for all allocated q_vectors[], but potentially do netif_napi_del() for part of them, then kfree q_vectors and leave invalid pointers at dev->napi_list. Reproducer: [root@host ~]# cat repro.sh #!/bin/bash pf_dbsf="0000:41:00.0" vf0_dbsf="0000:41:02.0" g_pids=() function do_set_numvf() { echo 2 >/sys/bus/pci/devices/${pf_dbsf}/sriov_numvfs sleep $((RANDOM%3+1)) echo 0 >/sys/bus/pci/devices/${pf_dbsf}/sriov_numvfs sleep $((RANDOM%3+1)) } function do_set_channel() { local nic=$(ls -1 --indicator-style=none /sys/bus/pci/devices/${vf0_dbsf}/net/) [ -z "$nic" ] && { sleep $((RANDOM%3)) ; return 1; } ifconfig $nic 192.168.18.5 netmask 255.255.255.0 ifconfig $nic up ethtool -L $nic combined 1 ethtool -L $nic combined 4 sleep $((RANDOM%3)) } function on_exit() { local pid for pid in "${g_pids[@]}"; do kill -0 "$pid" &>/dev/null && kill "$pid" &>/dev/null done g_pids=() } trap "on_exit; exit" EXIT while :; do do_set_numvf ; done & g_pids+=($!) while :; do do_set_channel ; done & g_pids+=($!) wait Result: [ 4093.900222] ================================================================== [ 4093.900230] BUG: KASAN: use-after-free in free_netdev+0x308/0x390 [ 4093.900232] Read of size 8 at addr ffff88b4dc145640 by task repro.sh/6699 [ 4093.900233] [ 4093.900236] CPU: 10 PID: 6699 Comm: repro.sh Kdump: loaded Tainted: G O --------- -t - 4.18.0 #1 [ 4093.900238] Hardware name: Powerleader PR2008AL/H12DSi-N6, BIOS 2.0 04/09/2021 [ 4093.900239] Call Trace: [ 4093.900244] dump_stack+0x71/0xab [ 4093.900249] print_address_description+0x6b/0x290 [ 4093.900251] ? free_netdev+0x308/0x390 [ 4093.900252] kasan_report+0x14a/0x2b0 [ 4093.900254] free_netdev+0x308/0x390 [ 4093.900261] iavf_remove+0x825/0xd20 [iavf] [ 4093.900265] pci_device_remove+0xa8/0x1f0 [ 4093.900268] device_release_driver_internal+0x1c6/0x460 [ 4093.900271] pci_stop_bus_device+0x101/0x150 [ 4093.900273] pci_stop_and_remove_bus_device+0xe/0x20 [ 4093.900275] pci_iov_remove_virtfn+0x187/0x420 [ 4093.900277] ? pci_iov_add_virtfn+0xe10/0xe10 [ 4093.900278] ? pci_get_subsys+0x90/0x90 [ 4093.900280] sriov_disable+0xed/0x3e0 [ 4093.900282] ? bus_find_device+0x12d/0x1a0 [ 4093.900290] i40e_free_vfs+0x754/0x1210 [i40e] [ 4093.900298] ? i40e_reset_all_vfs+0x880/0x880 [i40e] [ 4093.900299] ? pci_get_device+0x7c/0x90 [ 4093.900300] ? pci_get_subsys+0x90/0x90 [ 4093.900306] ? pci_vfs_assigned.part.7+0x144/0x210 [ 4093.900309] ? __mutex_lock_slowpath+0x10/0x10 [ 4093.900315] i40e_pci_sriov_configure+0x1fa/0x2e0 [i40e] [ 4093.900318] sriov_numvfs_store+0x214/0x290 [ 4093.900320] ? sriov_totalvfs_show+0x30/0x30 [ 4093.900321] ? __mutex_lock_slowpath+0x10/0x10 [ 4093.900323] ? __check_object_size+0x15a/0x350 [ 4093.900326] kernfs_fop_write+0x280/0x3f0 [ 4093.900329] vfs_write+0x145/0x440 [ 4093.900330] ksys_write+0xab/0x160 [ 4093.900332] ? __ia32_sys_read+0xb0/0xb0 [ 4093.900334] ? fput_many+0x1a/0x120 [ 4093.900335] ? filp_close+0xf0/0x130 [ 4093.900338] do_syscall_64+0xa0/0x370 [ 4093.900339] ? page_fault+0x8/0x30 [ 4093.900341] entry_SYSCALL_64_after_hwframe+0x65/0xca [ 4093.900357] RIP: 0033:0x7f16ad4d22c0 [ 4093.900359] Code: 73 01 c3 48 8b 0d d8 cb 2c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d 89 24 2d 00 00 75 10 b8 01 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 fe dd 01 00 48 89 04 24 [ 4093.900360] RSP: 002b:00007ffd6491b7f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 4093.900362] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f16ad4d22c0 [ 4093.900363] RDX: 0000000000000002 RSI: 0000000001a41408 RDI: 0000000000000001 [ 4093.900364] RBP: 0000000001a41408 R08: 00007f16ad7a1780 R09: 00007f16ae1f2700 [ 4093.9003 ---truncated--- CVE-2023-53556 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53556.html CVE-2023-53556 https://bugzilla.suse.com/1251059 SUSE Bug 1251059 In the Linux kernel, the following vulnerability has been resolved: fprobe: Release rethook after the ftrace_ops is unregistered While running bpf selftests it's possible to get following fault: general protection fault, probably for non-canonical address \ 0x6b6b6b6b6b6b6b6b: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC NOPTI ... Call Trace: <TASK> fprobe_handler+0xc1/0x270 ? __pfx_bpf_testmod_init+0x10/0x10 ? __pfx_bpf_testmod_init+0x10/0x10 ? bpf_fentry_test1+0x5/0x10 ? bpf_fentry_test1+0x5/0x10 ? bpf_testmod_init+0x22/0x80 ? do_one_initcall+0x63/0x2e0 ? rcu_is_watching+0xd/0x40 ? kmalloc_trace+0xaf/0xc0 ? do_init_module+0x60/0x250 ? __do_sys_finit_module+0xac/0x120 ? do_syscall_64+0x37/0x90 ? entry_SYSCALL_64_after_hwframe+0x72/0xdc </TASK> In unregister_fprobe function we can't release fp->rethook while it's possible there are some of its users still running on another cpu. Moving rethook_free call after fp->ops is unregistered with unregister_ftrace_function call. CVE-2023-53557 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53557.html CVE-2023-53557 https://bugzilla.suse.com/1251054 SUSE Bug 1251054 In the Linux kernel, the following vulnerability has been resolved: rcu-tasks: Avoid pr_info() with spin lock in cblist_init_generic() pr_info() is called with rtp->cbs_gbl_lock spin lock locked. Because pr_info() calls printk() that might sleep, this will result in BUG like below: [ 0.206455] cblist_init_generic: Setting adjustable number of callback queues. [ 0.206463] [ 0.206464] ============================= [ 0.206464] [ BUG: Invalid wait context ] [ 0.206465] 5.19.0-00428-g9de1f9c8ca51 #5 Not tainted [ 0.206466] ----------------------------- [ 0.206466] swapper/0/1 is trying to lock: [ 0.206467] ffffffffa0167a58 (&port_lock_key){....}-{3:3}, at: serial8250_console_write+0x327/0x4a0 [ 0.206473] other info that might help us debug this: [ 0.206473] context-{5:5} [ 0.206474] 3 locks held by swapper/0/1: [ 0.206474] #0: ffffffff9eb597e0 (rcu_tasks.cbs_gbl_lock){....}-{2:2}, at: cblist_init_generic.constprop.0+0x14/0x1f0 [ 0.206478] #1: ffffffff9eb579c0 (console_lock){+.+.}-{0:0}, at: _printk+0x63/0x7e [ 0.206482] #2: ffffffff9ea77780 (console_owner){....}-{0:0}, at: console_emit_next_record.constprop.0+0x111/0x330 [ 0.206485] stack backtrace: [ 0.206486] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.19.0-00428-g9de1f9c8ca51 #5 [ 0.206488] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-1.fc36 04/01/2014 [ 0.206489] Call Trace: [ 0.206490] <TASK> [ 0.206491] dump_stack_lvl+0x6a/0x9f [ 0.206493] __lock_acquire.cold+0x2d7/0x2fe [ 0.206496] ? stack_trace_save+0x46/0x70 [ 0.206497] lock_acquire+0xd1/0x2f0 [ 0.206499] ? serial8250_console_write+0x327/0x4a0 [ 0.206500] ? __lock_acquire+0x5c7/0x2720 [ 0.206502] _raw_spin_lock_irqsave+0x3d/0x90 [ 0.206504] ? serial8250_console_write+0x327/0x4a0 [ 0.206506] serial8250_console_write+0x327/0x4a0 [ 0.206508] console_emit_next_record.constprop.0+0x180/0x330 [ 0.206511] console_unlock+0xf7/0x1f0 [ 0.206512] vprintk_emit+0xf7/0x330 [ 0.206514] _printk+0x63/0x7e [ 0.206516] cblist_init_generic.constprop.0.cold+0x24/0x32 [ 0.206518] rcu_init_tasks_generic+0x5/0xd9 [ 0.206522] kernel_init_freeable+0x15b/0x2a2 [ 0.206523] ? rest_init+0x160/0x160 [ 0.206526] kernel_init+0x11/0x120 [ 0.206527] ret_from_fork+0x1f/0x30 [ 0.206530] </TASK> [ 0.207018] cblist_init_generic: Setting shift to 1 and lim to 1. This patch moves pr_info() so that it is called without rtp->cbs_gbl_lock locked. CVE-2023-53558 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53558.html CVE-2023-53558 https://bugzilla.suse.com/1251081 SUSE Bug 1251081 In the Linux kernel, the following vulnerability has been resolved: ip_vti: fix potential slab-use-after-free in decode_session6 When ip_vti device is set to the qdisc of the sfb type, the cb field of the sent skb may be modified during enqueuing. Then, slab-use-after-free may occur when ip_vti device sends IPv6 packets. As commit f855691975bb ("xfrm6: Fix the nexthdr offset in _decode_session6.") showed, xfrm_decode_session was originally intended only for the receive path. IP6CB(skb)->nhoff is not set during transmission. Therefore, set the cb field in the skb to 0 before sending packets. CVE-2023-53559 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53559.html CVE-2023-53559 https://bugzilla.suse.com/1251052 SUSE Bug 1251052 In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Add histograms to hist_vars if they have referenced variables Hist triggers can have referenced variables without having direct variables fields. This can be the case if referenced variables are added for trigger actions. In this case the newly added references will not have field variables. Not taking such referenced variables into consideration can result in a bug where it would be possible to remove hist trigger with variables being refenced. This will result in a bug that is easily reproducable like so $ cd /sys/kernel/tracing $ echo 'synthetic_sys_enter char[] comm; long id' >> synthetic_events $ echo 'hist:keys=common_pid.execname,id.syscall:vals=hitcount:comm=common_pid.execname' >> events/raw_syscalls/sys_enter/trigger $ echo 'hist:keys=common_pid.execname,id.syscall:onmatch(raw_syscalls.sys_enter).synthetic_sys_enter($comm, id)' >> events/raw_syscalls/sys_enter/trigger $ echo '!hist:keys=common_pid.execname,id.syscall:vals=hitcount:comm=common_pid.execname' >> events/raw_syscalls/sys_enter/trigger [ 100.263533] ================================================================== [ 100.264634] BUG: KASAN: slab-use-after-free in resolve_var_refs+0xc7/0x180 [ 100.265520] Read of size 8 at addr ffff88810375d0f0 by task bash/439 [ 100.266320] [ 100.266533] CPU: 2 PID: 439 Comm: bash Not tainted 6.5.0-rc1 #4 [ 100.267277] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-20220807_005459-localhost 04/01/2014 [ 100.268561] Call Trace: [ 100.268902] <TASK> [ 100.269189] dump_stack_lvl+0x4c/0x70 [ 100.269680] print_report+0xc5/0x600 [ 100.270165] ? resolve_var_refs+0xc7/0x180 [ 100.270697] ? kasan_complete_mode_report_info+0x80/0x1f0 [ 100.271389] ? resolve_var_refs+0xc7/0x180 [ 100.271913] kasan_report+0xbd/0x100 [ 100.272380] ? resolve_var_refs+0xc7/0x180 [ 100.272920] __asan_load8+0x71/0xa0 [ 100.273377] resolve_var_refs+0xc7/0x180 [ 100.273888] event_hist_trigger+0x749/0x860 [ 100.274505] ? kasan_save_stack+0x2a/0x50 [ 100.275024] ? kasan_set_track+0x29/0x40 [ 100.275536] ? __pfx_event_hist_trigger+0x10/0x10 [ 100.276138] ? ksys_write+0xd1/0x170 [ 100.276607] ? do_syscall_64+0x3c/0x90 [ 100.277099] ? entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 100.277771] ? destroy_hist_data+0x446/0x470 [ 100.278324] ? event_hist_trigger_parse+0xa6c/0x3860 [ 100.278962] ? __pfx_event_hist_trigger_parse+0x10/0x10 [ 100.279627] ? __kasan_check_write+0x18/0x20 [ 100.280177] ? mutex_unlock+0x85/0xd0 [ 100.280660] ? __pfx_mutex_unlock+0x10/0x10 [ 100.281200] ? kfree+0x7b/0x120 [ 100.281619] ? ____kasan_slab_free+0x15d/0x1d0 [ 100.282197] ? event_trigger_write+0xac/0x100 [ 100.282764] ? __kasan_slab_free+0x16/0x20 [ 100.283293] ? __kmem_cache_free+0x153/0x2f0 [ 100.283844] ? sched_mm_cid_remote_clear+0xb1/0x250 [ 100.284550] ? __pfx_sched_mm_cid_remote_clear+0x10/0x10 [ 100.285221] ? event_trigger_write+0xbc/0x100 [ 100.285781] ? __kasan_check_read+0x15/0x20 [ 100.286321] ? __bitmap_weight+0x66/0xa0 [ 100.286833] ? _find_next_bit+0x46/0xe0 [ 100.287334] ? task_mm_cid_work+0x37f/0x450 [ 100.287872] event_triggers_call+0x84/0x150 [ 100.288408] trace_event_buffer_commit+0x339/0x430 [ 100.289073] ? ring_buffer_event_data+0x3f/0x60 [ 100.292189] trace_event_raw_event_sys_enter+0x8b/0xe0 [ 100.295434] syscall_trace_enter.constprop.0+0x18f/0x1b0 [ 100.298653] syscall_enter_from_user_mode+0x32/0x40 [ 100.301808] do_syscall_64+0x1a/0x90 [ 100.304748] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 100.307775] RIP: 0033:0x7f686c75c1cb [ 100.310617] Code: 73 01 c3 48 8b 0d 65 3c 10 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 21 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 35 3c 10 00 f7 d8 64 89 01 48 [ 100.317847] RSP: 002b:00007ffc60137a38 EFLAGS: 00000246 ORIG_RAX: 0000000000000021 [ 100.321200] RA ---truncated--- CVE-2023-53560 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53560.html CVE-2023-53560 https://bugzilla.suse.com/1251045 SUSE Bug 1251045 In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver After loading the amd-pstate-ut driver, amd_pstate_ut_check_perf() and amd_pstate_ut_check_freq() use cpufreq_cpu_get() to get the policy of the CPU and mark it as busy. In these functions, cpufreq_cpu_put() should be used to release the policy, but it is not, so any other entity trying to access the policy is blocked indefinitely. One such scenario is when amd_pstate mode is changed, leading to the following splat: [ 1332.103727] INFO: task bash:2929 blocked for more than 120 seconds. [ 1332.110001] Not tainted 6.5.0-rc2-amd-pstate-ut #5 [ 1332.115315] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1332.123140] task:bash state:D stack:0 pid:2929 ppid:2873 flags:0x00004006 [ 1332.123143] Call Trace: [ 1332.123145] <TASK> [ 1332.123148] __schedule+0x3c1/0x16a0 [ 1332.123154] ? _raw_read_lock_irqsave+0x2d/0x70 [ 1332.123157] schedule+0x6f/0x110 [ 1332.123160] schedule_timeout+0x14f/0x160 [ 1332.123162] ? preempt_count_add+0x86/0xd0 [ 1332.123165] __wait_for_common+0x92/0x190 [ 1332.123168] ? __pfx_schedule_timeout+0x10/0x10 [ 1332.123170] wait_for_completion+0x28/0x30 [ 1332.123173] cpufreq_policy_put_kobj+0x4d/0x90 [ 1332.123177] cpufreq_policy_free+0x157/0x1d0 [ 1332.123178] ? preempt_count_add+0x58/0xd0 [ 1332.123180] cpufreq_remove_dev+0xb6/0x100 [ 1332.123182] subsys_interface_unregister+0x114/0x120 [ 1332.123185] ? preempt_count_add+0x58/0xd0 [ 1332.123187] ? __pfx_amd_pstate_change_driver_mode+0x10/0x10 [ 1332.123190] cpufreq_unregister_driver+0x3b/0xd0 [ 1332.123192] amd_pstate_change_driver_mode+0x1e/0x50 [ 1332.123194] store_status+0xe9/0x180 [ 1332.123197] dev_attr_store+0x1b/0x30 [ 1332.123199] sysfs_kf_write+0x42/0x50 [ 1332.123202] kernfs_fop_write_iter+0x143/0x1d0 [ 1332.123204] vfs_write+0x2df/0x400 [ 1332.123208] ksys_write+0x6b/0xf0 [ 1332.123210] __x64_sys_write+0x1d/0x30 [ 1332.123213] do_syscall_64+0x60/0x90 [ 1332.123216] ? fpregs_assert_state_consistent+0x2e/0x50 [ 1332.123219] ? exit_to_user_mode_prepare+0x49/0x1a0 [ 1332.123223] ? irqentry_exit_to_user_mode+0xd/0x20 [ 1332.123225] ? irqentry_exit+0x3f/0x50 [ 1332.123226] ? exc_page_fault+0x8e/0x190 [ 1332.123228] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 1332.123232] RIP: 0033:0x7fa74c514a37 [ 1332.123234] RSP: 002b:00007ffe31dd0788 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 1332.123238] RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 00007fa74c514a37 [ 1332.123239] RDX: 0000000000000008 RSI: 000055e27c447aa0 RDI: 0000000000000001 [ 1332.123241] RBP: 000055e27c447aa0 R08: 00007fa74c5d1460 R09: 000000007fffffff [ 1332.123242] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000008 [ 1332.123244] R13: 00007fa74c61a780 R14: 00007fa74c616600 R15: 00007fa74c615a00 [ 1332.123247] </TASK> Fix this by calling cpufreq_cpu_put() wherever necessary. [ rjw: Subject and changelog edits ] CVE-2023-53563 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53563.html CVE-2023-53563 https://bugzilla.suse.com/1251038 SUSE Bug 1251038 In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: don't leak memory if dev_set_name() fails When dev_set_name() fails, zcdn_create() doesn't free the newly allocated resources. Do it. CVE-2023-53568 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53568.html CVE-2023-53568 https://bugzilla.suse.com/1251035 SUSE Bug 1251035 In the Linux kernel, the following vulnerability has been resolved: wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems() nl80211_parse_mbssid_elems() uses a u8 variable num_elems to count the number of MBSSID elements in the nested netlink attribute attrs, which can lead to an integer overflow if a user of the nl80211 interface specifies 256 or more elements in the corresponding attribute in userspace. The integer overflow can lead to a heap buffer overflow as num_elems determines the size of the trailing array in elems, and this array is thereafter written to for each element in attrs. Note that this vulnerability only affects devices with the wiphy->mbssid_max_interfaces member set for the wireless physical device struct in the device driver, and can only be triggered by a process with CAP_NET_ADMIN capabilities. Fix this by checking for a maximum of 255 elements in attrs. CVE-2023-53570 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53570.html CVE-2023-53570 https://bugzilla.suse.com/1251031 SUSE Bug 1251031 In the Linux kernel, the following vulnerability has been resolved: clk: imx: scu: use _safe list iterator to avoid a use after free This loop is freeing "clk" so it needs to use list_for_each_entry_safe(). Otherwise it dereferences a freed variable to get the next item on the loop. CVE-2023-53572 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53572.html CVE-2023-53572 https://bugzilla.suse.com/1251027 SUSE Bug 1251027 In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: delete timer and free skb queue when unloading Fix possible crash and memory leak on driver unload by deleting TX purge timer and freeing C2H queue in 'rtw_core_deinit()', shrink critical section in the latter by freeing COEX queue out of TX report lock scope. CVE-2023-53574 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53574.html CVE-2023-53574 https://bugzilla.suse.com/1251222 SUSE Bug 1251222 https://bugzilla.suse.com/1251984 SUSE Bug 1251984 In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix potential array out of bounds access Account for IWL_SEC_WEP_KEY_OFFSET when needed while verifying key_len size in iwl_mvm_sec_key_add(). CVE-2023-53575 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53575.html CVE-2023-53575 https://bugzilla.suse.com/1251067 SUSE Bug 1251067 In the Linux kernel, the following vulnerability has been resolved: bpf, cpumap: Make sure kthread is running before map update returns The following warning was reported when running stress-mode enabled xdp_redirect_cpu with some RT threads: ------------[ cut here ]------------ WARNING: CPU: 4 PID: 65 at kernel/bpf/cpumap.c:135 CPU: 4 PID: 65 Comm: kworker/4:1 Not tainted 6.5.0-rc2+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: events cpu_map_kthread_stop RIP: 0010:put_cpu_map_entry+0xda/0x220 ...... Call Trace: <TASK> ? show_regs+0x65/0x70 ? __warn+0xa5/0x240 ...... ? put_cpu_map_entry+0xda/0x220 cpu_map_kthread_stop+0x41/0x60 process_one_work+0x6b0/0xb80 worker_thread+0x96/0x720 kthread+0x1a5/0x1f0 ret_from_fork+0x3a/0x70 ret_from_fork_asm+0x1b/0x30 </TASK> The root cause is the same as commit 436901649731 ("bpf: cpumap: Fix memory leak in cpu_map_update_elem"). The kthread is stopped prematurely by kthread_stop() in cpu_map_kthread_stop(), and kthread() doesn't call cpu_map_kthread_run() at all but XDP program has already queued some frames or skbs into ptr_ring. So when __cpu_map_ring_cleanup() checks the ptr_ring, it will find it was not emptied and report a warning. An alternative fix is to use __cpu_map_ring_cleanup() to drop these pending frames or skbs when kthread_stop() returns -EINTR, but it may confuse the user, because these frames or skbs have been handled correctly by XDP program. So instead of dropping these frames or skbs, just make sure the per-cpu kthread is running before __cpu_map_entry_alloc() returns. After apply the fix, the error handle for kthread_stop() will be unnecessary because it will always return 0, so just remove it. CVE-2023-53577 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53577.html CVE-2023-53577 https://bugzilla.suse.com/1251028 SUSE Bug 1251028 In the Linux kernel, the following vulnerability has been resolved: gpio: mvebu: fix irq domain leak Uwe Kleine-König pointed out we still have one resource leak in the mvebu driver triggered on driver detach. Let's address it with a custom devm action. CVE-2023-53579 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53579.html CVE-2023-53579 https://bugzilla.suse.com/1251170 SUSE Bug 1251170 In the Linux kernel, the following vulnerability has been resolved: USB: Gadget: core: Help prevent panic during UVC unconfigure Avichal Rakesh reported a kernel panic that occurred when the UVC gadget driver was removed from a gadget's configuration. The panic involves a somewhat complicated interaction between the kernel driver and a userspace component (as described in the Link tag below), but the analysis did make one thing clear: The Gadget core should accomodate gadget drivers calling usb_gadget_deactivate() as part of their unbind procedure. Currently this doesn't work. gadget_unbind_driver() calls driver->unbind() while holding the udc->connect_lock mutex, and usb_gadget_deactivate() attempts to acquire that mutex, which will result in a deadlock. The simple fix is for gadget_unbind_driver() to release the mutex when invoking the ->unbind() callback. There is no particular reason for it to be holding the mutex at that time, and the mutex isn't held while the ->bind() callback is invoked. So we'll drop the mutex before performing the unbind callback and reacquire it afterward. We'll also add a couple of comments to usb_gadget_activate() and usb_gadget_deactivate(). Because they run in process context they must not be called from a gadget driver's ->disconnect() callback, which (according to the kerneldoc for struct usb_gadget_driver in include/linux/usb/gadget.h) may run in interrupt context. This may help prevent similar bugs from arising in the future. CVE-2023-53580 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53580.html CVE-2023-53580 https://bugzilla.suse.com/1251105 SUSE Bug 1251105 In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Check for NOT_READY flag state after locking Currently the check for NOT_READY flag is performed before obtaining the necessary lock. This opens a possibility for race condition when the flow is concurrently removed from unready_flows list by the workqueue task, which causes a double-removal from the list and a crash[0]. Fix the issue by moving the flag check inside the section protected by uplink_priv->unready_flows_lock mutex. [0]: [44376.389654] general protection fault, probably for non-canonical address 0xdead000000000108: 0000 [#1] SMP [44376.391665] CPU: 7 PID: 59123 Comm: tc Not tainted 6.4.0-rc4+ #1 [44376.392984] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [44376.395342] RIP: 0010:mlx5e_tc_del_fdb_flow+0xb3/0x340 [mlx5_core] [44376.396857] Code: 00 48 8b b8 68 ce 02 00 e8 8a 4d 02 00 4c 8d a8 a8 01 00 00 4c 89 ef e8 8b 79 88 e1 48 8b 83 98 06 00 00 48 8b 93 90 06 00 00 <48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de 48 89 83 90 06 [44376.399167] RSP: 0018:ffff88812cc97570 EFLAGS: 00010246 [44376.399680] RAX: dead000000000122 RBX: ffff8881088e3800 RCX: ffff8881881bac00 [44376.400337] RDX: dead000000000100 RSI: ffff88812cc97500 RDI: ffff8881242f71b0 [44376.401001] RBP: ffff88811cbb0940 R08: 0000000000000400 R09: 0000000000000001 [44376.401663] R10: 0000000000000001 R11: 0000000000000000 R12: ffff88812c944000 [44376.402342] R13: ffff8881242f71a8 R14: ffff8881222b4000 R15: 0000000000000000 [44376.402999] FS: 00007f0451104800(0000) GS:ffff88852cb80000(0000) knlGS:0000000000000000 [44376.403787] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [44376.404343] CR2: 0000000000489108 CR3: 0000000123a79003 CR4: 0000000000370ea0 [44376.405004] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [44376.405665] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [44376.406339] Call Trace: [44376.406651] <TASK> [44376.406939] ? die_addr+0x33/0x90 [44376.407311] ? exc_general_protection+0x192/0x390 [44376.407795] ? asm_exc_general_protection+0x22/0x30 [44376.408292] ? mlx5e_tc_del_fdb_flow+0xb3/0x340 [mlx5_core] [44376.408876] __mlx5e_tc_del_fdb_peer_flow+0xbc/0xe0 [mlx5_core] [44376.409482] mlx5e_tc_del_flow+0x42/0x210 [mlx5_core] [44376.410055] mlx5e_flow_put+0x25/0x50 [mlx5_core] [44376.410529] mlx5e_delete_flower+0x24b/0x350 [mlx5_core] [44376.411043] tc_setup_cb_reoffload+0x22/0x80 [44376.411462] fl_reoffload+0x261/0x2f0 [cls_flower] [44376.411907] ? mlx5e_rep_indr_setup_ft_cb+0x160/0x160 [mlx5_core] [44376.412481] ? mlx5e_rep_indr_setup_ft_cb+0x160/0x160 [mlx5_core] [44376.413044] tcf_block_playback_offloads+0x76/0x170 [44376.413497] tcf_block_unbind+0x7b/0xd0 [44376.413881] tcf_block_setup+0x17d/0x1c0 [44376.414269] tcf_block_offload_cmd.isra.0+0xf1/0x130 [44376.414725] tcf_block_offload_unbind+0x43/0x70 [44376.415153] __tcf_block_put+0x82/0x150 [44376.415532] ingress_destroy+0x22/0x30 [sch_ingress] [44376.415986] qdisc_destroy+0x3b/0xd0 [44376.416343] qdisc_graft+0x4d0/0x620 [44376.416706] tc_get_qdisc+0x1c9/0x3b0 [44376.417074] rtnetlink_rcv_msg+0x29c/0x390 [44376.419978] ? rep_movs_alternative+0x3a/0xa0 [44376.420399] ? rtnl_calcit.isra.0+0x120/0x120 [44376.420813] netlink_rcv_skb+0x54/0x100 [44376.421192] netlink_unicast+0x1f6/0x2c0 [44376.421573] netlink_sendmsg+0x232/0x4a0 [44376.421980] sock_sendmsg+0x38/0x60 [44376.422328] ____sys_sendmsg+0x1d0/0x1e0 [44376.422709] ? copy_msghdr_from_user+0x6d/0xa0 [44376.423127] ___sys_sendmsg+0x80/0xc0 [44376.423495] ? ___sys_recvmsg+0x8b/0xc0 [44376.423869] __sys_sendmsg+0x51/0x90 [44376.424226] do_syscall_64+0x3d/0x90 [44376.424587] entry_SYSCALL_64_after_hwframe+0x46/0xb0 [44376.425046] RIP: 0033:0x7f045134f887 [44376.425403] Code: 0a 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b9 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 ---truncated--- CVE-2023-53581 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53581.html CVE-2023-53581 https://bugzilla.suse.com/1251106 SUSE Bug 1251106 In the Linux kernel, the following vulnerability has been resolved: perf: RISC-V: Remove PERF_HES_STOPPED flag checking in riscv_pmu_start() Since commit 096b52fd2bb4 ("perf: RISC-V: throttle perf events") the perf_sample_event_took() function was added to report time spent in overflow interrupts. If the interrupt takes too long, the perf framework will lower the sysctl_perf_event_sample_rate and max_samples_per_tick. When hwc->interrupts is larger than max_samples_per_tick, the hwc->interrupts will be set to MAX_INTERRUPTS, and events will be throttled within the __perf_event_account_interrupt() function. However, the RISC-V PMU driver doesn't call riscv_pmu_stop() to update the PERF_HES_STOPPED flag after perf_event_overflow() in pmu_sbi_ovf_handler() function to avoid throttling. When the perf framework unthrottled the event in the timer interrupt handler, it triggers riscv_pmu_start() function and causes a WARN_ON_ONCE() warning, as shown below: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 240 at drivers/perf/riscv_pmu.c:184 riscv_pmu_start+0x7c/0x8e Modules linked in: CPU: 0 PID: 240 Comm: ls Not tainted 6.4-rc4-g19d0788e9ef2 #1 Hardware name: SiFive (DT) epc : riscv_pmu_start+0x7c/0x8e ra : riscv_pmu_start+0x28/0x8e epc : ffffffff80aef864 ra : ffffffff80aef810 sp : ffff8f80004db6f0 gp : ffffffff81c83750 tp : ffffaf80069f9bc0 t0 : ffff8f80004db6c0 t1 : 0000000000000000 t2 : 000000000000001f s0 : ffff8f80004db720 s1 : ffffaf8008ca1068 a0 : 0000ffffffffffff a1 : 0000000000000000 a2 : 0000000000000001 a3 : 0000000000000870 a4 : 0000000000000000 a5 : 0000000000000000 a6 : 0000000000000840 a7 : 0000000000000030 s2 : 0000000000000000 s3 : ffffaf8005165800 s4 : ffffaf800424da00 s5 : ffffffffffffffff s6 : ffffffff81cc7590 s7 : 0000000000000000 s8 : 0000000000000006 s9 : 0000000000000001 s10: ffffaf807efbc340 s11: ffffaf807efbbf00 t3 : ffffaf8006a16028 t4 : 00000000dbfbb796 t5 : 0000000700000000 t6 : ffffaf8005269870 status: 0000000200000100 badaddr: 0000000000000000 cause: 0000000000000003 [<ffffffff80aef864>] riscv_pmu_start+0x7c/0x8e [<ffffffff80185b56>] perf_adjust_freq_unthr_context+0x15e/0x174 [<ffffffff80188642>] perf_event_task_tick+0x88/0x9c [<ffffffff800626a8>] scheduler_tick+0xfe/0x27c [<ffffffff800b5640>] update_process_times+0x9a/0xba [<ffffffff800c5bd4>] tick_sched_handle+0x32/0x66 [<ffffffff800c5e0c>] tick_sched_timer+0x64/0xb0 [<ffffffff800b5e50>] __hrtimer_run_queues+0x156/0x2f4 [<ffffffff800b6bdc>] hrtimer_interrupt+0xe2/0x1fe [<ffffffff80acc9e8>] riscv_timer_interrupt+0x38/0x42 [<ffffffff80090a16>] handle_percpu_devid_irq+0x90/0x1d2 [<ffffffff8008a9f4>] generic_handle_domain_irq+0x28/0x36 After referring other PMU drivers like Arm, Loongarch, Csky, and Mips, they don't call *_pmu_stop() to update with PERF_HES_STOPPED flag after perf_event_overflow() function nor do they add PERF_HES_STOPPED flag checking in *_pmu_start() which don't cause this warning. Thus, it's recommended to remove this unnecessary check in riscv_pmu_start() function to prevent this warning. CVE-2023-53583 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53583.html CVE-2023-53583 https://bugzilla.suse.com/1251108 SUSE Bug 1251108 In the Linux kernel, the following vulnerability has been resolved: bpf: reject unhashed sockets in bpf_sk_assign The semantics for bpf_sk_assign are as follows: sk = some_lookup_func() bpf_sk_assign(skb, sk) bpf_sk_release(sk) That is, the sk is not consumed by bpf_sk_assign. The function therefore needs to make sure that sk lives long enough to be consumed from __inet_lookup_skb. The path through the stack for a TCPv4 packet is roughly: netif_receive_skb_core: takes RCU read lock __netif_receive_skb_core: sch_handle_ingress: tcf_classify: bpf_sk_assign() deliver_ptype_list_skb: deliver_skb: ip_packet_type->func == ip_rcv: ip_rcv_core: ip_rcv_finish_core: dst_input: ip_local_deliver: ip_local_deliver_finish: ip_protocol_deliver_rcu: tcp_v4_rcv: __inet_lookup_skb: skb_steal_sock The existing helper takes advantage of the fact that everything happens in the same RCU critical section: for sockets with SOCK_RCU_FREE set bpf_sk_assign never takes a reference. skb_steal_sock then checks SOCK_RCU_FREE again and does sock_put if necessary. This approach assumes that SOCK_RCU_FREE is never set on a sk between bpf_sk_assign and skb_steal_sock, but this invariant is violated by unhashed UDP sockets. A new UDP socket is created in TCP_CLOSE state but without SOCK_RCU_FREE set. That flag is only added in udp_lib_get_port() which happens when a socket is bound. When bpf_sk_assign was added it wasn't possible to access unhashed UDP sockets from BPF, so this wasn't a problem. This changed in commit 0c48eefae712 ("sock_map: Lift socket state restriction for datagram sockets"), but the helper wasn't adjusted accordingly. The following sequence of events will therefore lead to a refcount leak: 1. Add socket(AF_INET, SOCK_DGRAM) to a sockmap. 2. Pull socket out of sockmap and bpf_sk_assign it. Since SOCK_RCU_FREE is not set we increment the refcount. 3. bind() or connect() the socket, setting SOCK_RCU_FREE. 4. skb_steal_sock will now set refcounted = false due to SOCK_RCU_FREE. 5. tcp_v4_rcv() skips sock_put(). Fix the problem by rejecting unhashed sockets in bpf_sk_assign(). This matches the behaviour of __inet_lookup_skb which is ultimately the goal of bpf_sk_assign(). CVE-2023-53585 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53585.html CVE-2023-53585 https://bugzilla.suse.com/1251126 SUSE Bug 1251126 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: check for station first in client probe When probing a client, first check if we have it, and then check for the channel context, otherwise you can trigger the warning there easily by probing when the AP isn't even started yet. Since a client existing means the AP is also operating, we can then keep the warning. Also simplify the moved code a bit. CVE-2023-53588 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53588.html CVE-2023-53588 https://bugzilla.suse.com/1251206 SUSE Bug 1251206 In the Linux kernel, the following vulnerability has been resolved: cifs: Release folio lock on fscache read hit. Under the current code, when cifs_readpage_worker is called, the call contract is that the callee should unlock the page. This is documented in the read_folio section of Documentation/filesystems/vfs.rst as: > The filesystem should unlock the folio once the read has completed, > whether it was successful or not. Without this change, when fscache is in use and cache hit occurs during a read, the page lock is leaked, producing the following stack on subsequent reads (via mmap) to the page: $ cat /proc/3890/task/12864/stack [<0>] folio_wait_bit_common+0x124/0x350 [<0>] filemap_read_folio+0xad/0xf0 [<0>] filemap_fault+0x8b1/0xab0 [<0>] __do_fault+0x39/0x150 [<0>] do_fault+0x25c/0x3e0 [<0>] __handle_mm_fault+0x6ca/0xc70 [<0>] handle_mm_fault+0xe9/0x350 [<0>] do_user_addr_fault+0x225/0x6c0 [<0>] exc_page_fault+0x84/0x1b0 [<0>] asm_exc_page_fault+0x27/0x30 This requires a reboot to resolve; it is a deadlock. Note however that the call to cifs_readpage_from_fscache does mark the page clean, but does not free the folio lock. This happens in __cifs_readpage_from_fscache on success. Releasing the lock at that point however is not appropriate as cifs_readahead also calls cifs_readpage_from_fscache and *does* unconditionally release the lock after its return. This change therefore effectively makes cifs_readpage_worker work like cifs_readahead. CVE-2023-53593 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53593.html CVE-2023-53593 https://bugzilla.suse.com/1251132 SUSE Bug 1251132 In the Linux kernel, the following vulnerability has been resolved: drivers: base: Free devm resources when unregistering a device In the current code, devres_release_all() only gets called if the device has a bus and has been probed. This leads to issues when using bus-less or driver-less devices where the device might never get freed if a managed resource holds a reference to the device. This is happening in the DRM framework for example. We should thus call devres_release_all() in the device_del() function to make sure that the device-managed actions are properly executed when the device is unregistered, even if it has neither a bus nor a driver. This is effectively the same change than commit 2f8d16a996da ("devres: release resources on device_del()") that got reverted by commit a525a3ddeaca ("driver core: free devres in device_release") over memory leaks concerns. This patch effectively combines the two commits mentioned above to release the resources both on device_del() and device_release() and get the best of both worlds. CVE-2023-53596 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53596.html CVE-2023-53596 https://bugzilla.suse.com/1251161 SUSE Bug 1251161 In the Linux kernel, the following vulnerability has been resolved: cifs: fix mid leak during reconnection after timeout threshold When the number of responses with status of STATUS_IO_TIMEOUT exceeds a specified threshold (NUM_STATUS_IO_TIMEOUT), we reconnect the connection. But we do not return the mid, or the credits returned for the mid, or reduce the number of in-flight requests. This bug could result in the server->in_flight count to go bad, and also cause a leak in the mids. This change moves the check to a few lines below where the response is decrypted, even of the response is read from the transform header. This way, the code for returning the mids can be reused. Also, the cifs_reconnect was reconnecting just the transport connection before. In case of multi-channel, this may not be what we want to do after several timeouts. Changed that to reconnect the session and the tree too. Also renamed NUM_STATUS_IO_TIMEOUT to a more appropriate name MAX_STATUS_IO_TIMEOUT. CVE-2023-53597 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53597.html CVE-2023-53597 https://bugzilla.suse.com/1251159 SUSE Bug 1251159 In the Linux kernel, the following vulnerability has been resolved: crypto: af_alg - Fix missing initialisation affecting gcm-aes-s390 Fix af_alg_alloc_areq() to initialise areq->first_rsgl.sgl.sgt.sgl to point to the scatterlist array in areq->first_rsgl.sgl.sgl. Without this, the gcm-aes-s390 driver will oops when it tries to do gcm_walk_start() on req->dst because req->dst is set to the value of areq->first_rsgl.sgl.sgl by _aead_recvmsg() calling aead_request_set_crypt(). The problem comes if an empty ciphertext is passed: the loop in af_alg_get_rsgl() just passes straight out and doesn't set areq->first_rsgl up. This isn't a problem on x86_64 using gcmaes_crypt_by_sg() because, as far as I can tell, that ignores req->dst and only uses req->src[*]. [*] Is this a bug in aesni-intel_glue.c? The s390x oops looks something like: Unable to handle kernel pointer dereference in virtual kernel address space Failing address: 0000000a00000000 TEID: 0000000a00000803 Fault in home space mode while using kernel ASCE. AS:00000000a43a0007 R3:0000000000000024 Oops: 003b ilc:2 [#1] SMP ... Call Trace: [<000003ff7fc3d47e>] gcm_walk_start+0x16/0x28 [aes_s390] [<00000000a2a342f2>] crypto_aead_decrypt+0x9a/0xb8 [<00000000a2a60888>] aead_recvmsg+0x478/0x698 [<00000000a2e519a0>] sock_recvmsg+0x70/0xb0 [<00000000a2e51a56>] sock_read_iter+0x76/0xa0 [<00000000a273e066>] vfs_read+0x26e/0x2a8 [<00000000a273e8c4>] ksys_read+0xbc/0x100 [<00000000a311d808>] __do_syscall+0x1d0/0x1f8 [<00000000a312ff30>] system_call+0x70/0x98 Last Breaking-Event-Address: [<000003ff7fc3e6b4>] gcm_aes_crypt+0x104/0xa68 [aes_s390] CVE-2023-53599 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53599.html CVE-2023-53599 https://bugzilla.suse.com/1251150 SUSE Bug 1251150 In the Linux kernel, the following vulnerability has been resolved: tunnels: fix kasan splat when generating ipv4 pmtu error If we try to emit an icmp error in response to a nonliner skb, we get BUG: KASAN: slab-out-of-bounds in ip_compute_csum+0x134/0x220 Read of size 4 at addr ffff88811c50db00 by task iperf3/1691 CPU: 2 PID: 1691 Comm: iperf3 Not tainted 6.5.0-rc3+ #309 [..] kasan_report+0x105/0x140 ip_compute_csum+0x134/0x220 iptunnel_pmtud_build_icmp+0x554/0x1020 skb_tunnel_check_pmtu+0x513/0xb80 vxlan_xmit_one+0x139e/0x2ef0 vxlan_xmit+0x1867/0x2760 dev_hard_start_xmit+0x1ee/0x4f0 br_dev_queue_push_xmit+0x4d1/0x660 [..] ip_compute_csum() cannot deal with nonlinear skbs, so avoid it. After this change, splat is gone and iperf3 is no longer stuck. CVE-2023-53600 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53600.html CVE-2023-53600 https://bugzilla.suse.com/1251152 SUSE Bug 1251152 In the Linux kernel, the following vulnerability has been resolved: bonding: do not assume skb mac_header is set Drivers must not assume in their ndo_start_xmit() that skbs have their mac_header set. skb->data is all what is needed. bonding seems to be one of the last offender as caught by syzbot: WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 skb_mac_offset include/linux/skbuff.h:2913 [inline] WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 bond_xmit_hash drivers/net/bonding/bond_main.c:4170 [inline] WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 bond_xmit_3ad_xor_slave_get drivers/net/bonding/bond_main.c:5149 [inline] WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 bond_3ad_xor_xmit drivers/net/bonding/bond_main.c:5186 [inline] WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 __bond_start_xmit drivers/net/bonding/bond_main.c:5442 [inline] WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 bond_start_xmit+0x14ab/0x19d0 drivers/net/bonding/bond_main.c:5470 Modules linked in: CPU: 1 PID: 12155 Comm: syz-executor.3 Not tainted 6.1.30-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023 RIP: 0010:skb_mac_header include/linux/skbuff.h:2907 [inline] RIP: 0010:skb_mac_offset include/linux/skbuff.h:2913 [inline] RIP: 0010:bond_xmit_hash drivers/net/bonding/bond_main.c:4170 [inline] RIP: 0010:bond_xmit_3ad_xor_slave_get drivers/net/bonding/bond_main.c:5149 [inline] RIP: 0010:bond_3ad_xor_xmit drivers/net/bonding/bond_main.c:5186 [inline] RIP: 0010:__bond_start_xmit drivers/net/bonding/bond_main.c:5442 [inline] RIP: 0010:bond_start_xmit+0x14ab/0x19d0 drivers/net/bonding/bond_main.c:5470 Code: 8b 7c 24 30 e8 76 dd 1a 01 48 85 c0 74 0d 48 89 c3 e8 29 67 2e fe e9 15 ef ff ff e8 1f 67 2e fe e9 10 ef ff ff e8 15 67 2e fe <0f> 0b e9 45 f8 ff ff e8 09 67 2e fe e9 dc fa ff ff e8 ff 66 2e fe RSP: 0018:ffffc90002fff6e0 EFLAGS: 00010283 RAX: ffffffff835874db RBX: 000000000000ffff RCX: 0000000000040000 RDX: ffffc90004dcf000 RSI: 00000000000000b5 RDI: 00000000000000b6 RBP: ffffc90002fff8b8 R08: ffffffff83586d16 R09: ffffffff83586584 R10: 0000000000000007 R11: ffff8881599fc780 R12: ffff88811b6a7b7e R13: 1ffff110236d4f6f R14: ffff88811b6a7ac0 R15: 1ffff110236d4f76 FS: 00007f2e9eb47700(0000) GS:ffff8881f6b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b2e421000 CR3: 000000010e6d4000 CR4: 00000000003526e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> [<ffffffff8471a49f>] netdev_start_xmit include/linux/netdevice.h:4925 [inline] [<ffffffff8471a49f>] __dev_direct_xmit+0x4ef/0x850 net/core/dev.c:4380 [<ffffffff851d845b>] dev_direct_xmit include/linux/netdevice.h:3043 [inline] [<ffffffff851d845b>] packet_direct_xmit+0x18b/0x300 net/packet/af_packet.c:284 [<ffffffff851c7472>] packet_snd net/packet/af_packet.c:3112 [inline] [<ffffffff851c7472>] packet_sendmsg+0x4a22/0x64d0 net/packet/af_packet.c:3143 [<ffffffff8467a4b2>] sock_sendmsg_nosec net/socket.c:716 [inline] [<ffffffff8467a4b2>] sock_sendmsg net/socket.c:736 [inline] [<ffffffff8467a4b2>] __sys_sendto+0x472/0x5f0 net/socket.c:2139 [<ffffffff8467a715>] __do_sys_sendto net/socket.c:2151 [inline] [<ffffffff8467a715>] __se_sys_sendto net/socket.c:2147 [inline] [<ffffffff8467a715>] __x64_sys_sendto+0xe5/0x100 net/socket.c:2147 [<ffffffff8553071f>] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [<ffffffff8553071f>] do_syscall_64+0x2f/0x50 arch/x86/entry/common.c:80 [<ffffffff85600087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd CVE-2023-53601 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53601.html CVE-2023-53601 https://bugzilla.suse.com/1251153 SUSE Bug 1251153 In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix memory leak in WMI firmware stats Memory allocated for firmware pdev, vdev and beacon statistics are not released during rmmod. Fix it by calling ath11k_fw_stats_free() function before hardware unregister. While at it, avoid calling ath11k_fw_stats_free() while processing the firmware stats received in the WMI event because the local list is getting spliced and reinitialised and hence there are no elements in the list after splicing. Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1 CVE-2023-53602 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53602.html CVE-2023-53602 https://bugzilla.suse.com/1251076 SUSE Bug 1251076 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid fcport pointer dereference Klocwork reported warning of NULL pointer may be dereferenced. The routine exits when sa_ctl is NULL and fcport is allocated after the exit call thus causing NULL fcport pointer to dereference at the time of exit. To avoid fcport pointer dereference, exit the routine when sa_ctl is NULL. CVE-2023-53603 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53603.html CVE-2023-53603 https://bugzilla.suse.com/1251180 SUSE Bug 1251180 In the Linux kernel, the following vulnerability has been resolved: ipmi_si: fix a memleak in try_smi_init() Kmemleak reported the following leak info in try_smi_init(): unreferenced object 0xffff00018ecf9400 (size 1024): comm "modprobe", pid 2707763, jiffies 4300851415 (age 773.308s) backtrace: [<000000004ca5b312>] __kmalloc+0x4b8/0x7b0 [<00000000953b1072>] try_smi_init+0x148/0x5dc [ipmi_si] [<000000006460d325>] 0xffff800081b10148 [<0000000039206ea5>] do_one_initcall+0x64/0x2a4 [<00000000601399ce>] do_init_module+0x50/0x300 [<000000003c12ba3c>] load_module+0x7a8/0x9e0 [<00000000c246fffe>] __se_sys_init_module+0x104/0x180 [<00000000eea99093>] __arm64_sys_init_module+0x24/0x30 [<0000000021b1ef87>] el0_svc_common.constprop.0+0x94/0x250 [<0000000070f4f8b7>] do_el0_svc+0x48/0xe0 [<000000005a05337f>] el0_svc+0x24/0x3c [<000000005eb248d6>] el0_sync_handler+0x160/0x164 [<0000000030a59039>] el0_sync+0x160/0x180 The problem was that when an error occurred before handlers registration and after allocating `new_smi->si_sm`, the variable wouldn't be freed in the error handling afterwards since `shutdown_smi()` hadn't been registered yet. Fix it by adding a `kfree()` in the error handling path in `try_smi_init()`. CVE-2023-53611 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53611.html CVE-2023-53611 https://bugzilla.suse.com/1251123 SUSE Bug 1251123 In the Linux kernel, the following vulnerability has been resolved: dax: Fix dax_mapping_release() use after free A CONFIG_DEBUG_KOBJECT_RELEASE test of removing a device-dax region provider (like modprobe -r dax_hmem) yields: kobject: 'mapping0' (ffff93eb460e8800): kobject_release, parent 0000000000000000 (delayed 2000) [..] DEBUG_LOCKS_WARN_ON(1) WARNING: CPU: 23 PID: 282 at kernel/locking/lockdep.c:232 __lock_acquire+0x9fc/0x2260 [..] RIP: 0010:__lock_acquire+0x9fc/0x2260 [..] Call Trace: <TASK> [..] lock_acquire+0xd4/0x2c0 ? ida_free+0x62/0x130 _raw_spin_lock_irqsave+0x47/0x70 ? ida_free+0x62/0x130 ida_free+0x62/0x130 dax_mapping_release+0x1f/0x30 device_release+0x36/0x90 kobject_delayed_cleanup+0x46/0x150 Due to attempting ida_free() on an ida object that has already been freed. Devices typically only hold a reference on their parent while registered. If a child needs a parent object to complete its release it needs to hold a reference that it drops from its release callback. Arrange for a dax_mapping to pin its parent dev_dax instance until dax_mapping_release(). CVE-2023-53613 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53613.html CVE-2023-53613 https://bugzilla.suse.com/1251119 SUSE Bug 1251119 In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix deletion race condition System crash when using debug kernel due to link list corruption. The cause of the link list corruption is due to session deletion was allowed to queue up twice. Here's the internal trace that show the same port was allowed to double queue for deletion on different cpu. 20808683956 015 qla2xxx [0000:13:00.1]-e801:4: Scheduling sess ffff93ebf9306800 for deletion 50:06:0e:80:12:48:ff:50 fc4_type 1 20808683957 027 qla2xxx [0000:13:00.1]-e801:4: Scheduling sess ffff93ebf9306800 for deletion 50:06:0e:80:12:48:ff:50 fc4_type 1 Move the clearing/setting of deleted flag lock. CVE-2023-53615 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53615.html CVE-2023-53615 https://bugzilla.suse.com/1251113 SUSE Bug 1251113 In the Linux kernel, the following vulnerability has been resolved: jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount syzbot found an invalid-free in diUnmount: BUG: KASAN: double-free in slab_free mm/slub.c:3661 [inline] BUG: KASAN: double-free in __kmem_cache_free+0x71/0x110 mm/slub.c:3674 Free of addr ffff88806f410000 by task syz-executor131/3632 CPU: 0 PID: 3632 Comm: syz-executor131 Not tainted 6.1.0-rc7-syzkaller-00012-gca57f02295f1 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report_invalid_free+0xac/0xd0 mm/kasan/report.c:460 ____kasan_slab_free+0xfb/0x120 kasan_slab_free include/linux/kasan.h:177 [inline] slab_free_hook mm/slub.c:1724 [inline] slab_free_freelist_hook+0x12e/0x1a0 mm/slub.c:1750 slab_free mm/slub.c:3661 [inline] __kmem_cache_free+0x71/0x110 mm/slub.c:3674 diUnmount+0xef/0x100 fs/jfs/jfs_imap.c:195 jfs_umount+0x108/0x370 fs/jfs/jfs_umount.c:63 jfs_put_super+0x86/0x190 fs/jfs/super.c:194 generic_shutdown_super+0x130/0x310 fs/super.c:492 kill_block_super+0x79/0xd0 fs/super.c:1428 deactivate_locked_super+0xa7/0xf0 fs/super.c:332 cleanup_mnt+0x494/0x520 fs/namespace.c:1186 task_work_run+0x243/0x300 kernel/task_work.c:179 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0x664/0x2070 kernel/exit.c:820 do_group_exit+0x1fd/0x2b0 kernel/exit.c:950 __do_sys_exit_group kernel/exit.c:961 [inline] __se_sys_exit_group kernel/exit.c:959 [inline] __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:959 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 [...] JFS_IP(ipimap)->i_imap is not setting to NULL after free in diUnmount. If jfs_remount() free JFS_IP(ipimap)->i_imap but then failed at diMount(). JFS_IP(ipimap)->i_imap will be freed once again. Fix this problem by setting JFS_IP(ipimap)->i_imap to NULL after free. CVE-2023-53616 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53616.html CVE-2023-53616 https://bugzilla.suse.com/1251215 SUSE Bug 1251215 In the Linux kernel, the following vulnerability has been resolved: soc: aspeed: socinfo: Add kfree for kstrdup Add kfree() in the later error handling in order to avoid memory leak. CVE-2023-53617 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53617.html CVE-2023-53617 https://bugzilla.suse.com/1251268 SUSE Bug 1251268 In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it's a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won't be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption that corrupted on-disk data can trigger that ASSERT(). [FIX] Besides the dedicated fix and the graceful exit, also let tree-checker to check such root keys, to make sure reloc trees can only exist for subvolumes. CVE-2023-53618 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53618.html CVE-2023-53618 https://bugzilla.suse.com/1251748 SUSE Bug 1251748 In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free If nf_conntrack_init_start() fails (for example due to a register_nf_conntrack_bpf() failure), the nf_conntrack_helper_fini() clean-up path frees the nf_ct_helper_hash map. When built with NF_CONNTRACK=y, further netfilter modules (e.g: netfilter_conntrack_ftp) can still be loaded and call nf_conntrack_helpers_register(), independently of whether nf_conntrack initialized correctly. This accesses the nf_ct_helper_hash dangling pointer and causes a uaf, possibly leading to random memory corruption. This patch guards nf_conntrack_helper_register() from accessing a freed or uninitialized nf_ct_helper_hash pointer and fixes possible uses-after-free when loading a conntrack module. CVE-2023-53619 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53619.html CVE-2023-53619 https://bugzilla.suse.com/1251743 SUSE Bug 1251743 https://bugzilla.suse.com/1251745 SUSE Bug 1251745 In the Linux kernel, the following vulnerability has been resolved: memcontrol: ensure memcg acquired by id is properly set up In the eviction recency check, we attempt to retrieve the memcg to which the folio belonged when it was evicted, by the memcg id stored in the shadow entry. However, there is a chance that the retrieved memcg is not the original memcg that has been killed, but a new one which happens to have the same id. This is a somewhat unfortunate, but acceptable and rare inaccuracy in the heuristics. However, if we retrieve this new memcg between its allocation and when it is properly attached to the memcg hierarchy, we could run into the following NULL pointer exception during the memcg hierarchy traversal done in mem_cgroup_get_nr_swap_pages(): [ 155757.793456] BUG: kernel NULL pointer dereference, address: 00000000000000c0 [ 155757.807568] #PF: supervisor read access in kernel mode [ 155757.818024] #PF: error_code(0x0000) - not-present page [ 155757.828482] PGD 401f77067 P4D 401f77067 PUD 401f76067 PMD 0 [ 155757.839985] Oops: 0000 [#1] SMP [ 155757.887870] RIP: 0010:mem_cgroup_get_nr_swap_pages+0x3d/0xb0 [ 155757.899377] Code: 29 19 4a 02 48 39 f9 74 63 48 8b 97 c0 00 00 00 48 8b b7 58 02 00 00 48 2b b7 c0 01 00 00 48 39 f0 48 0f 4d c6 48 39 d1 74 42 <48> 8b b2 c0 00 00 00 48 8b ba 58 02 00 00 48 2b ba c0 01 00 00 48 [ 155757.937125] RSP: 0018:ffffc9002ecdfbc8 EFLAGS: 00010286 [ 155757.947755] RAX: 00000000003a3b1c RBX: 000007ffffffffff RCX: ffff888280183000 [ 155757.962202] RDX: 0000000000000000 RSI: 0007ffffffffffff RDI: ffff888bbc2d1000 [ 155757.976648] RBP: 0000000000000001 R08: 000000000000000b R09: ffff888ad9cedba0 [ 155757.991094] R10: ffffea0039c07900 R11: 0000000000000010 R12: ffff888b23a7b000 [ 155758.005540] R13: 0000000000000000 R14: ffff888bbc2d1000 R15: 000007ffffc71354 [ 155758.019991] FS: 00007f6234c68640(0000) GS:ffff88903f9c0000(0000) knlGS:0000000000000000 [ 155758.036356] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 155758.048023] CR2: 00000000000000c0 CR3: 0000000a83eb8004 CR4: 00000000007706e0 [ 155758.062473] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 155758.076924] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 155758.091376] PKRU: 55555554 [ 155758.096957] Call Trace: [ 155758.102016] <TASK> [ 155758.106502] ? __die+0x78/0xc0 [ 155758.112793] ? page_fault_oops+0x286/0x380 [ 155758.121175] ? exc_page_fault+0x5d/0x110 [ 155758.129209] ? asm_exc_page_fault+0x22/0x30 [ 155758.137763] ? mem_cgroup_get_nr_swap_pages+0x3d/0xb0 [ 155758.148060] workingset_test_recent+0xda/0x1b0 [ 155758.157133] workingset_refault+0xca/0x1e0 [ 155758.165508] filemap_add_folio+0x4d/0x70 [ 155758.173538] page_cache_ra_unbounded+0xed/0x190 [ 155758.182919] page_cache_sync_ra+0xd6/0x1e0 [ 155758.191738] filemap_read+0x68d/0xdf0 [ 155758.199495] ? mlx5e_napi_poll+0x123/0x940 [ 155758.207981] ? __napi_schedule+0x55/0x90 [ 155758.216095] __x64_sys_pread64+0x1d6/0x2c0 [ 155758.224601] do_syscall_64+0x3d/0x80 [ 155758.232058] entry_SYSCALL_64_after_hwframe+0x46/0xb0 [ 155758.242473] RIP: 0033:0x7f62c29153b5 [ 155758.249938] Code: e8 48 89 75 f0 89 7d f8 48 89 4d e0 e8 b4 e6 f7 ff 41 89 c0 4c 8b 55 e0 48 8b 55 e8 48 8b 75 f0 8b 7d f8 b8 11 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 45 f8 e8 e7 e6 f7 ff 48 8b [ 155758.288005] RSP: 002b:00007f6234c5ffd0 EFLAGS: 00000293 ORIG_RAX: 0000000000000011 [ 155758.303474] RAX: ffffffffffffffda RBX: 00007f628c4e70c0 RCX: 00007f62c29153b5 [ 155758.318075] RDX: 000000000003c041 RSI: 00007f61d2986000 RDI: 0000000000000076 [ 155758.332678] RBP: 00007f6234c5fff0 R08: 0000000000000000 R09: 0000000064d5230c [ 155758.347452] R10: 000000000027d450 R11: 0000000000000293 R12: 000000000003c041 [ 155758.362044] R13: 00007f61d2986000 R14: 00007f629e11b060 R15: 000000000027d450 [ 155758.376661] </TASK> This patch fixes the issue by moving the memcg's id publication from the alloc stage to ---truncated--- CVE-2023-53621 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53621.html CVE-2023-53621 https://bugzilla.suse.com/1251323 SUSE Bug 1251323 In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix possible data races in gfs2_show_options() Some fields such as gt_logd_secs of the struct gfs2_tune are accessed without holding the lock gt_spin in gfs2_show_options(): val = sdp->sd_tune.gt_logd_secs; if (val != 30) seq_printf(s, ",commit=%d", val); And thus can cause data races when gfs2_show_options() and other functions such as gfs2_reconfigure() are concurrently executed: spin_lock(&gt->gt_spin); gt->gt_logd_secs = newargs->ar_commit; To fix these possible data races, the lock sdp->sd_tune.gt_spin is acquired before accessing the fields of gfs2_tune and released after these accesses. Further changes by Andreas: - Don't hold the spin lock over the seq_printf operations. CVE-2023-53622 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53622.html CVE-2023-53622 https://bugzilla.suse.com/1251777 SUSE Bug 1251777 In the Linux kernel, the following vulnerability has been resolved: platform/x86: dell-sysman: Fix reference leak If a duplicate attribute is found using kset_find_obj(), a reference to that attribute is returned. This means that we need to dispose it accordingly. Use kobject_put() to dispose the duplicate attribute in such a case. Compile-tested only. CVE-2023-53631 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53631.html CVE-2023-53631 https://bugzilla.suse.com/1251529 SUSE Bug 1251529 In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Take RTNL lock when needed before calling xdp_set_features() Hold RTNL lock when calling xdp_set_features() with a registered netdev, as the call triggers the netdev notifiers. This could happen when switching from uplink rep to nic profile for example. This resolves the following call trace: RTNL: assertion failed at net/core/dev.c (1953) WARNING: CPU: 6 PID: 112670 at net/core/dev.c:1953 call_netdevice_notifiers_info+0x7c/0x80 Modules linked in: sch_mqprio sch_mqprio_lib act_tunnel_key act_mirred act_skbedit cls_matchall nfnetlink_cttimeout act_gact cls_flower sch_ingress bonding ib_umad ip_gre rdma_ucm mlx5_vfio_pci ipip tunnel4 ip6_gre gre mlx5_ib vfio_pci vfio_pci_core vfio_iommu_type1 ib_uverbs vfio mlx5_core ib_ipoib geneve nf_tables ip6_tunnel tunnel6 iptable_raw openvswitch nsh rpcrdma ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_cm ib_core xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry overlay zram zsmalloc fuse [last unloaded: ib_uverbs] CPU: 6 PID: 112670 Comm: devlink Not tainted 6.4.0-rc7_for_upstream_min_debug_2023_06_28_17_02 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:call_netdevice_notifiers_info+0x7c/0x80 Code: 90 ff 80 3d 2d 6b f7 00 00 75 c5 ba a1 07 00 00 48 c7 c6 e4 ce 0b 82 48 c7 c7 c8 f4 04 82 c6 05 11 6b f7 00 01 e8 a4 7c 8e ff <0f> 0b eb a2 0f 1f 44 00 00 55 48 89 e5 41 54 48 83 e4 f0 48 83 ec RSP: 0018:ffff8882a21c3948 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffffffff82e6f880 RCX: 0000000000000027 RDX: ffff88885f99b5c8 RSI: 0000000000000001 RDI: ffff88885f99b5c0 RBP: 0000000000000028 R08: ffff88887ffabaa8 R09: 0000000000000003 R10: ffff88887fecbac0 R11: ffff88887ff7bac0 R12: ffff8882a21c3968 R13: ffff88811c018940 R14: 0000000000000000 R15: ffff8881274401a0 FS: 00007fe141c81800(0000) GS:ffff88885f980000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f787c28b948 CR3: 000000014bcf3005 CR4: 0000000000370ea0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? __warn+0x79/0x120 ? call_netdevice_notifiers_info+0x7c/0x80 ? report_bug+0x17c/0x190 ? handle_bug+0x3c/0x60 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? call_netdevice_notifiers_info+0x7c/0x80 ? call_netdevice_notifiers_info+0x7c/0x80 call_netdevice_notifiers+0x2e/0x50 mlx5e_set_xdp_feature+0x21/0x50 [mlx5_core] mlx5e_nic_init+0xf1/0x1a0 [mlx5_core] mlx5e_netdev_init_profile+0x76/0x110 [mlx5_core] mlx5e_netdev_attach_profile+0x1f/0x90 [mlx5_core] mlx5e_netdev_change_profile+0x92/0x160 [mlx5_core] mlx5e_netdev_attach_nic_profile+0x1b/0x30 [mlx5_core] mlx5e_vport_rep_unload+0xaa/0xc0 [mlx5_core] __esw_offloads_unload_rep+0x52/0x60 [mlx5_core] mlx5_esw_offloads_rep_unload+0x52/0x70 [mlx5_core] esw_offloads_unload_rep+0x34/0x70 [mlx5_core] esw_offloads_disable+0x2b/0x90 [mlx5_core] mlx5_eswitch_disable_locked+0x1b9/0x210 [mlx5_core] mlx5_devlink_eswitch_mode_set+0xf5/0x630 [mlx5_core] ? devlink_get_from_attrs_lock+0x9e/0x110 devlink_nl_cmd_eswitch_set_doit+0x60/0xe0 genl_family_rcv_msg_doit.isra.0+0xc2/0x110 genl_rcv_msg+0x17d/0x2b0 ? devlink_get_from_attrs_lock+0x110/0x110 ? devlink_nl_cmd_eswitch_get_doit+0x290/0x290 ? devlink_pernet_pre_exit+0xf0/0xf0 ? genl_family_rcv_msg_doit.isra.0+0x110/0x110 netlink_rcv_skb+0x54/0x100 genl_rcv+0x24/0x40 netlink_unicast+0x1f6/0x2c0 netlink_sendmsg+0x232/0x4a0 sock_sendmsg+0x38/0x60 ? _copy_from_user+0x2a/0x60 __sys_sendto+0x110/0x160 ? __count_memcg_events+0x48/0x90 ? handle_mm_fault+0x161/0x260 ? do_user_addr_fault+0x278/0x6e0 __x64_sys_sendto+0x20/0x30 do_syscall_64+0x3d/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033 ---truncated--- CVE-2023-53632 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53632.html CVE-2023-53632 https://bugzilla.suse.com/1251269 SUSE Bug 1251269 In the Linux kernel, the following vulnerability has been resolved: accel/qaic: Fix a leak in map_user_pages() If get_user_pages_fast() allocates some pages but not as many as we wanted, then the current code leaks those pages. Call put_page() on the pages before returning. CVE-2023-53633 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53633.html CVE-2023-53633 https://bugzilla.suse.com/1251746 SUSE Bug 1251746 In the Linux kernel, the following vulnerability has been resolved: octeon_ep: cancel queued works in probe error path If it fails to get the devices's MAC address, octep_probe exits while leaving the delayed work intr_poll_task queued. When the work later runs, it's a use after free. Move the cancelation of intr_poll_task from octep_remove into octep_device_cleanup. This does not change anything in the octep_remove flow, but octep_device_cleanup is called also in the octep_probe error path, where the cancelation is needed. Note that the cancelation of ctrl_mbox_task has to follow intr_poll_task's, because the ctrl_mbox_task may be queued by intr_poll_task. CVE-2023-53638 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53638.html CVE-2023-53638 https://bugzilla.suse.com/1251328 SUSE Bug 1251328 In the Linux kernel, the following vulnerability has been resolved: bpf: Make bpf_refcount_acquire fallible for non-owning refs This patch fixes an incorrect assumption made in the original bpf_refcount series [0], specifically that the BPF program calling bpf_refcount_acquire on some node can always guarantee that the node is alive. In that series, the patch adding failure behavior to rbtree_add and list_push_{front, back} breaks this assumption for non-owning references. Consider the following program: n = bpf_kptr_xchg(&mapval, NULL); /* skip error checking */ bpf_spin_lock(&l); if(bpf_rbtree_add(&t, &n->rb, less)) { bpf_refcount_acquire(n); /* Failed to add, do something else with the node */ } bpf_spin_unlock(&l); It's incorrect to assume that bpf_refcount_acquire will always succeed in this scenario. bpf_refcount_acquire is being called in a critical section here, but the lock being held is associated with rbtree t, which isn't necessarily the lock associated with the tree that the node is already in. So after bpf_rbtree_add fails to add the node and calls bpf_obj_drop in it, the program has no ownership of the node's lifetime. Therefore the node's refcount can be decr'd to 0 at any time after the failing rbtree_add. If this happens before the refcount_acquire above, the node might be free'd, and regardless refcount_acquire will be incrementing a 0 refcount. Later patches in the series exercise this scenario, resulting in the expected complaint from the kernel (without this patch's changes): refcount_t: addition on 0; use-after-free. WARNING: CPU: 1 PID: 207 at lib/refcount.c:25 refcount_warn_saturate+0xbc/0x110 Modules linked in: bpf_testmod(O) CPU: 1 PID: 207 Comm: test_progs Tainted: G O 6.3.0-rc7-02231-g723de1a718a2-dirty #371 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 RIP: 0010:refcount_warn_saturate+0xbc/0x110 Code: 6f 64 f6 02 01 e8 84 a3 5c ff 0f 0b eb 9d 80 3d 5e 64 f6 02 00 75 94 48 c7 c7 e0 13 d2 82 c6 05 4e 64 f6 02 01 e8 64 a3 5c ff <0f> 0b e9 7a ff ff ff 80 3d 38 64 f6 02 00 0f 85 6d ff ff ff 48 c7 RSP: 0018:ffff88810b9179b0 EFLAGS: 00010082 RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000 RDX: 0000000000000202 RSI: 0000000000000008 RDI: ffffffff857c3680 RBP: ffff88810027d3c0 R08: ffffffff8125f2a4 R09: ffff88810b9176e7 R10: ffffed1021722edc R11: 746e756f63666572 R12: ffff88810027d388 R13: ffff88810027d3c0 R14: ffffc900005fe030 R15: ffffc900005fe048 FS: 00007fee0584a700(0000) GS:ffff88811b280000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005634a96f6c58 CR3: 0000000108ce9002 CR4: 0000000000770ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> bpf_refcount_acquire_impl+0xb5/0xc0 (rest of output snipped) The patch addresses this by changing bpf_refcount_acquire_impl to use refcount_inc_not_zero instead of refcount_inc and marking bpf_refcount_acquire KF_RET_NULL. For owning references, though, we know the above scenario is not possible and thus that bpf_refcount_acquire will always succeed. Some verifier bookkeeping is added to track "is input owning ref?" for bpf_refcount_acquire calls and return false from is_kfunc_ret_null for bpf_refcount_acquire on owning refs despite it being marked KF_RET_NULL. Existing selftests using bpf_refcount_acquire are modified where necessary to NULL-check its return value. [0]: https://lore.kernel.org/bpf/20230415201811.343116-1-davemarchevsky@fb.com/ CVE-2023-53645 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53645.html CVE-2023-53645 https://bugzilla.suse.com/1251321 SUSE Bug 1251321 In the Linux kernel, the following vulnerability has been resolved: drm/i915/perf: add sentinel to xehp_oa_b_counters Arrays passed to reg_in_range_table should end with empty record. The patch solves KASAN detected bug with signature: BUG: KASAN: global-out-of-bounds in xehp_is_valid_b_counter_addr+0x2c7/0x350 [i915] Read of size 4 at addr ffffffffa1555d90 by task perf/1518 CPU: 4 PID: 1518 Comm: perf Tainted: G U 6.4.0-kasan_438-g3303d06107f3+ #1 Hardware name: Intel Corporation Meteor Lake Client Platform/MTL-P DDR5 SODIMM SBS RVP, BIOS MTLPFWI1.R00.3223.D80.2305311348 05/31/2023 Call Trace: <TASK> ... xehp_is_valid_b_counter_addr+0x2c7/0x350 [i915] (cherry picked from commit 2f42c5afb34b5696cf5fe79e744f99be9b218798) CVE-2023-53646 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53646.html CVE-2023-53646 https://bugzilla.suse.com/1251742 SUSE Bug 1251742 In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Don't dereference ACPI root object handle Since the commit referenced in the Fixes: tag below the VMBus client driver is walking the ACPI namespace up from the VMBus ACPI device to the ACPI namespace root object trying to find Hyper-V MMIO ranges. However, if it is not able to find them it ends trying to walk resources of the ACPI namespace root object itself. This object has all-ones handle, which causes a NULL pointer dereference in the ACPI code (from dereferencing this pointer with an offset). This in turn causes an oops on boot with VMBus host implementations that do not provide Hyper-V MMIO ranges in their VMBus ACPI device or its ancestors. The QEMU VMBus implementation is an example of such implementation. I guess providing these ranges is optional, since all tested Windows versions seem to be able to use VMBus devices without them. Fix this by explicitly terminating the lookup at the ACPI namespace root object. Note that Linux guests under KVM/QEMU do not use the Hyper-V PV interface by default - they only do so if the KVM PV interface is missing or disabled. Example stack trace of such oops: [ 3.710827] ? __die+0x1f/0x60 [ 3.715030] ? page_fault_oops+0x159/0x460 [ 3.716008] ? exc_page_fault+0x73/0x170 [ 3.716959] ? asm_exc_page_fault+0x22/0x30 [ 3.717957] ? acpi_ns_lookup+0x7a/0x4b0 [ 3.718898] ? acpi_ns_internalize_name+0x79/0xc0 [ 3.720018] acpi_ns_get_node_unlocked+0xb5/0xe0 [ 3.721120] ? acpi_ns_check_object_type+0xfe/0x200 [ 3.722285] ? acpi_rs_convert_aml_to_resource+0x37/0x6e0 [ 3.723559] ? down_timeout+0x3a/0x60 [ 3.724455] ? acpi_ns_get_node+0x3a/0x60 [ 3.725412] acpi_ns_get_node+0x3a/0x60 [ 3.726335] acpi_ns_evaluate+0x1c3/0x2c0 [ 3.727295] acpi_ut_evaluate_object+0x64/0x1b0 [ 3.728400] acpi_rs_get_method_data+0x2b/0x70 [ 3.729476] ? vmbus_platform_driver_probe+0x1d0/0x1d0 [hv_vmbus] [ 3.730940] ? vmbus_platform_driver_probe+0x1d0/0x1d0 [hv_vmbus] [ 3.732411] acpi_walk_resources+0x78/0xd0 [ 3.733398] vmbus_platform_driver_probe+0x9f/0x1d0 [hv_vmbus] [ 3.734802] platform_probe+0x3d/0x90 [ 3.735684] really_probe+0x19b/0x400 [ 3.736570] ? __device_attach_driver+0x100/0x100 [ 3.737697] __driver_probe_device+0x78/0x160 [ 3.738746] driver_probe_device+0x1f/0x90 [ 3.739743] __driver_attach+0xc2/0x1b0 [ 3.740671] bus_for_each_dev+0x70/0xc0 [ 3.741601] bus_add_driver+0x10e/0x210 [ 3.742527] driver_register+0x55/0xf0 [ 3.744412] ? 0xffffffffc039a000 [ 3.745207] hv_acpi_init+0x3c/0x1000 [hv_vmbus] CVE-2023-53647 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53647.html CVE-2023-53647 https://bugzilla.suse.com/1251732 SUSE Bug 1251732 In the Linux kernel, the following vulnerability has been resolved: ALSA: ac97: Fix possible NULL dereference in snd_ac97_mixer smatch error: sound/pci/ac97/ac97_codec.c:2354 snd_ac97_mixer() error: we previously assumed 'rac97' could be null (see line 2072) remove redundant assignment, return error if rac97 is NULL. CVE-2023-53648 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53648.html CVE-2023-53648 https://bugzilla.suse.com/1251750 SUSE Bug 1251750 In the Linux kernel, the following vulnerability has been resolved: perf trace: Really free the evsel->priv area In 3cb4d5e00e037c70 ("perf trace: Free syscall tp fields in evsel->priv") it only was freeing if strcmp(evsel->tp_format->system, "syscalls") returned zero, while the corresponding initialization of evsel->priv was being performed if it was _not_ zero, i.e. if the tp system wasn't 'syscalls'. Just stop looking for that and free it if evsel->priv was set, which should be equivalent. Also use the pre-existing evsel_trace__delete() function. This resolves these leaks, detected with: $ make EXTRA_CFLAGS="-fsanitize=address" BUILD_BPF_SKEL=1 CORESIGHT=1 O=/tmp/build/perf-tools-next -C tools/perf install-bin ================================================================= ==481565==ERROR: LeakSanitizer: detected memory leaks Direct leak of 40 byte(s) in 1 object(s) allocated from: #0 0x7f7343cba097 in calloc (/lib64/libasan.so.8+0xba097) #1 0x987966 in zalloc (/home/acme/bin/perf+0x987966) #2 0x52f9b9 in evsel_trace__new /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:307 #3 0x52f9b9 in evsel__syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:333 #4 0x52f9b9 in evsel__init_raw_syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:458 #5 0x52f9b9 in perf_evsel__raw_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:480 #6 0x540e8b in trace__add_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:3212 #7 0x540e8b in trace__run /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:3891 #8 0x540e8b in cmd_trace /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:5156 #9 0x5ef262 in run_builtin /home/acme/git/perf-tools-next/tools/perf/perf.c:323 #10 0x4196da in handle_internal_command /home/acme/git/perf-tools-next/tools/perf/perf.c:377 #11 0x4196da in run_argv /home/acme/git/perf-tools-next/tools/perf/perf.c:421 #12 0x4196da in main /home/acme/git/perf-tools-next/tools/perf/perf.c:537 #13 0x7f7342c4a50f in __libc_start_call_main (/lib64/libc.so.6+0x2750f) Direct leak of 40 byte(s) in 1 object(s) allocated from: #0 0x7f7343cba097 in calloc (/lib64/libasan.so.8+0xba097) #1 0x987966 in zalloc (/home/acme/bin/perf+0x987966) #2 0x52f9b9 in evsel_trace__new /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:307 #3 0x52f9b9 in evsel__syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:333 #4 0x52f9b9 in evsel__init_raw_syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:458 #5 0x52f9b9 in perf_evsel__raw_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:480 #6 0x540dd1 in trace__add_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:3205 #7 0x540dd1 in trace__run /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:3891 #8 0x540dd1 in cmd_trace /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:5156 #9 0x5ef262 in run_builtin /home/acme/git/perf-tools-next/tools/perf/perf.c:323 #10 0x4196da in handle_internal_command /home/acme/git/perf-tools-next/tools/perf/perf.c:377 #11 0x4196da in run_argv /home/acme/git/perf-tools-next/tools/perf/perf.c:421 #12 0x4196da in main /home/acme/git/perf-tools-next/tools/perf/perf.c:537 #13 0x7f7342c4a50f in __libc_start_call_main (/lib64/libc.so.6+0x2750f) SUMMARY: AddressSanitizer: 80 byte(s) leaked in 2 allocation(s). [root@quaco ~]# With this we plug all leaks with "perf trace sleep 1". CVE-2023-53649 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53649.html CVE-2023-53649 https://bugzilla.suse.com/1251749 SUSE Bug 1251749 In the Linux kernel, the following vulnerability has been resolved: fbdev: omapfb: lcd_mipid: Fix an error handling path in mipid_spi_probe() If 'mipid_detect()' fails, we must free 'md' to avoid a memory leak. CVE-2023-53650 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53650.html CVE-2023-53650 https://bugzilla.suse.com/1251283 SUSE Bug 1251283 In the Linux kernel, the following vulnerability has been resolved: vdpa: Add features attr to vdpa_nl_policy for nlattr length check The vdpa_nl_policy structure is used to validate the nlattr when parsing the incoming nlmsg. It will ensure the attribute being described produces a valid nlattr pointer in info->attrs before entering into each handler in vdpa_nl_ops. That is to say, the missing part in vdpa_nl_policy may lead to illegal nlattr after parsing, which could lead to OOB read just like CVE-2023-3773. This patch adds the missing nla_policy for vdpa features attr to avoid such bugs. CVE-2023-53652 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53652.html CVE-2023-53652 https://bugzilla.suse.com/1251754 SUSE Bug 1251754 In the Linux kernel, the following vulnerability has been resolved: media: amphion: fix REVERSE_INULL issues reported by coverity null-checking of a pointor is suggested before dereferencing it CVE-2023-53653 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53653.html CVE-2023-53653 https://bugzilla.suse.com/1251755 SUSE Bug 1251755 In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: Add validation before accessing cgx and lmac with the addition of new MAC blocks like CN10K RPM and CN10KB RPM_USX, LMACs are noncontiguous and CGX blocks are also noncontiguous. But during RVU driver initialization, the driver is assuming they are contiguous and trying to access cgx or lmac with their id which is resulting in kernel panic. This patch fixes the issue by adding proper checks. [ 23.219150] pc : cgx_lmac_read+0x38/0x70 [ 23.219154] lr : rvu_program_channels+0x3f0/0x498 [ 23.223852] sp : ffff000100d6fc80 [ 23.227158] x29: ffff000100d6fc80 x28: ffff00010009f880 x27: 000000000000005a [ 23.234288] x26: ffff000102586768 x25: 0000000000002500 x24: fffffffffff0f000 CVE-2023-53654 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53654.html CVE-2023-53654 https://bugzilla.suse.com/1251756 SUSE Bug 1251756 In the Linux kernel, the following vulnerability has been resolved: drivers/perf: hisi: Don't migrate perf to the CPU going to teardown The driver needs to migrate the perf context if the current using CPU going to teardown. By the time calling the cpuhp::teardown() callback the cpu_online_mask() hasn't updated yet and still includes the CPU going to teardown. In current driver's implementation we may migrate the context to the teardown CPU and leads to the below calltrace: ... [ 368.104662][ T932] task:cpuhp/0 state:D stack: 0 pid: 15 ppid: 2 flags:0x00000008 [ 368.113699][ T932] Call trace: [ 368.116834][ T932] __switch_to+0x7c/0xbc [ 368.120924][ T932] __schedule+0x338/0x6f0 [ 368.125098][ T932] schedule+0x50/0xe0 [ 368.128926][ T932] schedule_preempt_disabled+0x18/0x24 [ 368.134229][ T932] __mutex_lock.constprop.0+0x1d4/0x5dc [ 368.139617][ T932] __mutex_lock_slowpath+0x1c/0x30 [ 368.144573][ T932] mutex_lock+0x50/0x60 [ 368.148579][ T932] perf_pmu_migrate_context+0x84/0x2b0 [ 368.153884][ T932] hisi_pcie_pmu_offline_cpu+0x90/0xe0 [hisi_pcie_pmu] [ 368.160579][ T932] cpuhp_invoke_callback+0x2a0/0x650 [ 368.165707][ T932] cpuhp_thread_fun+0xe4/0x190 [ 368.170316][ T932] smpboot_thread_fn+0x15c/0x1a0 [ 368.175099][ T932] kthread+0x108/0x13c [ 368.179012][ T932] ret_from_fork+0x10/0x18 ... Use function cpumask_any_but() to find one correct active cpu to fixes this issue. CVE-2023-53656 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53656.html CVE-2023-53656 https://bugzilla.suse.com/1251758 SUSE Bug 1251758 In the Linux kernel, the following vulnerability has been resolved: ice: Don't tx before switchdev is fully configured There is possibility that ice_eswitch_port_start_xmit might be called while some resources are still not allocated which might cause NULL pointer dereference. Fix this by checking if switchdev configuration was finished. CVE-2023-53657 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53657.html CVE-2023-53657 https://bugzilla.suse.com/1251319 SUSE Bug 1251319 In the Linux kernel, the following vulnerability has been resolved: spi: bcm-qspi: return error if neither hif_mspi nor mspi is available If neither a "hif_mspi" nor "mspi" resource is present, the driver will just early exit in probe but still return success. Apart from not doing anything meaningful, this would then also lead to a null pointer access on removal, as platform_get_drvdata() would return NULL, which it would then try to dereference when trying to unregister the spi master. Fix this by unconditionally calling devm_ioremap_resource(), as it can handle a NULL res and will then return a viable ERR_PTR() if we get one. The "return 0;" was previously a "goto qspi_resource_err;" where then ret was returned, but since ret was still initialized to 0 at this place this was a valid conversion in 63c5395bb7a9 ("spi: bcm-qspi: Fix use-after-free on unbind"). The issue was not introduced by this commit, only made more obvious. CVE-2023-53658 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53658.html CVE-2023-53658 https://bugzilla.suse.com/1251759 SUSE Bug 1251759 In the Linux kernel, the following vulnerability has been resolved: iavf: Fix out-of-bounds when setting channels on remove If we set channels greater during iavf_remove(), and waiting reset done would be timeout, then returned with error but changed num_active_queues directly, that will lead to OOB like the following logs. Because the num_active_queues is greater than tx/rx_rings[] allocated actually. Reproducer: [root@host ~]# cat repro.sh #!/bin/bash pf_dbsf="0000:41:00.0" vf0_dbsf="0000:41:02.0" g_pids=() function do_set_numvf() { echo 2 >/sys/bus/pci/devices/${pf_dbsf}/sriov_numvfs sleep $((RANDOM%3+1)) echo 0 >/sys/bus/pci/devices/${pf_dbsf}/sriov_numvfs sleep $((RANDOM%3+1)) } function do_set_channel() { local nic=$(ls -1 --indicator-style=none /sys/bus/pci/devices/${vf0_dbsf}/net/) [ -z "$nic" ] && { sleep $((RANDOM%3)) ; return 1; } ifconfig $nic 192.168.18.5 netmask 255.255.255.0 ifconfig $nic up ethtool -L $nic combined 1 ethtool -L $nic combined 4 sleep $((RANDOM%3)) } function on_exit() { local pid for pid in "${g_pids[@]}"; do kill -0 "$pid" &>/dev/null && kill "$pid" &>/dev/null done g_pids=() } trap "on_exit; exit" EXIT while :; do do_set_numvf ; done & g_pids+=($!) while :; do do_set_channel ; done & g_pids+=($!) wait Result: [ 3506.152887] iavf 0000:41:02.0: Removing device [ 3510.400799] ================================================================== [ 3510.400820] BUG: KASAN: slab-out-of-bounds in iavf_free_all_tx_resources+0x156/0x160 [iavf] [ 3510.400823] Read of size 8 at addr ffff88b6f9311008 by task repro.sh/55536 [ 3510.400823] [ 3510.400830] CPU: 101 PID: 55536 Comm: repro.sh Kdump: loaded Tainted: G O --------- -t - 4.18.0 #1 [ 3510.400832] Hardware name: Powerleader PR2008AL/H12DSi-N6, BIOS 2.0 04/09/2021 [ 3510.400835] Call Trace: [ 3510.400851] dump_stack+0x71/0xab [ 3510.400860] print_address_description+0x6b/0x290 [ 3510.400865] ? iavf_free_all_tx_resources+0x156/0x160 [iavf] [ 3510.400868] kasan_report+0x14a/0x2b0 [ 3510.400873] iavf_free_all_tx_resources+0x156/0x160 [iavf] [ 3510.400880] iavf_remove+0x2b6/0xc70 [iavf] [ 3510.400884] ? iavf_free_all_rx_resources+0x160/0x160 [iavf] [ 3510.400891] ? wait_woken+0x1d0/0x1d0 [ 3510.400895] ? notifier_call_chain+0xc1/0x130 [ 3510.400903] pci_device_remove+0xa8/0x1f0 [ 3510.400910] device_release_driver_internal+0x1c6/0x460 [ 3510.400916] pci_stop_bus_device+0x101/0x150 [ 3510.400919] pci_stop_and_remove_bus_device+0xe/0x20 [ 3510.400924] pci_iov_remove_virtfn+0x187/0x420 [ 3510.400927] ? pci_iov_add_virtfn+0xe10/0xe10 [ 3510.400929] ? pci_get_subsys+0x90/0x90 [ 3510.400932] sriov_disable+0xed/0x3e0 [ 3510.400936] ? bus_find_device+0x12d/0x1a0 [ 3510.400953] i40e_free_vfs+0x754/0x1210 [i40e] [ 3510.400966] ? i40e_reset_all_vfs+0x880/0x880 [i40e] [ 3510.400968] ? pci_get_device+0x7c/0x90 [ 3510.400970] ? pci_get_subsys+0x90/0x90 [ 3510.400982] ? pci_vfs_assigned.part.7+0x144/0x210 [ 3510.400987] ? __mutex_lock_slowpath+0x10/0x10 [ 3510.400996] i40e_pci_sriov_configure+0x1fa/0x2e0 [i40e] [ 3510.401001] sriov_numvfs_store+0x214/0x290 [ 3510.401005] ? sriov_totalvfs_show+0x30/0x30 [ 3510.401007] ? __mutex_lock_slowpath+0x10/0x10 [ 3510.401011] ? __check_object_size+0x15a/0x350 [ 3510.401018] kernfs_fop_write+0x280/0x3f0 [ 3510.401022] vfs_write+0x145/0x440 [ 3510.401025] ksys_write+0xab/0x160 [ 3510.401028] ? __ia32_sys_read+0xb0/0xb0 [ 3510.401031] ? fput_many+0x1a/0x120 [ 3510.401032] ? filp_close+0xf0/0x130 [ 3510.401038] do_syscall_64+0xa0/0x370 [ 3510.401041] ? page_fault+0x8/0x30 [ 3510.401043] entry_SYSCALL_64_after_hwframe+0x65/0xca [ 3510.401073] RIP: 0033:0x7f3a9bb842c0 [ 3510.401079] Code: 73 01 c3 48 8b 0d d8 cb 2c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d 89 24 2d 00 00 75 10 b8 01 00 00 00 0f 05 <48> 3d ---truncated--- CVE-2023-53659 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53659.html CVE-2023-53659 https://bugzilla.suse.com/1251247 SUSE Bug 1251247 https://bugzilla.suse.com/1251248 SUSE Bug 1251248 In the Linux kernel, the following vulnerability has been resolved: bpf, cpumap: Handle skb as well when clean up ptr_ring The following warning was reported when running xdp_redirect_cpu with both skb-mode and stress-mode enabled: ------------[ cut here ]------------ Incorrect XDP memory type (-2128176192) usage WARNING: CPU: 7 PID: 1442 at net/core/xdp.c:405 Modules linked in: CPU: 7 PID: 1442 Comm: kworker/7:0 Tainted: G 6.5.0-rc2+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: events __cpu_map_entry_free RIP: 0010:__xdp_return+0x1e4/0x4a0 ...... Call Trace: <TASK> ? show_regs+0x65/0x70 ? __warn+0xa5/0x240 ? __xdp_return+0x1e4/0x4a0 ...... xdp_return_frame+0x4d/0x150 __cpu_map_entry_free+0xf9/0x230 process_one_work+0x6b0/0xb80 worker_thread+0x96/0x720 kthread+0x1a5/0x1f0 ret_from_fork+0x3a/0x70 ret_from_fork_asm+0x1b/0x30 </TASK> The reason for the warning is twofold. One is due to the kthread cpu_map_kthread_run() is stopped prematurely. Another one is __cpu_map_ring_cleanup() doesn't handle skb mode and treats skbs in ptr_ring as XDP frames. Prematurely-stopped kthread will be fixed by the preceding patch and ptr_ring will be empty when __cpu_map_ring_cleanup() is called. But as the comments in __cpu_map_ring_cleanup() said, handling and freeing skbs in ptr_ring as well to "catch any broken behaviour gracefully". CVE-2023-53660 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53660.html CVE-2023-53660 https://bugzilla.suse.com/1251721 SUSE Bug 1251721 In the Linux kernel, the following vulnerability has been resolved: ext4: fix memory leaks in ext4_fname_{setup_filename,prepare_lookup} If the filename casefolding fails, we'll be leaking memory from the fscrypt_name struct, namely from the 'crypto_buf.name' member. Make sure we free it in the error path on both ext4_fname_setup_filename() and ext4_fname_prepare_lookup() functions. CVE-2023-53662 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53662.html CVE-2023-53662 https://bugzilla.suse.com/1251282 SUSE Bug 1251282 In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Check instead of asserting on nested TSC scaling support Check for nested TSC scaling support on nested SVM VMRUN instead of asserting that TSC scaling is exposed to L1 if L1's MSR_AMD64_TSC_RATIO has diverged from KVM's default. Userspace can trigger the WARN at will by writing the MSR and then updating guest CPUID to hide the feature (modifying guest CPUID is allowed anytime before KVM_RUN). E.g. hacking KVM's state_test selftest to do vcpu_set_msr(vcpu, MSR_AMD64_TSC_RATIO, 0); vcpu_clear_cpuid_feature(vcpu, X86_FEATURE_TSCRATEMSR); after restoring state in a new VM+vCPU yields an endless supply of: ------------[ cut here ]------------ WARNING: CPU: 164 PID: 62565 at arch/x86/kvm/svm/nested.c:699 nested_vmcb02_prepare_control+0x3d6/0x3f0 [kvm_amd] Call Trace: <TASK> enter_svm_guest_mode+0x114/0x560 [kvm_amd] nested_svm_vmrun+0x260/0x330 [kvm_amd] vmrun_interception+0x29/0x30 [kvm_amd] svm_invoke_exit_handler+0x35/0x100 [kvm_amd] svm_handle_exit+0xe7/0x180 [kvm_amd] kvm_arch_vcpu_ioctl_run+0x1eab/0x2570 [kvm] kvm_vcpu_ioctl+0x4c9/0x5b0 [kvm] __se_sys_ioctl+0x7a/0xc0 __x64_sys_ioctl+0x21/0x30 do_syscall_64+0x41/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x45ca1b Note, the nested #VMEXIT path has the same flaw, but needs a different fix and will be handled separately. CVE-2023-53663 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53663.html CVE-2023-53663 https://bugzilla.suse.com/1251290 SUSE Bug 1251290 In the Linux kernel, the following vulnerability has been resolved: md: don't dereference mddev after export_rdev() Except for initial reference, mddev->kobject is referenced by rdev->kobject, and if the last rdev is freed, there is no guarantee that mddev is still valid. Hence mddev should not be used anymore after export_rdev(). This problem can be triggered by following test for mdadm at very low rate: New file: mdadm/tests/23rdev-lifetime devname=${dev0##*/} devt=`cat /sys/block/$devname/dev` pid="" runtime=2 clean_up_test() { pill -9 $pid echo clear > /sys/block/md0/md/array_state } trap 'clean_up_test' EXIT add_by_sysfs() { while true; do echo $devt > /sys/block/md0/md/new_dev done } remove_by_sysfs(){ while true; do echo remove > /sys/block/md0/md/dev-${devname}/state done } echo md0 > /sys/module/md_mod/parameters/new_array || die "create md0 failed" add_by_sysfs & pid="$pid $!" remove_by_sysfs & pid="$pid $!" sleep $runtime exit 0 Test cmd: ./test --save-logs --logdir=/tmp/ --keep-going --dev=loop --tests=23rdev-lifetime Test result: general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6bcb: 0000 [#4] PREEMPT SMP CPU: 0 PID: 1292 Comm: test Tainted: G D W 6.5.0-rc2-00121-g01e55c376936 #562 RIP: 0010:md_wakeup_thread+0x9e/0x320 [md_mod] Call Trace: <TASK> mddev_unlock+0x1b6/0x310 [md_mod] rdev_attr_store+0xec/0x190 [md_mod] sysfs_kf_write+0x52/0x70 kernfs_fop_write_iter+0x19a/0x2a0 vfs_write+0x3b5/0x770 ksys_write+0x74/0x150 __x64_sys_write+0x22/0x30 do_syscall_64+0x40/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd Fix this problem by don't dereference mddev after export_rdev(). CVE-2023-53665 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53665.html CVE-2023-53665 https://bugzilla.suse.com/1251270 SUSE Bug 1251270 In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd938x: fix missing mbhc init error handling MBHC initialisation can fail so add the missing error handling to avoid dereferencing an error pointer when later configuring the jack: Unable to handle kernel paging request at virtual address fffffffffffffff8 pc : wcd_mbhc_start+0x28/0x380 [snd_soc_wcd_mbhc] lr : wcd938x_codec_set_jack+0x28/0x48 [snd_soc_wcd938x] Call trace: wcd_mbhc_start+0x28/0x380 [snd_soc_wcd_mbhc] wcd938x_codec_set_jack+0x28/0x48 [snd_soc_wcd938x] snd_soc_component_set_jack+0x28/0x8c [snd_soc_core] qcom_snd_wcd_jack_setup+0x7c/0x19c [snd_soc_qcom_common] sc8280xp_snd_init+0x20/0x2c [snd_soc_sc8280xp] snd_soc_link_init+0x28/0x90 [snd_soc_core] snd_soc_bind_card+0x628/0xbfc [snd_soc_core] snd_soc_register_card+0xec/0x104 [snd_soc_core] devm_snd_soc_register_card+0x4c/0xa4 [snd_soc_core] sc8280xp_platform_probe+0xf0/0x108 [snd_soc_sc8280xp] CVE-2023-53666 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53666.html CVE-2023-53666 https://bugzilla.suse.com/1251760 SUSE Bug 1251760 In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix deadloop issue on reading trace_pipe Soft lockup occurs when reading file 'trace_pipe': watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [cat:4488] [...] RIP: 0010:ring_buffer_empty_cpu+0xed/0x170 RSP: 0018:ffff88810dd6fc48 EFLAGS: 00000246 RAX: 0000000000000000 RBX: 0000000000000246 RCX: ffffffff93d1aaeb RDX: ffff88810a280040 RSI: 0000000000000008 RDI: ffff88811164b218 RBP: ffff88811164b218 R08: 0000000000000000 R09: ffff88815156600f R10: ffffed102a2acc01 R11: 0000000000000001 R12: 0000000051651901 R13: 0000000000000000 R14: ffff888115e49500 R15: 0000000000000000 [...] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8d853c2000 CR3: 000000010dcd8000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: __find_next_entry+0x1a8/0x4b0 ? peek_next_entry+0x250/0x250 ? down_write+0xa5/0x120 ? down_write_killable+0x130/0x130 trace_find_next_entry_inc+0x3b/0x1d0 tracing_read_pipe+0x423/0xae0 ? tracing_splice_read_pipe+0xcb0/0xcb0 vfs_read+0x16b/0x490 ksys_read+0x105/0x210 ? __ia32_sys_pwrite64+0x200/0x200 ? switch_fpu_return+0x108/0x220 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x61/0xc6 Through the vmcore, I found it's because in tracing_read_pipe(), ring_buffer_empty_cpu() found some buffer is not empty but then it cannot read anything due to "rb_num_of_entries() == 0" always true, Then it infinitely loop the procedure due to user buffer not been filled, see following code path: tracing_read_pipe() { ... ... waitagain: tracing_wait_pipe() // 1. find non-empty buffer here trace_find_next_entry_inc() // 2. loop here try to find an entry __find_next_entry() ring_buffer_empty_cpu(); // 3. find non-empty buffer peek_next_entry() // 4. but peek always return NULL ring_buffer_peek() rb_buffer_peek() rb_get_reader_page() // 5. because rb_num_of_entries() == 0 always true here // then return NULL // 6. user buffer not been filled so goto 'waitgain' // and eventually leads to an deadloop in kernel!!! } By some analyzing, I found that when resetting ringbuffer, the 'entries' of its pages are not all cleared (see rb_reset_cpu()). Then when reducing the ringbuffer, and if some reduced pages exist dirty 'entries' data, they will be added into 'cpu_buffer->overrun' (see rb_remove_pages()), which cause wrong 'overrun' count and eventually cause the deadloop issue. To fix it, we need to clear every pages in rb_reset_cpu(). CVE-2023-53668 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53668.html CVE-2023-53668 https://bugzilla.suse.com/1251286 SUSE Bug 1251286 In the Linux kernel, the following vulnerability has been resolved: nvme-core: fix dev_pm_qos memleak Call dev_pm_qos_hide_latency_tolerance() in the error unwind patch to avoid following kmemleak:- blktests (master) # kmemleak-clear; ./check nvme/044; blktests (master) # kmemleak-scan ; kmemleak-show nvme/044 (Test bi-directional authentication) [passed] runtime 2.111s ... 2.124s unreferenced object 0xffff888110c46240 (size 96): comm "nvme", pid 33461, jiffies 4345365353 (age 75.586s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<0000000069ac2cec>] kmalloc_trace+0x25/0x90 [<000000006acc66d5>] dev_pm_qos_update_user_latency_tolerance+0x6f/0x100 [<00000000cc376ea7>] nvme_init_ctrl+0x38e/0x410 [nvme_core] [<000000007df61b4b>] 0xffffffffc05e88b3 [<00000000d152b985>] 0xffffffffc05744cb [<00000000f04a4041>] vfs_write+0xc5/0x3c0 [<00000000f9491baf>] ksys_write+0x5f/0xe0 [<000000001c46513d>] do_syscall_64+0x3b/0x90 [<00000000ecf348fe>] entry_SYSCALL_64_after_hwframe+0x72/0xdc CVE-2023-53670 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53670.html CVE-2023-53670 https://bugzilla.suse.com/1251762 SUSE Bug 1251762 In the Linux kernel, the following vulnerability has been resolved: btrfs: output extra debug info if we failed to find an inline backref [BUG] Syzbot reported several warning triggered inside lookup_inline_extent_backref(). [CAUSE] As usual, the reproducer doesn't reliably trigger locally here, but at least we know the WARN_ON() is triggered when an inline backref can not be found, and it can only be triggered when @insert is true. (I.e. inserting a new inline backref, which means the backref should already exist) [ENHANCEMENT] After the WARN_ON(), dump all the parameters and the extent tree leaf to help debug. CVE-2023-53672 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53672.html CVE-2023-53672 https://bugzilla.suse.com/1251780 SUSE Bug 1251780 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: call disconnect callback before deleting conn In hci_cs_disconnect, we do hci_conn_del even if disconnection failed. ISO, L2CAP and SCO connections refer to the hci_conn without hci_conn_get, so disconn_cfm must be called so they can clean up their conn, otherwise use-after-free occurs. ISO: ========================================================== iso_sock_connect:880: sk 00000000eabd6557 iso_connect_cis:356: 70:1a:b8:98:ff:a2 -> 28:3d:c2:4a:7e:da ... iso_conn_add:140: hcon 000000001696f1fd conn 00000000b6251073 hci_dev_put:1487: hci0 orig refcnt 17 __iso_chan_add:214: conn 00000000b6251073 iso_sock_clear_timer:117: sock 00000000eabd6557 state 3 ... hci_rx_work:4085: hci0 Event packet hci_event_packet:7601: hci0: event 0x0f hci_cmd_status_evt:4346: hci0: opcode 0x0406 hci_cs_disconnect:2760: hci0: status 0x0c hci_sent_cmd_data:3107: hci0 opcode 0x0406 hci_conn_del:1151: hci0 hcon 000000001696f1fd handle 2560 hci_conn_unlink:1102: hci0: hcon 000000001696f1fd hci_conn_drop:1451: hcon 00000000d8521aaf orig refcnt 2 hci_chan_list_flush:2780: hcon 000000001696f1fd hci_dev_put:1487: hci0 orig refcnt 21 hci_dev_put:1487: hci0 orig refcnt 20 hci_req_cmd_complete:3978: opcode 0x0406 status 0x0c ... <no iso_* activity on sk/conn> ... iso_sock_sendmsg:1098: sock 00000000dea5e2e0, sk 00000000eabd6557 BUG: kernel NULL pointer dereference, address: 0000000000000668 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-1.fc38 04/01/2014 RIP: 0010:iso_sock_sendmsg (net/bluetooth/iso.c:1112) bluetooth ========================================================== L2CAP: ================================================================== hci_cmd_status_evt:4359: hci0: opcode 0x0406 hci_cs_disconnect:2760: hci0: status 0x0c hci_sent_cmd_data:3085: hci0 opcode 0x0406 hci_conn_del:1151: hci0 hcon ffff88800c999000 handle 3585 hci_conn_unlink:1102: hci0: hcon ffff88800c999000 hci_chan_list_flush:2780: hcon ffff88800c999000 hci_chan_del:2761: hci0 hcon ffff88800c999000 chan ffff888018ddd280 ... BUG: KASAN: slab-use-after-free in hci_send_acl+0x2d/0x540 [bluetooth] Read of size 8 at addr ffff888018ddd298 by task bluetoothd/1175 CPU: 0 PID: 1175 Comm: bluetoothd Tainted: G E 6.4.0-rc4+ #2 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-1.fc38 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x5b/0x90 print_report+0xcf/0x670 ? __virt_addr_valid+0xf8/0x180 ? hci_send_acl+0x2d/0x540 [bluetooth] kasan_report+0xa8/0xe0 ? hci_send_acl+0x2d/0x540 [bluetooth] hci_send_acl+0x2d/0x540 [bluetooth] ? __pfx___lock_acquire+0x10/0x10 l2cap_chan_send+0x1fd/0x1300 [bluetooth] ? l2cap_sock_sendmsg+0xf2/0x170 [bluetooth] ? __pfx_l2cap_chan_send+0x10/0x10 [bluetooth] ? lock_release+0x1d5/0x3c0 ? mark_held_locks+0x1a/0x90 l2cap_sock_sendmsg+0x100/0x170 [bluetooth] sock_write_iter+0x275/0x280 ? __pfx_sock_write_iter+0x10/0x10 ? __pfx___lock_acquire+0x10/0x10 do_iter_readv_writev+0x176/0x220 ? __pfx_do_iter_readv_writev+0x10/0x10 ? find_held_lock+0x83/0xa0 ? selinux_file_permission+0x13e/0x210 do_iter_write+0xda/0x340 vfs_writev+0x1b4/0x400 ? __pfx_vfs_writev+0x10/0x10 ? __seccomp_filter+0x112/0x750 ? populate_seccomp_data+0x182/0x220 ? __fget_light+0xdf/0x100 ? do_writev+0x19d/0x210 do_writev+0x19d/0x210 ? __pfx_do_writev+0x10/0x10 ? mark_held_locks+0x1a/0x90 do_syscall_64+0x60/0x90 ? lockdep_hardirqs_on_prepare+0x149/0x210 ? do_syscall_64+0x6c/0x90 ? lockdep_hardirqs_on_prepare+0x149/0x210 entry_SYSCALL_64_after_hwframe+0x72/0xdc RIP: 0033:0x7ff45cb23e64 Code: 15 d1 1f 0d 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 80 3d 9d a7 0d 00 00 74 13 b8 14 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 28 89 54 24 1c 48 89 RSP: 002b:00007fff21ae09b8 EFLAGS: 00000202 ORIG_RAX: 0000000000000014 RAX: ffffffffffffffda RBX: ---truncated--- CVE-2023-53673 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53673.html CVE-2023-53673 https://bugzilla.suse.com/1251763 SUSE Bug 1251763 https://bugzilla.suse.com/1251983 SUSE Bug 1251983 In the Linux kernel, the following vulnerability has been resolved: clk: Fix memory leak in devm_clk_notifier_register() devm_clk_notifier_register() allocates a devres resource for clk notifier but didn't register that to the device, so the notifier didn't get unregistered on device detach and the allocated resource was leaked. Fix the issue by registering the resource through devres_add(). This issue was found with kmemleak on a Chromebook. CVE-2023-53674 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53674.html CVE-2023-53674 https://bugzilla.suse.com/1251764 SUSE Bug 1251764 In the Linux kernel, the following vulnerability has been resolved: bcache: Fix __bch_btree_node_alloc to make the failure behavior consistent In some specific situations, the return value of __bch_btree_node_alloc may be NULL. This may lead to a potential NULL pointer dereference in caller function like a calling chain : btree_split->bch_btree_node_alloc->__bch_btree_node_alloc. Fix it by initializing the return value in __bch_btree_node_alloc. CVE-2023-53681 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53681.html CVE-2023-53681 https://bugzilla.suse.com/1251769 SUSE Bug 1251769 In the Linux kernel, the following vulnerability has been resolved: net/handshake: fix null-ptr-deref in handshake_nl_done_doit() We should not call trace_handshake_cmd_done_err() if socket lookup has failed. Also we should call trace_handshake_cmd_done_err() before releasing the file, otherwise dereferencing sock->sk can return garbage. This also reverts 7afc6d0a107f ("net/handshake: Fix uninitialized local variable") Unable to handle kernel paging request at virtual address dfff800000000003 KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f] Mem abort info: ESR = 0x0000000096000005 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x05: level 1 translation fault Data abort info: ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [dfff800000000003] address between user and kernel address ranges Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP Modules linked in: CPU: 1 PID: 5986 Comm: syz-executor292 Not tainted 6.5.0-rc7-syzkaller-gfe4469582053 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023 pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : handshake_nl_done_doit+0x198/0x9c8 net/handshake/netlink.c:193 lr : handshake_nl_done_doit+0x180/0x9c8 sp : ffff800096e37180 x29: ffff800096e37200 x28: 1ffff00012dc6e34 x27: dfff800000000000 x26: ffff800096e373d0 x25: 0000000000000000 x24: 00000000ffffffa8 x23: ffff800096e373f0 x22: 1ffff00012dc6e38 x21: 0000000000000000 x20: ffff800096e371c0 x19: 0000000000000018 x18: 0000000000000000 x17: 0000000000000000 x16: ffff800080516cc4 x15: 0000000000000001 x14: 1fffe0001b14aa3b x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000003 x8 : 0000000000000003 x7 : ffff800080afe47c x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff800080a88078 x2 : 0000000000000001 x1 : 00000000ffffffa8 x0 : 0000000000000000 Call trace: handshake_nl_done_doit+0x198/0x9c8 net/handshake/netlink.c:193 genl_family_rcv_msg_doit net/netlink/genetlink.c:970 [inline] genl_family_rcv_msg net/netlink/genetlink.c:1050 [inline] genl_rcv_msg+0x96c/0xc50 net/netlink/genetlink.c:1067 netlink_rcv_skb+0x214/0x3c4 net/netlink/af_netlink.c:2549 genl_rcv+0x38/0x50 net/netlink/genetlink.c:1078 netlink_unicast_kernel net/netlink/af_netlink.c:1339 [inline] netlink_unicast+0x660/0x8d4 net/netlink/af_netlink.c:1365 netlink_sendmsg+0x834/0xb18 net/netlink/af_netlink.c:1914 sock_sendmsg_nosec net/socket.c:725 [inline] sock_sendmsg net/socket.c:748 [inline] ____sys_sendmsg+0x56c/0x840 net/socket.c:2494 ___sys_sendmsg net/socket.c:2548 [inline] __sys_sendmsg+0x26c/0x33c net/socket.c:2577 __do_sys_sendmsg net/socket.c:2586 [inline] __se_sys_sendmsg net/socket.c:2584 [inline] __arm64_sys_sendmsg+0x80/0x94 net/socket.c:2584 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 el0_svc+0x58/0x16c arch/arm64/kernel/entry-common.c:678 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591 Code: 12800108 b90043e8 910062b3 d343fe68 (387b6908) CVE-2023-53686 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53686.html CVE-2023-53686 https://bugzilla.suse.com/1251771 SUSE Bug 1251771 In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating clk When the best clk is searched, we iterate over all possible clk. If we find a better match, the previous one, if any, needs to be freed. If a better match has already been found, we still need to free the new one, otherwise it leaks. CVE-2023-53687 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53687.html CVE-2023-53687 https://bugzilla.suse.com/1251772 SUSE Bug 1251772 In the Linux kernel, the following vulnerability has been resolved: USB: gadget: Fix the memory leak in raw_gadget driver Currently, increasing raw_dev->count happens before invoke the raw_queue_event(), if the raw_queue_event() return error, invoke raw_release() will not trigger the dev_free() to be called. [ 268.905865][ T5067] raw-gadget.0 gadget.0: failed to queue event [ 268.912053][ T5067] udc dummy_udc.0: failed to start USB Raw Gadget: -12 [ 268.918885][ T5067] raw-gadget.0: probe of gadget.0 failed with error -12 [ 268.925956][ T5067] UDC core: USB Raw Gadget: couldn't find an available UDC or it's busy [ 268.934657][ T5067] misc raw-gadget: fail, usb_gadget_register_driver returned -16 BUG: memory leak [<ffffffff8154bf94>] kmalloc_trace+0x24/0x90 mm/slab_common.c:1076 [<ffffffff8347eb55>] kmalloc include/linux/slab.h:582 [inline] [<ffffffff8347eb55>] kzalloc include/linux/slab.h:703 [inline] [<ffffffff8347eb55>] dev_new drivers/usb/gadget/legacy/raw_gadget.c:191 [inline] [<ffffffff8347eb55>] raw_open+0x45/0x110 drivers/usb/gadget/legacy/raw_gadget.c:385 [<ffffffff827d1d09>] misc_open+0x1a9/0x1f0 drivers/char/misc.c:165 [<ffffffff8154bf94>] kmalloc_trace+0x24/0x90 mm/slab_common.c:1076 [<ffffffff8347cd2f>] kmalloc include/linux/slab.h:582 [inline] [<ffffffff8347cd2f>] raw_ioctl_init+0xdf/0x410 drivers/usb/gadget/legacy/raw_gadget.c:460 [<ffffffff8347dfe9>] raw_ioctl+0x5f9/0x1120 drivers/usb/gadget/legacy/raw_gadget.c:1250 [<ffffffff81685173>] vfs_ioctl fs/ioctl.c:51 [inline] [<ffffffff8154bf94>] kmalloc_trace+0x24/0x90 mm/slab_common.c:1076 [<ffffffff833ecc6a>] kmalloc include/linux/slab.h:582 [inline] [<ffffffff833ecc6a>] kzalloc include/linux/slab.h:703 [inline] [<ffffffff833ecc6a>] dummy_alloc_request+0x5a/0xe0 drivers/usb/gadget/udc/dummy_hcd.c:665 [<ffffffff833e9132>] usb_ep_alloc_request+0x22/0xd0 drivers/usb/gadget/udc/core.c:196 [<ffffffff8347f13d>] gadget_bind+0x6d/0x370 drivers/usb/gadget/legacy/raw_gadget.c:292 This commit therefore invoke kref_get() under the condition that raw_queue_event() return success. CVE-2023-53693 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53693.html CVE-2023-53693 https://bugzilla.suse.com/1252489 SUSE Bug 1252489 In the Linux kernel, the following vulnerability has been resolved: nvdimm: Fix memleak of pmu attr_groups in unregister_nvdimm_pmu() Memory pointed by 'nd_pmu->pmu.attr_groups' is allocated in function 'register_nvdimm_pmu' and is lost after 'kfree(nd_pmu)' call in function 'unregister_nvdimm_pmu'. CVE-2023-53697 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53697.html CVE-2023-53697 https://bugzilla.suse.com/1252534 SUSE Bug 1252534 In the Linux kernel, the following vulnerability has been resolved: xsk: fix refcount underflow in error path Fix a refcount underflow problem reported by syzbot that can happen when a system is running out of memory. If xp_alloc_tx_descs() fails, and it can only fail due to not having enough memory, then the error path is triggered. In this error path, the refcount of the pool is decremented as it has incremented before. However, the reference to the pool in the socket was not nulled. This means that when the socket is closed later, the socket teardown logic will think that there is a pool attached to the socket and try to decrease the refcount again, leading to a refcount underflow. I chose this fix as it involved adding just a single line. Another option would have been to move xp_get_pool() and the assignment of xs->pool to after the if-statement and using xs_umem->pool instead of xs->pool in the whole if-statement resulting in somewhat simpler code, but this would have led to much more churn in the code base perhaps making it harder to backport. CVE-2023-53698 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53698.html CVE-2023-53698 https://bugzilla.suse.com/1252479 SUSE Bug 1252479 In the Linux kernel, the following vulnerability has been resolved: riscv: move memblock_allow_resize() after linear mapping is ready The initial memblock metadata is accessed from kernel image mapping. The regions arrays need to "reallocated" from memblock and accessed through linear mapping to cover more memblock regions. So the resizing should not be allowed until linear mapping is ready. Note that there are memblock allocations when building linear mapping. This patch is similar to 24cc61d8cb5a ("arm64: memblock: don't permit memblock resizing until linear mapping is up"). In following log, many memblock regions are reserved before create_linear_mapping_page_table(). And then it triggered reallocation of memblock.reserved.regions and memcpy the old array in kernel image mapping to the new array in linear mapping which caused a page fault. [ 0.000000] memblock_reserve: [0x00000000bf01f000-0x00000000bf01ffff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf021000-0x00000000bf021fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf023000-0x00000000bf023fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf025000-0x00000000bf025fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf027000-0x00000000bf027fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf029000-0x00000000bf029fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf02b000-0x00000000bf02bfff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf02d000-0x00000000bf02dfff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf02f000-0x00000000bf02ffff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf030000-0x00000000bf030fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] OF: reserved mem: 0x0000000080000000..0x000000008007ffff (512 KiB) map non-reusable mmode_resv0@80000000 [ 0.000000] memblock_reserve: [0x00000000bf000000-0x00000000bf001fed] paging_init+0x19a/0x5ae [ 0.000000] memblock_phys_alloc_range: 4096 bytes align=0x1000 from=0x0000000000000000 max_addr=0x0000000000000000 alloc_pmd_fixmap+0x14/0x1c [ 0.000000] memblock_reserve: [0x000000017ffff000-0x000000017fffffff] memblock_alloc_range_nid+0xb8/0x128 [ 0.000000] memblock: reserved is doubled to 256 at [0x000000017fffd000-0x000000017fffe7ff] [ 0.000000] Unable to handle kernel paging request at virtual address ff600000ffffd000 [ 0.000000] Oops [#1] [ 0.000000] Modules linked in: [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 6.4.0-rc1-00011-g99a670b2069c #66 [ 0.000000] Hardware name: riscv-virtio,qemu (DT) [ 0.000000] epc : __memcpy+0x60/0xf8 [ 0.000000] ra : memblock_double_array+0x192/0x248 [ 0.000000] epc : ffffffff8081d214 ra : ffffffff80a3dfc0 sp : ffffffff81403bd0 [ 0.000000] gp : ffffffff814fbb38 tp : ffffffff8140dac0 t0 : 0000000001600000 [ 0.000000] t1 : 0000000000000000 t2 : 000000008f001000 s0 : ffffffff81403c60 [ 0.000000] s1 : ffffffff80c0bc98 a0 : ff600000ffffd000 a1 : ffffffff80c0bcd8 [ 0.000000] a2 : 0000000000000c00 a3 : ffffffff80c0c8d8 a4 : 0000000080000000 [ 0.000000] a5 : 0000000000080000 a6 : 0000000000000000 a7 : 0000000080200000 [ 0.000000] s2 : ff600000ffffd000 s3 : 0000000000002000 s4 : 0000000000000c00 [ 0.000000] s5 : ffffffff80c0bc60 s6 : ffffffff80c0bcc8 s7 : 0000000000000000 [ 0.000000] s8 : ffffffff814fd0a8 s9 : 000000017fffe7ff s10: 0000000000000000 [ 0.000000] s11: 0000000000001000 t3 : 0000000000001000 t4 : 0000000000000000 [ 0.000000] t5 : 000000008f003000 t6 : ff600000ffffd000 [ 0.000000] status: 0000000200000100 badaddr: ff600000ffffd000 cause: 000000000000000f [ 0.000000] [<fff ---truncated--- CVE-2023-53699 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53699.html CVE-2023-53699 https://bugzilla.suse.com/1252550 SUSE Bug 1252550 In the Linux kernel, the following vulnerability has been resolved: HID: amd_sfh: Fix for shift-out-of-bounds Shift operation of 'exp' and 'shift' variables exceeds the maximum number of shift values in the u32 range leading to UBSAN shift-out-of-bounds. ... [ 6.120512] UBSAN: shift-out-of-bounds in drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50 [ 6.120598] shift exponent 104 is too large for 64-bit type 'long unsigned int' [ 6.120659] CPU: 4 PID: 96 Comm: kworker/4:1 Not tainted 6.4.0amd_1-next-20230519-dirty #10 [ 6.120665] Hardware name: AMD Birman-PHX/Birman-PHX, BIOS SFH_with_HPD_SEN.FD 04/05/2023 [ 6.120667] Workqueue: events amd_sfh_work_buffer [amd_sfh] [ 6.120687] Call Trace: [ 6.120690] <TASK> [ 6.120694] dump_stack_lvl+0x48/0x70 [ 6.120704] dump_stack+0x10/0x20 [ 6.120707] ubsan_epilogue+0x9/0x40 [ 6.120716] __ubsan_handle_shift_out_of_bounds+0x10f/0x170 [ 6.120720] ? psi_group_change+0x25f/0x4b0 [ 6.120729] float_to_int.cold+0x18/0xba [amd_sfh] [ 6.120739] get_input_rep+0x57/0x340 [amd_sfh] [ 6.120748] ? __schedule+0xba7/0x1b60 [ 6.120756] ? __pfx_get_input_rep+0x10/0x10 [amd_sfh] [ 6.120764] amd_sfh_work_buffer+0x91/0x180 [amd_sfh] [ 6.120772] process_one_work+0x229/0x430 [ 6.120780] worker_thread+0x4a/0x3c0 [ 6.120784] ? __pfx_worker_thread+0x10/0x10 [ 6.120788] kthread+0xf7/0x130 [ 6.120792] ? __pfx_kthread+0x10/0x10 [ 6.120795] ret_from_fork+0x29/0x50 [ 6.120804] </TASK> ... Fix this by adding the condition to validate shift ranges. CVE-2023-53703 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53703.html CVE-2023-53703 https://bugzilla.suse.com/1252553 SUSE Bug 1252553 In the Linux kernel, the following vulnerability has been resolved: clk: imx: clk-imx8mp: improve error handling in imx8mp_clocks_probe() Replace of_iomap() and kzalloc() with devm_of_iomap() and devm_kzalloc() which can automatically release the related memory when the device or driver is removed or unloaded to avoid potential memory leak. In this case, iounmap(anatop_base) in line 427,433 are removed as manual release is not required. Besides, referring to clk-imx8mq.c, check the return code of of_clk_add_hw_provider, if it returns negtive, print error info and unregister hws, which makes the program more robust. CVE-2023-53704 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53704.html CVE-2023-53704 https://bugzilla.suse.com/1252490 SUSE Bug 1252490 In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1 The type of size is unsigned int, if size is 0x40000000, there will be an integer overflow, size will be zero after size *= sizeof(uint32_t), will cause uninitialized memory to be referenced later. CVE-2023-53707 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53707.html CVE-2023-53707 https://bugzilla.suse.com/1252632 SUSE Bug 1252632 In the Linux kernel, the following vulnerability has been resolved: ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects If a badly constructed firmware includes multiple `ACPI_TYPE_PACKAGE` objects while evaluating the AMD LPS0 _DSM, there will be a memory leak. Explicitly guard against this. CVE-2023-53708 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53708.html CVE-2023-53708 https://bugzilla.suse.com/1252537 SUSE Bug 1252537 In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a potential data corruption We must ensure that the subrequests are joined back into the head before we can retransmit a request. If the head was not on the commit lists, because the server wrote it synchronously, we still need to add it back to the retransmission list. Add a call that mirrors the effect of nfs_cancel_remove_inode() for O_DIRECT. CVE-2023-53711 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53711.html CVE-2023-53711 https://bugzilla.suse.com/1252536 SUSE Bug 1252536 In the Linux kernel, the following vulnerability has been resolved: arm64: sme: Use STR P to clear FFR context field in streaming SVE mode The FFR is a predicate register which can vary between 16 and 256 bits in size depending upon the configured vector length. When saving the SVE state in streaming SVE mode, the FFR register is inaccessible and so commit 9f5848665788 ("arm64/sve: Make access to FFR optional") simply clears the FFR field of the in-memory context structure. Unfortunately, it achieves this using an unconditional 8-byte store and so if the SME vector length is anything other than 64 bytes in size we will either fail to clear the entire field or, worse, we will corrupt memory immediately following the structure. This has led to intermittent kfence splats in CI [1] and can trigger kmalloc Redzone corruption messages when running the 'fp-stress' kselftest: | ============================================================================= | BUG kmalloc-1k (Not tainted): kmalloc Redzone overwritten | ----------------------------------------------------------------------------- | | 0xffff000809bf1e22-0xffff000809bf1e27 @offset=7714. First byte 0x0 instead of 0xcc | Allocated in do_sme_acc+0x9c/0x220 age=2613 cpu=1 pid=531 | __kmalloc+0x8c/0xcc | do_sme_acc+0x9c/0x220 | ... Replace the 8-byte store with a store of a predicate register which has been zero-initialised with PFALSE, ensuring that the entire field is cleared in memory. [1] https://lore.kernel.org/r/CA+G9fYtU7HsV0R0dp4XEH5xXHSJFw8KyDf5VQrLLfMxWfxQkag@mail.gmail.com CVE-2023-53713 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53713.html CVE-2023-53713 https://bugzilla.suse.com/1252559 SUSE Bug 1252559 https://bugzilla.suse.com/1253760 SUSE Bug 1253760 In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Do not swap cpu_buffer during resize process When ring_buffer_swap_cpu was called during resize process, the cpu buffer was swapped in the middle, resulting in incorrect state. Continuing to run in the wrong state will result in oops. This issue can be easily reproduced using the following two scripts: /tmp # cat test1.sh //#! /bin/sh for i in `seq 0 100000` do echo 2000 > /sys/kernel/debug/tracing/buffer_size_kb sleep 0.5 echo 5000 > /sys/kernel/debug/tracing/buffer_size_kb sleep 0.5 done /tmp # cat test2.sh //#! /bin/sh for i in `seq 0 100000` do echo irqsoff > /sys/kernel/debug/tracing/current_tracer sleep 1 echo nop > /sys/kernel/debug/tracing/current_tracer sleep 1 done /tmp # ./test1.sh & /tmp # ./test2.sh & A typical oops log is as follows, sometimes with other different oops logs. [ 231.711293] WARNING: CPU: 0 PID: 9 at kernel/trace/ring_buffer.c:2026 rb_update_pages+0x378/0x3f8 [ 231.713375] Modules linked in: [ 231.714735] CPU: 0 PID: 9 Comm: kworker/0:1 Tainted: G W 6.5.0-rc1-00276-g20edcec23f92 #15 [ 231.716750] Hardware name: linux,dummy-virt (DT) [ 231.718152] Workqueue: events update_pages_handler [ 231.719714] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 231.721171] pc : rb_update_pages+0x378/0x3f8 [ 231.722212] lr : rb_update_pages+0x25c/0x3f8 [ 231.723248] sp : ffff800082b9bd50 [ 231.724169] x29: ffff800082b9bd50 x28: ffff8000825f7000 x27: 0000000000000000 [ 231.726102] x26: 0000000000000001 x25: fffffffffffff010 x24: 0000000000000ff0 [ 231.728122] x23: ffff0000c3a0b600 x22: ffff0000c3a0b5c0 x21: fffffffffffffe0a [ 231.730203] x20: ffff0000c3a0b600 x19: ffff0000c0102400 x18: 0000000000000000 [ 231.732329] x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffffe7aa8510 [ 231.734212] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000002 [ 231.736291] x11: ffff8000826998a8 x10: ffff800082b9baf0 x9 : ffff800081137558 [ 231.738195] x8 : fffffc00030e82c8 x7 : 0000000000000000 x6 : 0000000000000001 [ 231.740192] x5 : ffff0000ffbafe00 x4 : 0000000000000000 x3 : 0000000000000000 [ 231.742118] x2 : 00000000000006aa x1 : 0000000000000001 x0 : ffff0000c0007208 [ 231.744196] Call trace: [ 231.744892] rb_update_pages+0x378/0x3f8 [ 231.745893] update_pages_handler+0x1c/0x38 [ 231.746893] process_one_work+0x1f0/0x468 [ 231.747852] worker_thread+0x54/0x410 [ 231.748737] kthread+0x124/0x138 [ 231.749549] ret_from_fork+0x10/0x20 [ 231.750434] ---[ end trace 0000000000000000 ]--- [ 233.720486] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [ 233.721696] Mem abort info: [ 233.721935] ESR = 0x0000000096000004 [ 233.722283] EC = 0x25: DABT (current EL), IL = 32 bits [ 233.722596] SET = 0, FnV = 0 [ 233.722805] EA = 0, S1PTW = 0 [ 233.723026] FSC = 0x04: level 0 translation fault [ 233.723458] Data abort info: [ 233.723734] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 [ 233.724176] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 233.724589] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 233.725075] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000104943000 [ 233.725592] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 [ 233.726231] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP [ 233.726720] Modules linked in: [ 233.727007] CPU: 0 PID: 9 Comm: kworker/0:1 Tainted: G W 6.5.0-rc1-00276-g20edcec23f92 #15 [ 233.727777] Hardware name: linux,dummy-virt (DT) [ 233.728225] Workqueue: events update_pages_handler [ 233.728655] pstate: 200000c5 (nzCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 233.729054] pc : rb_update_pages+0x1a8/0x3f8 [ 233.729334] lr : rb_update_pages+0x154/0x3f8 [ 233.729592] sp : ffff800082b9bd50 [ 233.729792] x29: ffff800082b9bd50 x28: ffff8000825f7000 x27: 00000000 ---truncated--- CVE-2023-53718 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53718.html CVE-2023-53718 https://bugzilla.suse.com/1252564 SUSE Bug 1252564 In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Fix a NULL pointer dereference in ath12k_mac_op_hw_scan() In ath12k_mac_op_hw_scan(), the return value of kzalloc() is directly used in memcpy(), which may lead to a NULL pointer dereference on failure of kzalloc(). Fix this bug by adding a check of arg.extraie.ptr. Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0-03427-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.15378.4 CVE-2023-53721 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53721.html CVE-2023-53721 https://bugzilla.suse.com/1252561 SUSE Bug 1252561 In the Linux kernel, the following vulnerability has been resolved: md: raid1: fix potential OOB in raid1_remove_disk() If rddev->raid_disk is greater than mddev->raid_disks, there will be an out-of-bounds in raid1_remove_disk(). We have already found similar reports as follows: 1) commit d17f744e883b ("md-raid10: fix KASAN warning") 2) commit 1ebc2cec0b7d ("dm raid: fix KASAN warning in raid5_remove_disk") Fix this bug by checking whether the "number" variable is valid. CVE-2023-53722 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53722.html CVE-2023-53722 https://bugzilla.suse.com/1252499 SUSE Bug 1252499 https://bugzilla.suse.com/1252500 SUSE Bug 1252500 In the Linux kernel, the following vulnerability has been resolved: clocksource/drivers/cadence-ttc: Fix memory leak in ttc_timer_probe Smatch reports: drivers/clocksource/timer-cadence-ttc.c:529 ttc_timer_probe() warn: 'timer_baseaddr' from of_iomap() not released on lines: 498,508,516. timer_baseaddr may have the problem of not being released after use, I replaced it with the devm_of_iomap() function and added the clk_put() function to cleanup the "clk_ce" and "clk_cs". CVE-2023-53725 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53725.html CVE-2023-53725 https://bugzilla.suse.com/1252492 SUSE Bug 1252492 In the Linux kernel, the following vulnerability has been resolved: arm64: csum: Fix OoB access in IP checksum code for negative lengths Although commit c2c24edb1d9c ("arm64: csum: Fix pathological zero-length calls") added an early return for zero-length input, syzkaller has popped up with an example of a _negative_ length which causes an undefined shift and an out-of-bounds read: | BUG: KASAN: slab-out-of-bounds in do_csum+0x44/0x254 arch/arm64/lib/csum.c:39 | Read of size 4294966928 at addr ffff0000d7ac0170 by task syz-executor412/5975 | | CPU: 0 PID: 5975 Comm: syz-executor412 Not tainted 6.4.0-rc4-syzkaller-g908f31f2a05b #0 | Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023 | Call trace: | dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:233 | show_stack+0x2c/0x44 arch/arm64/kernel/stacktrace.c:240 | __dump_stack lib/dump_stack.c:88 [inline] | dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106 | print_address_description mm/kasan/report.c:351 [inline] | print_report+0x174/0x514 mm/kasan/report.c:462 | kasan_report+0xd4/0x130 mm/kasan/report.c:572 | kasan_check_range+0x264/0x2a4 mm/kasan/generic.c:187 | __kasan_check_read+0x20/0x30 mm/kasan/shadow.c:31 | do_csum+0x44/0x254 arch/arm64/lib/csum.c:39 | csum_partial+0x30/0x58 lib/checksum.c:128 | gso_make_checksum include/linux/skbuff.h:4928 [inline] | __udp_gso_segment+0xaf4/0x1bc4 net/ipv4/udp_offload.c:332 | udp6_ufo_fragment+0x540/0xca0 net/ipv6/udp_offload.c:47 | ipv6_gso_segment+0x5cc/0x1760 net/ipv6/ip6_offload.c:119 | skb_mac_gso_segment+0x2b4/0x5b0 net/core/gro.c:141 | __skb_gso_segment+0x250/0x3d0 net/core/dev.c:3401 | skb_gso_segment include/linux/netdevice.h:4859 [inline] | validate_xmit_skb+0x364/0xdbc net/core/dev.c:3659 | validate_xmit_skb_list+0x94/0x130 net/core/dev.c:3709 | sch_direct_xmit+0xe8/0x548 net/sched/sch_generic.c:327 | __dev_xmit_skb net/core/dev.c:3805 [inline] | __dev_queue_xmit+0x147c/0x3318 net/core/dev.c:4210 | dev_queue_xmit include/linux/netdevice.h:3085 [inline] | packet_xmit+0x6c/0x318 net/packet/af_packet.c:276 | packet_snd net/packet/af_packet.c:3081 [inline] | packet_sendmsg+0x376c/0x4c98 net/packet/af_packet.c:3113 | sock_sendmsg_nosec net/socket.c:724 [inline] | sock_sendmsg net/socket.c:747 [inline] | __sys_sendto+0x3b4/0x538 net/socket.c:2144 Extend the early return to reject negative lengths as well, aligning our implementation with the generic code in lib/checksum.c CVE-2023-53726 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53726.html CVE-2023-53726 https://bugzilla.suse.com/1252565 SUSE Bug 1252565 In the Linux kernel, the following vulnerability has been resolved: net/sched: fq_pie: avoid stalls in fq_pie_timer() When setting a high number of flows (limit being 65536), fq_pie_timer() is currently using too much time as syzbot reported. Add logic to yield the cpu every 2048 flows (less than 150 usec on debug kernels). It should also help by not blocking qdisc fast paths for too long. Worst case (65536 flows) would need 31 jiffies for a complete scan. Relevant extract from syzbot report: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-.... } 2663 jiffies s: 873 root: 0x1/. rcu: blocking rcu_node structures (internal RCU debug): Sending NMI from CPU 1 to CPUs 0: NMI backtrace for cpu 0 CPU: 0 PID: 5177 Comm: syz-executor273 Not tainted 6.5.0-syzkaller-00453-g727dbda16b83 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023 RIP: 0010:check_kcov_mode kernel/kcov.c:173 [inline] RIP: 0010:write_comp_data+0x21/0x90 kernel/kcov.c:236 Code: 2e 0f 1f 84 00 00 00 00 00 65 8b 05 01 b2 7d 7e 49 89 f1 89 c6 49 89 d2 81 e6 00 01 00 00 49 89 f8 65 48 8b 14 25 80 b9 03 00 <a9> 00 01 ff 00 74 0e 85 f6 74 59 8b 82 04 16 00 00 85 c0 74 4f 8b RSP: 0018:ffffc90000007bb8 EFLAGS: 00000206 RAX: 0000000000000101 RBX: ffffc9000dc0d140 RCX: ffffffff885893b0 RDX: ffff88807c075940 RSI: 0000000000000100 RDI: 0000000000000001 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc9000dc0d178 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 0000555555d54380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f6b442f6130 CR3: 000000006fe1c000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <NMI> </NMI> <IRQ> pie_calculate_probability+0x480/0x850 net/sched/sch_pie.c:415 fq_pie_timer+0x1da/0x4f0 net/sched/sch_fq_pie.c:387 call_timer_fn+0x1a0/0x580 kernel/time/timer.c:1700 CVE-2023-53727 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53727.html CVE-2023-53727 https://bugzilla.suse.com/1252566 SUSE Bug 1252566 In the Linux kernel, the following vulnerability has been resolved: posix-timers: Ensure timer ID search-loop limit is valid posix_timer_add() tries to allocate a posix timer ID by starting from the cached ID which was stored by the last successful allocation. This is done in a loop searching the ID space for a free slot one by one. The loop has to terminate when the search wrapped around to the starting point. But that's racy vs. establishing the starting point. That is read out lockless, which leads to the following problem: CPU0 CPU1 posix_timer_add() start = sig->posix_timer_id; lock(hash_lock); ... posix_timer_add() if (++sig->posix_timer_id < 0) start = sig->posix_timer_id; sig->posix_timer_id = 0; So CPU1 can observe a negative start value, i.e. -1, and the loop break never happens because the condition can never be true: if (sig->posix_timer_id == start) break; While this is unlikely to ever turn into an endless loop as the ID space is huge (INT_MAX), the racy read of the start value caught the attention of KCSAN and Dmitry unearthed that incorrectness. Rewrite it so that all id operations are under the hash lock. CVE-2023-53728 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53728.html CVE-2023-53728 https://bugzilla.suse.com/1252668 SUSE Bug 1252668 In the Linux kernel, the following vulnerability has been resolved: soc: qcom: qmi_encdec: Restrict string length in decode The QMI TLV value for strings in a lot of qmi element info structures account for null terminated strings with MAX_LEN + 1. If a string is actually MAX_LEN + 1 length, this will cause an out of bounds access when the NULL character is appended in decoding. CVE-2023-53729 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53729.html CVE-2023-53729 https://bugzilla.suse.com/1252496 SUSE Bug 1252496 In the Linux kernel, the following vulnerability has been resolved: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled when unlock. DEADLOCK might happen if we have held other locks and disabled IRQ before invoking it. Fix it by using spin_lock_irqsave() instead, which can keep IRQ state consistent with before when unlock. ================================ WARNING: inconsistent lock state 5.10.0-02758-g8e5f91fd772f #26 Not tainted -------------------------------- inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage. kworker/2:3/388 [HC0[0]:SC0[0]:HE0:SE1] takes: ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spin_lock_irq ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfq_bio_merge+0x141/0x390 {IN-HARDIRQ-W} state was registered at: __lock_acquire+0x3d7/0x1070 lock_acquire+0x197/0x4a0 __raw_spin_lock_irqsave _raw_spin_lock_irqsave+0x3b/0x60 bfq_idle_slice_timer_body bfq_idle_slice_timer+0x53/0x1d0 __run_hrtimer+0x477/0xa70 __hrtimer_run_queues+0x1c6/0x2d0 hrtimer_interrupt+0x302/0x9e0 local_apic_timer_interrupt __sysvec_apic_timer_interrupt+0xfd/0x420 run_sysvec_on_irqstack_cond sysvec_apic_timer_interrupt+0x46/0xa0 asm_sysvec_apic_timer_interrupt+0x12/0x20 irq event stamp: 837522 hardirqs last enabled at (837521): [<ffffffff84b9419d>] __raw_spin_unlock_irqrestore hardirqs last enabled at (837521): [<ffffffff84b9419d>] _raw_spin_unlock_irqrestore+0x3d/0x40 hardirqs last disabled at (837522): [<ffffffff84b93fa3>] __raw_spin_lock_irq hardirqs last disabled at (837522): [<ffffffff84b93fa3>] _raw_spin_lock_irq+0x43/0x50 softirqs last enabled at (835852): [<ffffffff84e00558>] __do_softirq+0x558/0x8ec softirqs last disabled at (835845): [<ffffffff84c010ff>] asm_call_irq_on_stack+0xf/0x20 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&bfqd->lock); <Interrupt> lock(&bfqd->lock); *** DEADLOCK *** 3 locks held by kworker/2:3/388: #0: ffff888107af0f38 ((wq_completion)kthrotld){+.+.}-{0:0}, at: process_one_work+0x742/0x13f0 #1: ffff8881176bfdd8 ((work_completion)(&td->dispatch_work)){+.+.}-{0:0}, at: process_one_work+0x777/0x13f0 #2: ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spin_lock_irq #2: ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfq_bio_merge+0x141/0x390 stack backtrace: CPU: 2 PID: 388 Comm: kworker/2:3 Not tainted 5.10.0-02758-g8e5f91fd772f #26 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Workqueue: kthrotld blk_throtl_dispatch_work_fn Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x107/0x167 print_usage_bug valid_state mark_lock_irq.cold+0x32/0x3a mark_lock+0x693/0xbc0 mark_held_locks+0x9e/0xe0 __trace_hardirqs_on_caller lockdep_hardirqs_on_prepare.part.0+0x151/0x360 trace_hardirqs_on+0x5b/0x180 __raw_spin_unlock_irq _raw_spin_unlock_irq+0x24/0x40 spin_unlock_irq adjust_inuse_and_calc_cost+0x4fb/0x970 ioc_rqos_merge+0x277/0x740 __rq_qos_merge+0x62/0xb0 rq_qos_merge bio_attempt_back_merge+0x12c/0x4a0 blk_mq_sched_try_merge+0x1b6/0x4d0 bfq_bio_merge+0x24a/0x390 __blk_mq_sched_bio_merge+0xa6/0x460 blk_mq_sched_bio_merge blk_mq_submit_bio+0x2e7/0x1ee0 __submit_bio_noacct_mq+0x175/0x3b0 submit_bio_noacct+0x1fb/0x270 blk_throtl_dispatch_work_fn+0x1ef/0x2b0 process_one_work+0x83e/0x13f0 process_scheduled_works worker_thread+0x7e3/0xd80 kthread+0x353/0x470 ret_from_fork+0x1f/0x30 CVE-2023-53730 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53730.html CVE-2023-53730 https://bugzilla.suse.com/1252495 SUSE Bug 1252495 In the Linux kernel, the following vulnerability has been resolved: netlink: fix potential deadlock in netlink_set_err() syzbot reported a possible deadlock in netlink_set_err() [1] A similar issue was fixed in commit 1d482e666b8e ("netlink: disable IRQs for netlink_lock_table()") in netlink_lock_table() This patch adds IRQ safety to netlink_set_err() and __netlink_diag_dump() which were not covered by cited commit. [1] WARNING: possible irq lock inversion dependency detected 6.4.0-rc6-syzkaller-00240-g4e9f0ec38852 #0 Not tainted syz-executor.2/23011 just changed the state of lock: ffffffff8e1a7a58 (nl_table_lock){.+.?}-{2:2}, at: netlink_set_err+0x2e/0x3a0 net/netlink/af_netlink.c:1612 but this lock was taken by another, SOFTIRQ-safe lock in the past: (&local->queue_stop_reason_lock){..-.}-{2:2} and interrupts could create inverse lock ordering between them. other info that might help us debug this: Possible interrupt unsafe locking scenario: CPU0 CPU1 ---- ---- lock(nl_table_lock); local_irq_disable(); lock(&local->queue_stop_reason_lock); lock(nl_table_lock); <Interrupt> lock(&local->queue_stop_reason_lock); *** DEADLOCK *** CVE-2023-53731 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53731.html CVE-2023-53731 https://bugzilla.suse.com/1252481 SUSE Bug 1252481 In the Linux kernel, the following vulnerability has been resolved: net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode When u32_replace_hw_knode fails, we need to undo the tcf_bind_filter operation done at u32_set_parms. CVE-2023-53733 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2023-53733.html CVE-2023-53733 https://bugzilla.suse.com/1252685 SUSE Bug 1252685 In the Linux kernel, the following vulnerability has been resolved: net: tls: handle backlogging of crypto requests Since we're setting the CRYPTO_TFM_REQ_MAY_BACKLOG flag on our requests to the crypto API, crypto_aead_{encrypt,decrypt} can return -EBUSY instead of -EINPROGRESS in valid situations. For example, when the cryptd queue for AESNI is full (easy to trigger with an artificially low cryptd.cryptd_max_cpu_qlen), requests will be enqueued to the backlog but still processed. In that case, the async callback will also be called twice: first with err == -EINPROGRESS, which it seems we can just ignore, then with err == 0. Compared to Sabrina's original patch this version uses the new tls_*crypt_async_wait() helpers and converts the EBUSY to EINPROGRESS to avoid having to modify all the error handling paths. The handling is identical. CVE-2024-26584 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2024-26584.html CVE-2024-26584 https://bugzilla.suse.com/1220186 SUSE Bug 1220186 In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier. CVE-2024-58240 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2024-58240.html CVE-2024-58240 https://bugzilla.suse.com/1248847 SUSE Bug 1248847 In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: fix race condition in unaccepted memory handling The page allocator tracks the number of zones that have unaccepted memory using static_branch_enc/dec() and uses that static branch in hot paths to determine if it needs to deal with unaccepted memory. Borislav and Thomas pointed out that the tracking is racy: operations on static_branch are not serialized against adding/removing unaccepted pages to/from the zone. Sanity checks inside static_branch machinery detects it: WARNING: CPU: 0 PID: 10 at kernel/jump_label.c:276 __static_key_slow_dec_cpuslocked+0x8e/0xa0 The comment around the WARN() explains the problem: /* * Warn about the '-1' case though; since that means a * decrement is concurrent with a first (0->1) increment. IOW * people are trying to disable something that wasn't yet fully * enabled. This suggests an ordering problem on the user side. */ The effect of this static_branch optimization is only visible on microbenchmark. Instead of adding more complexity around it, remove it altogether. CVE-2025-38008 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38008.html CVE-2025-38008 https://bugzilla.suse.com/1244939 SUSE Bug 1244939 In the Linux kernel, the following vulnerability has been resolved: netlink: Fix wraparounds of sk->sk_rmem_alloc. Netlink has this pattern in some places if (atomic_read(&sk->sk_rmem_alloc) > sk->sk_rcvbuf) atomic_add(skb->truesize, &sk->sk_rmem_alloc); , which has the same problem fixed by commit 5a465a0da13e ("udp: Fix multiple wraparounds of sk->sk_rmem_alloc."). For example, if we set INT_MAX to SO_RCVBUFFORCE, the condition is always false as the two operands are of int. Then, a single socket can eat as many skb as possible until OOM happens, and we can see multiple wraparounds of sk->sk_rmem_alloc. Let's fix it by using atomic_add_return() and comparing the two variables as unsigned int. Before: [root@fedora ~]# ss -f netlink Recv-Q Send-Q Local Address:Port Peer Address:Port -1668710080 0 rtnl:nl_wraparound/293 * After: [root@fedora ~]# ss -f netlink Recv-Q Send-Q Local Address:Port Peer Address:Port 2147483072 0 rtnl:nl_wraparound/290 * ^ `--- INT_MAX - 576 CVE-2025-38465 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38465.html CVE-2025-38465 https://bugzilla.suse.com/1247118 SUSE Bug 1247118 In the Linux kernel, the following vulnerability has been resolved: tracing: Add down_write(trace_event_sem) when adding trace event When a module is loaded, it adds trace events defined by the module. It may also need to modify the modules trace printk formats to replace enum names with their values. If two modules are loaded at the same time, the adding of the event to the ftrace_events list can corrupt the walking of the list in the code that is modifying the printk format strings and crash the kernel. The addition of the event should take the trace_event_sem for write while it adds the new event. Also add a lockdep_assert_held() on that semaphore in __trace_add_event_dirs() as it iterates the list. CVE-2025-38539 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38539.html CVE-2025-38539 https://bugzilla.suse.com/1248211 SUSE Bug 1248211 In the Linux kernel, the following vulnerability has been resolved: mptcp: plug races between subflow fail and subflow creation We have races similar to the one addressed by the previous patch between subflow failing and additional subflow creation. They are just harder to trigger. The solution is similar. Use a separate flag to track the condition 'socket state prevent any additional subflow creation' protected by the fallback lock. The socket fallback makes such flag true, and also receiving or sending an MP_FAIL option. The field 'allow_infinite_fallback' is now always touched under the relevant lock, we can drop the ONCE annotation on write. CVE-2025-38552 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38552.html CVE-2025-38552 https://bugzilla.suse.com/1248230 SUSE Bug 1248230 In the Linux kernel, the following vulnerability has been resolved: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al Check pde->proc_ops->proc_lseek directly may cause UAF in rmmod scenario. It's a gap in proc_reg_open() after commit 654b33ada4ab("proc: fix UAF in proc_get_inode()"). Followed by AI Viro's suggestion, fix it in same manner. CVE-2025-38653 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38653.html CVE-2025-38653 https://bugzilla.suse.com/1248630 SUSE Bug 1248630 In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() The buffer length check before calling uvc_parse_format() only ensured that the buffer has at least 3 bytes (buflen > 2), buf the function accesses buffer[3], requiring at least 4 bytes. This can lead to an out-of-bounds read if the buffer has exactly 3 bytes. Fix it by checking that the buffer has at least 4 bytes in uvc_parse_format(). CVE-2025-38680 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38680.html CVE-2025-38680 https://bugzilla.suse.com/1249203 SUSE Bug 1249203 In the Linux kernel, the following vulnerability has been resolved: mm/ptdump: take the memory hotplug lock inside ptdump_walk_pgd() Memory hot remove unmaps and tears down various kernel page table regions as required. The ptdump code can race with concurrent modifications of the kernel page tables. When leaf entries are modified concurrently, the dump code may log stale or inconsistent information for a VA range, but this is otherwise not harmful. But when intermediate levels of kernel page table are freed, the dump code will continue to use memory that has been freed and potentially reallocated for another purpose. In such cases, the ptdump code may dereference bogus addresses, leading to a number of potential problems. To avoid the above mentioned race condition, platforms such as arm64, riscv and s390 take memory hotplug lock, while dumping kernel page table via the sysfs interface /sys/kernel/debug/kernel_page_tables. Similar race condition exists while checking for pages that might have been marked W+X via /sys/kernel/debug/kernel_page_tables/check_wx_pages which in turn calls ptdump_check_wx(). Instead of solving this race condition again, let's just move the memory hotplug lock inside generic ptdump_check_wx() which will benefit both the scenarios. Drop get_online_mems() and put_online_mems() combination from all existing platform ptdump code paths. CVE-2025-38681 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38681.html CVE-2025-38681 https://bugzilla.suse.com/1249204 SUSE Bug 1249204 In the Linux kernel, the following vulnerability has been resolved: hv_netvsc: Fix panic during namespace deletion with VF The existing code move the VF NIC to new namespace when NETDEV_REGISTER is received on netvsc NIC. During deletion of the namespace, default_device_exit_batch() >> default_device_exit_net() is called. When netvsc NIC is moved back and registered to the default namespace, it automatically brings VF NIC back to the default namespace. This will cause the default_device_exit_net() >> for_each_netdev_safe loop unable to detect the list end, and hit NULL ptr: [ 231.449420] mana 7870:00:00.0 enP30832s1: Moved VF to namespace with: eth0 [ 231.449656] BUG: kernel NULL pointer dereference, address: 0000000000000010 [ 231.450246] #PF: supervisor read access in kernel mode [ 231.450579] #PF: error_code(0x0000) - not-present page [ 231.450916] PGD 17b8a8067 P4D 0 [ 231.451163] Oops: Oops: 0000 [#1] SMP NOPTI [ 231.451450] CPU: 82 UID: 0 PID: 1394 Comm: kworker/u768:1 Not tainted 6.16.0-rc4+ #3 VOLUNTARY [ 231.452042] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 11/21/2024 [ 231.452692] Workqueue: netns cleanup_net [ 231.452947] RIP: 0010:default_device_exit_batch+0x16c/0x3f0 [ 231.453326] Code: c0 0c f5 b3 e8 d5 db fe ff 48 85 c0 74 15 48 c7 c2 f8 fd ca b2 be 10 00 00 00 48 8d 7d c0 e8 7b 77 25 00 49 8b 86 28 01 00 00 <48> 8b 50 10 4c 8b 2a 4c 8d 62 f0 49 83 ed 10 4c 39 e0 0f 84 d6 00 [ 231.454294] RSP: 0018:ff75fc7c9bf9fd00 EFLAGS: 00010246 [ 231.454610] RAX: 0000000000000000 RBX: 0000000000000002 RCX: 61c8864680b583eb [ 231.455094] RDX: ff1fa9f71462d800 RSI: ff75fc7c9bf9fd38 RDI: 0000000030766564 [ 231.455686] RBP: ff75fc7c9bf9fd78 R08: 0000000000000000 R09: 0000000000000000 [ 231.456126] R10: 0000000000000001 R11: 0000000000000004 R12: ff1fa9f70088e340 [ 231.456621] R13: ff1fa9f70088e340 R14: ffffffffb3f50c20 R15: ff1fa9f7103e6340 [ 231.457161] FS: 0000000000000000(0000) GS:ff1faa6783a08000(0000) knlGS:0000000000000000 [ 231.457707] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 231.458031] CR2: 0000000000000010 CR3: 0000000179ab2006 CR4: 0000000000b73ef0 [ 231.458434] Call Trace: [ 231.458600] <TASK> [ 231.458777] ops_undo_list+0x100/0x220 [ 231.459015] cleanup_net+0x1b8/0x300 [ 231.459285] process_one_work+0x184/0x340 To fix it, move the ns change to a workqueue, and take rtnl_lock to avoid changing the netdev list when default_device_exit_net() is using it. CVE-2025-38683 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38683.html CVE-2025-38683 https://bugzilla.suse.com/1249159 SUSE Bug 1249159 In the Linux kernel, the following vulnerability has been resolved: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit This issue triggers when a userspace program does an ioctl FBIOPUT_CON2FBMAP by passing console number and frame buffer number. Ideally this maps console to frame buffer and updates the screen if console is visible. As part of mapping it has to do resize of console according to frame buffer info. if this resize fails and returns from vc_do_resize() and continues further. At this point console and new frame buffer are mapped and sets display vars. Despite failure still it continue to proceed updating the screen at later stages where vc_data is related to previous frame buffer and frame buffer info and display vars are mapped to new frame buffer and eventully leading to out-of-bounds write in fast_imageblit(). This bheviour is excepted only when fg_console is equal to requested console which is a visible console and updates screen with invalid struct references in fbcon_putcs(). CVE-2025-38685 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38685.html CVE-2025-38685 https://bugzilla.suse.com/1249220 SUSE Bug 1249220 https://bugzilla.suse.com/1249240 SUSE Bug 1249240 In the Linux kernel, the following vulnerability has been resolved: comedi: fix race between polling and detaching syzbot reports a use-after-free in comedi in the below link, which is due to comedi gladly removing the allocated async area even though poll requests are still active on the wait_queue_head inside of it. This can cause a use-after-free when the poll entries are later triggered or removed, as the memory for the wait_queue_head has been freed. We need to check there are no tasks queued on any of the subdevices' wait queues before allowing the device to be detached by the `COMEDI_DEVCONFIG` ioctl. Tasks will read-lock `dev->attach_lock` before adding themselves to the subdevice wait queue, so fix the problem in the `COMEDI_DEVCONFIG` ioctl handler by write-locking `dev->attach_lock` before checking that all of the subdevices are safe to be deleted. This includes testing for any sleepers on the subdevices' wait queues. It remains locked until the device has been detached. This requires the `comedi_device_detach()` function to be refactored slightly, moving the bulk of it into new function `comedi_device_detach_locked()`. Note that the refactor of `comedi_device_detach()` results in `comedi_device_cancel_all()` now being called while `dev->attach_lock` is write-locked, which wasn't the case previously, but that does not matter. Thanks to Jens Axboe for diagnosing the problem and co-developing this patch. CVE-2025-38687 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38687.html CVE-2025-38687 https://bugzilla.suse.com/1249177 SUSE Bug 1249177 In the Linux kernel, the following vulnerability has been resolved: pNFS: Fix uninited ptr deref in block/scsi layout The error occurs on the third attempt to encode extents. When function ext_tree_prepare_commit() reallocates a larger buffer to retry encoding extents, the "layoutupdate_pages" page array is initialized only after the retry loop. But ext_tree_free_commitdata() is called on every iteration and tries to put pages in the array, thus dereferencing uninitialized pointers. An additional problem is that there is no limit on the maximum possible buffer_size. When there are too many extents, the client may create a layoutcommit that is larger than the maximum possible RPC size accepted by the server. During testing, we observed two typical scenarios. First, one memory page for extents is enough when we work with small files, append data to the end of the file, or preallocate extents before writing. But when we fill a new large file without preallocating, the number of extents can be huge, and counting the number of written extents in ext_tree_encode_commit() does not help much. Since this number increases even more between unlocking and locking of ext_tree, the reallocated buffer may not be large enough again and again. CVE-2025-38691 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38691.html CVE-2025-38691 https://bugzilla.suse.com/1249215 SUSE Bug 1249215 In the Linux kernel, the following vulnerability has been resolved: exfat: add cluster chain loop check for dir An infinite loop may occur if the following conditions occur due to file system corruption. (1) Condition for exfat_count_dir_entries() to loop infinitely. - The cluster chain includes a loop. - There is no UNUSED entry in the cluster chain. (2) Condition for exfat_create_upcase_table() to loop infinitely. - The cluster chain of the root directory includes a loop. - There are no UNUSED entry and up-case table entry in the cluster chain of the root directory. (3) Condition for exfat_load_bitmap() to loop infinitely. - The cluster chain of the root directory includes a loop. - There are no UNUSED entry and bitmap entry in the cluster chain of the root directory. (4) Condition for exfat_find_dir_entry() to loop infinitely. - The cluster chain includes a loop. - The unused directory entries were exhausted by some operation. (5) Condition for exfat_check_dir_empty() to loop infinitely. - The cluster chain includes a loop. - The unused directory entries were exhausted by some operation. - All files and sub-directories under the directory are deleted. This commit adds checks to break the above infinite loop. CVE-2025-38692 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38692.html CVE-2025-38692 https://bugzilla.suse.com/1249221 SUSE Bug 1249221 https://bugzilla.suse.com/1249239 SUSE Bug 1249239 In the Linux kernel, the following vulnerability has been resolved: media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and w7090p_tuner_read_serpar In w7090p_tuner_write_serpar, msg is controlled by user. When msg[0].buf is null and msg[0].len is zero, former checks on msg[0].buf would be passed. If accessing msg[0].buf[2] without sanity check, null pointer deref would happen. We add check on msg[0].len to prevent crash. Similar commit: commit 0ed554fd769a ("media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()") CVE-2025-38693 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38693.html CVE-2025-38693 https://bugzilla.suse.com/1249190 SUSE Bug 1249190 In the Linux kernel, the following vulnerability has been resolved: media: dvb-frontends: dib7090p: fix null-ptr-deref in dib7090p_rw_on_apb() In dib7090p_rw_on_apb, msg is controlled by user. When msg[0].buf is null and msg[0].len is zero, former checks on msg[0].buf would be passed. If accessing msg[0].buf[2] without sanity check, null pointer deref would happen. We add check on msg[0].len to prevent crash. Similar issue occurs when access msg[1].buf[0] and msg[1].buf[1]. Similar commit: commit 0ed554fd769a ("media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()") CVE-2025-38694 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38694.html CVE-2025-38694 https://bugzilla.suse.com/1249272 SUSE Bug 1249272 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure If a call to lpfc_sli4_read_rev() from lpfc_sli4_hba_setup() fails, the resultant cleanup routine lpfc_sli4_vport_delete_fcp_xri_aborted() may occur before sli4_hba.hdwqs are allocated. This may result in a null pointer dereference when attempting to take the abts_io_buf_list_lock for the first hardware queue. Fix by adding a null ptr check on phba->sli4_hba.hdwq and early return because this situation means there must have been an error during port initialization. CVE-2025-38695 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38695.html CVE-2025-38695 https://bugzilla.suse.com/1249285 SUSE Bug 1249285 In the Linux kernel, the following vulnerability has been resolved: jfs: upper bound check of tree index in dbAllocAG When computing the tree index in dbAllocAG, we never check if we are out of bounds realative to the size of the stree. This could happen in a scenario where the filesystem metadata are corrupted. CVE-2025-38697 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38697.html CVE-2025-38697 https://bugzilla.suse.com/1249257 SUSE Bug 1249257 In the Linux kernel, the following vulnerability has been resolved: jfs: Regular file corruption check The reproducer builds a corrupted file on disk with a negative i_size value. Add a check when opening this file to avoid subsequent operation failures. CVE-2025-38698 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38698.html CVE-2025-38698 https://bugzilla.suse.com/1249255 SUSE Bug 1249255 https://bugzilla.suse.com/1253014 SUSE Bug 1253014 In the Linux kernel, the following vulnerability has been resolved: scsi: bfa: Double-free fix When the bfad_im_probe() function fails during initialization, the memory pointed to by bfad->im is freed without setting bfad->im to NULL. Subsequently, during driver uninstallation, when the state machine enters the bfad_sm_stopping state and calls the bfad_im_probe_undo() function, it attempts to free the memory pointed to by bfad->im again, thereby triggering a double-free vulnerability. Set bfad->im to NULL if probing fails. CVE-2025-38699 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38699.html CVE-2025-38699 https://bugzilla.suse.com/1249224 SUSE Bug 1249224 In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated In case of an ib_fast_reg_mr allocation failure during iSER setup, the machine hits a panic because iscsi_conn->dd_data is initialized unconditionally, even when no memory is allocated (dd_size == 0). This leads invalid pointer dereference during connection teardown. Fix by setting iscsi_conn->dd_data only if memory is actually allocated. Panic trace: ------------ iser: iser_create_fastreg_desc: Failed to allocate ib_fast_reg_mr err=-12 iser: iser_alloc_rx_descriptors: failed allocating rx descriptors / data buffers BUG: unable to handle page fault for address: fffffffffffffff8 RIP: 0010:swake_up_locked.part.5+0xa/0x40 Call Trace: complete+0x31/0x40 iscsi_iser_conn_stop+0x88/0xb0 [ib_iser] iscsi_stop_conn+0x66/0xc0 [scsi_transport_iscsi] iscsi_if_stop_conn+0x14a/0x150 [scsi_transport_iscsi] iscsi_if_rx+0x1135/0x1834 [scsi_transport_iscsi] ? netlink_lookup+0x12f/0x1b0 ? netlink_deliver_tap+0x2c/0x200 netlink_unicast+0x1ab/0x280 netlink_sendmsg+0x257/0x4f0 ? _copy_from_user+0x29/0x60 sock_sendmsg+0x5f/0x70 CVE-2025-38700 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38700.html CVE-2025-38700 https://bugzilla.suse.com/1249182 SUSE Bug 1249182 In the Linux kernel, the following vulnerability has been resolved: fbdev: fix potential buffer overflow in do_register_framebuffer() The current implementation may lead to buffer overflow when: 1. Unregistration creates NULL gaps in registered_fb[] 2. All array slots become occupied despite num_registered_fb < FB_MAX 3. The registration loop exceeds array bounds Add boundary check to prevent registered_fb[FB_MAX] access. CVE-2025-38702 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38702.html CVE-2025-38702 https://bugzilla.suse.com/1249254 SUSE Bug 1249254 In the Linux kernel, the following vulnerability has been resolved: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() snd_soc_remove_pcm_runtime() might be called with rtd == NULL which will leads to null pointer dereference. This was reproduced with topology loading and marking a link as ignore due to missing hardware component on the system. On module removal the soc_tplg_remove_link() would call snd_soc_remove_pcm_runtime() with rtd == NULL since the link was ignored, no runtime was created. CVE-2025-38706 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38706.html CVE-2025-38706 https://bugzilla.suse.com/1249195 SUSE Bug 1249195 https://bugzilla.suse.com/1250193 SUSE Bug 1250193 In the Linux kernel, the following vulnerability has been resolved: hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file() When the volume header contains erroneous values that do not reflect the actual state of the filesystem, hfsplus_fill_super() assumes that the attributes file is not yet created, which later results in hitting BUG_ON() when hfsplus_create_attributes_file() is called. Replace this BUG_ON() with -EIO error with a message to suggest running fsck tool. CVE-2025-38712 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38712.html CVE-2025-38712 https://bugzilla.suse.com/1249194 SUSE Bug 1249194 In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() The hfsplus_readdir() method is capable to crash by calling hfsplus_uni2asc(): [ 667.121659][ T9805] ================================================================== [ 667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10 [ 667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805 [ 667.124578][ T9805] [ 667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full) [ 667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 667.124890][ T9805] Call Trace: [ 667.124893][ T9805] <TASK> [ 667.124896][ T9805] dump_stack_lvl+0x10e/0x1f0 [ 667.124911][ T9805] print_report+0xd0/0x660 [ 667.124920][ T9805] ? __virt_addr_valid+0x81/0x610 [ 667.124928][ T9805] ? __phys_addr+0xe8/0x180 [ 667.124934][ T9805] ? hfsplus_uni2asc+0x902/0xa10 [ 667.124942][ T9805] kasan_report+0xc6/0x100 [ 667.124950][ T9805] ? hfsplus_uni2asc+0x902/0xa10 [ 667.124959][ T9805] hfsplus_uni2asc+0x902/0xa10 [ 667.124966][ T9805] ? hfsplus_bnode_read+0x14b/0x360 [ 667.124974][ T9805] hfsplus_readdir+0x845/0xfc0 [ 667.124984][ T9805] ? __pfx_hfsplus_readdir+0x10/0x10 [ 667.124994][ T9805] ? stack_trace_save+0x8e/0xc0 [ 667.125008][ T9805] ? iterate_dir+0x18b/0xb20 [ 667.125015][ T9805] ? trace_lock_acquire+0x85/0xd0 [ 667.125022][ T9805] ? lock_acquire+0x30/0x80 [ 667.125029][ T9805] ? iterate_dir+0x18b/0xb20 [ 667.125037][ T9805] ? down_read_killable+0x1ed/0x4c0 [ 667.125044][ T9805] ? putname+0x154/0x1a0 [ 667.125051][ T9805] ? __pfx_down_read_killable+0x10/0x10 [ 667.125058][ T9805] ? apparmor_file_permission+0x239/0x3e0 [ 667.125069][ T9805] iterate_dir+0x296/0xb20 [ 667.125076][ T9805] __x64_sys_getdents64+0x13c/0x2c0 [ 667.125084][ T9805] ? __pfx___x64_sys_getdents64+0x10/0x10 [ 667.125091][ T9805] ? __x64_sys_openat+0x141/0x200 [ 667.125126][ T9805] ? __pfx_filldir64+0x10/0x10 [ 667.125134][ T9805] ? do_user_addr_fault+0x7fe/0x12f0 [ 667.125143][ T9805] do_syscall_64+0xc9/0x480 [ 667.125151][ T9805] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9 [ 667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48 [ 667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9 [ 667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9 [ 667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004 [ 667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110 [ 667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260 [ 667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 667.125207][ T9805] </TASK> [ 667.125210][ T9805] [ 667.145632][ T9805] Allocated by task 9805: [ 667.145991][ T9805] kasan_save_stack+0x20/0x40 [ 667.146352][ T9805] kasan_save_track+0x14/0x30 [ 667.146717][ T9805] __kasan_kmalloc+0xaa/0xb0 [ 667.147065][ T9805] __kmalloc_noprof+0x205/0x550 [ 667.147448][ T9805] hfsplus_find_init+0x95/0x1f0 [ 667.147813][ T9805] hfsplus_readdir+0x220/0xfc0 [ 667.148174][ T9805] iterate_dir+0x296/0xb20 [ 667.148549][ T9805] __x64_sys_getdents64+0x13c/0x2c0 [ 667.148937][ T9805] do_syscall_64+0xc9/0x480 [ 667.149291][ T9805] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 667.149809][ T9805] [ 667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000 [ 667.150030][ T9805] which belongs to the cache kmalloc-2k of size 2048 [ 667.151282][ T9805] The buggy address is located 0 bytes to the right of [ 667.151282][ T9805] allocated 1036-byte region [ffff88802592f000, ffff88802592f40c) [ 667.1 ---truncated--- CVE-2025-38713 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38713.html CVE-2025-38713 https://bugzilla.suse.com/1249200 SUSE Bug 1249200 https://bugzilla.suse.com/1249738 SUSE Bug 1249738 In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() The hfsplus_bnode_read() method can trigger the issue: [ 174.852007][ T9784] ================================================================== [ 174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360 [ 174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784 [ 174.854059][ T9784] [ 174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full) [ 174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 174.854286][ T9784] Call Trace: [ 174.854289][ T9784] <TASK> [ 174.854292][ T9784] dump_stack_lvl+0x10e/0x1f0 [ 174.854305][ T9784] print_report+0xd0/0x660 [ 174.854315][ T9784] ? __virt_addr_valid+0x81/0x610 [ 174.854323][ T9784] ? __phys_addr+0xe8/0x180 [ 174.854330][ T9784] ? hfsplus_bnode_read+0x2f4/0x360 [ 174.854337][ T9784] kasan_report+0xc6/0x100 [ 174.854346][ T9784] ? hfsplus_bnode_read+0x2f4/0x360 [ 174.854354][ T9784] hfsplus_bnode_read+0x2f4/0x360 [ 174.854362][ T9784] hfsplus_bnode_dump+0x2ec/0x380 [ 174.854370][ T9784] ? __pfx_hfsplus_bnode_dump+0x10/0x10 [ 174.854377][ T9784] ? hfsplus_bnode_write_u16+0x83/0xb0 [ 174.854385][ T9784] ? srcu_gp_start+0xd0/0x310 [ 174.854393][ T9784] ? __mark_inode_dirty+0x29e/0xe40 [ 174.854402][ T9784] hfsplus_brec_remove+0x3d2/0x4e0 [ 174.854411][ T9784] __hfsplus_delete_attr+0x290/0x3a0 [ 174.854419][ T9784] ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10 [ 174.854427][ T9784] ? __pfx___hfsplus_delete_attr+0x10/0x10 [ 174.854436][ T9784] ? __asan_memset+0x23/0x50 [ 174.854450][ T9784] hfsplus_delete_all_attrs+0x262/0x320 [ 174.854459][ T9784] ? __pfx_hfsplus_delete_all_attrs+0x10/0x10 [ 174.854469][ T9784] ? rcu_is_watching+0x12/0xc0 [ 174.854476][ T9784] ? __mark_inode_dirty+0x29e/0xe40 [ 174.854483][ T9784] hfsplus_delete_cat+0x845/0xde0 [ 174.854493][ T9784] ? __pfx_hfsplus_delete_cat+0x10/0x10 [ 174.854507][ T9784] hfsplus_unlink+0x1ca/0x7c0 [ 174.854516][ T9784] ? __pfx_hfsplus_unlink+0x10/0x10 [ 174.854525][ T9784] ? down_write+0x148/0x200 [ 174.854532][ T9784] ? __pfx_down_write+0x10/0x10 [ 174.854540][ T9784] vfs_unlink+0x2fe/0x9b0 [ 174.854549][ T9784] do_unlinkat+0x490/0x670 [ 174.854557][ T9784] ? __pfx_do_unlinkat+0x10/0x10 [ 174.854565][ T9784] ? __might_fault+0xbc/0x130 [ 174.854576][ T9784] ? getname_flags.part.0+0x1c5/0x550 [ 174.854584][ T9784] __x64_sys_unlink+0xc5/0x110 [ 174.854592][ T9784] do_syscall_64+0xc9/0x480 [ 174.854600][ T9784] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167 [ 174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08 [ 174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057 [ 174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167 [ 174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50 [ 174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40 [ 174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0 [ 174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 174.854658][ T9784] </TASK> [ 174.854661][ T9784] [ 174.879281][ T9784] Allocated by task 9784: [ 174.879664][ T9784] kasan_save_stack+0x20/0x40 [ 174.880082][ T9784] kasan_save_track+0x14/0x30 [ 174.880500][ T9784] __kasan_kmalloc+0xaa/0xb0 [ 174.880908][ T9784] __kmalloc_noprof+0x205/0x550 [ 174.881337][ T9784] __hfs_bnode_create+0x107/0x890 [ 174.881779][ T9784] hfsplus_bnode_find+0x2d0/0xd10 [ 174.882222][ T9784] hfsplus_brec_find+0x2b0/0x520 [ 174.882659][ T9784] hfsplus_delete_all_attrs+0x23b/0x3 ---truncated--- CVE-2025-38714 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38714.html CVE-2025-38714 https://bugzilla.suse.com/1249260 SUSE Bug 1249260 https://bugzilla.suse.com/1249596 SUSE Bug 1249596 In the Linux kernel, the following vulnerability has been resolved: hfs: fix slab-out-of-bounds in hfs_bnode_read() This patch introduces is_bnode_offset_valid() method that checks the requested offset value. Also, it introduces check_and_correct_requested_length() method that checks and correct the requested length (if it is necessary). These methods are used in hfs_bnode_read(), hfs_bnode_write(), hfs_bnode_clear(), hfs_bnode_copy(), and hfs_bnode_move() with the goal to prevent the access out of allocated memory and triggering the crash. CVE-2025-38715 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38715.html CVE-2025-38715 https://bugzilla.suse.com/1249196 SUSE Bug 1249196 In the Linux kernel, the following vulnerability has been resolved: sctp: linearize cloned gso packets in sctp_rcv A cloned head skb still shares these frag skbs in fraglist with the original head skb. It's not safe to access these frag skbs. syzbot reported two use-of-uninitialized-memory bugs caused by this: BUG: KMSAN: uninit-value in sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211 sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211 sctp_assoc_bh_rcv+0x1a7/0xc50 net/sctp/associola.c:998 sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88 sctp_backlog_rcv+0x397/0xdb0 net/sctp/input.c:331 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1122 __release_sock+0x1da/0x330 net/core/sock.c:3106 release_sock+0x6b/0x250 net/core/sock.c:3660 sctp_wait_for_connect+0x487/0x820 net/sctp/socket.c:9360 sctp_sendmsg_to_asoc+0x1ec1/0x1f00 net/sctp/socket.c:1885 sctp_sendmsg+0x32b9/0x4a80 net/sctp/socket.c:2031 inet_sendmsg+0x25a/0x280 net/ipv4/af_inet.c:851 sock_sendmsg_nosec net/socket.c:718 [inline] and BUG: KMSAN: uninit-value in sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987 sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987 sctp_inq_push+0x2a3/0x350 net/sctp/inqueue.c:88 sctp_backlog_rcv+0x3c7/0xda0 net/sctp/input.c:331 sk_backlog_rcv+0x142/0x420 include/net/sock.h:1148 __release_sock+0x1d3/0x330 net/core/sock.c:3213 release_sock+0x6b/0x270 net/core/sock.c:3767 sctp_wait_for_connect+0x458/0x820 net/sctp/socket.c:9367 sctp_sendmsg_to_asoc+0x223a/0x2260 net/sctp/socket.c:1886 sctp_sendmsg+0x3910/0x49f0 net/sctp/socket.c:2032 inet_sendmsg+0x269/0x2a0 net/ipv4/af_inet.c:851 sock_sendmsg_nosec net/socket.c:712 [inline] This patch fixes it by linearizing cloned gso packets in sctp_rcv(). CVE-2025-38718 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38718.html CVE-2025-38718 https://bugzilla.suse.com/1249161 SUSE Bug 1249161 In the Linux kernel, the following vulnerability has been resolved: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() Lei Lu recently reported that nfsd4_setclientid_confirm() did not check the return value from get_client_locked(). a SETCLIENTID_CONFIRM could race with a confirmed client expiring and fail to get a reference. That could later lead to a UAF. Fix this by getting a reference early in the case where there is an extant confirmed client. If that fails then treat it as if there were no confirmed client found at all. In the case where the unconfirmed client is expiring, just fail and return the result from get_client_locked(). CVE-2025-38724 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38724.html CVE-2025-38724 https://bugzilla.suse.com/1249169 SUSE Bug 1249169 In the Linux kernel, the following vulnerability has been resolved: net: usb: asix_devices: add phy_mask for ax88772 mdio bus Without setting phy_mask for ax88772 mdio bus, current driver may create at most 32 mdio phy devices with phy address range from 0x00 ~ 0x1f. DLink DUB-E100 H/W Ver B1 is such a device. However, only one main phy device will bind to net phy driver. This is creating issue during system suspend/resume since phy_polling_mode() in phy_state_machine() will directly deference member of phydev->drv for non-main phy devices. Then NULL pointer dereference issue will occur. Due to only external phy or internal phy is necessary, add phy_mask for ax88772 mdio bus to workarnoud the issue. CVE-2025-38725 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38725.html CVE-2025-38725 https://bugzilla.suse.com/1249170 SUSE Bug 1249170 In the Linux kernel, the following vulnerability has been resolved: netlink: avoid infinite retry looping in netlink_unicast() netlink_attachskb() checks for the socket's read memory allocation constraints. Firstly, it has: rmem < READ_ONCE(sk->sk_rcvbuf) to check if the just increased rmem value fits into the socket's receive buffer. If not, it proceeds and tries to wait for the memory under: rmem + skb->truesize > READ_ONCE(sk->sk_rcvbuf) The checks don't cover the case when skb->truesize + sk->sk_rmem_alloc is equal to sk->sk_rcvbuf. Thus the function neither successfully accepts these conditions, nor manages to reschedule the task - and is called in retry loop for indefinite time which is caught as: rcu: INFO: rcu_sched self-detected stall on CPU rcu: 0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212 (t=26000 jiffies g=230833 q=259957) NMI backtrace for cpu 0 CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014 Call Trace: <IRQ> dump_stack lib/dump_stack.c:120 nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105 nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62 rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335 rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590 update_process_times kernel/time/timer.c:1953 tick_sched_handle kernel/time/tick-sched.c:227 tick_sched_timer kernel/time/tick-sched.c:1399 __hrtimer_run_queues kernel/time/hrtimer.c:1652 hrtimer_interrupt kernel/time/hrtimer.c:1717 __sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1113 asm_call_irq_on_stack arch/x86/entry/entry_64.S:808 </IRQ> netlink_attachskb net/netlink/af_netlink.c:1234 netlink_unicast net/netlink/af_netlink.c:1349 kauditd_send_queue kernel/audit.c:776 kauditd_thread kernel/audit.c:897 kthread kernel/kthread.c:328 ret_from_fork arch/x86/entry/entry_64.S:304 Restore the original behavior of the check which commit in Fixes accidentally missed when restructuring the code. Found by Linux Verification Center (linuxtesting.org). CVE-2025-38727 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38727.html CVE-2025-38727 https://bugzilla.suse.com/1249166 SUSE Bug 1249166 In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Validate UAC3 power domain descriptors, too UAC3 power domain descriptors need to be verified with its variable bLength for avoiding the unexpected OOB accesses by malicious firmware, too. CVE-2025-38729 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38729.html CVE-2025-38729 https://bugzilla.suse.com/1249164 SUSE Bug 1249164 In the Linux kernel, the following vulnerability has been resolved: net/smc: fix UAF on smcsk after smc_listen_out() BPF CI testing report a UAF issue: [ 16.446633] BUG: kernel NULL pointer dereference, address: 000000000000003 0 [ 16.447134] #PF: supervisor read access in kernel mod e [ 16.447516] #PF: error_code(0x0000) - not-present pag e [ 16.447878] PGD 0 P4D 0 [ 16.448063] Oops: Oops: 0000 [#1] PREEMPT SMP NOPT I [ 16.448409] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Tainted: G OE 6.13.0-rc3-g89e8a75fda73-dirty #4 2 [ 16.449124] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODUL E [ 16.449502] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/201 4 [ 16.450201] Workqueue: smc_hs_wq smc_listen_wor k [ 16.450531] RIP: 0010:smc_listen_work+0xc02/0x159 0 [ 16.452158] RSP: 0018:ffffb5ab40053d98 EFLAGS: 0001024 6 [ 16.452526] RAX: 0000000000000001 RBX: 0000000000000002 RCX: 000000000000030 0 [ 16.452994] RDX: 0000000000000280 RSI: 00003513840053f0 RDI: 000000000000000 0 [ 16.453492] RBP: ffffa097808e3800 R08: ffffa09782dba1e0 R09: 000000000000000 5 [ 16.453987] R10: 0000000000000000 R11: 0000000000000000 R12: ffffa0978274640 0 [ 16.454497] R13: 0000000000000000 R14: 0000000000000000 R15: ffffa09782d4092 0 [ 16.454996] FS: 0000000000000000(0000) GS:ffffa097bbc00000(0000) knlGS:000000000000000 0 [ 16.455557] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003 3 [ 16.455961] CR2: 0000000000000030 CR3: 0000000102788004 CR4: 0000000000770ef 0 [ 16.456459] PKRU: 5555555 4 [ 16.456654] Call Trace : [ 16.456832] <TASK > [ 16.456989] ? __die+0x23/0x7 0 [ 16.457215] ? page_fault_oops+0x180/0x4c 0 [ 16.457508] ? __lock_acquire+0x3e6/0x249 0 [ 16.457801] ? exc_page_fault+0x68/0x20 0 [ 16.458080] ? asm_exc_page_fault+0x26/0x3 0 [ 16.458389] ? smc_listen_work+0xc02/0x159 0 [ 16.458689] ? smc_listen_work+0xc02/0x159 0 [ 16.458987] ? lock_is_held_type+0x8f/0x10 0 [ 16.459284] process_one_work+0x1ea/0x6d 0 [ 16.459570] worker_thread+0x1c3/0x38 0 [ 16.459839] ? __pfx_worker_thread+0x10/0x1 0 [ 16.460144] kthread+0xe0/0x11 0 [ 16.460372] ? __pfx_kthread+0x10/0x1 0 [ 16.460640] ret_from_fork+0x31/0x5 0 [ 16.460896] ? __pfx_kthread+0x10/0x1 0 [ 16.461166] ret_from_fork_asm+0x1a/0x3 0 [ 16.461453] </TASK > [ 16.461616] Modules linked in: bpf_testmod(OE) [last unloaded: bpf_testmod(OE) ] [ 16.462134] CR2: 000000000000003 0 [ 16.462380] ---[ end trace 0000000000000000 ]--- [ 16.462710] RIP: 0010:smc_listen_work+0xc02/0x1590 The direct cause of this issue is that after smc_listen_out_connected(), newclcsock->sk may be NULL since it will releases the smcsk. Therefore, if the application closes the socket immediately after accept, newclcsock->sk can be NULL. A possible execution order could be as follows: smc_listen_work | userspace ----------------------------------------------------------------- lock_sock(sk) | smc_listen_out_connected() | | \- smc_listen_out | | | \- release_sock | | |- sk->sk_data_ready() | | fd = accept(); | close(fd); | \- socket->sk = NULL; /* newclcsock->sk is NULL now */ SMC_STAT_SERV_SUCC_INC(sock_net(newclcsock->sk)) Since smc_listen_out_connected() will not fail, simply swapping the order of the code can easily fix this issue. CVE-2025-38734 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38734.html CVE-2025-38734 https://bugzilla.suse.com/1249324 SUSE Bug 1249324 In the Linux kernel, the following vulnerability has been resolved: gve: prevent ethtool ops after shutdown A crash can occur if an ethtool operation is invoked after shutdown() is called. shutdown() is invoked during system shutdown to stop DMA operations without performing expensive deallocations. It is discouraged to unregister the netdev in this path, so the device may still be visible to userspace and kernel helpers. In gve, shutdown() tears down most internal data structures. If an ethtool operation is dispatched after shutdown(), it will dereference freed or NULL pointers, leading to a kernel panic. While graceful shutdown normally quiesces userspace before invoking the reboot syscall, forced shutdowns (as observed on GCP VMs) can still trigger this path. Fix by calling netif_device_detach() in shutdown(). This marks the device as detached so the ethtool ioctl handler will skip dispatching operations to the driver. CVE-2025-38735 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38735.html CVE-2025-38735 https://bugzilla.suse.com/1249288 SUSE Bug 1249288 In the Linux kernel, the following vulnerability has been resolved: net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization Syzbot reported shift-out-of-bounds exception on MDIO bus initialization. The PHY address should be masked to 5 bits (0-31). Without this mask, invalid PHY addresses could be used, potentially causing issues with MDIO bus operations. Fix this by masking the PHY address with 0x1f (31 decimal) to ensure it stays within the valid range. CVE-2025-38736 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-38736.html CVE-2025-38736 https://bugzilla.suse.com/1249318 SUSE Bug 1249318 In the Linux kernel, the following vulnerability has been resolved: ppp: fix race conditions in ppp_fill_forward_path ppp_fill_forward_path() has two race conditions: 1. The ppp->channels list can change between list_empty() and list_first_entry(), as ppp_lock() is not held. If the only channel is deleted in ppp_disconnect_channel(), list_first_entry() may access an empty head or a freed entry, and trigger a panic. 2. pch->chan can be NULL. When ppp_unregister_channel() is called, pch->chan is set to NULL before pch is removed from ppp->channels. Fix these by using a lockless RCU approach: - Use list_first_or_null_rcu() to safely test and access the first list entry. - Convert list modifications on ppp->channels to their RCU variants and add synchronize_net() after removal. - Check for a NULL pch->chan before dereferencing it. CVE-2025-39673 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39673.html CVE-2025-39673 https://bugzilla.suse.com/1249320 SUSE Bug 1249320 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null pointer check in mod_hdcp_hdcp1_create_session() The function mod_hdcp_hdcp1_create_session() calls the function get_first_active_display(), but does not check its return value. The return value is a null pointer if the display list is empty. This will lead to a null pointer dereference. Add a null pointer check for get_first_active_display() and return MOD_HDCP_STATUS_DISPLAY_NOT_FOUND if the function return null. This is similar to the commit c3e9826a2202 ("drm/amd/display: Add null pointer check for get_first_active_display()"). (cherry picked from commit 5e43eb3cd731649c4f8b9134f857be62a416c893) CVE-2025-39675 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39675.html CVE-2025-39675 https://bugzilla.suse.com/1249263 SUSE Bug 1249263 In the Linux kernel, the following vulnerability has been resolved: scsi: qla4xxx: Prevent a potential error pointer dereference The qla4xxx_get_ep_fwdb() function is supposed to return NULL on error, but qla4xxx_ep_connect() returns error pointers. Propagating the error pointers will lead to an Oops in the caller, so change the error pointers to NULL. CVE-2025-39676 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39676.html CVE-2025-39676 https://bugzilla.suse.com/1249302 SUSE Bug 1249302 In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/nvif: Fix potential memory leak in nvif_vmm_ctor(). When the nvif_vmm_type is invalid, we will return error directly without freeing the args in nvif_vmm_ctor(), which leading a memory leak. Fix it by setting the ret -EINVAL and goto done. CVE-2025-39679 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39679.html CVE-2025-39679 https://bugzilla.suse.com/1249338 SUSE Bug 1249338 In the Linux kernel, the following vulnerability has been resolved: tracing: Limit access to parser->buffer when trace_get_user failed When the length of the string written to set_ftrace_filter exceeds FTRACE_BUFF_MAX, the following KASAN alarm will be triggered: BUG: KASAN: slab-out-of-bounds in strsep+0x18c/0x1b0 Read of size 1 at addr ffff0000d00bd5ba by task ash/165 CPU: 1 UID: 0 PID: 165 Comm: ash Not tainted 6.16.0-g6bcdbd62bd56-dirty Hardware name: linux,dummy-virt (DT) Call trace: show_stack+0x34/0x50 (C) dump_stack_lvl+0xa0/0x158 print_address_description.constprop.0+0x88/0x398 print_report+0xb0/0x280 kasan_report+0xa4/0xf0 __asan_report_load1_noabort+0x20/0x30 strsep+0x18c/0x1b0 ftrace_process_regex.isra.0+0x100/0x2d8 ftrace_regex_release+0x484/0x618 __fput+0x364/0xa58 ____fput+0x28/0x40 task_work_run+0x154/0x278 do_notify_resume+0x1f0/0x220 el0_svc+0xec/0xf0 el0t_64_sync_handler+0xa0/0xe8 el0t_64_sync+0x1ac/0x1b0 The reason is that trace_get_user will fail when processing a string longer than FTRACE_BUFF_MAX, but not set the end of parser->buffer to 0. Then an OOB access will be triggered in ftrace_regex_release-> ftrace_process_regex->strsep->strpbrk. We can solve this problem by limiting access to parser->buffer when trace_get_user failed. CVE-2025-39683 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39683.html CVE-2025-39683 https://bugzilla.suse.com/1249286 SUSE Bug 1249286 In the Linux kernel, the following vulnerability has been resolved: comedi: Fix use of uninitialized memory in do_insn_ioctl() and do_insnlist_ioctl() syzbot reports a KMSAN kernel-infoleak in `do_insn_ioctl()`. A kernel buffer is allocated to hold `insn->n` samples (each of which is an `unsigned int`). For some instruction types, `insn->n` samples are copied back to user-space, unless an error code is being returned. The problem is that not all the instruction handlers that need to return data to userspace fill in the whole `insn->n` samples, so that there is an information leak. There is a similar syzbot report for `do_insnlist_ioctl()`, although it does not have a reproducer for it at the time of writing. One culprit is `insn_rw_emulate_bits()` which is used as the handler for `INSN_READ` or `INSN_WRITE` instructions for subdevices that do not have a specific handler for that instruction, but do have an `INSN_BITS` handler. For `INSN_READ` it only fills in at most 1 sample, so if `insn->n` is greater than 1, the remaining `insn->n - 1` samples copied to userspace will be uninitialized kernel data. Another culprit is `vm80xx_ai_insn_read()` in the "vm80xx" driver. It never returns an error, even if it fails to fill the buffer. Fix it in `do_insn_ioctl()` and `do_insnlist_ioctl()` by making sure that uninitialized parts of the allocated buffer are zeroed before handling each instruction. Thanks to Arnaud Lecomte for their fix to `do_insn_ioctl()`. That fix replaced the call to `kmalloc_array()` with `kcalloc()`, but it is not always necessary to clear the whole buffer. CVE-2025-39684 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39684.html CVE-2025-39684 https://bugzilla.suse.com/1249281 SUSE Bug 1249281 In the Linux kernel, the following vulnerability has been resolved: comedi: pcl726: Prevent invalid irq number The reproducer passed in an irq number(0x80008000) that was too large, which triggered the oob. Added an interrupt number check to prevent users from passing in an irq number that was too large. If `it->options[1]` is 31, then `1 << it->options[1]` is still invalid because it shifts a 1-bit into the sign bit (which is UB in C). Possible solutions include reducing the upper bound on the `it->options[1]` value to 30 or lower, or using `1U << it->options[1]`. The old code would just not attempt to request the IRQ if the `options[1]` value were invalid. And it would still configure the device without interrupts even if the call to `request_irq` returned an error. So it would be better to combine this test with the test below. CVE-2025-39685 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39685.html CVE-2025-39685 https://bugzilla.suse.com/1249282 SUSE Bug 1249282 In the Linux kernel, the following vulnerability has been resolved: comedi: Make insn_rw_emulate_bits() do insn->n samples The `insn_rw_emulate_bits()` function is used as a default handler for `INSN_READ` instructions for subdevices that have a handler for `INSN_BITS` but not for `INSN_READ`. Similarly, it is used as a default handler for `INSN_WRITE` instructions for subdevices that have a handler for `INSN_BITS` but not for `INSN_WRITE`. It works by emulating the `INSN_READ` or `INSN_WRITE` instruction handling with a constructed `INSN_BITS` instruction. However, `INSN_READ` and `INSN_WRITE` instructions are supposed to be able read or write multiple samples, indicated by the `insn->n` value, but `insn_rw_emulate_bits()` currently only handles a single sample. For `INSN_READ`, the comedi core will copy `insn->n` samples back to user-space. (That triggered KASAN kernel-infoleak errors when `insn->n` was greater than 1, but that is being fixed more generally elsewhere in the comedi core.) Make `insn_rw_emulate_bits()` either handle `insn->n` samples, or return an error, to conform to the general expectation for `INSN_READ` and `INSN_WRITE` handlers. CVE-2025-39686 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39686.html CVE-2025-39686 https://bugzilla.suse.com/1249312 SUSE Bug 1249312 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid a NULL pointer dereference [WHY] Although unlikely drm_atomic_get_new_connector_state() or drm_atomic_get_old_connector_state() can return NULL. [HOW] Check returns before dereference. (cherry picked from commit 1e5e8d672fec9f2ab352be121be971877bff2af9) CVE-2025-39693 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39693.html CVE-2025-39693 https://bugzilla.suse.com/1249279 SUSE Bug 1249279 In the Linux kernel, the following vulnerability has been resolved: s390/sclp: Fix SCCB present check Tracing code called by the SCLP interrupt handler contains early exits if the SCCB address associated with an interrupt is NULL. This check is performed after physical to virtual address translation. If the kernel identity mapping does not start at address zero, the resulting virtual address is never zero, so that the NULL checks won't work. Subsequently this may result in incorrect accesses to the first page of the identity mapping. Fix this by introducing a function that handles the NULL case before address translation. CVE-2025-39694 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39694.html CVE-2025-39694 https://bugzilla.suse.com/1249299 SUSE Bug 1249299 In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a race when updating an existing write After nfs_lock_and_join_requests() tests for whether the request is still attached to the mapping, nothing prevents a call to nfs_inode_remove_request() from succeeding until we actually lock the page group. The reason is that whoever called nfs_inode_remove_request() doesn't necessarily have a lock on the page group head. So in order to avoid races, let's take the page group lock earlier in nfs_lock_and_join_requests(), and hold it across the removal of the request in nfs_inode_remove_request(). CVE-2025-39697 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39697.html CVE-2025-39697 https://bugzilla.suse.com/1249319 SUSE Bug 1249319 In the Linux kernel, the following vulnerability has been resolved: ACPI: pfr_update: Fix the driver update version check The security-version-number check should be used rather than the runtime version check for driver updates. Otherwise, the firmware update would fail when the update binary had a lower runtime version number than the current one. [ rjw: Changelog edits ] CVE-2025-39701 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39701.html CVE-2025-39701 https://bugzilla.suse.com/1249308 SUSE Bug 1249308 In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: Fix MAC comparison to be constant-time To prevent timing attacks, MACs need to be compared in constant time. Use the appropriate helper function for this. CVE-2025-39702 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39702.html CVE-2025-39702 https://bugzilla.suse.com/1249317 SUSE Bug 1249317 In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Destroy KFD debugfs after destroy KFD wq Since KFD proc content was moved to kernel debugfs, we can't destroy KFD debugfs before kfd_process_destroy_wq. Move kfd_process_destroy_wq prior to kfd_debugfs_fini to fix a kernel NULL pointer problem. It happens when /sys/kernel/debug/kfd was already destroyed in kfd_debugfs_fini but kfd_process_destroy_wq calls kfd_debugfs_remove_process. This line debugfs_remove_recursive(entry->proc_dentry); tries to remove /sys/kernel/debug/kfd/proc/<pid> while /sys/kernel/debug/kfd is already gone. It hangs the kernel by kernel NULL pointer. (cherry picked from commit 0333052d90683d88531558dcfdbf2525cc37c233) CVE-2025-39706 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39706.html CVE-2025-39706 https://bugzilla.suse.com/1249413 SUSE Bug 1249413 In the Linux kernel, the following vulnerability has been resolved: media: venus: protect against spurious interrupts during probe Make sure the interrupt handler is initialized before the interrupt is registered. If the IRQ is registered before hfi_create(), it's possible that an interrupt fires before the handler setup is complete, leading to a NULL dereference. This error condition has been observed during system boot on Rb3Gen2. CVE-2025-39709 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39709.html CVE-2025-39709 https://bugzilla.suse.com/1249278 SUSE Bug 1249278 In the Linux kernel, the following vulnerability has been resolved: media: venus: Add a check for packet size after reading from shared memory Add a check to ensure that the packet size does not exceed the number of available words after reading the packet header from shared memory. This ensures that the size provided by the firmware is safe to process and prevent potential out-of-bounds memory access. CVE-2025-39710 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39710.html CVE-2025-39710 https://bugzilla.suse.com/1249304 SUSE Bug 1249304 In the Linux kernel, the following vulnerability has been resolved: media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() In the interrupt handler rain_interrupt(), the buffer full check on rain->buf_len is performed before acquiring rain->buf_lock. This creates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as rain->buf_len is concurrently accessed and modified in the work handler rain_irq_work_handler() under the same lock. Multiple interrupt invocations can race, with each reading buf_len before it becomes full and then proceeding. This can lead to both interrupts attempting to write to the buffer, incrementing buf_len beyond its capacity (DATA_SIZE) and causing a buffer overflow. Fix this bug by moving the spin_lock() to before the buffer full check. This ensures that the check and the subsequent buffer modification are performed atomically, preventing the race condition. An corresponding spin_unlock() is added to the overflow path to correctly release the lock. This possible bug was found by an experimental static analysis tool developed by our team. CVE-2025-39713 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39713.html CVE-2025-39713 https://bugzilla.suse.com/1249321 SUSE Bug 1249321 In the Linux kernel, the following vulnerability has been resolved: media: usbtv: Lock resolution while streaming When an program is streaming (ffplay) and another program (qv4l2) changes the TV standard from NTSC to PAL, the kernel crashes due to trying to copy to unmapped memory. Changing from NTSC to PAL increases the resolution in the usbtv struct, but the video plane buffer isn't adjusted, so it overflows. [hverkuil: call vb2_is_busy instead of vb2_is_streaming] CVE-2025-39714 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39714.html CVE-2025-39714 https://bugzilla.suse.com/1249273 SUSE Bug 1249273 In the Linux kernel, the following vulnerability has been resolved: iio: imu: bno055: fix OOB access of hw_xlate array Fix a potential out-of-bounds array access of the hw_xlate array in bno055.c. In bno055_get_regmask(), hw_xlate was iterated over the length of the vals array instead of the length of the hw_xlate array. In the case of bno055_gyr_scale, the vals array is larger than the hw_xlate array, so this could result in an out-of-bounds access. In practice, this shouldn't happen though because a match should always be found which breaks out of the for loop before it iterates beyond the end of the hw_xlate array. By adding a new hw_xlate_len field to the bno055_sysfs_attr, we can be sure we are iterating over the correct length. CVE-2025-39719 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39719.html CVE-2025-39719 https://bugzilla.suse.com/1249271 SUSE Bug 1249271 In the Linux kernel, the following vulnerability has been resolved: crypto: qat - flush misc workqueue during device shutdown Repeated loading and unloading of a device specific QAT driver, for example qat_4xxx, in a tight loop can lead to a crash due to a use-after-free scenario. This occurs when a power management (PM) interrupt triggers just before the device-specific driver (e.g., qat_4xxx.ko) is unloaded, while the core driver (intel_qat.ko) remains loaded. Since the driver uses a shared workqueue (`qat_misc_wq`) across all devices and owned by intel_qat.ko, a deferred routine from the device-specific driver may still be pending in the queue. If this routine executes after the driver is unloaded, it can dereference freed memory, resulting in a page fault and kernel crash like the following: BUG: unable to handle page fault for address: ffa000002e50a01c #PF: supervisor read access in kernel mode RIP: 0010:pm_bh_handler+0x1d2/0x250 [intel_qat] Call Trace: pm_bh_handler+0x1d2/0x250 [intel_qat] process_one_work+0x171/0x340 worker_thread+0x277/0x3a0 kthread+0xf0/0x120 ret_from_fork+0x2d/0x50 To prevent this, flush the misc workqueue during device shutdown to ensure that all pending work items are completed before the driver is unloaded. Note: This approach may slightly increase shutdown latency if the workqueue contains jobs from other devices, but it ensures correctness and stability. CVE-2025-39721 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39721.html CVE-2025-39721 https://bugzilla.suse.com/1249323 SUSE Bug 1249323 In the Linux kernel, the following vulnerability has been resolved: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. In serial8250_do_startup(), calling serial_port_out(port, UART_LCR, UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter function enables the FIFO via serial_out(p, UART_FCR, p->fcr). Execution proceeds to the serial_port_in(port, UART_RX). This satisfies the PSLVERR trigger condition. When another CPU (e.g., using printk()) is accessing the UART (UART is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) == (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter dw8250_force_idle(). Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock to fix this issue. Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70 CVE-2025-39724 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39724.html CVE-2025-39724 https://bugzilla.suse.com/1249265 SUSE Bug 1249265 In the Linux kernel, the following vulnerability has been resolved: s390/ism: fix concurrency management in ism_cmd() The s390x ISM device data sheet clearly states that only one request-response sequence is allowable per ISM function at any point in time. Unfortunately as of today the s390/ism driver in Linux does not honor that requirement. This patch aims to rectify that. This problem was discovered based on Aliaksei's bug report which states that for certain workloads the ISM functions end up entering error state (with PEC 2 as seen from the logs) after a while and as a consequence connections handled by the respective function break, and for future connection requests the ISM device is not considered -- given it is in a dysfunctional state. During further debugging PEC 3A was observed as well. A kernel message like [ 1211.244319] zpci: 061a:00:00.0: Event 0x2 reports an error for PCI function 0x61a is a reliable indicator of the stated function entering error state with PEC 2. Let me also point out that a kernel message like [ 1211.244325] zpci: 061a:00:00.0: The ism driver bound to the device does not support error recovery is a reliable indicator that the ISM function won't be auto-recovered because the ISM driver currently lacks support for it. On a technical level, without this synchronization, commands (inputs to the FW) may be partially or fully overwritten (corrupted) by another CPU trying to issue commands on the same function. There is hard evidence that this can lead to DMB token values being used as DMB IOVAs, leading to PEC 2 PCI events indicating invalid DMA. But this is only one of the failure modes imaginable. In theory even completely losing one command and executing another one twice and then trying to interpret the outputs as if the command we intended to execute was actually executed and not the other one is also possible. Frankly, I don't feel confident about providing an exhaustive list of possible consequences. CVE-2025-39726 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39726.html CVE-2025-39726 https://bugzilla.suse.com/1249266 SUSE Bug 1249266 In the Linux kernel, the following vulnerability has been resolved: NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() The function needs to check the minimal filehandle length before it can access the embedded filehandle. CVE-2025-39730 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39730.html CVE-2025-39730 https://bugzilla.suse.com/1249296 SUSE Bug 1249296 In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() ath11k_mac_disable_peer_fixed_rate() is passed as the iterator to ieee80211_iterate_stations_atomic(). Note in this case the iterator is required to be atomic, however ath11k_mac_disable_peer_fixed_rate() does not follow it as it might sleep. Consequently below warning is seen: BUG: sleeping function called from invalid context at wmi.c:304 Call Trace: <TASK> dump_stack_lvl __might_resched.cold ath11k_wmi_cmd_send ath11k_wmi_set_peer_param ath11k_mac_disable_peer_fixed_rate ieee80211_iterate_stations_atomic ath11k_mac_op_set_bitrate_mask.cold Change to ieee80211_iterate_stations_mtx() to fix this issue. Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 CVE-2025-39732 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39732.html CVE-2025-39732 https://bugzilla.suse.com/1249292 SUSE Bug 1249292 In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-qcom: Add SM6115 MDSS compatible Add the SM6115 MDSS compatible to clients compatible list, as it also needs that workaround. Without this workaround, for example, QRB4210 RB2 which is based on SM4250/SM6115 generates a lot of smmu unhandled context faults during boot: arm_smmu_context_fault: 116854 callbacks suppressed arm-smmu c600000.iommu: Unhandled context fault: fsr=0x402, iova=0x5c0ec600, fsynr=0x320021, cbfrsynra=0x420, cb=5 arm-smmu c600000.iommu: FSR = 00000402 [Format=2 TF], SID=0x420 arm-smmu c600000.iommu: FSYNR0 = 00320021 [S1CBNDX=50 PNU PLVL=1] arm-smmu c600000.iommu: Unhandled context fault: fsr=0x402, iova=0x5c0d7800, fsynr=0x320021, cbfrsynra=0x420, cb=5 arm-smmu c600000.iommu: FSR = 00000402 [Format=2 TF], SID=0x420 and also failed initialisation of lontium lt9611uxc, gpu and dpu is observed: (binding MDSS components triggered by lt9611uxc have failed) ------------[ cut here ]------------ !aspace WARNING: CPU: 6 PID: 324 at drivers/gpu/drm/msm/msm_gem_vma.c:130 msm_gem_vma_init+0x150/0x18c [msm] Modules linked in: ... (long list of modules) CPU: 6 UID: 0 PID: 324 Comm: (udev-worker) Not tainted 6.15.0-03037-gaacc73ceeb8b #4 PREEMPT Hardware name: Qualcomm Technologies, Inc. QRB4210 RB2 (DT) pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : msm_gem_vma_init+0x150/0x18c [msm] lr : msm_gem_vma_init+0x150/0x18c [msm] sp : ffff80008144b280 ... Call trace: msm_gem_vma_init+0x150/0x18c [msm] (P) get_vma_locked+0xc0/0x194 [msm] msm_gem_get_and_pin_iova_range+0x4c/0xdc [msm] msm_gem_kernel_new+0x48/0x160 [msm] msm_gpu_init+0x34c/0x53c [msm] adreno_gpu_init+0x1b0/0x2d8 [msm] a6xx_gpu_init+0x1e8/0x9e0 [msm] adreno_bind+0x2b8/0x348 [msm] component_bind_all+0x100/0x230 msm_drm_bind+0x13c/0x3d0 [msm] try_to_bring_up_aggregate_device+0x164/0x1d0 __component_add+0xa4/0x174 component_add+0x14/0x20 dsi_dev_attach+0x20/0x34 [msm] dsi_host_attach+0x58/0x98 [msm] devm_mipi_dsi_attach+0x34/0x90 lt9611uxc_attach_dsi.isra.0+0x94/0x124 [lontium_lt9611uxc] lt9611uxc_probe+0x540/0x5fc [lontium_lt9611uxc] i2c_device_probe+0x148/0x2a8 really_probe+0xbc/0x2c0 __driver_probe_device+0x78/0x120 driver_probe_device+0x3c/0x154 __driver_attach+0x90/0x1a0 bus_for_each_dev+0x68/0xb8 driver_attach+0x24/0x30 bus_add_driver+0xe4/0x208 driver_register+0x68/0x124 i2c_register_driver+0x48/0xcc lt9611uxc_driver_init+0x20/0x1000 [lontium_lt9611uxc] do_one_initcall+0x60/0x1d4 do_init_module+0x54/0x1fc load_module+0x1748/0x1c8c init_module_from_file+0x74/0xa0 __arm64_sys_finit_module+0x130/0x2f8 invoke_syscall+0x48/0x104 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x2c/0x80 el0t_64_sync_handler+0x10c/0x138 el0t_64_sync+0x198/0x19c ---[ end trace 0000000000000000 ]--- msm_dpu 5e01000.display-controller: [drm:msm_gpu_init [msm]] *ERROR* could not allocate memptrs: -22 msm_dpu 5e01000.display-controller: failed to load adreno gpu platform a400000.remoteproc:glink-edge:apr:service@7:dais: Adding to iommu group 19 msm_dpu 5e01000.display-controller: failed to bind 5900000.gpu (ops a3xx_ops [msm]): -22 msm_dpu 5e01000.display-controller: adev bind failed: -22 lt9611uxc 0-002b: failed to attach dsi to host lt9611uxc 0-002b: probe with driver lt9611uxc failed with error -22 CVE-2025-39739 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39739.html CVE-2025-39739 https://bugzilla.suse.com/1249542 SUSE Bug 1249542 In the Linux kernel, the following vulnerability has been resolved: RDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask() The function divides number of online CPUs by num_core_siblings, and later checks the divider by zero. This implies a possibility to get and divide-by-zero runtime error. Fix it by moving the check prior to division. This also helps to save one indentation level. CVE-2025-39742 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39742.html CVE-2025-39742 https://bugzilla.suse.com/1247374 SUSE Bug 1247374 https://bugzilla.suse.com/1249479 SUSE Bug 1249479 https://bugzilla.suse.com/1249480 SUSE Bug 1249480 https://bugzilla.suse.com/1253291 SUSE Bug 1253291 In the Linux kernel, the following vulnerability has been resolved: jfs: truncate good inode pages when hard link is 0 The fileset value of the inode copy from the disk by the reproducer is AGGR_RESERVED_I. When executing evict, its hard link number is 0, so its inode pages are not truncated. This causes the bugon to be triggered when executing clear_inode() because nrpages is greater than 0. CVE-2025-39743 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39743.html CVE-2025-39743 https://bugzilla.suse.com/1247374 SUSE Bug 1247374 https://bugzilla.suse.com/1249489 SUSE Bug 1249489 https://bugzilla.suse.com/1249491 SUSE Bug 1249491 In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Correct tid cleanup when tid setup fails Currently, if any error occurs during ath12k_dp_rx_peer_tid_setup(), the tid value is already incremented, even though the corresponding TID is not actually allocated. Proceed to ath12k_dp_rx_peer_tid_delete() starting from unallocated tid, which might leads to freeing unallocated TID and cause potential crash or out-of-bounds access. Hence, fix by correctly decrementing tid before cleanup to match only the successfully allocated TIDs. Also, remove tid-- from failure case of ath12k_dp_rx_peer_frag_setup(), as decrementing the tid before cleanup in loop will take care of this. Compile tested only. CVE-2025-39750 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39750.html CVE-2025-39750 https://bugzilla.suse.com/1249523 SUSE Bug 1249523 https://bugzilla.suse.com/1252715 SUSE Bug 1252715 This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. CVE-2025-39751 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39751.html CVE-2025-39751 https://bugzilla.suse.com/1249538 SUSE Bug 1249538 https://bugzilla.suse.com/1249539 SUSE Bug 1249539 In the Linux kernel, the following vulnerability has been resolved: fs: Prevent file descriptor table allocations exceeding INT_MAX When sysctl_nr_open is set to a very high value (for example, 1073741816 as set by systemd), processes attempting to use file descriptors near the limit can trigger massive memory allocation attempts that exceed INT_MAX, resulting in a WARNING in mm/slub.c: WARNING: CPU: 0 PID: 44 at mm/slub.c:5027 __kvmalloc_node_noprof+0x21a/0x288 This happens because kvmalloc_array() and kvmalloc() check if the requested size exceeds INT_MAX and emit a warning when the allocation is not flagged with __GFP_NOWARN. Specifically, when nr_open is set to 1073741816 (0x3ffffff8) and a process calls dup2(oldfd, 1073741880), the kernel attempts to allocate: - File descriptor array: 1073741880 * 8 bytes = 8,589,935,040 bytes - Multiple bitmaps: ~400MB - Total allocation size: > 8GB (exceeding INT_MAX = 2,147,483,647) Reproducer: 1. Set /proc/sys/fs/nr_open to 1073741816: # echo 1073741816 > /proc/sys/fs/nr_open 2. Run a program that uses a high file descriptor: #include <unistd.h> #include <sys/resource.h> int main() { struct rlimit rlim = {1073741824, 1073741824}; setrlimit(RLIMIT_NOFILE, &rlim); dup2(2, 1073741880); // Triggers the warning return 0; } 3. Observe WARNING in dmesg at mm/slub.c:5027 systemd commit a8b627a introduced automatic bumping of fs.nr_open to the maximum possible value. The rationale was that systems with memory control groups (memcg) no longer need separate file descriptor limits since memory is properly accounted. However, this change overlooked that: 1. The kernel's allocation functions still enforce INT_MAX as a maximum size regardless of memcg accounting 2. Programs and tests that legitimately test file descriptor limits can inadvertently trigger massive allocations 3. The resulting allocations (>8GB) are impractical and will always fail systemd's algorithm starts with INT_MAX and keeps halving the value until the kernel accepts it. On most systems, this results in nr_open being set to 1073741816 (0x3ffffff8), which is just under 1GB of file descriptors. While processes rarely use file descriptors near this limit in normal operation, certain selftests (like tools/testing/selftests/core/unshare_test.c) and programs that test file descriptor limits can trigger this issue. Fix this by adding a check in alloc_fdtable() to ensure the requested allocation size does not exceed INT_MAX. This causes the operation to fail with -EMFILE instead of triggering a kernel warning and avoids the impractical >8GB memory allocation request. CVE-2025-39756 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39756.html CVE-2025-39756 https://bugzilla.suse.com/1249512 SUSE Bug 1249512 In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Validate UAC3 cluster segment descriptors UAC3 class segment descriptors need to be verified whether their sizes match with the declared lengths and whether they fit with the allocated buffer sizes, too. Otherwise malicious firmware may lead to the unexpected OOB accesses. CVE-2025-39757 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39757.html CVE-2025-39757 https://bugzilla.suse.com/1249515 SUSE Bug 1249515 In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix the sendmsg byte count in siw_tcp_sendpages Ever since commit c2ff29e99a76 ("siw: Inline do_tcp_sendpages()"), we have been doing this: static int siw_tcp_sendpages(struct socket *s, struct page **page, int offset, size_t size) [...] /* Calculate the number of bytes we need to push, for this page * specifically */ size_t bytes = min_t(size_t, PAGE_SIZE - offset, size); /* If we can't splice it, then copy it in, as normal */ if (!sendpage_ok(page[i])) msg.msg_flags &= ~MSG_SPLICE_PAGES; /* Set the bvec pointing to the page, with len $bytes */ bvec_set_page(&bvec, page[i], bytes, offset); /* Set the iter to $size, aka the size of the whole sendpages (!!!) */ iov_iter_bvec(&msg.msg_iter, ITER_SOURCE, &bvec, 1, size); try_page_again: lock_sock(sk); /* Sendmsg with $size size (!!!) */ rv = tcp_sendmsg_locked(sk, &msg, size); This means we've been sending oversized iov_iters and tcp_sendmsg calls for a while. This has a been a benign bug because sendpage_ok() always returned true. With the recent slab allocator changes being slowly introduced into next (that disallow sendpage on large kmalloc allocations), we have recently hit out-of-bounds crashes, due to slight differences in iov_iter behavior between the MSG_SPLICE_PAGES and "regular" copy paths: (MSG_SPLICE_PAGES) skb_splice_from_iter iov_iter_extract_pages iov_iter_extract_bvec_pages uses i->nr_segs to correctly stop in its tracks before OoB'ing everywhere skb_splice_from_iter gets a "short" read (!MSG_SPLICE_PAGES) skb_copy_to_page_nocache copy=iov_iter_count [...] copy_from_iter /* this doesn't help */ if (unlikely(iter->count < len)) len = iter->count; iterate_bvec ... and we run off the bvecs Fix this by properly setting the iov_iter's byte count, plus sending the correct byte count to tcp_sendmsg_locked. CVE-2025-39758 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39758.html CVE-2025-39758 https://bugzilla.suse.com/1249490 SUSE Bug 1249490 In the Linux kernel, the following vulnerability has been resolved: btrfs: qgroup: fix race between quota disable and quota rescan ioctl There's a race between a task disabling quotas and another running the rescan ioctl that can result in a use-after-free of qgroup records from the fs_info->qgroup_tree rbtree. This happens as follows: 1) Task A enters btrfs_ioctl_quota_rescan() -> btrfs_qgroup_rescan(); 2) Task B enters btrfs_quota_disable() and calls btrfs_qgroup_wait_for_completion(), which does nothing because at that point fs_info->qgroup_rescan_running is false (it wasn't set yet by task A); 3) Task B calls btrfs_free_qgroup_config() which starts freeing qgroups from fs_info->qgroup_tree without taking the lock fs_info->qgroup_lock; 4) Task A enters qgroup_rescan_zero_tracking() which starts iterating the fs_info->qgroup_tree tree while holding fs_info->qgroup_lock, but task B is freeing qgroup records from that tree without holding the lock, resulting in a use-after-free. Fix this by taking fs_info->qgroup_lock at btrfs_free_qgroup_config(). Also at btrfs_qgroup_rescan() don't start the rescan worker if quotas were already disabled. CVE-2025-39759 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39759.html CVE-2025-39759 https://bugzilla.suse.com/1249522 SUSE Bug 1249522 In the Linux kernel, the following vulnerability has been resolved: usb: core: config: Prevent OOB read in SS endpoint companion parsing usb_parse_ss_endpoint_companion() checks descriptor type before length, enabling a potentially odd read outside of the buffer size. Fix this up by checking the size first before looking at any of the fields in the descriptor. CVE-2025-39760 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39760.html CVE-2025-39760 https://bugzilla.suse.com/1249598 SUSE Bug 1249598 In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Decrement TID on RX peer frag setup error handling Currently, TID is not decremented before peer cleanup, during error handling path of ath12k_dp_rx_peer_frag_setup(). This could lead to out-of-bounds access in peer->rx_tid[]. Hence, add a decrement operation for TID, before peer cleanup to ensures proper cleanup and prevents out-of-bounds access issues when the RX peer frag setup fails. Found during code review. Compile tested only. CVE-2025-39761 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39761.html CVE-2025-39761 https://bugzilla.suse.com/1249554 SUSE Bug 1249554 https://bugzilla.suse.com/1249555 SUSE Bug 1249555 In the Linux kernel, the following vulnerability has been resolved: ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered If a synchronous error is detected as a result of user-space process triggering a 2-bit uncorrected error, the CPU will take a synchronous error exception such as Synchronous External Abort (SEA) on Arm64. The kernel will queue a memory_failure() work which poisons the related page, unmaps the page, and then sends a SIGBUS to the process, so that a system wide panic can be avoided. However, no memory_failure() work will be queued when abnormal synchronous errors occur. These errors can include situations like invalid PA, unexpected severity, no memory failure config support, invalid GUID section, etc. In such a case, the user-space process will trigger SEA again. This loop can potentially exceed the platform firmware threshold or even trigger a kernel hard lockup, leading to a system reboot. Fix it by performing a force kill if no memory_failure() work is queued for synchronous errors. [ rjw: Changelog edits ] CVE-2025-39763 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39763.html CVE-2025-39763 https://bugzilla.suse.com/1249615 SUSE Bug 1249615 In the Linux kernel, the following vulnerability has been resolved: drm/hisilicon/hibmc: fix the hibmc loaded failed bug When hibmc loaded failed, the driver use hibmc_unload to free the resource, but the mutexes in mode.config are not init, which will access an NULL pointer. Just change goto statement to return, because hibnc_hw_init() doesn't need to free anything. CVE-2025-39772 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39772.html CVE-2025-39772 https://bugzilla.suse.com/1249506 SUSE Bug 1249506 In the Linux kernel, the following vulnerability has been resolved: PCI: endpoint: Fix configfs group list head handling Doing a list_del() on the epf_group field of struct pci_epf_driver in pci_epf_remove_cfs() is not correct as this field is a list head, not a list entry. This list_del() call triggers a KASAN warning when an endpoint function driver which has a configfs attribute group is torn down: ================================================================== BUG: KASAN: slab-use-after-free in pci_epf_remove_cfs+0x17c/0x198 Write of size 8 at addr ffff00010f4a0d80 by task rmmod/319 CPU: 3 UID: 0 PID: 319 Comm: rmmod Not tainted 6.16.0-rc2 #1 NONE Hardware name: Radxa ROCK 5B (DT) Call trace: show_stack+0x2c/0x84 (C) dump_stack_lvl+0x70/0x98 print_report+0x17c/0x538 kasan_report+0xb8/0x190 __asan_report_store8_noabort+0x20/0x2c pci_epf_remove_cfs+0x17c/0x198 pci_epf_unregister_driver+0x18/0x30 nvmet_pci_epf_cleanup_module+0x24/0x30 [nvmet_pci_epf] __arm64_sys_delete_module+0x264/0x424 invoke_syscall+0x70/0x260 el0_svc_common.constprop.0+0xac/0x230 do_el0_svc+0x40/0x58 el0_svc+0x48/0xdc el0t_64_sync_handler+0x10c/0x138 el0t_64_sync+0x198/0x19c ... Remove this incorrect list_del() call from pci_epf_remove_cfs(). CVE-2025-39783 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39783.html CVE-2025-39783 https://bugzilla.suse.com/1249486 SUSE Bug 1249486 In the Linux kernel, the following vulnerability has been resolved: bus: mhi: host: Detect events pointing to unexpected TREs When a remote device sends a completion event to the host, it contains a pointer to the consumed TRE. The host uses this pointer to process all of the TREs between it and the host's local copy of the ring's read pointer. This works when processing completion for chained transactions, but can lead to nasty results if the device sends an event for a single-element transaction with a read pointer that is multiple elements ahead of the host's read pointer. For instance, if the host accesses an event ring while the device is updating it, the pointer inside of the event might still point to an old TRE. If the host uses the channel's xfer_cb() to directly free the buffer pointed to by the TRE, the buffer will be double-freed. This behavior was observed on an ep that used upstream EP stack without 'commit 6f18d174b73d ("bus: mhi: ep: Update read pointer only after buffer is written")'. Where the device updated the events ring pointer before updating the event contents, so it left a window where the host was able to access the stale data the event pointed to, before the device had the chance to update them. The usual pattern was that the host received an event pointing to a TRE that is not immediately after the last processed one, so it got treated as if it was a chained transaction, processing all of the TREs in between the two read pointers. This commit aims to harden the host by ensuring transactions where the event points to a TRE that isn't local_rp + 1 are chained. [mani: added stable tag and reworded commit message] CVE-2025-39790 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39790.html CVE-2025-39790 https://bugzilla.suse.com/1249548 SUSE Bug 1249548 https://bugzilla.suse.com/1249549 SUSE Bug 1249549 In the Linux kernel, the following vulnerability has been resolved: ARM: tegra: Use I/O memcpy to write to IRAM Kasan crashes the kernel trying to check boundaries when using the normal memcpy. CVE-2025-39794 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39794.html CVE-2025-39794 https://bugzilla.suse.com/1249595 SUSE Bug 1249595 In the Linux kernel, the following vulnerability has been resolved: xfrm: Duplicate SPI Handling The issue originates when Strongswan initiates an XFRM_MSG_ALLOCSPI Netlink message, which triggers the kernel function xfrm_alloc_spi(). This function is expected to ensure uniqueness of the Security Parameter Index (SPI) for inbound Security Associations (SAs). However, it can return success even when the requested SPI is already in use, leading to duplicate SPIs assigned to multiple inbound SAs, differentiated only by their destination addresses. This behavior causes inconsistencies during SPI lookups for inbound packets. Since the lookup may return an arbitrary SA among those with the same SPI, packet processing can fail, resulting in packet drops. According to RFC 4301 section 4.4.2 , for inbound processing a unicast SA is uniquely identified by the SPI and optionally protocol. Reproducing the Issue Reliably: To consistently reproduce the problem, restrict the available SPI range in charon.conf : spi_min = 0x10000000 spi_max = 0x10000002 This limits the system to only 2 usable SPI values. Next, create more than 2 Child SA. each using unique pair of src/dst address. As soon as the 3rd Child SA is initiated, it will be assigned a duplicate SPI, since the SPI pool is already exhausted. With a narrow SPI range, the issue is consistently reproducible. With a broader/default range, it becomes rare and unpredictable. Current implementation: xfrm_spi_hash() lookup function computes hash using daddr, proto, and family. So if two SAs have the same SPI but different destination addresses, then they will: a. Hash into different buckets b. Be stored in different linked lists (byspi + h) c. Not be seen in the same hlist_for_each_entry_rcu() iteration. As a result, the lookup will result in NULL and kernel allows that Duplicate SPI Proposed Change: xfrm_state_lookup_spi_proto() does a truly global search - across all states, regardless of hash bucket and matches SPI and proto. CVE-2025-39797 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39797.html CVE-2025-39797 https://bugzilla.suse.com/1249608 SUSE Bug 1249608 In the Linux kernel, the following vulnerability has been resolved: NFS: Fix the setting of capabilities when automounting a new filesystem Capabilities cannot be inherited when we cross into a new filesystem. They need to be reset to the minimal defaults, and then probed for again. CVE-2025-39798 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39798.html CVE-2025-39798 https://bugzilla.suse.com/1249774 SUSE Bug 1249774 In the Linux kernel, the following vulnerability has been resolved: btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() If we find an unexpected generation for the extent buffer we are cloning at btrfs_copy_root(), we just WARN_ON() and don't error out and abort the transaction, meaning we allow to persist metadata with an unexpected generation. Instead of warning only, abort the transaction and return -EUCLEAN. CVE-2025-39800 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39800.html CVE-2025-39800 https://bugzilla.suse.com/1250177 SUSE Bug 1250177 In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Remove WARN_ON for device endpoint command timeouts This commit addresses a rarely observed endpoint command timeout which causes kernel panic due to warn when 'panic_on_warn' is enabled and unnecessary call trace prints when 'panic_on_warn' is disabled. It is seen during fast software-controlled connect/disconnect testcases. The following is one such endpoint command timeout that we observed: 1. Connect ======= ->dwc3_thread_interrupt ->dwc3_ep0_interrupt ->configfs_composite_setup ->composite_setup ->usb_ep_queue ->dwc3_gadget_ep0_queue ->__dwc3_gadget_ep0_queue ->__dwc3_ep0_do_control_data ->dwc3_send_gadget_ep_cmd 2. Disconnect ========== ->dwc3_thread_interrupt ->dwc3_gadget_disconnect_interrupt ->dwc3_ep0_reset_state ->dwc3_ep0_end_control_data ->dwc3_send_gadget_ep_cmd In the issue scenario, in Exynos platforms, we observed that control transfers for the previous connect have not yet been completed and end transfer command sent as a part of the disconnect sequence and processing of USB_ENDPOINT_HALT feature request from the host timeout. This maybe an expected scenario since the controller is processing EP commands sent as a part of the previous connect. It maybe better to remove WARN_ON in all places where device endpoint commands are sent to avoid unnecessary kernel panic due to warn. CVE-2025-39801 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39801.html CVE-2025-39801 https://bugzilla.suse.com/1250450 SUSE Bug 1250450 In the Linux kernel, the following vulnerability has been resolved: HID: multitouch: fix slab out-of-bounds access in mt_report_fixup() A malicious HID device can trigger a slab out-of-bounds during mt_report_fixup() by passing in report descriptor smaller than 607 bytes. mt_report_fixup() attempts to patch byte offset 607 of the descriptor with 0x25 by first checking if byte offset 607 is 0x15 however it lacks bounds checks to verify if the descriptor is big enough before conducting this check. Fix this bug by ensuring the descriptor size is at least 608 bytes before accessing it. Below is the KASAN splat after the out of bounds access happens: [ 13.671954] ================================================================== [ 13.672667] BUG: KASAN: slab-out-of-bounds in mt_report_fixup+0x103/0x110 [ 13.673297] Read of size 1 at addr ffff888103df39df by task kworker/0:1/10 [ 13.673297] [ 13.673297] CPU: 0 UID: 0 PID: 10 Comm: kworker/0:1 Not tainted 6.15.0-00005-gec5d573d83f4-dirty #3 [ 13.673297] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/04 [ 13.673297] Call Trace: [ 13.673297] <TASK> [ 13.673297] dump_stack_lvl+0x5f/0x80 [ 13.673297] print_report+0xd1/0x660 [ 13.673297] kasan_report+0xe5/0x120 [ 13.673297] __asan_report_load1_noabort+0x18/0x20 [ 13.673297] mt_report_fixup+0x103/0x110 [ 13.673297] hid_open_report+0x1ef/0x810 [ 13.673297] mt_probe+0x422/0x960 [ 13.673297] hid_device_probe+0x2e2/0x6f0 [ 13.673297] really_probe+0x1c6/0x6b0 [ 13.673297] __driver_probe_device+0x24f/0x310 [ 13.673297] driver_probe_device+0x4e/0x220 [ 13.673297] __device_attach_driver+0x169/0x320 [ 13.673297] bus_for_each_drv+0x11d/0x1b0 [ 13.673297] __device_attach+0x1b8/0x3e0 [ 13.673297] device_initial_probe+0x12/0x20 [ 13.673297] bus_probe_device+0x13d/0x180 [ 13.673297] device_add+0xe3a/0x1670 [ 13.673297] hid_add_device+0x31d/0xa40 [...] CVE-2025-39806 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39806.html CVE-2025-39806 https://bugzilla.suse.com/1249888 SUSE Bug 1249888 In the Linux kernel, the following vulnerability has been resolved: HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() in ntrig_report_version(), hdev parameter passed from hid_probe(). sending descriptor to /dev/uhid can make hdev->dev.parent->parent to null if hdev->dev.parent->parent is null, usb_dev has invalid address(0xffffffffffffff58) that hid_to_usb_dev(hdev) returned when usb_rcvctrlpipe() use usb_dev,it trigger page fault error for address(0xffffffffffffff58) add null check logic to ntrig_report_version() before calling hid_to_usb_dev() CVE-2025-39808 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39808.html CVE-2025-39808 https://bugzilla.suse.com/1250088 SUSE Bug 1250088 In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix memory corruption when FW resources change during ifdown bnxt_set_dflt_rings() assumes that it is always called before any TC has been created. So it doesn't take bp->num_tc into account and assumes that it is always 0 or 1. In the FW resource or capability change scenario, the FW will return flags in bnxt_hwrm_if_change() that will cause the driver to reinitialize and call bnxt_cancel_reservations(). This will lead to bnxt_init_dflt_ring_mode() calling bnxt_set_dflt_rings() and bp->num_tc may be greater than 1. This will cause bp->tx_ring[] to be sized too small and cause memory corruption in bnxt_alloc_cp_rings(). Fix it by properly scaling the TX rings by bp->num_tc in the code paths mentioned above. Add 2 helper functions to determine bp->tx_nr_rings and bp->tx_nr_rings_per_tc. CVE-2025-39810 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39810.html CVE-2025-39810 https://bugzilla.suse.com/1249975 SUSE Bug 1249975 In the Linux kernel, the following vulnerability has been resolved: sctp: initialize more fields in sctp_v6_from_sk() syzbot found that sin6_scope_id was not properly initialized, leading to undefined behavior. Clear sin6_scope_id and sin6_flowinfo. BUG: KMSAN: uninit-value in __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649 __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649 sctp_inet6_cmp_addr+0x4f2/0x510 net/sctp/ipv6.c:983 sctp_bind_addr_conflict+0x22a/0x3b0 net/sctp/bind_addr.c:390 sctp_get_port_local+0x21eb/0x2440 net/sctp/socket.c:8452 sctp_get_port net/sctp/socket.c:8523 [inline] sctp_listen_start net/sctp/socket.c:8567 [inline] sctp_inet_listen+0x710/0xfd0 net/sctp/socket.c:8636 __sys_listen_socket net/socket.c:1912 [inline] __sys_listen net/socket.c:1927 [inline] __do_sys_listen net/socket.c:1932 [inline] __se_sys_listen net/socket.c:1930 [inline] __x64_sys_listen+0x343/0x4c0 net/socket.c:1930 x64_sys_call+0x271d/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:51 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Local variable addr.i.i created at: sctp_get_port net/sctp/socket.c:8515 [inline] sctp_listen_start net/sctp/socket.c:8567 [inline] sctp_inet_listen+0x650/0xfd0 net/sctp/socket.c:8636 __sys_listen_socket net/socket.c:1912 [inline] __sys_listen net/socket.c:1927 [inline] __do_sys_listen net/socket.c:1932 [inline] __se_sys_listen net/socket.c:1930 [inline] __x64_sys_listen+0x343/0x4c0 net/socket.c:1930 CVE-2025-39812 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39812.html CVE-2025-39812 https://bugzilla.suse.com/1250202 SUSE Bug 1250202 In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump When calling ftrace_dump_one() concurrently with reading trace_pipe, a WARN_ON_ONCE() in trace_printk_seq() can be triggered due to a race condition. The issue occurs because: CPU0 (ftrace_dump) CPU1 (reader) echo z > /proc/sysrq-trigger !trace_empty(&iter) trace_iterator_reset(&iter) <- len = size = 0 cat /sys/kernel/tracing/trace_pipe trace_find_next_entry_inc(&iter) __find_next_entry ring_buffer_empty_cpu <- all empty return NULL trace_printk_seq(&iter.seq) WARN_ON_ONCE(s->seq.len >= s->seq.size) In the context between trace_empty() and trace_find_next_entry_inc() during ftrace_dump, the ring buffer data was consumed by other readers. This caused trace_find_next_entry_inc to return NULL, failing to populate `iter.seq`. At this point, due to the prior trace_iterator_reset, both `iter.seq.len` and `iter.seq.size` were set to 0. Since they are equal, the WARN_ON_ONCE condition is triggered. Move the trace_printk_seq() into the if block that checks to make sure the return value of trace_find_next_entry_inc() is non-NULL in ftrace_dump_one(), ensuring the 'iter.seq' is properly populated before subsequent operations. CVE-2025-39813 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39813.html CVE-2025-39813 https://bugzilla.suse.com/1250032 SUSE Bug 1250032 In the Linux kernel, the following vulnerability has been resolved: HID: asus: fix UAF via HID_CLAIMED_INPUT validation After hid_hw_start() is called hidinput_connect() will eventually be called to set up the device with the input layer since the HID_CONNECT_DEFAULT connect mask is used. During hidinput_connect() all input and output reports are processed and corresponding hid_inputs are allocated and configured via hidinput_configure_usages(). This process involves slot tagging report fields and configuring usages by setting relevant bits in the capability bitmaps. However it is possible that the capability bitmaps are not set at all leading to the subsequent hidinput_has_been_populated() check to fail leading to the freeing of the hid_input and the underlying input device. This becomes problematic because a malicious HID device like a ASUS ROG N-Key keyboard can trigger the above scenario via a specially crafted descriptor which then leads to a user-after-free when the name of the freed input device is written to later on after hid_hw_start(). Below, report 93 intentionally utilises the HID_UP_UNDEFINED Usage Page which is skipped during usage configuration, leading to the frees. 0x05, 0x0D, // Usage Page (Digitizer) 0x09, 0x05, // Usage (Touch Pad) 0xA1, 0x01, // Collection (Application) 0x85, 0x0D, // Report ID (13) 0x06, 0x00, 0xFF, // Usage Page (Vendor Defined 0xFF00) 0x09, 0xC5, // Usage (0xC5) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x04, // Report Count (4) 0xB1, 0x02, // Feature (Data,Var,Abs) 0x85, 0x5D, // Report ID (93) 0x06, 0x00, 0x00, // Usage Page (Undefined) 0x09, 0x01, // Usage (0x01) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x1B, // Report Count (27) 0x81, 0x02, // Input (Data,Var,Abs) 0xC0, // End Collection Below is the KASAN splat after triggering the UAF: [ 21.672709] ================================================================== [ 21.673700] BUG: KASAN: slab-use-after-free in asus_probe+0xeeb/0xf80 [ 21.673700] Write of size 8 at addr ffff88810a0ac000 by task kworker/1:2/54 [ 21.673700] [ 21.673700] CPU: 1 UID: 0 PID: 54 Comm: kworker/1:2 Not tainted 6.16.0-rc4-g9773391cf4dd-dirty #36 PREEMPT(voluntary) [ 21.673700] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 [ 21.673700] Call Trace: [ 21.673700] <TASK> [ 21.673700] dump_stack_lvl+0x5f/0x80 [ 21.673700] print_report+0xd1/0x660 [ 21.673700] kasan_report+0xe5/0x120 [ 21.673700] __asan_report_store8_noabort+0x1b/0x30 [ 21.673700] asus_probe+0xeeb/0xf80 [ 21.673700] hid_device_probe+0x2ee/0x700 [ 21.673700] really_probe+0x1c6/0x6b0 [ 21.673700] __driver_probe_device+0x24f/0x310 [ 21.673700] driver_probe_device+0x4e/0x220 [...] [ 21.673700] [ 21.673700] Allocated by task 54: [ 21.673700] kasan_save_stack+0x3d/0x60 [ 21.673700] kasan_save_track+0x18/0x40 [ 21.673700] kasan_save_alloc_info+0x3b/0x50 [ 21.673700] __kasan_kmalloc+0x9c/0xa0 [ 21.673700] __kmalloc_cache_noprof+0x139/0x340 [ 21.673700] input_allocate_device+0x44/0x370 [ 21.673700] hidinput_connect+0xcb6/0x2630 [ 21.673700] hid_connect+0xf74/0x1d60 [ 21.673700] hid_hw_start+0x8c/0x110 [ 21.673700] asus_probe+0x5a3/0xf80 [ 21.673700] hid_device_probe+0x2ee/0x700 [ 21.673700] really_probe+0x1c6/0x6b0 [ 21.673700] __driver_probe_device+0x24f/0x310 [ 21.673700] driver_probe_device+0x4e/0x220 [...] [ 21.673700] [ 21.673700] Freed by task 54: [ 21.673700] kasan_save_stack+0x3d/0x60 [ 21.673700] kasan_save_track+0x18/0x40 [ 21.673700] kasan_save_free_info+0x3f/0x60 [ 21.673700] __kasan_slab_free+0x3c/0x50 [ 21.673700] kfre ---truncated--- CVE-2025-39824 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39824.html CVE-2025-39824 https://bugzilla.suse.com/1250007 SUSE Bug 1250007 In the Linux kernel, the following vulnerability has been resolved: net: rose: convert 'use' field to refcount_t The 'use' field in struct rose_neigh is used as a reference counter but lacks atomicity. This can lead to race conditions where a rose_neigh structure is freed while still being referenced by other code paths. For example, when rose_neigh->use becomes zero during an ioctl operation via rose_rt_ioctl(), the structure may be removed while its timer is still active, potentially causing use-after-free issues. This patch changes the type of 'use' from unsigned short to refcount_t and updates all code paths to use rose_neigh_hold() and rose_neigh_put() which operate reference counts atomically. CVE-2025-39826 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39826.html CVE-2025-39826 https://bugzilla.suse.com/1250203 SUSE Bug 1250203 https://bugzilla.suse.com/1252713 SUSE Bug 1252713 In the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot. CVE-2025-39827 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39827.html CVE-2025-39827 https://bugzilla.suse.com/1250204 SUSE Bug 1250204 https://bugzilla.suse.com/1252714 SUSE Bug 1252714 In the Linux kernel, the following vulnerability has been resolved: atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). syzbot reported the splat below. [0] When atmtcp_v_open() or atmtcp_v_close() is called via connect() or close(), atmtcp_send_control() is called to send an in-kernel special message. The message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length. Also, a pointer of struct atm_vcc is set to atmtcp_control.vcc. The notable thing is struct atmtcp_control is uAPI but has a space for an in-kernel pointer. struct atmtcp_control { struct atmtcp_hdr hdr; /* must be first */ ... atm_kptr_t vcc; /* both directions */ ... } __ATM_API_ALIGN; typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t; The special message is processed in atmtcp_recv_control() called from atmtcp_c_send(). atmtcp_c_send() is vcc->dev->ops->send() and called from 2 paths: 1. .ndo_start_xmit() (vcc->send() == atm_send_aal0()) 2. vcc_sendmsg() The problem is sendmsg() does not validate the message length and userspace can abuse atmtcp_recv_control() to overwrite any kptr by atmtcp_control. Let's add a new ->pre_send() hook to validate messages from sendmsg(). [0]: Oops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI KASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f] CPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline] RIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297 Code: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c RSP: 0018:ffffc90003f5f810 EFLAGS: 00010203 RAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c RBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd R10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000 R13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff FS: 00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0 Call Trace: <TASK> vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg+0x219/0x270 net/socket.c:729 ____sys_sendmsg+0x505/0x830 net/socket.c:2614 ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668 __sys_sendmsg net/socket.c:2700 [inline] __do_sys_sendmsg net/socket.c:2705 [inline] __se_sys_sendmsg net/socket.c:2703 [inline] __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2703 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f8d7e96a4a9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9 RDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005 RBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f R10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac R13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250 </TASK> Modules linked in: CVE-2025-39828 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39828.html CVE-2025-39828 https://bugzilla.suse.com/1250205 SUSE Bug 1250205 In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix lockdep assertion on sync reset unload event Fix lockdep assertion triggered during sync reset unload event. When the sync reset flow is initiated using the devlink reload fw_activate option, the PF already holds the devlink lock while handling unload event. In this case, delegate sync reset unload event handling back to the devlink callback process to avoid double-locking and resolve the lockdep warning. Kernel log: WARNING: CPU: 9 PID: 1578 at devl_assert_locked+0x31/0x40 [...] Call Trace: <TASK> mlx5_unload_one_devl_locked+0x2c/0xc0 [mlx5_core] mlx5_sync_reset_unload_event+0xaf/0x2f0 [mlx5_core] process_one_work+0x222/0x640 worker_thread+0x199/0x350 kthread+0x10b/0x230 ? __pfx_worker_thread+0x10/0x10 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x8e/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> CVE-2025-39832 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39832.html CVE-2025-39832 https://bugzilla.suse.com/1249901 SUSE Bug 1249901 In the Linux kernel, the following vulnerability has been resolved: mISDN: hfcpci: Fix warning when deleting uninitialized timer With CONFIG_DEBUG_OBJECTS_TIMERS unloading hfcpci module leads to the following splat: [ 250.215892] ODEBUG: assert_init not available (active state 0) object: ffffffffc01a3dc0 object type: timer_list hint: 0x0 [ 250.217520] WARNING: CPU: 0 PID: 233 at lib/debugobjects.c:612 debug_print_object+0x1b6/0x2c0 [ 250.218775] Modules linked in: hfcpci(-) mISDN_core [ 250.219537] CPU: 0 UID: 0 PID: 233 Comm: rmmod Not tainted 6.17.0-rc2-g6f713187ac98 #2 PREEMPT(voluntary) [ 250.220940] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 250.222377] RIP: 0010:debug_print_object+0x1b6/0x2c0 [ 250.223131] Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 4f 41 56 48 8b 14 dd a0 4e 01 9f 48 89 ee 48 c7 c7 20 46 01 9f e8 cb 84d [ 250.225805] RSP: 0018:ffff888015ea7c08 EFLAGS: 00010286 [ 250.226608] RAX: 0000000000000000 RBX: 0000000000000005 RCX: ffffffff9be93a95 [ 250.227708] RDX: 1ffff1100d945138 RSI: 0000000000000008 RDI: ffff88806ca289c0 [ 250.228993] RBP: ffffffff9f014a00 R08: 0000000000000001 R09: ffffed1002bd4f39 [ 250.230043] R10: ffff888015ea79cf R11: 0000000000000001 R12: 0000000000000001 [ 250.231185] R13: ffffffff9eea0520 R14: 0000000000000000 R15: ffff888015ea7cc8 [ 250.232454] FS: 00007f3208f01540(0000) GS:ffff8880caf5a000(0000) knlGS:0000000000000000 [ 250.233851] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 250.234856] CR2: 00007f32090a7421 CR3: 0000000004d63000 CR4: 00000000000006f0 [ 250.236117] Call Trace: [ 250.236599] <TASK> [ 250.236967] ? trace_irq_enable.constprop.0+0xd4/0x130 [ 250.237920] debug_object_assert_init+0x1f6/0x310 [ 250.238762] ? __pfx_debug_object_assert_init+0x10/0x10 [ 250.239658] ? __lock_acquire+0xdea/0x1c70 [ 250.240369] __try_to_del_timer_sync+0x69/0x140 [ 250.241172] ? __pfx___try_to_del_timer_sync+0x10/0x10 [ 250.242058] ? __timer_delete_sync+0xc6/0x120 [ 250.242842] ? lock_acquire+0x30/0x80 [ 250.243474] ? __timer_delete_sync+0xc6/0x120 [ 250.244262] __timer_delete_sync+0x98/0x120 [ 250.245015] HFC_cleanup+0x10/0x20 [hfcpci] [ 250.245704] __do_sys_delete_module+0x348/0x510 [ 250.246461] ? __pfx___do_sys_delete_module+0x10/0x10 [ 250.247338] do_syscall_64+0xc1/0x360 [ 250.247924] entry_SYSCALL_64_after_hwframe+0x77/0x7f Fix this by initializing hfc_tl timer with DEFINE_TIMER macro. Also, use mod_timer instead of manual timeout update. CVE-2025-39833 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39833.html CVE-2025-39833 https://bugzilla.suse.com/1250028 SUSE Bug 1250028 In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix OOB read/write in network-coding decode batadv_nc_skb_decode_packet() trusts coded_len and checks only against skb->len. XOR starts at sizeof(struct batadv_unicast_packet), reducing payload headroom, and the source skb length is not verified, allowing an out-of-bounds read and a small out-of-bounds write. Validate that coded_len fits within the payload area of both destination and source sk_buffs before XORing. CVE-2025-39839 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39839.html CVE-2025-39839 https://bugzilla.suse.com/1250291 SUSE Bug 1250291 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix buffer free/clear order in deferred receive path Fix a use-after-free window by correcting the buffer release sequence in the deferred receive path. The code freed the RQ buffer first and only then cleared the context pointer under the lock. Concurrent paths (e.g., ABTS and the repost path) also inspect and release the same pointer under the lock, so the old order could lead to double-free/UAF. Note that the repost path already uses the correct pattern: detach the pointer under the lock, then free it after dropping the lock. The deferred path should do the same. CVE-2025-39841 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39841.html CVE-2025-39841 https://bugzilla.suse.com/1250274 SUSE Bug 1250274 In the Linux kernel, the following vulnerability has been resolved: mm: move page table sync declarations to linux/pgtable.h During our internal testing, we started observing intermittent boot failures when the machine uses 4-level paging and has a large amount of persistent memory: BUG: unable to handle page fault for address: ffffe70000000034 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI RIP: 0010:__init_single_page+0x9/0x6d Call Trace: <TASK> __init_zone_device_page+0x17/0x5d memmap_init_zone_device+0x154/0x1bb pagemap_range+0x2e0/0x40f memremap_pages+0x10b/0x2f0 devm_memremap_pages+0x1e/0x60 dev_dax_probe+0xce/0x2ec [device_dax] dax_bus_probe+0x6d/0xc9 [... snip ...] </TASK> It turns out that the kernel panics while initializing vmemmap (struct page array) when the vmemmap region spans two PGD entries, because the new PGD entry is only installed in init_mm.pgd, but not in the page tables of other tasks. And looking at __populate_section_memmap(): if (vmemmap_can_optimize(altmap, pgmap)) // does not sync top level page tables r = vmemmap_populate_compound_pages(pfn, start, end, nid, pgmap); else // sync top level page tables in x86 r = vmemmap_populate(start, end, nid, altmap); In the normal path, vmemmap_populate() in arch/x86/mm/init_64.c synchronizes the top level page table (See commit 9b861528a801 ("x86-64, mem: Update all PGDs for direct mapping and vmemmap mapping changes")) so that all tasks in the system can see the new vmemmap area. However, when vmemmap_can_optimize() returns true, the optimized path skips synchronization of top-level page tables. This is because vmemmap_populate_compound_pages() is implemented in core MM code, which does not handle synchronization of the top-level page tables. Instead, the core MM has historically relied on each architecture to perform this synchronization manually. We're not the first party to encounter a crash caused by not-sync'd top level page tables: earlier this year, Gwan-gyeong Mun attempted to address the issue [1] [2] after hitting a kernel panic when x86 code accessed the vmemmap area before the corresponding top-level entries were synced. At that time, the issue was believed to be triggered only when struct page was enlarged for debugging purposes, and the patch did not get further updates. It turns out that current approach of relying on each arch to handle the page table sync manually is fragile because 1) it's easy to forget to sync the top level page table, and 2) it's also easy to overlook that the kernel should not access the vmemmap and direct mapping areas before the sync. # The solution: Make page table sync more code robust and harder to miss To address this, Dave Hansen suggested [3] [4] introducing {pgd,p4d}_populate_kernel() for updating kernel portion of the page tables and allow each architecture to explicitly perform synchronization when installing top-level entries. With this approach, we no longer need to worry about missing the sync step, reducing the risk of future regressions. The new interface reuses existing ARCH_PAGE_TABLE_SYNC_MASK, PGTBL_P*D_MODIFIED and arch_sync_kernel_mappings() facility used by vmalloc and ioremap to synchronize page tables. pgd_populate_kernel() looks like this: static inline void pgd_populate_kernel(unsigned long addr, pgd_t *pgd, p4d_t *p4d) { pgd_populate(&init_mm, pgd, p4d); if (ARCH_PAGE_TABLE_SYNC_MASK & PGTBL_PGD_MODIFIED) arch_sync_kernel_mappings(addr, addr); } It is worth noting that vmalloc() and apply_to_range() carefully synchronizes page tables by calling p*d_alloc_track() and arch_sync_kernel_mappings(), and thus they are not affected by ---truncated--- CVE-2025-39844 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39844.html CVE-2025-39844 https://bugzilla.suse.com/1250268 SUSE Bug 1250268 In the Linux kernel, the following vulnerability has been resolved: x86/mm/64: define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() Define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() to ensure page tables are properly synchronized when calling p*d_populate_kernel(). For 5-level paging, synchronization is performed via pgd_populate_kernel(). In 4-level paging, pgd_populate() is a no-op, so synchronization is instead performed at the P4D level via p4d_populate_kernel(). This fixes intermittent boot failures on systems using 4-level paging and a large amount of persistent memory: BUG: unable to handle page fault for address: ffffe70000000034 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI RIP: 0010:__init_single_page+0x9/0x6d Call Trace: <TASK> __init_zone_device_page+0x17/0x5d memmap_init_zone_device+0x154/0x1bb pagemap_range+0x2e0/0x40f memremap_pages+0x10b/0x2f0 devm_memremap_pages+0x1e/0x60 dev_dax_probe+0xce/0x2ec [device_dax] dax_bus_probe+0x6d/0xc9 [... snip ...] </TASK> It also fixes a crash in vmemmap_set_pmd() caused by accessing vmemmap before sync_global_pgds() [1]: BUG: unable to handle page fault for address: ffffeb3ff1200000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: Oops: 0002 [#1] PREEMPT SMP NOPTI Tainted: [W]=WARN RIP: 0010:vmemmap_set_pmd+0xff/0x230 <TASK> vmemmap_populate_hugepages+0x176/0x180 vmemmap_populate+0x34/0x80 __populate_section_memmap+0x41/0x90 sparse_add_section+0x121/0x3e0 __add_pages+0xba/0x150 add_pages+0x1d/0x70 memremap_pages+0x3dc/0x810 devm_memremap_pages+0x1c/0x60 xe_devm_add+0x8b/0x100 [xe] xe_tile_init_noalloc+0x6a/0x70 [xe] xe_device_probe+0x48c/0x740 [xe] [... snip ...] CVE-2025-39845 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39845.html CVE-2025-39845 https://bugzilla.suse.com/1250262 SUSE Bug 1250262 In the Linux kernel, the following vulnerability has been resolved: pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() In __iodyn_find_io_region(), pcmcia_make_resource() is assigned to res and used in pci_bus_alloc_resource(). There is a dereference of res in pci_bus_alloc_resource(), which could lead to a NULL pointer dereference on failure of pcmcia_make_resource(). Fix this bug by adding a check of res. CVE-2025-39846 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39846.html CVE-2025-39846 https://bugzilla.suse.com/1250263 SUSE Bug 1250263 In the Linux kernel, the following vulnerability has been resolved: ppp: fix memory leak in pad_compress_skb If alloc_skb() fails in pad_compress_skb(), it returns NULL without releasing the old skb. The caller does: skb = pad_compress_skb(ppp, skb); if (!skb) goto drop; drop: kfree_skb(skb); When pad_compress_skb() returns NULL, the reference to the old skb is lost and kfree_skb(skb) ends up doing nothing, leading to a memory leak. Align pad_compress_skb() semantics with realloc(): only free the old skb if allocation and compression succeed. At the call site, use the new_skb variable so the original skb is not lost when pad_compress_skb() fails. CVE-2025-39847 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39847.html CVE-2025-39847 https://bugzilla.suse.com/1250292 SUSE Bug 1250292 In the Linux kernel, the following vulnerability has been resolved: ax25: properly unshare skbs in ax25_kiss_rcv() Bernard Pidoux reported a regression apparently caused by commit c353e8983e0d ("net: introduce per netns packet chains"). skb->dev becomes NULL and we crash in __netif_receive_skb_core(). Before above commit, different kind of bugs or corruptions could happen without a major crash. But the root cause is that ax25_kiss_rcv() can queue/mangle input skb without checking if this skb is shared or not. Many thanks to Bernard Pidoux for his help, diagnosis and tests. We had a similar issue years ago fixed with commit 7aaed57c5c28 ("phonet: properly unshare skbs in phonet_rcv()"). CVE-2025-39848 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39848.html CVE-2025-39848 https://bugzilla.suse.com/1250298 SUSE Bug 1250298 In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() If the ssid->datalen is more than IEEE80211_MAX_SSID_LEN (32) it would lead to memory corruption so add some bounds checking. CVE-2025-39849 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39849.html CVE-2025-39849 https://bugzilla.suse.com/1250266 SUSE Bug 1250266 In the Linux kernel, the following vulnerability has been resolved: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects When the "proxy" option is enabled on a VXLAN device, the device will suppress ARP requests and IPv6 Neighbor Solicitation messages if it is able to reply on behalf of the remote host. That is, if a matching and valid neighbor entry is configured on the VXLAN device whose MAC address is not behind the "any" remote (0.0.0.0 / ::). The code currently assumes that the FDB entry for the neighbor's MAC address points to a valid remote destination, but this is incorrect if the entry is associated with an FDB nexthop group. This can result in a NPD [1][3] which can be reproduced using [2][4]. Fix by checking that the remote destination exists before dereferencing it. [1] BUG: kernel NULL pointer dereference, address: 0000000000000000 [...] CPU: 4 UID: 0 PID: 365 Comm: arping Not tainted 6.17.0-rc2-virtme-g2a89cb21162c #2 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 RIP: 0010:vxlan_xmit+0xb58/0x15f0 [...] Call Trace: <TASK> dev_hard_start_xmit+0x5d/0x1c0 __dev_queue_xmit+0x246/0xfd0 packet_sendmsg+0x113a/0x1850 __sock_sendmsg+0x38/0x70 __sys_sendto+0x126/0x180 __x64_sys_sendto+0x24/0x30 do_syscall_64+0xa4/0x260 entry_SYSCALL_64_after_hwframe+0x4b/0x53 [2] #!/bin/bash ip address add 192.0.2.1/32 dev lo ip nexthop add id 1 via 192.0.2.2 fdb ip nexthop add id 10 group 1 fdb ip link add name vx0 up type vxlan id 10010 local 192.0.2.1 dstport 4789 proxy ip neigh add 192.0.2.3 lladdr 00:11:22:33:44:55 nud perm dev vx0 bridge fdb add 00:11:22:33:44:55 dev vx0 self static nhid 10 arping -b -c 1 -s 192.0.2.1 -I vx0 192.0.2.3 [3] BUG: kernel NULL pointer dereference, address: 0000000000000000 [...] CPU: 13 UID: 0 PID: 372 Comm: ndisc6 Not tainted 6.17.0-rc2-virtmne-g6ee90cb26014 #3 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1v996), BIOS 1.17.0-4.fc41 04/01/2x014 RIP: 0010:vxlan_xmit+0x803/0x1600 [...] Call Trace: <TASK> dev_hard_start_xmit+0x5d/0x1c0 __dev_queue_xmit+0x246/0xfd0 ip6_finish_output2+0x210/0x6c0 ip6_finish_output+0x1af/0x2b0 ip6_mr_output+0x92/0x3e0 ip6_send_skb+0x30/0x90 rawv6_sendmsg+0xe6e/0x12e0 __sock_sendmsg+0x38/0x70 __sys_sendto+0x126/0x180 __x64_sys_sendto+0x24/0x30 do_syscall_64+0xa4/0x260 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f383422ec77 [4] #!/bin/bash ip address add 2001:db8:1::1/128 dev lo ip nexthop add id 1 via 2001:db8:1::1 fdb ip nexthop add id 10 group 1 fdb ip link add name vx0 up type vxlan id 10010 local 2001:db8:1::1 dstport 4789 proxy ip neigh add 2001:db8:1::3 lladdr 00:11:22:33:44:55 nud perm dev vx0 bridge fdb add 00:11:22:33:44:55 dev vx0 self static nhid 10 ndisc6 -r 1 -s 2001:db8:1::1 -w 1 2001:db8:1::3 vx0 CVE-2025-39850 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39850.html CVE-2025-39850 https://bugzilla.suse.com/1250276 SUSE Bug 1250276 In the Linux kernel, the following vulnerability has been resolved: vxlan: Fix NPD when refreshing an FDB entry with a nexthop object VXLAN FDB entries can point to either a remote destination or an FDB nexthop group. The latter is usually used in EVPN deployments where learning is disabled. However, when learning is enabled, an incoming packet might try to refresh an FDB entry that points to an FDB nexthop group and therefore does not have a remote. Such packets should be dropped, but they are only dropped after dereferencing the non-existent remote, resulting in a NPD [1] which can be reproduced using [2]. Fix by dropping such packets earlier. Remove the misleading comment from first_remote_rcu(). [1] BUG: kernel NULL pointer dereference, address: 0000000000000000 [...] CPU: 13 UID: 0 PID: 361 Comm: mausezahn Not tainted 6.17.0-rc1-virtme-g9f6b606b6b37 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 RIP: 0010:vxlan_snoop+0x98/0x1e0 [...] Call Trace: <TASK> vxlan_encap_bypass+0x209/0x240 encap_bypass_if_local+0xb1/0x100 vxlan_xmit_one+0x1375/0x17e0 vxlan_xmit+0x6b4/0x15f0 dev_hard_start_xmit+0x5d/0x1c0 __dev_queue_xmit+0x246/0xfd0 packet_sendmsg+0x113a/0x1850 __sock_sendmsg+0x38/0x70 __sys_sendto+0x126/0x180 __x64_sys_sendto+0x24/0x30 do_syscall_64+0xa4/0x260 entry_SYSCALL_64_after_hwframe+0x4b/0x53 [2] #!/bin/bash ip address add 192.0.2.1/32 dev lo ip address add 192.0.2.2/32 dev lo ip nexthop add id 1 via 192.0.2.3 fdb ip nexthop add id 10 group 1 fdb ip link add name vx0 up type vxlan id 10010 local 192.0.2.1 dstport 12345 localbypass ip link add name vx1 up type vxlan id 10020 local 192.0.2.2 dstport 54321 learning bridge fdb add 00:11:22:33:44:55 dev vx0 self static dst 192.0.2.2 port 54321 vni 10020 bridge fdb add 00:aa:bb:cc:dd:ee dev vx1 self static nhid 10 mausezahn vx0 -a 00:aa:bb:cc:dd:ee -b 00:11:22:33:44:55 -c 1 -q CVE-2025-39851 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39851.html CVE-2025-39851 https://bugzilla.suse.com/1250296 SUSE Bug 1250296 In the Linux kernel, the following vulnerability has been resolved: i40e: Fix potential invalid access when MAC list is empty list_first_entry() never returns NULL - if the list is empty, it still returns a pointer to an invalid object, leading to potential invalid memory access when dereferenced. Fix this by using list_first_entry_or_null instead of list_first_entry. CVE-2025-39853 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39853.html CVE-2025-39853 https://bugzilla.suse.com/1250275 SUSE Bug 1250275 In the Linux kernel, the following vulnerability has been resolved: ice: fix NULL access of tx->in_use in ice_ll_ts_intr Recent versions of the E810 firmware have support for an extra interrupt to handle report of the "low latency" Tx timestamps coming from the specialized low latency firmware interface. Instead of polling the registers, software can wait until the low latency interrupt is fired. This logic makes use of the Tx timestamp tracking structure, ice_ptp_tx, as it uses the same "ready" bitmap to track which Tx timestamps complete. Unfortunately, the ice_ll_ts_intr() function does not check if the tracker is initialized before its first access. This results in NULL dereference or use-after-free bugs similar to the issues fixed in the ice_ptp_ts_irq() function. Fix this by only checking the in_use bitmap (and other fields) if the tracker is marked as initialized. The reset flow will clear the init field under lock before it tears the tracker down, thus preventing any use-after-free or NULL access. CVE-2025-39854 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39854.html CVE-2025-39854 https://bugzilla.suse.com/1250297 SUSE Bug 1250297 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() syzbot reported the splat below without a repro. In the splat, a single thread calling bt_accept_dequeue() freed sk and touched it after that. The root cause would be the racy l2cap_sock_cleanup_listen() call added by the cited commit. bt_accept_dequeue() is called under lock_sock() except for l2cap_sock_release(). Two threads could see the same socket during the list iteration in bt_accept_dequeue(): CPU1 CPU2 (close()) ---- ---- sock_hold(sk) sock_hold(sk); lock_sock(sk) <-- block close() sock_put(sk) bt_accept_unlink(sk) sock_put(sk) <-- refcnt by bt_accept_enqueue() release_sock(sk) lock_sock(sk) sock_put(sk) bt_accept_unlink(sk) sock_put(sk) <-- last refcnt bt_accept_unlink(sk) <-- UAF Depending on the timing, the other thread could show up in the "Freed by task" part. Let's call l2cap_sock_cleanup_listen() under lock_sock() in l2cap_sock_release(). [0]: BUG: KASAN: slab-use-after-free in debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline] BUG: KASAN: slab-use-after-free in do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115 Read of size 4 at addr ffff88803b7eb1c4 by task syz.5.3276/16995 CPU: 3 UID: 0 PID: 16995 Comm: syz.5.3276 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcd/0x630 mm/kasan/report.c:482 kasan_report+0xe0/0x110 mm/kasan/report.c:595 debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline] do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115 spin_lock_bh include/linux/spinlock.h:356 [inline] release_sock+0x21/0x220 net/core/sock.c:3746 bt_accept_dequeue+0x505/0x600 net/bluetooth/af_bluetooth.c:312 l2cap_sock_cleanup_listen+0x5c/0x2a0 net/bluetooth/l2cap_sock.c:1451 l2cap_sock_release+0x5c/0x210 net/bluetooth/l2cap_sock.c:1425 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x3ff/0xb70 fs/file_table.c:468 task_work_run+0x14d/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xeb/0x110 kernel/entry/common.c:43 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline] do_syscall_64+0x3f6/0x4c0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f2accf8ebe9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffdb6cb1378 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: 0000000000000000 RBX: 00000000000426fb RCX: 00007f2accf8ebe9 RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003 RBP: 00007f2acd1b7da0 R08: 0000000000000001 R09: 00000012b6cb166f R10: 0000001b30e20000 R11: 0000000000000246 R12: 00007f2acd1b609c R13: 00007f2acd1b6090 R14: ffffffffffffffff R15: 00007ffdb6cb1490 </TASK> Allocated by task 5326: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:388 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:405 kasan_kmalloc include/linux/kasan.h:260 [inline] __do_kmalloc_node mm/slub.c:4365 [inline] __kmalloc_nopro ---truncated--- CVE-2025-39860 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39860.html CVE-2025-39860 https://bugzilla.suse.com/1250247 SUSE Bug 1250247 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: vhci: Prevent use-after-free by removing debugfs files early Move the creation of debugfs files into a dedicated function, and ensure they are explicitly removed during vhci_release(), before associated data structures are freed. Previously, debugfs files such as "force_suspend", "force_wakeup", and others were created under hdev->debugfs but not removed in vhci_release(). Since vhci_release() frees the backing vhci_data structure, any access to these files after release would result in use-after-free errors. Although hdev->debugfs is later freed in hci_release_dev(), user can access files after vhci_data is freed but before hdev->debugfs is released. CVE-2025-39861 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39861.html CVE-2025-39861 https://bugzilla.suse.com/1250249 SUSE Bug 1250249 In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work The brcmf_btcoex_detach() only shuts down the btcoex timer, if the flag timer_on is false. However, the brcmf_btcoex_timerfunc(), which runs as timer handler, sets timer_on to false. This creates critical race conditions: 1.If brcmf_btcoex_detach() is called while brcmf_btcoex_timerfunc() is executing, it may observe timer_on as false and skip the call to timer_shutdown_sync(). 2.The brcmf_btcoex_timerfunc() may then reschedule the brcmf_btcoex_info worker after the cancel_work_sync() has been executed, resulting in use-after-free bugs. The use-after-free bugs occur in two distinct scenarios, depending on the timing of when the brcmf_btcoex_info struct is freed relative to the execution of its worker thread. Scenario 1: Freed before the worker is scheduled The brcmf_btcoex_info is deallocated before the worker is scheduled. A race condition can occur when schedule_work(&bt_local->work) is called after the target memory has been freed. The sequence of events is detailed below: CPU0 | CPU1 brcmf_btcoex_detach | brcmf_btcoex_timerfunc | bt_local->timer_on = false; if (cfg->btcoex->timer_on) | ... | cancel_work_sync(); | ... | kfree(cfg->btcoex); // FREE | | schedule_work(&bt_local->work); // USE Scenario 2: Freed after the worker is scheduled The brcmf_btcoex_info is freed after the worker has been scheduled but before or during its execution. In this case, statements within the brcmf_btcoex_handler() - such as the container_of macro and subsequent dereferences of the brcmf_btcoex_info object will cause a use-after-free access. The following timeline illustrates this scenario: CPU0 | CPU1 brcmf_btcoex_detach | brcmf_btcoex_timerfunc | bt_local->timer_on = false; if (cfg->btcoex->timer_on) | ... | cancel_work_sync(); | ... | schedule_work(); // Reschedule | kfree(cfg->btcoex); // FREE | brcmf_btcoex_handler() // Worker /* | btci = container_of(....); // USE The kfree() above could | ... also occur at any point | btci-> // USE during the worker's execution| */ | To resolve the race conditions, drop the conditional check and call timer_shutdown_sync() directly. It can deactivate the timer reliably, regardless of its current state. Once stopped, the timer_on state is then set to false. CVE-2025-39863 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39863.html CVE-2025-39863 https://bugzilla.suse.com/1250281 SUSE Bug 1250281 In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: fix use-after-free in cmp_bss() Following bss_free() quirk introduced in commit 776b3580178f ("cfg80211: track hidden SSID networks properly"), adjust cfg80211_update_known_bss() to free the last beacon frame elements only if they're not shared via the corresponding 'hidden_beacon_bss' pointer. CVE-2025-39864 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39864.html CVE-2025-39864 https://bugzilla.suse.com/1250242 SUSE Bug 1250242 In the Linux kernel, the following vulnerability has been resolved: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished. CVE-2025-39866 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39866.html CVE-2025-39866 https://bugzilla.suse.com/1250455 SUSE Bug 1250455 In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map Fix a critical memory allocation bug in edma_setup_from_hw() where queue_priority_map was allocated with insufficient memory. The code declared queue_priority_map as s8 (*)[2] (pointer to array of 2 s8), but allocated memory using sizeof(s8) instead of the correct size. This caused out-of-bounds memory writes when accessing: queue_priority_map[i][0] = i; queue_priority_map[i][1] = i; The bug manifested as kernel crashes with "Oops - undefined instruction" on ARM platforms (BeagleBoard-X15) during EDMA driver probe, as the memory corruption triggered kernel hardening features on Clang. Change the allocation to use sizeof(*queue_priority_map) which automatically gets the correct size for the 2D array structure. CVE-2025-39869 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39869.html CVE-2025-39869 https://bugzilla.suse.com/1250406 SUSE Bug 1250406 In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix double free in idxd_setup_wqs() The clean up in idxd_setup_wqs() has had a couple bugs because the error handling is a bit subtle. It's simpler to just re-write it in a cleaner way. The issues here are: 1) If "idxd->max_wqs" is <= 0 then we call put_device(conf_dev) when "conf_dev" hasn't been initialized. 2) If kzalloc_node() fails then again "conf_dev" is invalid. It's either uninitialized or it points to the "conf_dev" from the previous iteration so it leads to a double free. It's better to free partial loop iterations within the loop and then the unwinding at the end can handle whole loop iterations. I also renamed the labels to describe what the goto does and not where the goto was located. CVE-2025-39870 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39870.html CVE-2025-39870 https://bugzilla.suse.com/1250402 SUSE Bug 1250402 In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Remove improper idxd_free The call to idxd_free() introduces a duplicate put_device() leading to a reference count underflow: refcount_t: underflow; use-after-free. WARNING: CPU: 15 PID: 4428 at lib/refcount.c:28 refcount_warn_saturate+0xbe/0x110 ... Call Trace: <TASK> idxd_remove+0xe4/0x120 [idxd] pci_device_remove+0x3f/0xb0 device_release_driver_internal+0x197/0x200 driver_detach+0x48/0x90 bus_remove_driver+0x74/0xf0 pci_unregister_driver+0x2e/0xb0 idxd_exit_module+0x34/0x7a0 [idxd] __do_sys_delete_module.constprop.0+0x183/0x280 do_syscall_64+0x54/0xd70 entry_SYSCALL_64_after_hwframe+0x76/0x7e The idxd_unregister_devices() which is invoked at the very beginning of idxd_remove(), already takes care of the necessary put_device() through the following call path: idxd_unregister_devices() -> device_unregister() -> put_device() In addition, when CONFIG_DEBUG_KOBJECT_RELEASE is enabled, put_device() may trigger asynchronous cleanup via schedule_delayed_work(). If idxd_free() is called immediately after, it can result in a use-after-free. Remove the improper idxd_free() to avoid both the refcount underflow and potential memory corruption during module unload. CVE-2025-39871 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39871.html CVE-2025-39871 https://bugzilla.suse.com/1250377 SUSE Bug 1250377 In the Linux kernel, the following vulnerability has been resolved: can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB can_put_echo_skb() takes ownership of the SKB and it may be freed during or after the call. However, xilinx_can xcan_write_frame() keeps using SKB after the call. Fix that by only calling can_put_echo_skb() after the code is done touching the SKB. The tx_lock is held for the entire xcan_write_frame() execution and also on the can_get_echo_skb() side so the order of operations does not matter. An earlier fix commit 3d3c817c3a40 ("can: xilinx_can: Fix usage of skb memory") did not move the can_put_echo_skb() call far enough. [mkl: add "commit" in front of sha1 in patch description] [mkl: fix indention] CVE-2025-39873 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39873.html CVE-2025-39873 https://bugzilla.suse.com/1250371 SUSE Bug 1250371 In the Linux kernel, the following vulnerability has been resolved: net: fec: Fix possible NPD in fec_enet_phy_reset_after_clk_enable() The function of_phy_find_device may return NULL, so we need to take care before dereferencing phy_dev. CVE-2025-39876 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39876.html CVE-2025-39876 https://bugzilla.suse.com/1250400 SUSE Bug 1250400 In the Linux kernel, the following vulnerability has been resolved: kernfs: Fix UAF in polling when open file is released A use-after-free (UAF) vulnerability was identified in the PSI (Pressure Stall Information) monitoring mechanism: BUG: KASAN: slab-use-after-free in psi_trigger_poll+0x3c/0x140 Read of size 8 at addr ffff3de3d50bd308 by task systemd/1 psi_trigger_poll+0x3c/0x140 cgroup_pressure_poll+0x70/0xa0 cgroup_file_poll+0x8c/0x100 kernfs_fop_poll+0x11c/0x1c0 ep_item_poll.isra.0+0x188/0x2c0 Allocated by task 1: cgroup_file_open+0x88/0x388 kernfs_fop_open+0x73c/0xaf0 do_dentry_open+0x5fc/0x1200 vfs_open+0xa0/0x3f0 do_open+0x7e8/0xd08 path_openat+0x2fc/0x6b0 do_filp_open+0x174/0x368 Freed by task 8462: cgroup_file_release+0x130/0x1f8 kernfs_drain_open_files+0x17c/0x440 kernfs_drain+0x2dc/0x360 kernfs_show+0x1b8/0x288 cgroup_file_show+0x150/0x268 cgroup_pressure_write+0x1dc/0x340 cgroup_file_write+0x274/0x548 Reproduction Steps: 1. Open test/cpu.pressure and establish epoll monitoring 2. Disable monitoring: echo 0 > test/cgroup.pressure 3. Re-enable monitoring: echo 1 > test/cgroup.pressure The race condition occurs because: 1. When cgroup.pressure is disabled (echo 0 > cgroup.pressure), it: - Releases PSI triggers via cgroup_file_release() - Frees of->priv through kernfs_drain_open_files() 2. While epoll still holds reference to the file and continues polling 3. Re-enabling (echo 1 > cgroup.pressure) accesses freed of->priv epolling disable/enable cgroup.pressure fd=open(cpu.pressure) while(1) ... epoll_wait kernfs_fop_poll kernfs_get_active = true echo 0 > cgroup.pressure ... cgroup_file_show kernfs_show // inactive kn kernfs_drain_open_files cft->release(of); kfree(ctx); ... kernfs_get_active = false echo 1 > cgroup.pressure kernfs_show kernfs_activate_one(kn); kernfs_fop_poll kernfs_get_active = true cgroup_file_poll psi_trigger_poll // UAF ... end: close(fd) To address this issue, introduce kernfs_get_active_of() for kernfs open files to obtain active references. This function will fail if the open file has been released. Replace kernfs_get_active() with kernfs_get_active_of() to prevent further operations on released file descriptors. CVE-2025-39881 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39881.html CVE-2025-39881 https://bugzilla.suse.com/1250379 SUSE Bug 1250379 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: fix potential OF node use-after-free The for_each_child_of_node() helper drops the reference it takes to each node as it iterates over children and an explicit of_node_put() is only needed when exiting the loop early. Drop the recently introduced bogus additional reference count decrement at each iteration that could potentially lead to a use-after-free. CVE-2025-39882 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39882.html CVE-2025-39882 https://bugzilla.suse.com/1250389 SUSE Bug 1250389 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: l2cap: Check encryption key size on incoming connection This is required for passing GAP/SEC/SEM/BI-04-C PTS test case: Security Mode 4 Level 4, Responder - Invalid Encryption Key Size - 128 bit This tests the security key with size from 1 to 15 bytes while the Security Mode 4 Level 4 requests 16 bytes key size. Currently PTS fails with the following logs: - expected:Connection Response: Code: [3 (0x03)] Code Identifier: (lt)WildCard: Exists(gt) Length: [8 (0x0008)] Destination CID: (lt)WildCard: Exists(gt) Source CID: [64 (0x0040)] Result: [3 (0x0003)] Connection refused - Security block Status: (lt)WildCard: Exists(gt), but received:Connection Response: Code: [3 (0x03)] Code Identifier: [1 (0x01)] Length: [8 (0x0008)] Destination CID: [64 (0x0040)] Source CID: [64 (0x0040)] Result: [0 (0x0000)] Connection Successful Status: [0 (0x0000)] No further information available And HCI logs: < HCI Command: Read Encrypti.. (0x05|0x0008) plen 2 Handle: 14 Address: 00:1B:DC:F2:24:10 (Vencer Co., Ltd.) > HCI Event: Command Complete (0x0e) plen 7 Read Encryption Key Size (0x05|0x0008) ncmd 1 Status: Success (0x00) Handle: 14 Address: 00:1B:DC:F2:24:10 (Vencer Co., Ltd.) Key size: 7 > ACL Data RX: Handle 14 flags 0x02 dlen 12 L2CAP: Connection Request (0x02) ident 1 len 4 PSM: 4097 (0x1001) Source CID: 64 < ACL Data TX: Handle 14 flags 0x00 dlen 16 L2CAP: Connection Response (0x03) ident 1 len 8 Destination CID: 64 Source CID: 64 Result: Connection successful (0x0000) Status: No further information available (0x0000) CVE-2025-39889 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39889.html CVE-2025-39889 https://bugzilla.suse.com/1249833 SUSE Bug 1249833 In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Initialize the chan_stats array to zero The adapter->chan_stats[] array is initialized in mwifiex_init_channel_scan_gap() with vmalloc(), which doesn't zero out memory. The array is filled in mwifiex_update_chan_statistics() and then the user can query the data in mwifiex_cfg80211_dump_survey(). There are two potential issues here. What if the user calls mwifiex_cfg80211_dump_survey() before the data has been filled in. Also the mwifiex_update_chan_statistics() function doesn't necessarily initialize the whole array. Since the array was not initialized at the start that could result in an information leak. Also this array is pretty small. It's a maximum of 900 bytes so it's more appropriate to use kcalloc() instead vmalloc(). CVE-2025-39891 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39891.html CVE-2025-39891 https://bugzilla.suse.com/1250712 SUSE Bug 1250712 In the Linux kernel, the following vulnerability has been resolved: sched: Fix sched_numa_find_nth_cpu() if mask offline sched_numa_find_nth_cpu() uses a bsearch to look for the 'closest' CPU in sched_domains_numa_masks and given cpus mask. However they might not intersect if all CPUs in the cpus mask are offline. bsearch will return NULL in that case, bail out instead of dereferencing a bogus pointer. The previous behaviour lead to this bug when using maxcpus=4 on an rk3399 (LLLLbb) (i.e. booting with all big CPUs offline): [ 1.422922] Unable to handle kernel paging request at virtual address ffffff8000000000 [ 1.423635] Mem abort info: [ 1.423889] ESR = 0x0000000096000006 [ 1.424227] EC = 0x25: DABT (current EL), IL = 32 bits [ 1.424715] SET = 0, FnV = 0 [ 1.424995] EA = 0, S1PTW = 0 [ 1.425279] FSC = 0x06: level 2 translation fault [ 1.425735] Data abort info: [ 1.425998] ISV = 0, ISS = 0x00000006, ISS2 = 0x00000000 [ 1.426499] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 1.426952] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 1.427428] swapper pgtable: 4k pages, 39-bit VAs, pgdp=0000000004a9f000 [ 1.428038] [ffffff8000000000] pgd=18000000f7fff403, p4d=18000000f7fff403, pud=18000000f7fff403, pmd=0000000000000000 [ 1.429014] Internal error: Oops: 0000000096000006 [#1] SMP [ 1.429525] Modules linked in: [ 1.429813] CPU: 3 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.17.0-rc4-dirty #343 PREEMPT [ 1.430559] Hardware name: Pine64 RockPro64 v2.1 (DT) [ 1.431012] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1.431634] pc : sched_numa_find_nth_cpu+0x2a0/0x488 [ 1.432094] lr : sched_numa_find_nth_cpu+0x284/0x488 [ 1.432543] sp : ffffffc084e1b960 [ 1.432843] x29: ffffffc084e1b960 x28: ffffff80078a8800 x27: ffffffc0846eb1d0 [ 1.433495] x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000 [ 1.434144] x23: 0000000000000000 x22: fffffffffff7f093 x21: ffffffc081de6378 [ 1.434792] x20: 0000000000000000 x19: 0000000ffff7f093 x18: 00000000ffffffff [ 1.435441] x17: 3030303866666666 x16: 66663d736b73616d x15: ffffffc104e1b5b7 [ 1.436091] x14: 0000000000000000 x13: ffffffc084712860 x12: 0000000000000372 [ 1.436739] x11: 0000000000000126 x10: ffffffc08476a860 x9 : ffffffc084712860 [ 1.437389] x8 : 00000000ffffefff x7 : ffffffc08476a860 x6 : 0000000000000000 [ 1.438036] x5 : 000000000000bff4 x4 : 0000000000000000 x3 : 0000000000000000 [ 1.438683] x2 : 0000000000000000 x1 : ffffffc0846eb000 x0 : ffffff8000407b68 [ 1.439332] Call trace: [ 1.439559] sched_numa_find_nth_cpu+0x2a0/0x488 (P) [ 1.440016] smp_call_function_any+0xc8/0xd0 [ 1.440416] armv8_pmu_init+0x58/0x27c [ 1.440770] armv8_cortex_a72_pmu_init+0x20/0x2c [ 1.441199] arm_pmu_device_probe+0x1e4/0x5e8 [ 1.441603] armv8_pmu_device_probe+0x1c/0x28 [ 1.442007] platform_probe+0x5c/0xac [ 1.442347] really_probe+0xbc/0x298 [ 1.442683] __driver_probe_device+0x78/0x12c [ 1.443087] driver_probe_device+0xdc/0x160 [ 1.443475] __driver_attach+0x94/0x19c [ 1.443833] bus_for_each_dev+0x74/0xd4 [ 1.444190] driver_attach+0x24/0x30 [ 1.444525] bus_add_driver+0xe4/0x208 [ 1.444874] driver_register+0x60/0x128 [ 1.445233] __platform_driver_register+0x24/0x30 [ 1.445662] armv8_pmu_driver_init+0x28/0x4c [ 1.446059] do_one_initcall+0x44/0x25c [ 1.446416] kernel_init_freeable+0x1dc/0x3bc [ 1.446820] kernel_init+0x20/0x1d8 [ 1.447151] ret_from_fork+0x10/0x20 [ 1.447493] Code: 90022e21 f000e5f5 910de2b5 2a1703e2 (f8767803) [ 1.448040] ---[ end trace 0000000000000000 ]--- [ 1.448483] note: swapper/0[1] exited with preempt_count 1 [ 1.449047] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 1.449741] SMP: stopping secondary CPUs [ 1.450105] Kernel Offset: disabled [ 1.450419] CPU features: 0x000000,00080000,20002001,0400421b [ ---truncated--- CVE-2025-39895 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39895.html CVE-2025-39895 https://bugzilla.suse.com/1250721 SUSE Bug 1250721 In the Linux kernel, the following vulnerability has been resolved: net_sched: gen_estimator: fix est_timer() vs CONFIG_PREEMPT_RT=y syzbot reported a WARNING in est_timer() [1] Problem here is that with CONFIG_PREEMPT_RT=y, timer callbacks can be preempted. Adopt preempt_disable_nested()/preempt_enable_nested() to fix this. [1] WARNING: CPU: 0 PID: 16 at ./include/linux/seqlock.h:221 __seqprop_assert include/linux/seqlock.h:221 [inline] WARNING: CPU: 0 PID: 16 at ./include/linux/seqlock.h:221 est_timer+0x6dc/0x9f0 net/core/gen_estimator.c:93 Modules linked in: CPU: 0 UID: 0 PID: 16 Comm: ktimers/0 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:__seqprop_assert include/linux/seqlock.h:221 [inline] RIP: 0010:est_timer+0x6dc/0x9f0 net/core/gen_estimator.c:93 Call Trace: <TASK> call_timer_fn+0x17e/0x5f0 kernel/time/timer.c:1747 expire_timers kernel/time/timer.c:1798 [inline] __run_timers kernel/time/timer.c:2372 [inline] __run_timer_base+0x648/0x970 kernel/time/timer.c:2384 run_timer_base kernel/time/timer.c:2393 [inline] run_timer_softirq+0xb7/0x180 kernel/time/timer.c:2403 handle_softirqs+0x22c/0x710 kernel/softirq.c:579 __do_softirq kernel/softirq.c:613 [inline] run_ktimerd+0xcf/0x190 kernel/softirq.c:1043 smpboot_thread_fn+0x53f/0xa60 kernel/smpboot.c:160 kthread+0x70e/0x8a0 kernel/kthread.c:463 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK> CVE-2025-39900 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39900.html CVE-2025-39900 https://bugzilla.suse.com/1250758 SUSE Bug 1250758 In the Linux kernel, the following vulnerability has been resolved: mm/slub: avoid accessing metadata when pointer is invalid in object_err() object_err() reports details of an object for further debugging, such as the freelist pointer, redzone, etc. However, if the pointer is invalid, attempting to access object metadata can lead to a crash since it does not point to a valid object. One known path to the crash is when alloc_consistency_checks() determines the pointer to the allocated object is invalid because of a freelist corruption, and calls object_err() to report it. The debug code should report and handle the corruption gracefully and not crash in the process. In case the pointer is NULL or check_valid_pointer() returns false for the pointer, only print the pointer value and skip accessing metadata. CVE-2025-39902 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39902.html CVE-2025-39902 https://bugzilla.suse.com/1250702 SUSE Bug 1250702 In the Linux kernel, the following vulnerability has been resolved: mtd: rawnand: stm32_fmc2: avoid overlapping mappings on ECC buffer Avoid below overlapping mappings by using a contiguous non-cacheable buffer. [ 4.077708] DMA-API: stm32_fmc2_nfc 48810000.nand-controller: cacheline tracking EEXIST, overlapping mappings aren't supported [ 4.089103] WARNING: CPU: 1 PID: 44 at kernel/dma/debug.c:568 add_dma_entry+0x23c/0x300 [ 4.097071] Modules linked in: [ 4.100101] CPU: 1 PID: 44 Comm: kworker/u4:2 Not tainted 6.1.82 #1 [ 4.106346] Hardware name: STMicroelectronics STM32MP257F VALID1 SNOR / MB1704 (LPDDR4 Power discrete) + MB1703 + MB1708 (SNOR MB1730) (DT) [ 4.118824] Workqueue: events_unbound deferred_probe_work_func [ 4.124674] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 4.131624] pc : add_dma_entry+0x23c/0x300 [ 4.135658] lr : add_dma_entry+0x23c/0x300 [ 4.139792] sp : ffff800009dbb490 [ 4.143016] x29: ffff800009dbb4a0 x28: 0000000004008022 x27: ffff8000098a6000 [ 4.150174] x26: 0000000000000000 x25: ffff8000099e7000 x24: ffff8000099e7de8 [ 4.157231] x23: 00000000ffffffff x22: 0000000000000000 x21: ffff8000098a6a20 [ 4.164388] x20: ffff000080964180 x19: ffff800009819ba0 x18: 0000000000000006 [ 4.171545] x17: 6361727420656e69 x16: 6c6568636163203a x15: 72656c6c6f72746e [ 4.178602] x14: 6f632d646e616e2e x13: ffff800009832f58 x12: 00000000000004ec [ 4.185759] x11: 00000000000001a4 x10: ffff80000988af58 x9 : ffff800009832f58 [ 4.192916] x8 : 00000000ffffefff x7 : ffff80000988af58 x6 : 80000000fffff000 [ 4.199972] x5 : 000000000000bff4 x4 : 0000000000000000 x3 : 0000000000000000 [ 4.207128] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000812d2c40 [ 4.214185] Call trace: [ 4.216605] add_dma_entry+0x23c/0x300 [ 4.220338] debug_dma_map_sg+0x198/0x350 [ 4.224373] __dma_map_sg_attrs+0xa0/0x110 [ 4.228411] dma_map_sg_attrs+0x10/0x2c [ 4.232247] stm32_fmc2_nfc_xfer.isra.0+0x1c8/0x3fc [ 4.237088] stm32_fmc2_nfc_seq_read_page+0xc8/0x174 [ 4.242127] nand_read_oob+0x1d4/0x8e0 [ 4.245861] mtd_read_oob_std+0x58/0x84 [ 4.249596] mtd_read_oob+0x90/0x150 [ 4.253231] mtd_read+0x68/0xac CVE-2025-39907 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39907.html CVE-2025-39907 https://bugzilla.suse.com/1250713 SUSE Bug 1250713 In the Linux kernel, the following vulnerability has been resolved: i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path If request_irq() in i40e_vsi_request_irq_msix() fails in an iteration later than the first, the error path wants to free the IRQs requested so far. However, it uses the wrong dev_id argument for free_irq(), so it does not free the IRQs correctly and instead triggers the warning: Trying to free already-free IRQ 173 WARNING: CPU: 25 PID: 1091 at kernel/irq/manage.c:1829 __free_irq+0x192/0x2c0 Modules linked in: i40e(+) [...] CPU: 25 UID: 0 PID: 1091 Comm: NetworkManager Not tainted 6.17.0-rc1+ #1 PREEMPT(lazy) Hardware name: [...] RIP: 0010:__free_irq+0x192/0x2c0 [...] Call Trace: <TASK> free_irq+0x32/0x70 i40e_vsi_request_irq_msix.cold+0x63/0x8b [i40e] i40e_vsi_request_irq+0x79/0x80 [i40e] i40e_vsi_open+0x21f/0x2f0 [i40e] i40e_open+0x63/0x130 [i40e] __dev_open+0xfc/0x210 __dev_change_flags+0x1fc/0x240 netif_change_flags+0x27/0x70 do_setlink.isra.0+0x341/0xc70 rtnl_newlink+0x468/0x860 rtnetlink_rcv_msg+0x375/0x450 netlink_rcv_skb+0x5c/0x110 netlink_unicast+0x288/0x3c0 netlink_sendmsg+0x20d/0x430 ____sys_sendmsg+0x3a2/0x3d0 ___sys_sendmsg+0x99/0xe0 __sys_sendmsg+0x8a/0xf0 do_syscall_64+0x82/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e [...] </TASK> ---[ end trace 0000000000000000 ]--- Use the same dev_id for free_irq() as for request_irq(). I tested this with inserting code to fail intentionally. CVE-2025-39911 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39911.html CVE-2025-39911 https://bugzilla.suse.com/1250704 SUSE Bug 1250704 In the Linux kernel, the following vulnerability has been resolved: pcmcia: Add error handling for add_interval() in do_validate_mem() In the do_validate_mem(), the call to add_interval() does not handle errors. If kmalloc() fails in add_interval(), it could result in a null pointer being inserted into the linked list, leading to illegal memory access when sub_interval() is called next. This patch adds an error handling for the add_interval(). If add_interval() returns an error, the function will return early with the error code. CVE-2025-39920 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39920.html CVE-2025-39920 https://bugzilla.suse.com/1250732 SUSE Bug 1250732 In the Linux kernel, the following vulnerability has been resolved: dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees When we don't have a clock specified in the device tree, we have no way to ensure the BAM is on. This is often the case for remotely-controlled or remotely-powered BAM instances. In this case, we need to read num-channels from the DT to have all the necessary information to complete probing. However, at the moment invalid device trees without clock and without num-channels still continue probing, because the error handling is missing return statements. The driver will then later try to read the number of channels from the registers. This is unsafe, because it relies on boot firmware and lucky timing to succeed. Unfortunately, the lack of proper error handling here has been abused for several Qualcomm SoCs upstream, causing early boot crashes in several situations [1, 2]. Avoid these early crashes by erroring out when any of the required DT properties are missing. Note that this will break some of the existing DTs upstream (mainly BAM instances related to the crypto engine). However, clearly these DTs have never been tested properly, since the error in the kernel log was just ignored. It's safer to disable the crypto engine for these broken DTBs. [1]: https://lore.kernel.org/r/CY01EKQVWE36.B9X5TDXAREPF@fairphone.com/ [2]: https://lore.kernel.org/r/20230626145959.646747-1-krzysztof.kozlowski@linaro.org/ CVE-2025-39923 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39923.html CVE-2025-39923 https://bugzilla.suse.com/1250741 SUSE Bug 1250741 In the Linux kernel, the following vulnerability has been resolved: can: j1939: implement NETDEV_UNREGISTER notification handler syzbot is reporting unregister_netdevice: waiting for vcan0 to become free. Usage count = 2 problem, for j1939 protocol did not have NETDEV_UNREGISTER notification handler for undoing changes made by j1939_sk_bind(). Commit 25fe97cb7620 ("can: j1939: move j1939_priv_put() into sk_destruct callback") expects that a call to j1939_priv_put() can be unconditionally delayed until j1939_sk_sock_destruct() is called. But we need to call j1939_priv_put() against an extra ref held by j1939_sk_bind() call (as a part of undoing changes made by j1939_sk_bind()) as soon as NETDEV_UNREGISTER notification fires (i.e. before j1939_sk_sock_destruct() is called via j1939_sk_release()). Otherwise, the extra ref on "struct j1939_priv" held by j1939_sk_bind() call prevents "struct net_device" from dropping the usage count to 1; making it impossible for unregister_netdevice() to continue. [mkl: remove space in front of label] CVE-2025-39925 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39925.html CVE-2025-39925 https://bugzilla.suse.com/1250736 SUSE Bug 1250736 In the Linux kernel, the following vulnerability has been resolved: crypto: af_alg - Set merge to zero early in af_alg_sendmsg If an error causes af_alg_sendmsg to abort, ctx->merge may contain a garbage value from the previous loop. This may then trigger a crash on the next entry into af_alg_sendmsg when it attempts to do a merge that can't be done. Fix this by setting ctx->merge to zero near the start of the loop. CVE-2025-39931 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39931.html CVE-2025-39931 https://bugzilla.suse.com/1251100 SUSE Bug 1251100 In the Linux kernel, the following vulnerability has been resolved: drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ If the interrupt occurs before resource initialization is complete, the interrupt handler/worker may access uninitialized data such as the I2C tcpc_client device, potentially leading to NULL pointer dereference. CVE-2025-39934 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39934.html CVE-2025-39934 https://bugzilla.suse.com/1251146 SUSE Bug 1251146 In the Linux kernel, the following vulnerability has been resolved: net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer Since commit 7d5e9737efda ("net: rfkill: gpio: get the name and type from device property") rfkill_find_type() gets called with the possibly uninitialized "const char *type_name;" local variable. On x86 systems when rfkill-gpio binds to a "BCM4752" or "LNV4752" acpi_device, the rfkill->type is set based on the ACPI acpi_device_id: rfkill->type = (unsigned)id->driver_data; and there is no "type" property so device_property_read_string() will fail and leave type_name uninitialized, leading to a potential crash. rfkill_find_type() does accept a NULL pointer, fix the potential crash by initializing type_name to NULL. Note likely sofar this has not been caught because: 1. Not many x86 machines actually have a "BCM4752"/"LNV4752" acpi_device 2. The stack happened to contain NULL where type_name is stored CVE-2025-39937 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39937.html CVE-2025-39937 https://bugzilla.suse.com/1251143 SUSE Bug 1251143 In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed If earlier opening of source graph fails (e.g. ADSP rejects due to incorrect audioreach topology), the graph is closed and "dai_data->graph[dai->id]" is assigned NULL. Preparing the DAI for sink graph continues though and next call to q6apm_lpass_dai_prepare() receives dai_data->graph[dai->id]=NULL leading to NULL pointer exception: qcom-apm gprsvc:service:2:1: Error (1) Processing 0x01001002 cmd qcom-apm gprsvc:service:2:1: DSP returned error[1001002] 1 q6apm-lpass-dais 30000000.remoteproc:glink-edge:gpr:service@1:bedais: fail to start APM port 78 q6apm-lpass-dais 30000000.remoteproc:glink-edge:gpr:service@1:bedais: ASoC: error at snd_soc_pcm_dai_prepare on TX_CODEC_DMA_TX_3: -22 Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a8 ... Call trace: q6apm_graph_media_format_pcm+0x48/0x120 (P) q6apm_lpass_dai_prepare+0x110/0x1b4 snd_soc_pcm_dai_prepare+0x74/0x108 __soc_pcm_prepare+0x44/0x160 dpcm_be_dai_prepare+0x124/0x1c0 CVE-2025-39938 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39938.html CVE-2025-39938 https://bugzilla.suse.com/1251134 SUSE Bug 1251134 In the Linux kernel, the following vulnerability has been resolved: cnic: Fix use-after-free bugs in cnic_delete_task The original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(), which does not guarantee that the delayed work item 'delete_task' has fully completed if it was already running. Additionally, the delayed work item is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after the cyclic work items have finished executing, a delayed work item may still exist in the workqueue. This leads to use-after-free scenarios where the cnic_dev is deallocated by cnic_free_dev(), while delete_task remains active and attempt to dereference cnic_dev in cnic_delete_task(). A typical race condition is illustrated below: CPU 0 (cleanup) | CPU 1 (delayed work callback) cnic_netdev_event() | cnic_stop_hw() | cnic_delete_task() cnic_cm_stop_bnx2x_hw() | ... cancel_delayed_work() | /* the queue_delayed_work() flush_workqueue() | executes after flush_workqueue()*/ | queue_delayed_work() cnic_free_dev(dev)//free | cnic_delete_task() //new instance | dev = cp->dev; //use Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the cyclic delayed work item is properly canceled and that any ongoing execution of the work item completes before the cnic_dev is deallocated. Furthermore, since cancel_delayed_work_sync() uses __flush_work(work, true) to synchronously wait for any currently executing instance of the work item to finish, the flush_workqueue() becomes redundant and should be removed. This bug was identified through static analysis. To reproduce the issue and validate the fix, I simulated the cnic PCI device in QEMU and introduced intentional delays - such as inserting calls to ssleep() within the cnic_delete_task() function - to increase the likelihood of triggering the bug. CVE-2025-39945 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39945.html CVE-2025-39945 https://bugzilla.suse.com/1251230 SUSE Bug 1251230 In the Linux kernel, the following vulnerability has been resolved: tls: make sure to abort the stream if headers are bogus Normally we wait for the socket to buffer up the whole record before we service it. If the socket has a tiny buffer, however, we read out the data sooner, to prevent connection stalls. Make sure that we abort the connection when we find out late that the record is actually invalid. Retrying the parsing is fine in itself but since we copy some more data each time before we parse we can overflow the allocated skb space. Constructing a scenario in which we're under pressure without enough data in the socket to parse the length upfront is quite hard. syzbot figured out a way to do this by serving us the header in small OOB sends, and then filling in the recvbuf with a large normal send. Make sure that tls_rx_msg_size() aborts strp, if we reach an invalid record there's really no way to recover. CVE-2025-39946 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39946.html CVE-2025-39946 https://bugzilla.suse.com/1251114 SUSE Bug 1251114 In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Harden uplink netdev access against device unbind The function mlx5_uplink_netdev_get() gets the uplink netdevice pointer from mdev->mlx5e_res.uplink_netdev. However, the netdevice can be removed and its pointer cleared when unbound from the mlx5_core.eth driver. This results in a NULL pointer, causing a kernel panic. BUG: unable to handle page fault for address: 0000000000001300 at RIP: 0010:mlx5e_vport_rep_load+0x22a/0x270 [mlx5_core] Call Trace: <TASK> mlx5_esw_offloads_rep_load+0x68/0xe0 [mlx5_core] esw_offloads_enable+0x593/0x910 [mlx5_core] mlx5_eswitch_enable_locked+0x341/0x420 [mlx5_core] mlx5_devlink_eswitch_mode_set+0x17e/0x3a0 [mlx5_core] devlink_nl_eswitch_set_doit+0x60/0xd0 genl_family_rcv_msg_doit+0xe0/0x130 genl_rcv_msg+0x183/0x290 netlink_rcv_skb+0x4b/0xf0 genl_rcv+0x24/0x40 netlink_unicast+0x255/0x380 netlink_sendmsg+0x1f3/0x420 __sock_sendmsg+0x38/0x60 __sys_sendto+0x119/0x180 do_syscall_64+0x53/0x1d0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 Ensure the pointer is valid before use by checking it for NULL. If it is valid, immediately call netdev_hold() to take a reference, and preventing the netdevice from being freed while it is in use. CVE-2025-39947 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39947.html CVE-2025-39947 https://bugzilla.suse.com/1251232 SUSE Bug 1251232 In the Linux kernel, the following vulnerability has been resolved: ice: fix Rx page leak on multi-buffer frames The ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each buffer in the current frame. This function was introduced as part of handling multi-buffer XDP support in the ice driver. It works by iterating over the buffers from first_desc up to 1 plus the total number of fragments in the frame, cached from before the XDP program was executed. If the hardware posts a descriptor with a size of 0, the logic used in ice_put_rx_mbuf() breaks. Such descriptors get skipped and don't get added as fragments in ice_add_xdp_frag. Since the buffer isn't counted as a fragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don't call ice_put_rx_buf(). Because we don't call ice_put_rx_buf(), we don't attempt to re-use the page or free it. This leaves a stale page in the ring, as we don't increment next_to_alloc. The ice_reuse_rx_page() assumes that the next_to_alloc has been incremented properly, and that it always points to a buffer with a NULL page. Since this function doesn't check, it will happily recycle a page over the top of the next_to_alloc buffer, losing track of the old page. Note that this leak only occurs for multi-buffer frames. The ice_put_rx_mbuf() function always handles at least one buffer, so a single-buffer frame will always get handled correctly. It is not clear precisely why the hardware hands us descriptors with a size of 0 sometimes, but it happens somewhat regularly with "jumbo frames" used by 9K MTU. To fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on all buffers between first_desc and next_to_clean. Borrow the logic of a similar function in i40e used for this same purpose. Use the same logic also in ice_get_pgcnts(). Instead of iterating over just the number of fragments, use a loop which iterates until the current index reaches to the next_to_clean element just past the current frame. Unlike i40e, the ice_put_rx_mbuf() function does call ice_put_rx_buf() on the last buffer of the frame indicating the end of packet. For non-linear (multi-buffer) frames, we need to take care when adjusting the pagecnt_bias. An XDP program might release fragments from the tail of the frame, in which case that fragment page is already released. Only update the pagecnt_bias for the first descriptor and fragments still remaining post-XDP program. Take care to only access the shared info for fragmented buffers, as this avoids a significant cache miss. The xdp_xmit value only needs to be updated if an XDP program is run, and only once per packet. Drop the xdp_xmit pointer argument from ice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function directly. This avoids needing to pass the argument and avoids an extra bit-wise OR for each buffer in the frame. Move the increment of the ntc local variable to ensure its updated *before* all calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic requires the index of the element just after the current frame. Now that we use an index pointer in the ring to identify the packet, we no longer need to track or cache the number of fragments in the rx_ring. CVE-2025-39948 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39948.html CVE-2025-39948 https://bugzilla.suse.com/1251233 SUSE Bug 1251233 In the Linux kernel, the following vulnerability has been resolved: qed: Don't collect too many protection override GRC elements In the protection override dump path, the firmware can return far too many GRC elements, resulting in attempting to write past the end of the previously-kmalloc'ed dump buffer. This will result in a kernel panic with reason: BUG: unable to handle kernel paging request at ADDRESS where "ADDRESS" is just past the end of the protection override dump buffer. The start address of the buffer is: p_hwfn->cdev->dbg_features[DBG_FEATURE_PROTECTION_OVERRIDE].dump_buf and the size of the buffer is buf_size in the same data structure. The panic can be arrived at from either the qede Ethernet driver path: [exception RIP: qed_grc_dump_addr_range+0x108] qed_protection_override_dump at ffffffffc02662ed [qed] qed_dbg_protection_override_dump at ffffffffc0267792 [qed] qed_dbg_feature at ffffffffc026aa8f [qed] qed_dbg_all_data at ffffffffc026b211 [qed] qed_fw_fatal_reporter_dump at ffffffffc027298a [qed] devlink_health_do_dump at ffffffff82497f61 devlink_health_report at ffffffff8249cf29 qed_report_fatal_error at ffffffffc0272baf [qed] qede_sp_task at ffffffffc045ed32 [qede] process_one_work at ffffffff81d19783 or the qedf storage driver path: [exception RIP: qed_grc_dump_addr_range+0x108] qed_protection_override_dump at ffffffffc068b2ed [qed] qed_dbg_protection_override_dump at ffffffffc068c792 [qed] qed_dbg_feature at ffffffffc068fa8f [qed] qed_dbg_all_data at ffffffffc0690211 [qed] qed_fw_fatal_reporter_dump at ffffffffc069798a [qed] devlink_health_do_dump at ffffffff8aa95e51 devlink_health_report at ffffffff8aa9ae19 qed_report_fatal_error at ffffffffc0697baf [qed] qed_hw_err_notify at ffffffffc06d32d7 [qed] qed_spq_post at ffffffffc06b1011 [qed] qed_fcoe_destroy_conn at ffffffffc06b2e91 [qed] qedf_cleanup_fcport at ffffffffc05e7597 [qedf] qedf_rport_event_handler at ffffffffc05e7bf7 [qedf] fc_rport_work at ffffffffc02da715 [libfc] process_one_work at ffffffff8a319663 Resolve this by clamping the firmware's return value to the maximum number of legal elements the firmware should return. CVE-2025-39949 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39949.html CVE-2025-39949 https://bugzilla.suse.com/1251177 SUSE Bug 1251177 In the Linux kernel, the following vulnerability has been resolved: wifi: wilc1000: avoid buffer overflow in WID string configuration Fix the following copy overflow warning identified by Smatch checker. drivers/net/wireless/microchip/wilc1000/wlan_cfg.c:184 wilc_wlan_parse_response_frame() error: '__memcpy()' 'cfg->s[i]->str' copy overflow (512 vs 65537) This patch introduces size check before accessing the memory buffer. The checks are base on the WID type of received data from the firmware. For WID string configuration, the size limit is determined by individual element size in 'struct wilc_cfg_str_vals' that is maintained in 'len' field of 'struct wilc_cfg_str'. CVE-2025-39952 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39952.html CVE-2025-39952 https://bugzilla.suse.com/1251216 SUSE Bug 1251216 In the Linux kernel, the following vulnerability has been resolved: tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). syzbot reported the splat below where a socket had tcp_sk(sk)->fastopen_rsk in the TCP_ESTABLISHED state. [0] syzbot reused the server-side TCP Fast Open socket as a new client before the TFO socket completes 3WHS: 1. accept() 2. connect(AF_UNSPEC) 3. connect() to another destination As of accept(), sk->sk_state is TCP_SYN_RECV, and tcp_disconnect() changes it to TCP_CLOSE and makes connect() possible, which restarts timers. Since tcp_disconnect() forgot to clear tcp_sk(sk)->fastopen_rsk, the retransmit timer triggered the warning and the intended packet was not retransmitted. Let's call reqsk_fastopen_remove() in tcp_disconnect(). [0]: WARNING: CPU: 2 PID: 0 at net/ipv4/tcp_timer.c:542 tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7)) Modules linked in: CPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted 6.17.0-rc5-g201825fb4278 #62 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7)) Code: 41 55 41 54 55 53 48 8b af b8 08 00 00 48 89 fb 48 85 ed 0f 84 55 01 00 00 0f b6 47 12 3c 03 74 0c 0f b6 47 12 3c 04 74 04 90 <0f> 0b 90 48 8b 85 c0 00 00 00 48 89 ef 48 8b 40 30 e8 6a 4f 06 3e RSP: 0018:ffffc900002f8d40 EFLAGS: 00010293 RAX: 0000000000000002 RBX: ffff888106911400 RCX: 0000000000000017 RDX: 0000000002517619 RSI: ffffffff83764080 RDI: ffff888106911400 RBP: ffff888106d5c000 R08: 0000000000000001 R09: ffffc900002f8de8 R10: 00000000000000c2 R11: ffffc900002f8ff8 R12: ffff888106911540 R13: ffff888106911480 R14: ffff888106911840 R15: ffffc900002f8de0 FS: 0000000000000000(0000) GS:ffff88907b768000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8044d69d90 CR3: 0000000002c30003 CR4: 0000000000370ef0 Call Trace: <IRQ> tcp_write_timer (net/ipv4/tcp_timer.c:738) call_timer_fn (kernel/time/timer.c:1747) __run_timers (kernel/time/timer.c:1799 kernel/time/timer.c:2372) timer_expire_remote (kernel/time/timer.c:2385 kernel/time/timer.c:2376 kernel/time/timer.c:2135) tmigr_handle_remote_up (kernel/time/timer_migration.c:944 kernel/time/timer_migration.c:1035) __walk_groups.isra.0 (kernel/time/timer_migration.c:533 (discriminator 1)) tmigr_handle_remote (kernel/time/timer_migration.c:1096) handle_softirqs (./arch/x86/include/asm/jump_label.h:36 ./include/trace/events/irq.h:142 kernel/softirq.c:580) irq_exit_rcu (kernel/softirq.c:614 kernel/softirq.c:453 kernel/softirq.c:680 kernel/softirq.c:696) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1050 (discriminator 35) arch/x86/kernel/apic/apic.c:1050 (discriminator 35)) </IRQ> CVE-2025-39955 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39955.html CVE-2025-39955 https://bugzilla.suse.com/1251804 SUSE Bug 1251804 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: increase scan_ies_len for S1G Currently the S1G capability element is not taken into account for the scan_ies_len, which leads to a buffer length validation failure in ieee80211_prep_hw_scan() and subsequent WARN in __ieee80211_start_scan(). This prevents hw scanning from functioning. To fix ensure we accommodate for the S1G capability length. CVE-2025-39957 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39957.html CVE-2025-39957 https://bugzilla.suse.com/1251810 SUSE Bug 1251810 In the Linux kernel, the following vulnerability has been resolved: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI x->id.spi == 0 means "no SPI assigned", but since commit 94f39804d891 ("xfrm: Duplicate SPI Handling"), we now create states and add them to the byspi list with this value. __xfrm_state_delete doesn't remove those states from the byspi list, since they shouldn't be there, and this shows up as a UAF the next time we go through the byspi list. CVE-2025-39965 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39965.html CVE-2025-39965 https://bugzilla.suse.com/1251967 SUSE Bug 1251967 In the Linux kernel, the following vulnerability has been resolved: fbcon: fix integer overflow in fbcon_do_set_font Fix integer overflow vulnerabilities in fbcon_do_set_font() where font size calculations could overflow when handling user-controlled font parameters. The vulnerabilities occur when: 1. CALC_FONTSZ(h, pitch, charcount) performs h * pith * charcount multiplication with user-controlled values that can overflow. 2. FONT_EXTRA_WORDS * sizeof(int) + size addition can also overflow 3. This results in smaller allocations than expected, leading to buffer overflows during font data copying. Add explicit overflow checking using check_mul_overflow() and check_add_overflow() kernel helpers to safety validate all size calculations before allocation. CVE-2025-39967 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39967.html CVE-2025-39967 https://bugzilla.suse.com/1252033 SUSE Bug 1252033 In the Linux kernel, the following vulnerability has been resolved: i40e: add max boundary check for VF filters There is no check for max filters that VF can request. Add it. CVE-2025-39968 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39968.html CVE-2025-39968 https://bugzilla.suse.com/1252047 SUSE Bug 1252047 In the Linux kernel, the following vulnerability has been resolved: i40e: fix validation of VF state in get resources VF state I40E_VF_STATE_ACTIVE is not the only state in which VF is actually active so it should not be used to determine if a VF is allowed to obtain resources. Use I40E_VF_STATE_RESOURCES_LOADED that is set only in i40e_vc_get_vf_resources_msg() and cleared during reset. CVE-2025-39969 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39969.html CVE-2025-39969 https://bugzilla.suse.com/1252044 SUSE Bug 1252044 In the Linux kernel, the following vulnerability has been resolved: i40e: fix input validation logic for action_meta Fix condition to check 'greater or equal' to prevent OOB dereference. CVE-2025-39970 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39970.html CVE-2025-39970 https://bugzilla.suse.com/1252051 SUSE Bug 1252051 In the Linux kernel, the following vulnerability has been resolved: i40e: fix idx validation in config queues msg Ensure idx is within range of active/initialized TCs when iterating over vf->ch[idx] in i40e_vc_config_queues_msg(). CVE-2025-39971 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39971.html CVE-2025-39971 https://bugzilla.suse.com/1252052 SUSE Bug 1252052 In the Linux kernel, the following vulnerability has been resolved: i40e: fix idx validation in i40e_validate_queue_map Ensure idx is within range of active/initialized TCs when iterating over vf->ch[idx] in i40e_validate_queue_map(). CVE-2025-39972 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39972.html CVE-2025-39972 https://bugzilla.suse.com/1252039 SUSE Bug 1252039 In the Linux kernel, the following vulnerability has been resolved: i40e: add validation for ring_len param The `ring_len` parameter provided by the virtual function (VF) is assigned directly to the hardware memory context (HMC) without any validation. To address this, introduce an upper boundary check for both Tx and Rx queue lengths. The maximum number of descriptors supported by the hardware is 8k-32. Additionally, enforce alignment constraints: Tx rings must be a multiple of 8, and Rx rings must be a multiple of 32. CVE-2025-39973 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39973.html CVE-2025-39973 https://bugzilla.suse.com/1247374 SUSE Bug 1247374 https://bugzilla.suse.com/1252035 SUSE Bug 1252035 https://bugzilla.suse.com/1252036 SUSE Bug 1252036 In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: Fix potential use after free in otx2_tc_add_flow() This code calls kfree_rcu(new_node, rcu) and then dereferences "new_node" and then dereferences it on the next line. Two lines later, we take a mutex so I don't think this is an RCU safe region. Re-order it to do the dereferences before queuing up the free. CVE-2025-39978 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39978.html CVE-2025-39978 https://bugzilla.suse.com/1252069 SUSE Bug 1252069 https://bugzilla.suse.com/1252071 SUSE Bug 1252071 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix possible UAFs This attemps to fix possible UAFs caused by struct mgmt_pending being freed while still being processed like in the following trace, in order to fix mgmt_pending_valid is introduce and use to check if the mgmt_pending hasn't been removed from the pending list, on the complete callbacks it is used to check and in addtion remove the cmd from the list while holding mgmt_pending_lock to avoid TOCTOU problems since if the cmd is left on the list it can still be accessed and freed. BUG: KASAN: slab-use-after-free in mgmt_add_adv_patterns_monitor_sync+0x35/0x50 net/bluetooth/mgmt.c:5223 Read of size 8 at addr ffff8880709d4dc0 by task kworker/u11:0/55 CPU: 0 UID: 0 PID: 55 Comm: kworker/u11:0 Not tainted 6.16.4 #2 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 Workqueue: hci0 hci_cmd_sync_work Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 mgmt_add_adv_patterns_monitor_sync+0x35/0x50 net/bluetooth/mgmt.c:5223 hci_cmd_sync_work+0x210/0x3a0 net/bluetooth/hci_sync.c:332 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x711/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/source/fuzzing/kernel/kasan/linux-6.16.4/arch/x86/entry/entry_64.S:245 </TASK> Allocated by task 12210: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __kmalloc_cache_noprof+0x230/0x3d0 mm/slub.c:4364 kmalloc_noprof include/linux/slab.h:905 [inline] kzalloc_noprof include/linux/slab.h:1039 [inline] mgmt_pending_new+0x65/0x1e0 net/bluetooth/mgmt_util.c:269 mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296 __add_adv_patterns_monitor+0x130/0x200 net/bluetooth/mgmt.c:5247 add_adv_patterns_monitor+0x214/0x360 net/bluetooth/mgmt.c:5364 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg+0x219/0x270 net/socket.c:729 sock_write_iter+0x258/0x330 net/socket.c:1133 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x5c9/0xb30 fs/read_write.c:686 ksys_write+0x145/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 12221: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:576 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x62/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2381 [inline] slab_free mm/slub.c:4648 [inline] kfree+0x18e/0x440 mm/slub.c:4847 mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline] mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257 __mgmt_power_off+0x169/0x350 net/bluetooth/mgmt.c:9444 hci_dev_close_sync+0x754/0x1330 net/bluetooth/hci_sync.c:5290 hci_dev_do_close net/bluetooth/hci_core.c:501 [inline] hci_dev_close+0x108/0x200 net/bluetooth/hci_core.c:526 sock_do_ioctl+0xd9/0x300 net/socket.c:1192 sock_ioctl+0x576/0x790 net/socket.c:1313 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf ---truncated--- CVE-2025-39981 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39981.html CVE-2025-39981 https://bugzilla.suse.com/1252060 SUSE Bug 1252060 https://bugzilla.suse.com/1252061 SUSE Bug 1252061 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync This fixes the following UFA in hci_acl_create_conn_sync where a connection still pending is command submission (conn->state == BT_OPEN) maybe freed, also since this also can happen with the likes of hci_le_create_conn_sync fix it as well: BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5ef/0x790 net/bluetooth/hci_sync.c:6861 Write of size 2 at addr ffff88805ffcc038 by task kworker/u11:2/9541 CPU: 1 UID: 0 PID: 9541 Comm: kworker/u11:2 Not tainted 6.16.0-rc7 #3 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 Workqueue: hci3 hci_cmd_sync_work Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x230 mm/kasan/report.c:480 kasan_report+0x118/0x150 mm/kasan/report.c:593 hci_acl_create_conn_sync+0x5ef/0x790 net/bluetooth/hci_sync.c:6861 hci_cmd_sync_work+0x210/0x3a0 net/bluetooth/hci_sync.c:332 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/source/fuzzing/kernel/kasan/linux-6.16-rc7/arch/x86/entry/entry_64.S:245 </TASK> Allocated by task 123736: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __kmalloc_cache_noprof+0x230/0x3d0 mm/slub.c:4359 kmalloc_noprof include/linux/slab.h:905 [inline] kzalloc_noprof include/linux/slab.h:1039 [inline] __hci_conn_add+0x233/0x1b30 net/bluetooth/hci_conn.c:939 hci_conn_add_unset net/bluetooth/hci_conn.c:1051 [inline] hci_connect_acl+0x16c/0x4e0 net/bluetooth/hci_conn.c:1634 pair_device+0x418/0xa70 net/bluetooth/mgmt.c:3556 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:712 [inline] __sock_sendmsg+0x219/0x270 net/socket.c:727 sock_write_iter+0x258/0x330 net/socket.c:1131 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x54b/0xa90 fs/read_write.c:686 ksys_write+0x145/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 103680: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:576 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x62/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2381 [inline] slab_free mm/slub.c:4643 [inline] kfree+0x18e/0x440 mm/slub.c:4842 device_release+0x9c/0x1c0 kobject_cleanup lib/kobject.c:689 [inline] kobject_release lib/kobject.c:720 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x22b/0x480 lib/kobject.c:737 hci_conn_cleanup net/bluetooth/hci_conn.c:175 [inline] hci_conn_del+0x8ff/0xcb0 net/bluetooth/hci_conn.c:1173 hci_conn_complete_evt+0x3c7/0x1040 net/bluetooth/hci_event.c:3199 hci_event_func net/bluetooth/hci_event.c:7477 [inline] hci_event_packet+0x7e0/0x1200 net/bluetooth/hci_event.c:7531 hci_rx_work+0x46a/0xe80 net/bluetooth/hci_core.c:4070 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/sour ---truncated--- CVE-2025-39982 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39982.html CVE-2025-39982 https://bugzilla.suse.com/1252083 SUSE Bug 1252083 In the Linux kernel, the following vulnerability has been resolved: net: tun: Update napi->skb after XDP process The syzbot report a UAF issue: BUG: KASAN: slab-use-after-free in skb_reset_mac_header include/linux/skbuff.h:3150 [inline] BUG: KASAN: slab-use-after-free in napi_frags_skb net/core/gro.c:723 [inline] BUG: KASAN: slab-use-after-free in napi_gro_frags+0x6e/0x1030 net/core/gro.c:758 Read of size 8 at addr ffff88802ef22c18 by task syz.0.17/6079 CPU: 0 UID: 0 PID: 6079 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 skb_reset_mac_header include/linux/skbuff.h:3150 [inline] napi_frags_skb net/core/gro.c:723 [inline] napi_gro_frags+0x6e/0x1030 net/core/gro.c:758 tun_get_user+0x28cb/0x3e20 drivers/net/tun.c:1920 tun_chr_write_iter+0x113/0x200 drivers/net/tun.c:1996 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x5c9/0xb30 fs/read_write.c:686 ksys_write+0x145/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> Allocated by task 6079: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:330 [inline] __kasan_mempool_unpoison_object+0xa0/0x170 mm/kasan/common.c:558 kasan_mempool_unpoison_object include/linux/kasan.h:388 [inline] napi_skb_cache_get+0x37b/0x6d0 net/core/skbuff.c:295 __alloc_skb+0x11e/0x2d0 net/core/skbuff.c:657 napi_alloc_skb+0x84/0x7d0 net/core/skbuff.c:811 napi_get_frags+0x69/0x140 net/core/gro.c:673 tun_napi_alloc_frags drivers/net/tun.c:1404 [inline] tun_get_user+0x77c/0x3e20 drivers/net/tun.c:1784 tun_chr_write_iter+0x113/0x200 drivers/net/tun.c:1996 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x5c9/0xb30 fs/read_write.c:686 ksys_write+0x145/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 6079: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:576 poison_slab_object mm/kasan/common.c:243 [inline] __kasan_slab_free+0x5b/0x80 mm/kasan/common.c:275 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2422 [inline] slab_free mm/slub.c:4695 [inline] kmem_cache_free+0x18f/0x400 mm/slub.c:4797 skb_pp_cow_data+0xdd8/0x13e0 net/core/skbuff.c:969 netif_skb_check_for_xdp net/core/dev.c:5390 [inline] netif_receive_generic_xdp net/core/dev.c:5431 [inline] do_xdp_generic+0x699/0x11a0 net/core/dev.c:5499 tun_get_user+0x2523/0x3e20 drivers/net/tun.c:1872 tun_chr_write_iter+0x113/0x200 drivers/net/tun.c:1996 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x5c9/0xb30 fs/read_write.c:686 ksys_write+0x145/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f After commit e6d5dbdd20aa ("xdp: add multi-buff support for xdp running in generic mode"), the original skb may be freed in skb_pp_cow_data() when XDP program was attached, which was allocated in tun_napi_alloc_frags(). However, the napi->skb still point to the original skb, update it after XDP process. CVE-2025-39984 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39984.html CVE-2025-39984 https://bugzilla.suse.com/1252081 SUSE Bug 1252081 In the Linux kernel, the following vulnerability has been resolved: can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow Sending an PF_PACKET allows to bypass the CAN framework logic and to directly reach the xmit() function of a CAN driver. The only check which is performed by the PF_PACKET framework is to make sure that skb->len fits the interface's MTU. Unfortunately, because the mcba_usb driver does not populate its net_device_ops->ndo_change_mtu(), it is possible for an attacker to configure an invalid MTU by doing, for example: $ ip link set can0 mtu 9999 After doing so, the attacker could open a PF_PACKET socket using the ETH_P_CANXL protocol: socket(PF_PACKET, SOCK_RAW, htons(ETH_P_CANXL)) to inject a malicious CAN XL frames. For example: struct canxl_frame frame = { .flags = 0xff, .len = 2048, }; The CAN drivers' xmit() function are calling can_dev_dropped_skb() to check that the skb is valid, unfortunately under above conditions, the malicious packet is able to go through can_dev_dropped_skb() checks: 1. the skb->protocol is set to ETH_P_CANXL which is valid (the function does not check the actual device capabilities). 2. the length is a valid CAN XL length. And so, mcba_usb_start_xmit() receives a CAN XL frame which it is not able to correctly handle and will thus misinterpret it as a CAN frame. This can result in a buffer overflow. The driver will consume cf->len as-is with no further checks on these lines: usb_msg.dlc = cf->len; memcpy(usb_msg.data, cf->data, usb_msg.dlc); Here, cf->len corresponds to the flags field of the CAN XL frame. In our previous example, we set canxl_frame->flags to 0xff. Because the maximum expected length is 8, a buffer overflow of 247 bytes occurs! Populate net_device_ops->ndo_change_mtu() to ensure that the interface's MTU can not be set to anything bigger than CAN_MTU. By fixing the root cause, this prevents the buffer overflow. CVE-2025-39985 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39985.html CVE-2025-39985 https://bugzilla.suse.com/1252082 SUSE Bug 1252082 In the Linux kernel, the following vulnerability has been resolved: can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow Sending an PF_PACKET allows to bypass the CAN framework logic and to directly reach the xmit() function of a CAN driver. The only check which is performed by the PF_PACKET framework is to make sure that skb->len fits the interface's MTU. Unfortunately, because the sun4i_can driver does not populate its net_device_ops->ndo_change_mtu(), it is possible for an attacker to configure an invalid MTU by doing, for example: $ ip link set can0 mtu 9999 After doing so, the attacker could open a PF_PACKET socket using the ETH_P_CANXL protocol: socket(PF_PACKET, SOCK_RAW, htons(ETH_P_CANXL)) to inject a malicious CAN XL frames. For example: struct canxl_frame frame = { .flags = 0xff, .len = 2048, }; The CAN drivers' xmit() function are calling can_dev_dropped_skb() to check that the skb is valid, unfortunately under above conditions, the malicious packet is able to go through can_dev_dropped_skb() checks: 1. the skb->protocol is set to ETH_P_CANXL which is valid (the function does not check the actual device capabilities). 2. the length is a valid CAN XL length. And so, sun4ican_start_xmit() receives a CAN XL frame which it is not able to correctly handle and will thus misinterpret it as a CAN frame. This can result in a buffer overflow. The driver will consume cf->len as-is with no further checks on this line: dlc = cf->len; Here, cf->len corresponds to the flags field of the CAN XL frame. In our previous example, we set canxl_frame->flags to 0xff. Because the maximum expected length is 8, a buffer overflow of 247 bytes occurs a couple line below when doing: for (i = 0; i < dlc; i++) writel(cf->data[i], priv->base + (dreg + i * 4)); Populate net_device_ops->ndo_change_mtu() to ensure that the interface's MTU can not be set to anything bigger than CAN_MTU. By fixing the root cause, this prevents the buffer overflow. CVE-2025-39986 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39986.html CVE-2025-39986 https://bugzilla.suse.com/1252078 SUSE Bug 1252078 In the Linux kernel, the following vulnerability has been resolved: can: hi311x: populate ndo_change_mtu() to prevent buffer overflow Sending an PF_PACKET allows to bypass the CAN framework logic and to directly reach the xmit() function of a CAN driver. The only check which is performed by the PF_PACKET framework is to make sure that skb->len fits the interface's MTU. Unfortunately, because the sun4i_can driver does not populate its net_device_ops->ndo_change_mtu(), it is possible for an attacker to configure an invalid MTU by doing, for example: $ ip link set can0 mtu 9999 After doing so, the attacker could open a PF_PACKET socket using the ETH_P_CANXL protocol: socket(PF_PACKET, SOCK_RAW, htons(ETH_P_CANXL)) to inject a malicious CAN XL frames. For example: struct canxl_frame frame = { .flags = 0xff, .len = 2048, }; The CAN drivers' xmit() function are calling can_dev_dropped_skb() to check that the skb is valid, unfortunately under above conditions, the malicious packet is able to go through can_dev_dropped_skb() checks: 1. the skb->protocol is set to ETH_P_CANXL which is valid (the function does not check the actual device capabilities). 2. the length is a valid CAN XL length. And so, hi3110_hard_start_xmit() receives a CAN XL frame which it is not able to correctly handle and will thus misinterpret it as a CAN frame. The driver will consume frame->len as-is with no further checks. This can result in a buffer overflow later on in hi3110_hw_tx() on this line: memcpy(buf + HI3110_FIFO_EXT_DATA_OFF, frame->data, frame->len); Here, frame->len corresponds to the flags field of the CAN XL frame. In our previous example, we set canxl_frame->flags to 0xff. Because the maximum expected length is 8, a buffer overflow of 247 bytes occurs! Populate net_device_ops->ndo_change_mtu() to ensure that the interface's MTU can not be set to anything bigger than CAN_MTU. By fixing the root cause, this prevents the buffer overflow. CVE-2025-39987 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39987.html CVE-2025-39987 https://bugzilla.suse.com/1252079 SUSE Bug 1252079 In the Linux kernel, the following vulnerability has been resolved: can: etas_es58x: populate ndo_change_mtu() to prevent buffer overflow Sending an PF_PACKET allows to bypass the CAN framework logic and to directly reach the xmit() function of a CAN driver. The only check which is performed by the PF_PACKET framework is to make sure that skb->len fits the interface's MTU. Unfortunately, because the etas_es58x driver does not populate its net_device_ops->ndo_change_mtu(), it is possible for an attacker to configure an invalid MTU by doing, for example: $ ip link set can0 mtu 9999 After doing so, the attacker could open a PF_PACKET socket using the ETH_P_CANXL protocol: socket(PF_PACKET, SOCK_RAW, htons(ETH_P_CANXL)); to inject a malicious CAN XL frames. For example: struct canxl_frame frame = { .flags = 0xff, .len = 2048, }; The CAN drivers' xmit() function are calling can_dev_dropped_skb() to check that the skb is valid, unfortunately under above conditions, the malicious packet is able to go through can_dev_dropped_skb() checks: 1. the skb->protocol is set to ETH_P_CANXL which is valid (the function does not check the actual device capabilities). 2. the length is a valid CAN XL length. And so, es58x_start_xmit() receives a CAN XL frame which it is not able to correctly handle and will thus misinterpret it as a CAN(FD) frame. This can result in a buffer overflow. For example, using the es581.4 variant, the frame will be dispatched to es581_4_tx_can_msg(), go through the last check at the beginning of this function: if (can_is_canfd_skb(skb)) return -EMSGSIZE; and reach this line: memcpy(tx_can_msg->data, cf->data, cf->len); Here, cf->len corresponds to the flags field of the CAN XL frame. In our previous example, we set canxl_frame->flags to 0xff. Because the maximum expected length is 8, a buffer overflow of 247 bytes occurs! Populate net_device_ops->ndo_change_mtu() to ensure that the interface's MTU can not be set to anything bigger than CAN_MTU or CANFD_MTU (depending on the device capabilities). By fixing the root cause, this prevents the buffer overflow. CVE-2025-39988 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39988.html CVE-2025-39988 https://bugzilla.suse.com/1252074 SUSE Bug 1252074 In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix NULL dereference in ath11k_qmi_m3_load() If ab->fw.m3_data points to data, then fw pointer remains null. Further, if m3_mem is not allocated, then fw is dereferenced to be passed to ath11k_err function. Replace fw->size by m3_len. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2025-39991 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39991.html CVE-2025-39991 https://bugzilla.suse.com/1252075 SUSE Bug 1252075 In the Linux kernel, the following vulnerability has been resolved: media: rc: fix races with imon_disconnect() Syzbot reports a KASAN issue as below: BUG: KASAN: use-after-free in __create_pipe include/linux/usb.h:1945 [inline] BUG: KASAN: use-after-free in send_packet+0xa2d/0xbc0 drivers/media/rc/imon.c:627 Read of size 4 at addr ffff8880256fb000 by task syz-executor314/4465 CPU: 2 PID: 4465 Comm: syz-executor314 Not tainted 6.0.0-rc1-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:317 [inline] print_report.cold+0x2ba/0x6e9 mm/kasan/report.c:433 kasan_report+0xb1/0x1e0 mm/kasan/report.c:495 __create_pipe include/linux/usb.h:1945 [inline] send_packet+0xa2d/0xbc0 drivers/media/rc/imon.c:627 vfd_write+0x2d9/0x550 drivers/media/rc/imon.c:991 vfs_write+0x2d7/0xdd0 fs/read_write.c:576 ksys_write+0x127/0x250 fs/read_write.c:631 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+0x63/0xcd The iMON driver improperly releases the usb_device reference in imon_disconnect without coordinating with active users of the device. Specifically, the fields usbdev_intf0 and usbdev_intf1 are not protected by the users counter (ictx->users). During probe, imon_init_intf0 or imon_init_intf1 increments the usb_device reference count depending on the interface. However, during disconnect, usb_put_dev is called unconditionally, regardless of actual usage. As a result, if vfd_write or other operations are still in progress after disconnect, this can lead to a use-after-free of the usb_device pointer. Thread 1 vfd_write Thread 2 imon_disconnect ... if usb_put_dev(ictx->usbdev_intf0) else usb_put_dev(ictx->usbdev_intf1) ... while send_packet if pipe = usb_sndintpipe( ictx->usbdev_intf0) UAF else pipe = usb_sndctrlpipe( ictx->usbdev_intf0, 0) UAF Guard access to usbdev_intf0 and usbdev_intf1 after disconnect by checking ictx->disconnected in all writer paths. Add early return with -ENODEV in send_packet(), vfd_write(), lcd_write() and display_open() if the device is no longer present. Set and read ictx->disconnected under ictx->lock to ensure memory synchronization. Acquire the lock in imon_disconnect() before setting the flag to synchronize with any ongoing operations. Ensure writers exit early and safely after disconnect before the USB core proceeds with cleanup. Found by Linux Verification Center (linuxtesting.org) with Syzkaller. CVE-2025-39993 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39993.html CVE-2025-39993 https://bugzilla.suse.com/1252070 SUSE Bug 1252070 In the Linux kernel, the following vulnerability has been resolved: media: tuner: xc5000: Fix use-after-free in xc5000_release The original code uses cancel_delayed_work() in xc5000_release(), which does not guarantee that the delayed work item timer_sleep has fully completed if it was already running. This leads to use-after-free scenarios where xc5000_release() may free the xc5000_priv while timer_sleep is still active and attempts to dereference the xc5000_priv. A typical race condition is illustrated below: CPU 0 (release thread) | CPU 1 (delayed work callback) xc5000_release() | xc5000_do_timer_sleep() cancel_delayed_work() | hybrid_tuner_release_state(priv) | kfree(priv) | | priv = container_of() // UAF Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the timer_sleep is properly canceled before the xc5000_priv memory is deallocated. A deadlock concern was considered: xc5000_release() is called in a process context and is not holding any locks that the timer_sleep work item might also need. Therefore, the use of the _sync() variant is safe here. This bug was initially identified through static analysis. [hverkuil: fix typo in Subject: tunner -> tuner] CVE-2025-39994 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39994.html CVE-2025-39994 https://bugzilla.suse.com/1252072 SUSE Bug 1252072 In the Linux kernel, the following vulnerability has been resolved: media: i2c: tc358743: Fix use-after-free bugs caused by orphan timer in probe The state->timer is a cyclic timer that schedules work_i2c_poll and delayed_work_enable_hotplug, while rearming itself. Using timer_delete() fails to guarantee the timer isn't still running when destroyed, similarly cancel_delayed_work() cannot ensure delayed_work_enable_hotplug has terminated if already executing. During probe failure after timer initialization, these may continue running as orphans and reference the already-freed tc358743_state object through tc358743_irq_poll_timer. The following is the trace captured by KASAN. BUG: KASAN: slab-use-after-free in __run_timer_base.part.0+0x7d7/0x8c0 Write of size 8 at addr ffff88800ded83c8 by task swapper/1/0 ... Call Trace: <IRQ> dump_stack_lvl+0x55/0x70 print_report+0xcf/0x610 ? __pfx_sched_balance_find_src_group+0x10/0x10 ? __run_timer_base.part.0+0x7d7/0x8c0 kasan_report+0xb8/0xf0 ? __run_timer_base.part.0+0x7d7/0x8c0 __run_timer_base.part.0+0x7d7/0x8c0 ? rcu_sched_clock_irq+0xb06/0x27d0 ? __pfx___run_timer_base.part.0+0x10/0x10 ? try_to_wake_up+0xb15/0x1960 ? tmigr_update_events+0x280/0x740 ? _raw_spin_lock_irq+0x80/0xe0 ? __pfx__raw_spin_lock_irq+0x10/0x10 tmigr_handle_remote_up+0x603/0x7e0 ? __pfx_tmigr_handle_remote_up+0x10/0x10 ? sched_balance_trigger+0x98/0x9f0 ? sched_tick+0x221/0x5a0 ? _raw_spin_lock_irq+0x80/0xe0 ? __pfx__raw_spin_lock_irq+0x10/0x10 ? tick_nohz_handler+0x339/0x440 ? __pfx_tmigr_handle_remote_up+0x10/0x10 __walk_groups.isra.0+0x42/0x150 tmigr_handle_remote+0x1f4/0x2e0 ? __pfx_tmigr_handle_remote+0x10/0x10 ? ktime_get+0x60/0x140 ? lapic_next_event+0x11/0x20 ? clockevents_program_event+0x1d4/0x2a0 ? hrtimer_interrupt+0x322/0x780 handle_softirqs+0x16a/0x550 irq_exit_rcu+0xaf/0xe0 sysvec_apic_timer_interrupt+0x70/0x80 </IRQ> ... Allocated by task 141: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7f/0x90 __kmalloc_node_track_caller_noprof+0x198/0x430 devm_kmalloc+0x7b/0x1e0 tc358743_probe+0xb7/0x610 i2c_device_probe+0x51d/0x880 really_probe+0x1ca/0x5c0 __driver_probe_device+0x248/0x310 driver_probe_device+0x44/0x120 __device_attach_driver+0x174/0x220 bus_for_each_drv+0x100/0x190 __device_attach+0x206/0x370 bus_probe_device+0x123/0x170 device_add+0xd25/0x1470 i2c_new_client_device+0x7a0/0xcd0 do_one_initcall+0x89/0x300 do_init_module+0x29d/0x7f0 load_module+0x4f48/0x69e0 init_module_from_file+0xe4/0x150 idempotent_init_module+0x320/0x670 __x64_sys_finit_module+0xbd/0x120 do_syscall_64+0xac/0x280 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 141: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3a/0x60 __kasan_slab_free+0x3f/0x50 kfree+0x137/0x370 release_nodes+0xa4/0x100 devres_release_group+0x1b2/0x380 i2c_device_probe+0x694/0x880 really_probe+0x1ca/0x5c0 __driver_probe_device+0x248/0x310 driver_probe_device+0x44/0x120 __device_attach_driver+0x174/0x220 bus_for_each_drv+0x100/0x190 __device_attach+0x206/0x370 bus_probe_device+0x123/0x170 device_add+0xd25/0x1470 i2c_new_client_device+0x7a0/0xcd0 do_one_initcall+0x89/0x300 do_init_module+0x29d/0x7f0 load_module+0x4f48/0x69e0 init_module_from_file+0xe4/0x150 idempotent_init_module+0x320/0x670 __x64_sys_finit_module+0xbd/0x120 do_syscall_64+0xac/0x280 entry_SYSCALL_64_after_hwframe+0x77/0x7f ... Replace timer_delete() with timer_delete_sync() and cancel_delayed_work() with cancel_delayed_work_sync() to ensure proper termination of timer and work items before resource cleanup. This bug was initially identified through static analysis. For reproduction and testing, I created a functional emulation of the tc358743 device via a kernel module and introduced faults through the debugfs interface. CVE-2025-39995 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39995.html CVE-2025-39995 https://bugzilla.suse.com/1252064 SUSE Bug 1252064 In the Linux kernel, the following vulnerability has been resolved: media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove The original code uses cancel_delayed_work() in flexcop_pci_remove(), which does not guarantee that the delayed work item irq_check_work has fully completed if it was already running. This leads to use-after-free scenarios where flexcop_pci_remove() may free the flexcop_device while irq_check_work is still active and attempts to dereference the device. A typical race condition is illustrated below: CPU 0 (remove) | CPU 1 (delayed work callback) flexcop_pci_remove() | flexcop_pci_irq_check_work() cancel_delayed_work() | flexcop_device_kfree(fc_pci->fc_dev) | | fc = fc_pci->fc_dev; // UAF This is confirmed by a KASAN report: ================================================================== BUG: KASAN: slab-use-after-free in __run_timer_base.part.0+0x7d7/0x8c0 Write of size 8 at addr ffff8880093aa8c8 by task bash/135 ... Call Trace: <IRQ> dump_stack_lvl+0x55/0x70 print_report+0xcf/0x610 ? __run_timer_base.part.0+0x7d7/0x8c0 kasan_report+0xb8/0xf0 ? __run_timer_base.part.0+0x7d7/0x8c0 __run_timer_base.part.0+0x7d7/0x8c0 ? __pfx___run_timer_base.part.0+0x10/0x10 ? __pfx_read_tsc+0x10/0x10 ? ktime_get+0x60/0x140 ? lapic_next_event+0x11/0x20 ? clockevents_program_event+0x1d4/0x2a0 run_timer_softirq+0xd1/0x190 handle_softirqs+0x16a/0x550 irq_exit_rcu+0xaf/0xe0 sysvec_apic_timer_interrupt+0x70/0x80 </IRQ> ... Allocated by task 1: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7f/0x90 __kmalloc_noprof+0x1be/0x460 flexcop_device_kmalloc+0x54/0xe0 flexcop_pci_probe+0x1f/0x9d0 local_pci_probe+0xdc/0x190 pci_device_probe+0x2fe/0x470 really_probe+0x1ca/0x5c0 __driver_probe_device+0x248/0x310 driver_probe_device+0x44/0x120 __driver_attach+0xd2/0x310 bus_for_each_dev+0xed/0x170 bus_add_driver+0x208/0x500 driver_register+0x132/0x460 do_one_initcall+0x89/0x300 kernel_init_freeable+0x40d/0x720 kernel_init+0x1a/0x150 ret_from_fork+0x10c/0x1a0 ret_from_fork_asm+0x1a/0x30 Freed by task 135: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3a/0x60 __kasan_slab_free+0x3f/0x50 kfree+0x137/0x370 flexcop_device_kfree+0x32/0x50 pci_device_remove+0xa6/0x1d0 device_release_driver_internal+0xf8/0x210 pci_stop_bus_device+0x105/0x150 pci_stop_and_remove_bus_device_locked+0x15/0x30 remove_store+0xcc/0xe0 kernfs_fop_write_iter+0x2c3/0x440 vfs_write+0x871/0xd70 ksys_write+0xee/0x1c0 do_syscall_64+0xac/0x280 entry_SYSCALL_64_after_hwframe+0x77/0x7f ... Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the delayed work item is properly canceled and any executing delayed work has finished before the device memory is deallocated. This bug was initially identified through static analysis. To reproduce and test it, I simulated the B2C2 FlexCop PCI device in QEMU and introduced artificial delays within the flexcop_pci_irq_check_work() function to increase the likelihood of triggering the bug. CVE-2025-39996 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39996.html CVE-2025-39996 https://bugzilla.suse.com/1252065 SUSE Bug 1252065 In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free The previous commit 0718a78f6a9f ("ALSA: usb-audio: Kill timer properly at removal") patched a UAF issue caused by the error timer. However, because the error timer kill added in this patch occurs after the endpoint delete, a race condition to UAF still occurs, albeit rarely. Additionally, since kill-cleanup for urb is also missing, freed memory can be accessed in interrupt context related to urb, which can cause UAF. Therefore, to prevent this, error timer and urb must be killed before freeing the heap memory. CVE-2025-39997 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-39997.html CVE-2025-39997 https://bugzilla.suse.com/1252056 SUSE Bug 1252056 In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait() There is a bug observed when rtw89_core_tx_kick_off_and_wait() tries to access already freed skb_data: BUG: KFENCE: use-after-free write in rtw89_core_tx_kick_off_and_wait drivers/net/wireless/realtek/rtw89/core.c:1110 CPU: 6 UID: 0 PID: 41377 Comm: kworker/u64:24 Not tainted 6.17.0-rc1+ #1 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS edk2-20250523-14.fc42 05/23/2025 Workqueue: events_unbound cfg80211_wiphy_work [cfg80211] Use-after-free write at 0x0000000020309d9d (in kfence-#251): rtw89_core_tx_kick_off_and_wait drivers/net/wireless/realtek/rtw89/core.c:1110 rtw89_core_scan_complete drivers/net/wireless/realtek/rtw89/core.c:5338 rtw89_hw_scan_complete_cb drivers/net/wireless/realtek/rtw89/fw.c:7979 rtw89_chanctx_proceed_cb drivers/net/wireless/realtek/rtw89/chan.c:3165 rtw89_chanctx_proceed drivers/net/wireless/realtek/rtw89/chan.h:141 rtw89_hw_scan_complete drivers/net/wireless/realtek/rtw89/fw.c:8012 rtw89_mac_c2h_scanofld_rsp drivers/net/wireless/realtek/rtw89/mac.c:5059 rtw89_fw_c2h_work drivers/net/wireless/realtek/rtw89/fw.c:6758 process_one_work kernel/workqueue.c:3241 worker_thread kernel/workqueue.c:3400 kthread kernel/kthread.c:463 ret_from_fork arch/x86/kernel/process.c:154 ret_from_fork_asm arch/x86/entry/entry_64.S:258 kfence-#251: 0x0000000056e2393d-0x000000009943cb62, size=232, cache=skbuff_head_cache allocated by task 41377 on cpu 6 at 77869.159548s (0.009551s ago): __alloc_skb net/core/skbuff.c:659 __netdev_alloc_skb net/core/skbuff.c:734 ieee80211_nullfunc_get net/mac80211/tx.c:5844 rtw89_core_send_nullfunc drivers/net/wireless/realtek/rtw89/core.c:3431 rtw89_core_scan_complete drivers/net/wireless/realtek/rtw89/core.c:5338 rtw89_hw_scan_complete_cb drivers/net/wireless/realtek/rtw89/fw.c:7979 rtw89_chanctx_proceed_cb drivers/net/wireless/realtek/rtw89/chan.c:3165 rtw89_chanctx_proceed drivers/net/wireless/realtek/rtw89/chan.c:3194 rtw89_hw_scan_complete drivers/net/wireless/realtek/rtw89/fw.c:8012 rtw89_mac_c2h_scanofld_rsp drivers/net/wireless/realtek/rtw89/mac.c:5059 rtw89_fw_c2h_work drivers/net/wireless/realtek/rtw89/fw.c:6758 process_one_work kernel/workqueue.c:3241 worker_thread kernel/workqueue.c:3400 kthread kernel/kthread.c:463 ret_from_fork arch/x86/kernel/process.c:154 ret_from_fork_asm arch/x86/entry/entry_64.S:258 freed by task 1045 on cpu 9 at 77869.168393s (0.001557s ago): ieee80211_tx_status_skb net/mac80211/status.c:1117 rtw89_pci_release_txwd_skb drivers/net/wireless/realtek/rtw89/pci.c:564 rtw89_pci_release_tx_skbs.isra.0 drivers/net/wireless/realtek/rtw89/pci.c:651 rtw89_pci_release_tx drivers/net/wireless/realtek/rtw89/pci.c:676 rtw89_pci_napi_poll drivers/net/wireless/realtek/rtw89/pci.c:4238 __napi_poll net/core/dev.c:7495 net_rx_action net/core/dev.c:7557 net/core/dev.c:7684 handle_softirqs kernel/softirq.c:580 do_softirq.part.0 kernel/softirq.c:480 __local_bh_enable_ip kernel/softirq.c:407 rtw89_pci_interrupt_threadfn drivers/net/wireless/realtek/rtw89/pci.c:927 irq_thread_fn kernel/irq/manage.c:1133 irq_thread kernel/irq/manage.c:1257 kthread kernel/kthread.c:463 ret_from_fork arch/x86/kernel/process.c:154 ret_from_fork_asm arch/x86/entry/entry_64.S:258 It is a consequence of a race between the waiting and the signaling side of the completion: Waiting thread Completing thread rtw89_core_tx_kick_off_and_wait() rcu_assign_pointer(skb_data->wait, wait) /* start waiting */ wait_for_completion_timeout() rtw89_pci_tx_status() rtw89_core_tx_wait_complete() rcu_read_lock() /* signals completion and ---truncated--- CVE-2025-40000 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40000.html CVE-2025-40000 https://bugzilla.suse.com/1252062 SUSE Bug 1252062 In the Linux kernel, the following vulnerability has been resolved: spi: cadence-quadspi: Implement refcount to handle unbind during busy driver support indirect read and indirect write operation with assumption no force device removal(unbind) operation. However force device removal(removal) is still available to root superuser. Unbinding driver during operation causes kernel crash. This changes ensure driver able to handle such operation for indirect read and indirect write by implementing refcount to track attached devices to the controller and gracefully wait and until attached devices remove operation completed before proceed with removal operation. CVE-2025-40005 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40005.html CVE-2025-40005 https://bugzilla.suse.com/1252349 SUSE Bug 1252349 In the Linux kernel, the following vulnerability has been resolved: afs: Fix potential null pointer dereference in afs_put_server afs_put_server() accessed server->debug_id before the NULL check, which could lead to a null pointer dereference. Move the debug_id assignment, ensuring we never dereference a NULL server pointer. CVE-2025-40010 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40010.html CVE-2025-40010 https://bugzilla.suse.com/1252332 SUSE Bug 1252332 In the Linux kernel, the following vulnerability has been resolved: drm/gma500: Fix null dereference in hdmi teardown pci_set_drvdata sets the value of pdev->driver_data to NULL, after which the driver_data obtained from the same dev is dereferenced in oaktrail_hdmi_i2c_exit, and the i2c_dev is extracted from it. To prevent this, swap these calls. Found by Linux Verification Center (linuxtesting.org) with Svacer. CVE-2025-40011 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40011.html CVE-2025-40011 https://bugzilla.suse.com/1252336 SUSE Bug 1252336 In the Linux kernel, the following vulnerability has been resolved: net/smc: fix warning in smc_rx_splice() when calling get_page() smc_lo_register_dmb() allocates DMB buffers with kzalloc(), which are later passed to get_page() in smc_rx_splice(). Since kmalloc memory is not page-backed, this triggers WARN_ON_ONCE() in get_page() and prevents holding a refcount on the buffer. This can lead to use-after-free if the memory is released before splice_to_pipe() completes. Use folio_alloc() instead, ensuring DMBs are page-backed and safe for get_page(). WARNING: CPU: 18 PID: 12152 at ./include/linux/mm.h:1330 smc_rx_splice+0xaf8/0xe20 [smc] CPU: 18 UID: 0 PID: 12152 Comm: smcapp Kdump: loaded Not tainted 6.17.0-rc3-11705-g9cf4672ecfee #10 NONE Hardware name: IBM 3931 A01 704 (z/VM 7.4.0) Krnl PSW : 0704e00180000000 000793161032696c (smc_rx_splice+0xafc/0xe20 [smc]) 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: 0000000000000000 001cee80007d3001 00077400000000f8 0000000000000005 0000000000000001 001cee80007d3006 0007740000001000 001c000000000000 000000009b0c99e0 0000000000001000 001c0000000000f8 001c000000000000 000003ffcc6f7c88 0007740003e98000 0007931600000005 000792969b2ff7b8 Krnl Code: 0007931610326960: af000000 mc 0,0 0007931610326964: a7f4ff43 brc 15,00079316103267ea #0007931610326968: af000000 mc 0,0 >000793161032696c: a7f4ff3f brc 15,00079316103267ea 0007931610326970: e320f1000004 lg %r2,256(%r15) 0007931610326976: c0e53fd1b5f5 brasl %r14,000793168fd5d560 000793161032697c: a7f4fbb5 brc 15,00079316103260e6 0007931610326980: b904002b lgr %r2,%r11 Call Trace: smc_rx_splice+0xafc/0xe20 [smc] smc_rx_splice+0x756/0xe20 [smc]) smc_rx_recvmsg+0xa74/0xe00 [smc] smc_splice_read+0x1ce/0x3b0 [smc] sock_splice_read+0xa2/0xf0 do_splice_read+0x198/0x240 splice_file_to_pipe+0x7e/0x110 do_splice+0x59e/0xde0 __do_splice+0x11a/0x2d0 __s390x_sys_splice+0x140/0x1f0 __do_syscall+0x122/0x280 system_call+0x6e/0x90 Last Breaking-Event-Address: smc_rx_splice+0x960/0xe20 [smc] ---[ end trace 0000000000000000 ]--- CVE-2025-40012 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40012.html CVE-2025-40012 https://bugzilla.suse.com/1252330 SUSE Bug 1252330 In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: audioreach: fix potential null pointer dereference It is possible that the topology parsing function audioreach_widget_load_module_common() could return NULL or an error pointer. Add missing NULL check so that we do not dereference it. CVE-2025-40013 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40013.html CVE-2025-40013 https://bugzilla.suse.com/1252348 SUSE Bug 1252348 In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID Per UVC 1.1+ specification 3.7.2, units and terminals must have a non-zero unique ID. ``` Each Unit and Terminal within the video function is assigned a unique identification number, the Unit ID (UID) or Terminal ID (TID), contained in the bUnitID or bTerminalID field of the descriptor. The value 0x00 is reserved for undefined ID, ``` If we add a new entity with id 0 or a duplicated ID, it will be marked as UVC_INVALID_ENTITY_ID. In a previous attempt commit 3dd075fe8ebb ("media: uvcvideo: Require entities to have a non-zero unique ID"), we ignored all the invalid units, this broke a lot of non-compatible cameras. Hopefully we are more lucky this time. This also prevents some syzkaller reproducers from triggering warnings due to a chain of entities referring to themselves. In one particular case, an Output Unit is connected to an Input Unit, both with the same ID of 1. But when looking up for the source ID of the Output Unit, that same entity is found instead of the input entity, which leads to such warnings. In another case, a backward chain was considered finished as the source ID was 0. Later on, that entity was found, but its pads were not valid. Here is a sample stack trace for one of those cases. [ 20.650953] usb 1-1: new high-speed USB device number 2 using dummy_hcd [ 20.830206] usb 1-1: Using ep0 maxpacket: 8 [ 20.833501] usb 1-1: config 0 descriptor?? [ 21.038518] usb 1-1: string descriptor 0 read error: -71 [ 21.038893] usb 1-1: Found UVC 0.00 device <unnamed> (2833:0201) [ 21.039299] uvcvideo 1-1:0.0: Entity type for entity Output 1 was not initialized! [ 21.041583] uvcvideo 1-1:0.0: Entity type for entity Input 1 was not initialized! [ 21.042218] ------------[ cut here ]------------ [ 21.042536] WARNING: CPU: 0 PID: 9 at drivers/media/mc/mc-entity.c:1147 media_create_pad_link+0x2c4/0x2e0 [ 21.043195] Modules linked in: [ 21.043535] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.11.0-rc7-00030-g3480e43aeccf #444 [ 21.044101] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 [ 21.044639] Workqueue: usb_hub_wq hub_event [ 21.045100] RIP: 0010:media_create_pad_link+0x2c4/0x2e0 [ 21.045508] Code: fe e8 20 01 00 00 b8 f4 ff ff ff 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 0f 0b eb e9 0f 0b eb 0a 0f 0b eb 06 <0f> 0b eb 02 0f 0b b8 ea ff ff ff eb d4 66 2e 0f 1f 84 00 00 00 00 [ 21.046801] RSP: 0018:ffffc9000004b318 EFLAGS: 00010246 [ 21.047227] RAX: ffff888004e5d458 RBX: 0000000000000000 RCX: ffffffff818fccf1 [ 21.047719] RDX: 000000000000007b RSI: 0000000000000000 RDI: ffff888004313290 [ 21.048241] RBP: ffff888004313290 R08: 0001ffffffffffff R09: 0000000000000000 [ 21.048701] R10: 0000000000000013 R11: 0001888004313290 R12: 0000000000000003 [ 21.049138] R13: ffff888004313080 R14: ffff888004313080 R15: 0000000000000000 [ 21.049648] FS: 0000000000000000(0000) GS:ffff88803ec00000(0000) knlGS:0000000000000000 [ 21.050271] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 21.050688] CR2: 0000592cc27635b0 CR3: 000000000431c000 CR4: 0000000000750ef0 [ 21.051136] PKRU: 55555554 [ 21.051331] Call Trace: [ 21.051480] <TASK> [ 21.051611] ? __warn+0xc4/0x210 [ 21.051861] ? media_create_pad_link+0x2c4/0x2e0 [ 21.052252] ? report_bug+0x11b/0x1a0 [ 21.052540] ? trace_hardirqs_on+0x31/0x40 [ 21.052901] ? handle_bug+0x3d/0x70 [ 21.053197] ? exc_invalid_op+0x1a/0x50 [ 21.053511] ? asm_exc_invalid_op+0x1a/0x20 [ 21.053924] ? media_create_pad_link+0x91/0x2e0 [ 21.054364] ? media_create_pad_link+0x2c4/0x2e0 [ 21.054834] ? media_create_pad_link+0x91/0x2e0 [ 21.055131] ? _raw_spin_unlock+0x1e/0x40 [ 21.055441] ? __v4l2_device_register_subdev+0x202/0x210 [ 21.055837] uvc_mc_register_entities+0x358/0x400 [ 21.056144] uvc_register_chains+0x1 ---truncated--- CVE-2025-40016 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40016.html CVE-2025-40016 https://bugzilla.suse.com/1252346 SUSE Bug 1252346 In the Linux kernel, the following vulnerability has been resolved: ipvs: Defer ip_vs_ftp unregister during netns cleanup On the netns cleanup path, __ip_vs_ftp_exit() may unregister ip_vs_ftp before connections with valid cp->app pointers are flushed, leading to a use-after-free. Fix this by introducing a global `exiting_module` flag, set to true in ip_vs_ftp_exit() before unregistering the pernet subsystem. In __ip_vs_ftp_exit(), skip ip_vs_ftp unregister if called during netns cleanup (when exiting_module is false) and defer it to __ip_vs_cleanup_batch(), which unregisters all apps after all connections are flushed. If called during module exit, unregister ip_vs_ftp immediately. CVE-2025-40018 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40018.html CVE-2025-40018 https://bugzilla.suse.com/1247374 SUSE Bug 1247374 https://bugzilla.suse.com/1252688 SUSE Bug 1252688 https://bugzilla.suse.com/1252689 SUSE Bug 1252689 https://bugzilla.suse.com/1253291 SUSE Bug 1253291 In the Linux kernel, the following vulnerability has been resolved: crypto: essiv - Check ssize for decryption and in-place encryption Move the ssize check to the start in essiv_aead_crypt so that it's also checked for decryption and in-place encryption. CVE-2025-40019 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40019.html CVE-2025-40019 https://bugzilla.suse.com/1252678 SUSE Bug 1252678 https://bugzilla.suse.com/1252719 SUSE Bug 1252719 In the Linux kernel, the following vulnerability has been resolved: can: peak_usb: fix shift-out-of-bounds issue Explicitly uses a 64-bit constant when the number of bits used for its shifting is 32 (which is the case for PC CAN FD interfaces supported by this driver). [mkl: update subject, apply manually] CVE-2025-40020 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40020.html CVE-2025-40020 https://bugzilla.suse.com/1252679 SUSE Bug 1252679 In the Linux kernel, the following vulnerability has been resolved: bus: fsl-mc: Check return value of platform_get_resource() platform_get_resource() returns NULL in case of failure, so check its return value and propagate the error in order to prevent NULL pointer dereference. CVE-2025-40029 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40029.html CVE-2025-40029 https://bugzilla.suse.com/1252772 SUSE Bug 1252772 In the Linux kernel, the following vulnerability has been resolved: PCI: endpoint: pci-epf-test: Add NULL check for DMA channels before release The fields dma_chan_tx and dma_chan_rx of the struct pci_epf_test can be NULL even after EPF initialization. Then it is prudent to check that they have non-NULL values before releasing the channels. Add the checks in pci_epf_test_clean_dma_chan(). Without the checks, NULL pointer dereferences happen and they can lead to a kernel panic in some cases: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000050 Call trace: dma_release_channel+0x2c/0x120 (P) pci_epf_test_epc_deinit+0x94/0xc0 [pci_epf_test] pci_epc_deinit_notify+0x74/0xc0 tegra_pcie_ep_pex_rst_irq+0x250/0x5d8 irq_thread_fn+0x34/0xb8 irq_thread+0x18c/0x2e8 kthread+0x14c/0x210 ret_from_fork+0x10/0x20 [mani: trimmed the stack trace] CVE-2025-40032 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40032.html CVE-2025-40032 https://bugzilla.suse.com/1252841 SUSE Bug 1252841 In the Linux kernel, the following vulnerability has been resolved: Input: uinput - zero-initialize uinput_ff_upload_compat to avoid info leak Struct ff_effect_compat is embedded twice inside uinput_ff_upload_compat, contains internal padding. In particular, there is a hole after struct ff_replay to satisfy alignment requirements for the following union member. Without clearing the structure, copy_to_user() may leak stack data to userspace. Initialize ff_up_compat to zero before filling valid fields. CVE-2025-40035 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40035.html CVE-2025-40035 https://bugzilla.suse.com/1252866 SUSE Bug 1252866 In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: fix possible map leak in fastrpc_put_args copy_to_user() failure would cause an early return without cleaning up the fdlist, which has been updated by the DSP. This could lead to map leak. Fix this by redirecting to a cleanup path on failure, ensuring that all mapped buffers are properly released before returning. CVE-2025-40036 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40036.html CVE-2025-40036 https://bugzilla.suse.com/1252865 SUSE Bug 1252865 In the Linux kernel, the following vulnerability has been resolved: fbdev: simplefb: Fix use after free in simplefb_detach_genpds() The pm_domain cleanup can not be devres managed as it uses struct simplefb_par which is allocated within struct fb_info by framebuffer_alloc(). This allocation is explicitly freed by unregister_framebuffer() in simplefb_remove(). Devres managed cleanup runs after the device remove call and thus can no longer access struct simplefb_par. Call simplefb_detach_genpds() explicitly from simplefb_destroy() like the cleanup functions for clocks and regulators. Fixes an use after free on M2 Mac mini during aperture_remove_conflicting_devices() using the downstream asahi kernel with Debian's kernel config. For unknown reasons this started to consistently dereference an invalid pointer in v6.16.3 based kernels. [ 6.736134] BUG: KASAN: slab-use-after-free in simplefb_detach_genpds+0x58/0x220 [ 6.743545] Read of size 4 at addr ffff8000304743f0 by task (udev-worker)/227 [ 6.750697] [ 6.752182] CPU: 6 UID: 0 PID: 227 Comm: (udev-worker) Tainted: G S 6.16.3-asahi+ #16 PREEMPTLAZY [ 6.752186] Tainted: [S]=CPU_OUT_OF_SPEC [ 6.752187] Hardware name: Apple Mac mini (M2, 2023) (DT) [ 6.752189] Call trace: [ 6.752190] show_stack+0x34/0x98 (C) [ 6.752194] dump_stack_lvl+0x60/0x80 [ 6.752197] print_report+0x17c/0x4d8 [ 6.752201] kasan_report+0xb4/0x100 [ 6.752206] __asan_report_load4_noabort+0x20/0x30 [ 6.752209] simplefb_detach_genpds+0x58/0x220 [ 6.752213] devm_action_release+0x50/0x98 [ 6.752216] release_nodes+0xd0/0x2c8 [ 6.752219] devres_release_all+0xfc/0x178 [ 6.752221] device_unbind_cleanup+0x28/0x168 [ 6.752224] device_release_driver_internal+0x34c/0x470 [ 6.752228] device_release_driver+0x20/0x38 [ 6.752231] bus_remove_device+0x1b0/0x380 [ 6.752234] device_del+0x314/0x820 [ 6.752238] platform_device_del+0x3c/0x1e8 [ 6.752242] platform_device_unregister+0x20/0x50 [ 6.752246] aperture_detach_platform_device+0x1c/0x30 [ 6.752250] aperture_detach_devices+0x16c/0x290 [ 6.752253] aperture_remove_conflicting_devices+0x34/0x50 ... [ 6.752343] [ 6.967409] Allocated by task 62: [ 6.970724] kasan_save_stack+0x3c/0x70 [ 6.974560] kasan_save_track+0x20/0x40 [ 6.978397] kasan_save_alloc_info+0x40/0x58 [ 6.982670] __kasan_kmalloc+0xd4/0xd8 [ 6.986420] __kmalloc_noprof+0x194/0x540 [ 6.990432] framebuffer_alloc+0xc8/0x130 [ 6.994444] simplefb_probe+0x258/0x2378 ... [ 7.054356] [ 7.055838] Freed by task 227: [ 7.058891] kasan_save_stack+0x3c/0x70 [ 7.062727] kasan_save_track+0x20/0x40 [ 7.066565] kasan_save_free_info+0x4c/0x80 [ 7.070751] __kasan_slab_free+0x6c/0xa0 [ 7.074675] kfree+0x10c/0x380 [ 7.077727] framebuffer_release+0x5c/0x90 [ 7.081826] simplefb_destroy+0x1b4/0x2c0 [ 7.085837] put_fb_info+0x98/0x100 [ 7.089326] unregister_framebuffer+0x178/0x320 [ 7.093861] simplefb_remove+0x3c/0x60 [ 7.097611] platform_remove+0x60/0x98 [ 7.101361] device_remove+0xb8/0x160 [ 7.105024] device_release_driver_internal+0x2fc/0x470 [ 7.110256] device_release_driver+0x20/0x38 [ 7.114529] bus_remove_device+0x1b0/0x380 [ 7.118628] device_del+0x314/0x820 [ 7.122116] platform_device_del+0x3c/0x1e8 [ 7.126302] platform_device_unregister+0x20/0x50 [ 7.131012] aperture_detach_platform_device+0x1c/0x30 [ 7.136157] aperture_detach_devices+0x16c/0x290 [ 7.140779] aperture_remove_conflicting_devices+0x34/0x50 ... CVE-2025-40037 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40037.html CVE-2025-40037 https://bugzilla.suse.com/1252819 SUSE Bug 1252819 In the Linux kernel, the following vulnerability has been resolved: net: nfc: nci: Add parameter validation for packet data Syzbot reported an uninitialized value bug in nci_init_req, which was introduced by commit 5aca7966d2a7 ("Merge tag 'perf-tools-fixes-for-v6.17-2025-09-16' of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools"). This bug arises due to very limited and poor input validation that was done at nic_valid_size(). This validation only validates the skb->len (directly reflects size provided at the userspace interface) with the length provided in the buffer itself (interpreted as NCI_HEADER). This leads to the processing of memory content at the address assuming the correct layout per what opcode requires there. This leads to the accesses to buffer of `skb_buff->data` which is not assigned anything yet. Following the same silent drop of packets of invalid sizes at `nic_valid_size()`, add validation of the data in the respective handlers and return error values in case of failure. Release the skb if error values are returned from handlers in `nci_nft_packet` and effectively do a silent drop Possible TODO: because we silently drop the packets, the call to `nci_request` will be waiting for completion of request and will face timeouts. These timeouts can get excessively logged in the dmesg. A proper handling of them may require to export `nci_request_cancel` (or propagate error handling from the nft packets handlers). CVE-2025-40043 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40043.html CVE-2025-40043 https://bugzilla.suse.com/1252787 SUSE Bug 1252787 In the Linux kernel, the following vulnerability has been resolved: fs: udf: fix OOB read in lengthAllocDescs handling When parsing Allocation Extent Descriptor, lengthAllocDescs comes from on-disk data and must be validated against the block size. Crafted or corrupted images may set lengthAllocDescs so that the total descriptor length (sizeof(allocExtDesc) + lengthAllocDescs) exceeds the buffer, leading udf_update_tag() to call crc_itu_t() on out-of-bounds memory and trigger a KASAN use-after-free read. BUG: KASAN: use-after-free in crc_itu_t+0x1d5/0x2b0 lib/crc-itu-t.c:60 Read of size 1 at addr ffff888041e7d000 by task syz-executor317/5309 CPU: 0 UID: 0 PID: 5309 Comm: syz-executor317 Not tainted 6.12.0-rc4-syzkaller-00261-g850925a8133c #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 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 crc_itu_t+0x1d5/0x2b0 lib/crc-itu-t.c:60 udf_update_tag+0x70/0x6a0 fs/udf/misc.c:261 udf_write_aext+0x4d8/0x7b0 fs/udf/inode.c:2179 extent_trunc+0x2f7/0x4a0 fs/udf/truncate.c:46 udf_truncate_tail_extent+0x527/0x7e0 fs/udf/truncate.c:106 udf_release_file+0xc1/0x120 fs/udf/file.c:185 __fput+0x23f/0x880 fs/file_table.c:431 task_work_run+0x24f/0x310 kernel/task_work.c:239 exit_task_work include/linux/task_work.h:43 [inline] do_exit+0xa2f/0x28e0 kernel/exit.c:939 do_group_exit+0x207/0x2c0 kernel/exit.c:1088 __do_sys_exit_group kernel/exit.c:1099 [inline] __se_sys_exit_group kernel/exit.c:1097 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1097 x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> Validate the computed total length against epos->bh->b_size. Found by Linux Verification Center (linuxtesting.org) with Syzkaller. CVE-2025-40044 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40044.html CVE-2025-40044 https://bugzilla.suse.com/1252785 SUSE Bug 1252785 In the Linux kernel, the following vulnerability has been resolved: Squashfs: fix uninit-value in squashfs_get_parent Syzkaller reports a "KMSAN: uninit-value in squashfs_get_parent" bug. This is caused by open_by_handle_at() being called with a file handle containing an invalid parent inode number. In particular the inode number is that of a symbolic link, rather than a directory. Squashfs_get_parent() gets called with that symbolic link inode, and accesses the parent member field. unsigned int parent_ino = squashfs_i(inode)->parent; Because non-directory inodes in Squashfs do not have a parent value, this is uninitialised, and this causes an uninitialised value access. The fix is to initialise parent with the invalid inode 0, which will cause an EINVAL error to be returned. Regular inodes used to share the parent field with the block_list_start field. This is removed in this commit to enable the parent field to contain the invalid inode number 0. CVE-2025-40049 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40049.html CVE-2025-40049 https://bugzilla.suse.com/1252822 SUSE Bug 1252822 In the Linux kernel, the following vulnerability has been resolved: vhost: vringh: Modify the return value check The return value of copy_from_iter and copy_to_iter can't be negative, check whether the copied lengths are equal. CVE-2025-40051 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40051.html CVE-2025-40051 https://bugzilla.suse.com/1252858 SUSE Bug 1252858 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix crypto buffers in non-linear memory The crypto API, through the scatterlist API, expects input buffers to be in linear memory. We handle this with the cifs_sg_set_buf() helper that converts vmalloc'd memory to their corresponding pages. However, when we allocate our aead_request buffer (@creq in smb2ops.c::crypt_message()), we do so with kvzalloc(), which possibly puts aead_request->__ctx in vmalloc area. AEAD algorithm then uses ->__ctx for its private/internal data and operations, and uses sg_set_buf() for such data on a few places. This works fine as long as @creq falls into kmalloc zone (small requests) or vmalloc'd memory is still within linear range. Tasks' stacks are vmalloc'd by default (CONFIG_VMAP_STACK=y), so too many tasks will increment the base stacks' addresses to a point where virt_addr_valid(buf) will fail (BUG() in sg_set_buf()) when that happens. In practice: too many parallel reads and writes on an encrypted mount will trigger this bug. To fix this, always alloc @creq with kmalloc() instead. Also drop the @sensitive_size variable/arguments since kfree_sensitive() doesn't need it. Backtrace: [ 945.272081] ------------[ cut here ]------------ [ 945.272774] kernel BUG at include/linux/scatterlist.h:209! [ 945.273520] Oops: invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI [ 945.274412] CPU: 7 UID: 0 PID: 56 Comm: kworker/u33:0 Kdump: loaded Not tainted 6.15.0-lku-11779-g8e9d6efccdd7-dirty #1 PREEMPT(voluntary) [ 945.275736] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-2-gc13ff2cd-prebuilt.qemu.org 04/01/2014 [ 945.276877] Workqueue: writeback wb_workfn (flush-cifs-2) [ 945.277457] RIP: 0010:crypto_gcm_init_common+0x1f9/0x220 [ 945.278018] Code: b0 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 48 c7 c0 00 00 00 80 48 2b 05 5c 58 e5 00 e9 58 ff ff ff <0f> 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 48 c7 04 24 01 00 00 00 48 8b [ 945.279992] RSP: 0018:ffffc90000a27360 EFLAGS: 00010246 [ 945.280578] RAX: 0000000000000000 RBX: ffffc90001d85060 RCX: 0000000000000030 [ 945.281376] RDX: 0000000000080000 RSI: 0000000000000000 RDI: ffffc90081d85070 [ 945.282145] RBP: ffffc90001d85010 R08: ffffc90001d85000 R09: 0000000000000000 [ 945.282898] R10: ffffc90001d85090 R11: 0000000000001000 R12: ffffc90001d85070 [ 945.283656] R13: ffff888113522948 R14: ffffc90001d85060 R15: ffffc90001d85010 [ 945.284407] FS: 0000000000000000(0000) GS:ffff8882e66cf000(0000) knlGS:0000000000000000 [ 945.285262] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 945.285884] CR2: 00007fa7ffdd31f4 CR3: 000000010540d000 CR4: 0000000000350ef0 [ 945.286683] Call Trace: [ 945.286952] <TASK> [ 945.287184] ? crypt_message+0x33f/0xad0 [cifs] [ 945.287719] crypto_gcm_encrypt+0x36/0xe0 [ 945.288152] crypt_message+0x54a/0xad0 [cifs] [ 945.288724] smb3_init_transform_rq+0x277/0x300 [cifs] [ 945.289300] smb_send_rqst+0xa3/0x160 [cifs] [ 945.289944] cifs_call_async+0x178/0x340 [cifs] [ 945.290514] ? __pfx_smb2_writev_callback+0x10/0x10 [cifs] [ 945.291177] smb2_async_writev+0x3e3/0x670 [cifs] [ 945.291759] ? find_held_lock+0x32/0x90 [ 945.292212] ? netfs_advance_write+0xf2/0x310 [ 945.292723] netfs_advance_write+0xf2/0x310 [ 945.293210] netfs_write_folio+0x346/0xcc0 [ 945.293689] ? __pfx__raw_spin_unlock_irq+0x10/0x10 [ 945.294250] netfs_writepages+0x117/0x460 [ 945.294724] do_writepages+0xbe/0x170 [ 945.295152] ? find_held_lock+0x32/0x90 [ 945.295600] ? kvm_sched_clock_read+0x11/0x20 [ 945.296103] __writeback_single_inode+0x56/0x4b0 [ 945.296643] writeback_sb_inodes+0x229/0x550 [ 945.297140] __writeback_inodes_wb+0x4c/0xe0 [ 945.297642] wb_writeback+0x2f1/0x3f0 [ 945.298069] wb_workfn+0x300/0x490 [ 945.298472] process_one_work+0x1fe/0x590 [ 945.298949] worker_thread+0x1ce/0x3c0 [ 945.299397] ? __pfx_worker_thread+0x10/0x10 [ 945.299900] kthr ---truncated--- CVE-2025-40052 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40052.html CVE-2025-40052 https://bugzilla.suse.com/1252851 SUSE Bug 1252851 In the Linux kernel, the following vulnerability has been resolved: vhost: vringh: Fix copy_to_iter return value check The return value of copy_to_iter can't be negative, check whether the copied length is equal to the requested length instead of checking for negative values. CVE-2025-40056 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40056.html CVE-2025-40056 https://bugzilla.suse.com/1252826 SUSE Bug 1252826 In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Disallow dirty tracking if incoherent page walk Dirty page tracking relies on the IOMMU atomically updating the dirty bit in the paging-structure entry. For this operation to succeed, the paging- structure memory must be coherent between the IOMMU and the CPU. In another word, if the iommu page walk is incoherent, dirty page tracking doesn't work. The Intel VT-d specification, Section 3.10 "Snoop Behavior" states: "Remapping hardware encountering the need to atomically update A/EA/D bits in a paging-structure entry that is not snooped will result in a non- recoverable fault." To prevent an IOMMU from being incorrectly configured for dirty page tracking when it is operating in an incoherent mode, mark SSADS as supported only when both ecap_slads and ecap_smpwc are supported. CVE-2025-40058 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40058.html CVE-2025-40058 https://bugzilla.suse.com/1252854 SUSE Bug 1252854 In the Linux kernel, the following vulnerability has been resolved: coresight: trbe: Return NULL pointer for allocation failures When the TRBE driver fails to allocate a buffer, it currently returns the error code "-ENOMEM". However, the caller etm_setup_aux() only checks for a NULL pointer, so it misses the error. As a result, the driver continues and eventually causes a kernel panic. Fix this by returning a NULL pointer from arm_trbe_alloc_buffer() on allocation failures. This allows that the callers can properly handle the failure. CVE-2025-40060 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40060.html CVE-2025-40060 https://bugzilla.suse.com/1252848 SUSE Bug 1252848 In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix race in do_task() when draining When do_task() exhausts its iteration budget (!ret), it sets the state to TASK_STATE_IDLE to reschedule, without a secondary check on the current task->state. This can overwrite the TASK_STATE_DRAINING state set by a concurrent call to rxe_cleanup_task() or rxe_disable_task(). While state changes are protected by a spinlock, both rxe_cleanup_task() and rxe_disable_task() release the lock while waiting for the task to finish draining in the while(!is_done(task)) loop. The race occurs if do_task() hits its iteration limit and acquires the lock in this window. The cleanup logic may then proceed while the task incorrectly reschedules itself, leading to a potential use-after-free. This bug was introduced during the migration from tasklets to workqueues, where the special handling for the draining case was lost. Fix this by restoring the original pre-migration behavior. If the state is TASK_STATE_DRAINING when iterations are exhausted, set cont to 1 to force a new loop iteration. This allows the task to finish its work, so that a subsequent iteration can reach the switch statement and correctly transition the state to TASK_STATE_DRAINED, stopping the task as intended. CVE-2025-40061 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40061.html CVE-2025-40061 https://bugzilla.suse.com/1252849 SUSE Bug 1252849 In the Linux kernel, the following vulnerability has been resolved: crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs When the initialization of qm->debug.acc_diff_reg fails, the probe process does not exit. However, after qm->debug.qm_diff_regs is freed, it is not set to NULL. This can lead to a double free when the remove process attempts to free it again. Therefore, qm->debug.qm_diff_regs should be set to NULL after it is freed. CVE-2025-40062 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40062.html CVE-2025-40062 https://bugzilla.suse.com/1252850 SUSE Bug 1252850 In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: Don't block input queue by waiting MSC Currently gsm_queue() processes incoming frames and when opening a DLC channel it calls gsm_dlci_open() which calls gsm_modem_update(). If basic mode is used it calls gsm_modem_upd_via_msc() and it cannot block the input queue by waiting the response to come into the same input queue. Instead allow sending Modem Status Command without waiting for remote end to respond. Define a new function gsm_modem_send_initial_msc() for this purpose. As MSC is only valid for basic encoding, it does not do anything for advanced or when convergence layer type 2 is used. CVE-2025-40071 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40071.html CVE-2025-40071 https://bugzilla.suse.com/1252797 SUSE Bug 1252797 In the Linux kernel, the following vulnerability has been resolved: bpf: Explicitly check accesses to bpf_sock_addr Syzkaller found a kernel warning on the following sock_addr program: 0: r0 = 0 1: r2 = *(u32 *)(r1 +60) 2: exit which triggers: verifier bug: error during ctx access conversion (0) This is happening because offset 60 in bpf_sock_addr corresponds to an implicit padding of 4 bytes, right after msg_src_ip4. Access to this padding isn't rejected in sock_addr_is_valid_access and it thus later fails to convert the access. This patch fixes it by explicitly checking the various fields of bpf_sock_addr in sock_addr_is_valid_access. I checked the other ctx structures and is_valid_access functions and didn't find any other similar cases. Other cases of (properly handled) padding are covered in new tests in a subsequent patch. CVE-2025-40078 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40078.html CVE-2025-40078 https://bugzilla.suse.com/1252789 SUSE Bug 1252789 In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0xa71/0xb90 fs/hfsplus/unicode.c:186 Read of size 2 at addr ffff8880289ef218 by task syz.6.248/14290 CPU: 0 UID: 0 PID: 14290 Comm: syz.6.248 Not tainted 6.16.4 #1 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1b0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x5f0 mm/kasan/report.c:482 kasan_report+0xca/0x100 mm/kasan/report.c:595 hfsplus_uni2asc+0xa71/0xb90 fs/hfsplus/unicode.c:186 hfsplus_listxattr+0x5b6/0xbd0 fs/hfsplus/xattr.c:738 vfs_listxattr+0xbe/0x140 fs/xattr.c:493 listxattr+0xee/0x190 fs/xattr.c:924 filename_listxattr fs/xattr.c:958 [inline] path_listxattrat+0x143/0x360 fs/xattr.c:988 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcb/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fe0e9fae16d Code: 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fe0eae67f98 EFLAGS: 00000246 ORIG_RAX: 00000000000000c3 RAX: ffffffffffffffda RBX: 00007fe0ea205fa0 RCX: 00007fe0e9fae16d RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000000 RBP: 00007fe0ea0480f0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fe0ea206038 R14: 00007fe0ea205fa0 R15: 00007fe0eae48000 </TASK> Allocated by task 14290: kasan_save_stack+0x24/0x50 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __do_kmalloc_node mm/slub.c:4333 [inline] __kmalloc_noprof+0x219/0x540 mm/slub.c:4345 kmalloc_noprof include/linux/slab.h:909 [inline] hfsplus_find_init+0x95/0x1f0 fs/hfsplus/bfind.c:21 hfsplus_listxattr+0x331/0xbd0 fs/hfsplus/xattr.c:697 vfs_listxattr+0xbe/0x140 fs/xattr.c:493 listxattr+0xee/0x190 fs/xattr.c:924 filename_listxattr fs/xattr.c:958 [inline] path_listxattrat+0x143/0x360 fs/xattr.c:988 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcb/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f When hfsplus_uni2asc is called from hfsplus_listxattr, it actually passes in a struct hfsplus_attr_unistr*. The size of the corresponding structure is different from that of hfsplus_unistr, so the previous fix (94458781aee6) is insufficient. The pointer on the unicode buffer is still going beyond the allocated memory. This patch introduces two warpper functions hfsplus_uni2asc_xattr_str and hfsplus_uni2asc_str to process two unicode buffers, struct hfsplus_attr_unistr* and struct hfsplus_unistr* respectively. When ustrlen value is bigger than the allocated memory size, the ustrlen value is limited to an safe size. CVE-2025-40082 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40082.html CVE-2025-40082 https://bugzilla.suse.com/1252775 SUSE Bug 1252775 In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix NULL pointer deference in try_to_register_card In try_to_register_card(), the return value of usb_ifnum_to_if() is passed directly to usb_interface_claimed() without a NULL check, which will lead to a NULL pointer dereference when creating an invalid USB audio device. Fix this by adding a check to ensure the interface pointer is valid before passing it to usb_interface_claimed(). CVE-2025-40085 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40085.html CVE-2025-40085 https://bugzilla.suse.com/1252873 SUSE Bug 1252873 In the Linux kernel, the following vulnerability has been resolved: NFSD: Define a proc_layoutcommit for the FlexFiles layout type Avoid a crash if a pNFS client should happen to send a LAYOUTCOMMIT operation on a FlexFiles layout. CVE-2025-40087 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40087.html CVE-2025-40087 https://bugzilla.suse.com/1252909 SUSE Bug 1252909 In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds read in hfsplus_strcasecmp() The hfsplus_strcasecmp() logic can trigger the issue: [ 117.317703][ T9855] ================================================================== [ 117.318353][ T9855] BUG: KASAN: slab-out-of-bounds in hfsplus_strcasecmp+0x1bc/0x490 [ 117.318991][ T9855] Read of size 2 at addr ffff88802160f40c by task repro/9855 [ 117.319577][ T9855] [ 117.319773][ T9855] CPU: 0 UID: 0 PID: 9855 Comm: repro Not tainted 6.17.0-rc6 #33 PREEMPT(full) [ 117.319780][ T9855] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 117.319783][ T9855] Call Trace: [ 117.319785][ T9855] <TASK> [ 117.319788][ T9855] dump_stack_lvl+0x1c1/0x2a0 [ 117.319795][ T9855] ? __virt_addr_valid+0x1c8/0x5c0 [ 117.319803][ T9855] ? __pfx_dump_stack_lvl+0x10/0x10 [ 117.319808][ T9855] ? rcu_is_watching+0x15/0xb0 [ 117.319816][ T9855] ? lock_release+0x4b/0x3e0 [ 117.319821][ T9855] ? __kasan_check_byte+0x12/0x40 [ 117.319828][ T9855] ? __virt_addr_valid+0x1c8/0x5c0 [ 117.319835][ T9855] ? __virt_addr_valid+0x4a5/0x5c0 [ 117.319842][ T9855] print_report+0x17e/0x7e0 [ 117.319848][ T9855] ? __virt_addr_valid+0x1c8/0x5c0 [ 117.319855][ T9855] ? __virt_addr_valid+0x4a5/0x5c0 [ 117.319862][ T9855] ? __phys_addr+0xd3/0x180 [ 117.319869][ T9855] ? hfsplus_strcasecmp+0x1bc/0x490 [ 117.319876][ T9855] kasan_report+0x147/0x180 [ 117.319882][ T9855] ? hfsplus_strcasecmp+0x1bc/0x490 [ 117.319891][ T9855] hfsplus_strcasecmp+0x1bc/0x490 [ 117.319900][ T9855] ? __pfx_hfsplus_cat_case_cmp_key+0x10/0x10 [ 117.319906][ T9855] hfs_find_rec_by_key+0xa9/0x1e0 [ 117.319913][ T9855] __hfsplus_brec_find+0x18e/0x470 [ 117.319920][ T9855] ? __pfx_hfsplus_bnode_find+0x10/0x10 [ 117.319926][ T9855] ? __pfx_hfs_find_rec_by_key+0x10/0x10 [ 117.319933][ T9855] ? __pfx___hfsplus_brec_find+0x10/0x10 [ 117.319942][ T9855] hfsplus_brec_find+0x28f/0x510 [ 117.319949][ T9855] ? __pfx_hfs_find_rec_by_key+0x10/0x10 [ 117.319956][ T9855] ? __pfx_hfsplus_brec_find+0x10/0x10 [ 117.319963][ T9855] ? __kmalloc_noprof+0x2a9/0x510 [ 117.319969][ T9855] ? hfsplus_find_init+0x8c/0x1d0 [ 117.319976][ T9855] hfsplus_brec_read+0x2b/0x120 [ 117.319983][ T9855] hfsplus_lookup+0x2aa/0x890 [ 117.319990][ T9855] ? __pfx_hfsplus_lookup+0x10/0x10 [ 117.320003][ T9855] ? d_alloc_parallel+0x2f0/0x15e0 [ 117.320008][ T9855] ? __lock_acquire+0xaec/0xd80 [ 117.320013][ T9855] ? __pfx_d_alloc_parallel+0x10/0x10 [ 117.320019][ T9855] ? __raw_spin_lock_init+0x45/0x100 [ 117.320026][ T9855] ? __init_waitqueue_head+0xa9/0x150 [ 117.320034][ T9855] __lookup_slow+0x297/0x3d0 [ 117.320039][ T9855] ? __pfx___lookup_slow+0x10/0x10 [ 117.320045][ T9855] ? down_read+0x1ad/0x2e0 [ 117.320055][ T9855] lookup_slow+0x53/0x70 [ 117.320065][ T9855] walk_component+0x2f0/0x430 [ 117.320073][ T9855] path_lookupat+0x169/0x440 [ 117.320081][ T9855] filename_lookup+0x212/0x590 [ 117.320089][ T9855] ? __pfx_filename_lookup+0x10/0x10 [ 117.320098][ T9855] ? strncpy_from_user+0x150/0x290 [ 117.320105][ T9855] ? getname_flags+0x1e5/0x540 [ 117.320112][ T9855] user_path_at+0x3a/0x60 [ 117.320117][ T9855] __x64_sys_umount+0xee/0x160 [ 117.320123][ T9855] ? __pfx___x64_sys_umount+0x10/0x10 [ 117.320129][ T9855] ? do_syscall_64+0xb7/0x3a0 [ 117.320135][ T9855] ? entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 117.320141][ T9855] ? entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 117.320145][ T9855] do_syscall_64+0xf3/0x3a0 [ 117.320150][ T9855] ? exc_page_fault+0x9f/0xf0 [ 117.320154][ T9855] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 117.320158][ T9855] RIP: 0033:0x7f7dd7908b07 [ 117.320163][ T9855] Code: 23 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 08 [ 117.320167][ T9855] RSP: 002b:00007ffd5ebd9698 EFLAGS: 00000202 ---truncated--- CVE-2025-40088 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40088.html CVE-2025-40088 https://bugzilla.suse.com/1252904 SUSE Bug 1252904 In the Linux kernel, the following vulnerability has been resolved: ixgbe: fix too early devlink_free() in ixgbe_remove() Since ixgbe_adapter is embedded in devlink, calling devlink_free() prematurely in the ixgbe_remove() path can lead to UAF. Move devlink_free() to the end. KASAN report: BUG: KASAN: use-after-free in ixgbe_reset_interrupt_capability+0x140/0x180 [ixgbe] Read of size 8 at addr ffff0000adf813e0 by task bash/2095 CPU: 1 UID: 0 PID: 2095 Comm: bash Tainted: G S 6.17.0-rc2-tnguy.net-queue+ #1 PREEMPT(full) [...] Call trace: show_stack+0x30/0x90 (C) dump_stack_lvl+0x9c/0xd0 print_address_description.constprop.0+0x90/0x310 print_report+0x104/0x1f0 kasan_report+0x88/0x180 __asan_report_load8_noabort+0x20/0x30 ixgbe_reset_interrupt_capability+0x140/0x180 [ixgbe] ixgbe_clear_interrupt_scheme+0xf8/0x130 [ixgbe] ixgbe_remove+0x2d0/0x8c0 [ixgbe] pci_device_remove+0xa0/0x220 device_remove+0xb8/0x170 device_release_driver_internal+0x318/0x490 device_driver_detach+0x40/0x68 unbind_store+0xec/0x118 drv_attr_store+0x64/0xb8 sysfs_kf_write+0xcc/0x138 kernfs_fop_write_iter+0x294/0x440 new_sync_write+0x1fc/0x588 vfs_write+0x480/0x6a0 ksys_write+0xf0/0x1e0 __arm64_sys_write+0x70/0xc0 invoke_syscall.constprop.0+0xcc/0x280 el0_svc_common.constprop.0+0xa8/0x248 do_el0_svc+0x44/0x68 el0_svc+0x54/0x160 el0t_64_sync_handler+0xa0/0xe8 el0t_64_sync+0x1b0/0x1b8 CVE-2025-40091 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40091.html CVE-2025-40091 https://bugzilla.suse.com/1252915 SUSE Bug 1252915 In the Linux kernel, the following vulnerability has been resolved: drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies When adding dependencies with drm_sched_job_add_dependency(), that function consumes the fence reference both on success and failure, so in the latter case the dma_fence_put() on the error path (xarray failed to expand) is a double free. Interestingly this bug appears to have been present ever since commit ebd5f74255b9 ("drm/sched: Add dependency tracking"), since the code back then looked like this: drm_sched_job_add_implicit_dependencies(): ... for (i = 0; i < fence_count; i++) { ret = drm_sched_job_add_dependency(job, fences[i]); if (ret) break; } for (; i < fence_count; i++) dma_fence_put(fences[i]); Which means for the failing 'i' the dma_fence_put was already a double free. Possibly there were no users at that time, or the test cases were insufficient to hit it. The bug was then only noticed and fixed after commit 9c2ba265352a ("drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2") landed, with its fixup of commit 4eaf02d6076c ("drm/scheduler: fix drm_sched_job_add_implicit_dependencies"). At that point it was a slightly different flavour of a double free, which commit 963d0b356935 ("drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder") noticed and attempted to fix. But it only moved the double free from happening inside the drm_sched_job_add_dependency(), when releasing the reference not yet obtained, to the caller, when releasing the reference already released by the former in the failure case. As such it is not easy to identify the right target for the fixes tag so lets keep it simple and just continue the chain. While fixing we also improve the comment and explain the reason for taking the reference and not dropping it. CVE-2025-40096 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40096.html CVE-2025-40096 https://bugzilla.suse.com/1252902 SUSE Bug 1252902 In the Linux kernel, the following vulnerability has been resolved: btrfs: do not assert we found block group item when creating free space tree Currently, when building a free space tree at populate_free_space_tree(), if we are not using the block group tree feature, we always expect to find block group items (either extent items or a block group item with key type BTRFS_BLOCK_GROUP_ITEM_KEY) when we search the extent tree with btrfs_search_slot_for_read(), so we assert that we found an item. However this expectation is wrong since we can have a new block group created in the current transaction which is still empty and for which we still have not added the block group's item to the extent tree, in which case we do not have any items in the extent tree associated to the block group. The insertion of a new block group's block group item in the extent tree happens at btrfs_create_pending_block_groups() when it calls the helper insert_block_group_item(). This typically is done when a transaction handle is released, committed or when running delayed refs (either as part of a transaction commit or when serving tickets for space reservation if we are low on free space). So remove the assertion at populate_free_space_tree() even when the block group tree feature is not enabled and update the comment to mention this case. Syzbot reported this with the following stack trace: BTRFS info (device loop3 state M): rebuilding free space tree assertion failed: ret == 0 :: 0, in fs/btrfs/free-space-tree.c:1115 ------------[ cut here ]------------ kernel BUG at fs/btrfs/free-space-tree.c:1115! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 1 UID: 0 PID: 6352 Comm: syz.3.25 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 RIP: 0010:populate_free_space_tree+0x700/0x710 fs/btrfs/free-space-tree.c:1115 Code: ff ff e8 d3 (...) RSP: 0018:ffffc9000430f780 EFLAGS: 00010246 RAX: 0000000000000043 RBX: ffff88805b709630 RCX: fea61d0e2e79d000 RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000 RBP: ffffc9000430f8b0 R08: ffffc9000430f4a7 R09: 1ffff92000861e94 R10: dffffc0000000000 R11: fffff52000861e95 R12: 0000000000000001 R13: 1ffff92000861f00 R14: dffffc0000000000 R15: 0000000000000000 FS: 00007f424d9fe6c0(0000) GS:ffff888125afc000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fd78ad212c0 CR3: 0000000076d68000 CR4: 00000000003526f0 Call Trace: <TASK> btrfs_rebuild_free_space_tree+0x1ba/0x6d0 fs/btrfs/free-space-tree.c:1364 btrfs_start_pre_rw_mount+0x128f/0x1bf0 fs/btrfs/disk-io.c:3062 btrfs_remount_rw fs/btrfs/super.c:1334 [inline] btrfs_reconfigure+0xaed/0x2160 fs/btrfs/super.c:1559 reconfigure_super+0x227/0x890 fs/super.c:1076 do_remount fs/namespace.c:3279 [inline] path_mount+0xd1a/0xfe0 fs/namespace.c:4027 do_mount fs/namespace.c:4048 [inline] __do_sys_mount fs/namespace.c:4236 [inline] __se_sys_mount+0x313/0x410 fs/namespace.c:4213 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f424e39066a Code: d8 64 89 02 (...) RSP: 002b:00007f424d9fde68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007f424d9fdef0 RCX: 00007f424e39066a RDX: 0000200000000180 RSI: 0000200000000380 RDI: 0000000000000000 RBP: 0000200000000180 R08: 00007f424d9fdef0 R09: 0000000000000020 R10: 0000000000000020 R11: 0000000000000246 R12: 0000200000000380 R13: 00007f424d9fdeb0 R14: 0000000000000000 R15: 00002000000002c0 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- CVE-2025-40100 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.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/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40100.html CVE-2025-40100 https://bugzilla.suse.com/1252918 SUSE Bug 1252918 In the Linux kernel, the following vulnerability has been resolved: ixgbevf: fix mailbox API compatibility by negotiating supported features There was backward compatibility in the terms of mailbox API. Various drivers from various OSes supporting 10G adapters from Intel portfolio could easily negotiate mailbox API. This convention has been broken since introducing API 1.4. Commit 0062e7cc955e ("ixgbevf: add VF IPsec offload code") added support for IPSec which is specific only for the kernel ixgbe driver. None of the rest of the Intel 10G PF/VF drivers supports it. And actually lack of support was not included in the IPSec implementation - there were no such code paths. No possibility to negotiate support for the feature was introduced along with introduction of the feature itself. Commit 339f28964147 ("ixgbevf: Add support for new mailbox communication between PF and VF") increasing API version to 1.5 did the same - it introduced code supported specifically by the PF ESX driver. It altered API version for the VF driver in the same time not touching the version defined for the PF ixgbe driver. It led to additional discrepancies, as the code provided within API 1.6 cannot be supported for Linux ixgbe driver as it causes crashes. The issue was noticed some time ago and mitigated by Jake within the commit d0725312adf5 ("ixgbevf: stop attempting IPSEC offload on Mailbox API 1.5"). As a result we have regression for IPsec support and after increasing API to version 1.6 ixgbevf driver stopped to support ESX MBX. To fix this mess add new mailbox op asking PF driver about supported features. Basing on a response determine whether to set support for IPSec and ESX-specific enhanced mailbox. New mailbox op, for compatibility purposes, must be added within new API revision, as API version of OOT PF & VF drivers is already increased to 1.6 and doesn't incorporate features negotiate op. Features negotiation mechanism gives possibility to be extended with new features when needed in the future. CVE-2025-40104 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_22-rt-1-150700.1.3.1 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.22.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.22.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/ https://www.suse.com/security/cve/CVE-2025-40104.html CVE-2025-40104 https://bugzilla.suse.com/1252921 SUSE Bug 1252921