Security update for the Linux Kernel SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2026:0587-1 Final 1 1 2026-02-20T10:04:28Z current 2026-02-20T10:04:28Z 2026-02-20T10:04:28Z 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-2023-54013: interconnect: Fix locking for runpm vs reclaim (bsc#1256280). - CVE-2025-39880: libceph: fix invalid accesses to ceph_connection_v1_info (bsc#1250388). - CVE-2025-40238: net/mlx5: Fix IPsec cleanup over MPV device (bsc#1254871). - CVE-2025-40254: net: openvswitch: remove never-working support for setting nsh fields (bsc#1254852). - CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842). - CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845). - CVE-2025-40261: nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839). - CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835). - CVE-2025-40328: smb: client: fix potential UAF in smb2_close_cached_fid() (bsc#1254624). - CVE-2025-40350: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ (bsc#1255260). - CVE-2025-40355: sysfs: check visibility before changing group attribute ownership (bsc#1255261). - CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102). - CVE-2025-68171: x86/fpu: Ensure XFD state on signal delivery (bsc#1255255). - CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327). - CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266). - CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269). - CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241). - CVE-2025-68215: ice: fix PTP cleanup on driver removal in error path (bsc#1255226). - CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216). - CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157). - CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268). - CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164). - CVE-2025-68284: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() (bsc#1255377). - CVE-2025-68285: libceph: fix potential use-after-free in have_mon_and_osd_map() (bsc#1255401). - CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128). - CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403). - CVE-2025-68301: net: atlantic: fix fragment overflow handling in RX path (bsc#1255120). - CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172). - CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417). - CVE-2025-68327: usb: renesas_usbhs: Fix synchronous external abort on unbind (bsc#1255488). - CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482). - CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544). - CVE-2025-68363: bpf: Check skb->transport_header is set in bpf_skb_check_mtu (bsc#1255552). - CVE-2025-68365: fs/ntfs3: Initialize allocated memory before use (bsc#1255548). - CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622). - CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547). - CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537). - CVE-2025-68379: RDMA/rxe: Fix null deref on srq->rq.queue after resize failure (bsc#1255695). - CVE-2025-68727: ntfs3: Fix uninit buffer allocated by __getname() (bsc#1255568). - CVE-2025-68728: ntfs3: fix uninit memory after failed mi_read in mi_format_new (bsc#1255539). - CVE-2025-68733: smack: fix bug: unprivileged task can create labels (bsc#1255615). - CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930). - CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579). - CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584). - CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582). - CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665). - CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659). - CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638). - CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688). - CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689). - CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646). - CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653). - CVE-2025-68803: nfsd: set security label during create operations (bsc#1256770). - CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641). - CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651). - CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680). - CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674). - CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754). - CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654). - CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645). - CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613). - CVE-2025-71080: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT (bsc#1256608). - CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622). - CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623). - CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628). - CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630). - CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612). - CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773). - CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777). - CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597). - CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605). - CVE-2025-71096: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (bsc#1256606). - CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607). - CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591). - CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726). - CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744). - CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779). - CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757). - CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733). - CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761). - CVE-2025-71137: octeontx2-pf: fix 'UBSAN: shift-out-of-bounds error' (bsc#1256760). - CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164). - CVE-2025-71156: gve: defer interrupt enabling until NAPI registration (bsc#1257167). - CVE-2025-71157: RDMA/core: always drop device refcount in ib_del_sub_device_and_put() (bsc#1257168). - CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035). - CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053). - CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217). - CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221). - CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220). - CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218). - CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180). - CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv. - CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236). - CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234). - CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232). - CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245). - CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207). The following non security issues were fixed: - ALSA: ctxfi: Fix potential OOB access in audio mixer handling (stable-fixes). - ALSA: scarlett2: Fix buffer overflow in config retrieval (git-fixes). - ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (git-fixes). - ALSA: usb-audio: Update for native DSD support quirks (stable-fixes). - ALSA: usb: Increase volume range that triggers a warning (git-fixes). - ASoC: Intel: sof_es8336: fix headphone GPIO logic inversion (git-fixes). - ASoC: amd: yc: Add quirk for Honor MagicBook X16 2025 (stable-fixes). - ASoC: codecs: wsa881x: Drop unused version readout (stable-fixes). - ASoC: codecs: wsa881x: fix unnecessary initialisation (git-fixes). - ASoC: codecs: wsa883x: fix unnecessary initialisation (git-fixes). - ASoC: codecs: wsa884x: fix codec initialisation (git-fixes). - ASoC: fsl: imx-card: Do not force slot width to sample width (git-fixes). - ASoC: fsl_sai: Add missing registers to cache default (stable-fixes). - ASoC: tlv320adcx140: fix null pointer (git-fixes). - ASoC: tlv320adcx140: fix word length (git-fixes). - Bluetooth: MGMT: Fix memory leak in set_ssp_complete (git-fixes). - Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work (git-fixes). - HID: usbhid: paper over wrong bNumDescriptor field (stable-fixes). - Input: i8042 - add quirk for ASUS Zenbook UX425QA_UM425QA (stable-fixes). - Input: i8042 - add quirks for MECHREVO Wujie 15X Pro (stable-fixes). - NFS: Fix up the automount fs_context to use the correct cred (git-fixes). - NFSD/blocklayout: Fix minlength check in proc_layoutget (git-fixes). - NFSD: Fix permission check for read access to executable-only files (git-fixes). - NFSD: use correct reservation type in nfsd4_scsi_fence_client (git-fixes). - NFSv4: ensure the open stateid seqid doesn't go backwards (git-fixes). - RDMA/mana_ib: Access remote atomic for MRs (git-fixes). - RDMA/mana_ib: Add device statistics support (git-fixes). - RDMA/mana_ib: Add port statistics support (git-fixes). - RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes). - RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes). - RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes). - RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes). - RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes). - RDMA/mana_ib: Extend modify QP (git-fixes). - RDMA/mana_ib: Fix error code in probe() (git-fixes). - RDMA/mana_ib: Fix integer overflow during queue creation (git-fixes). - RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690). - RDMA/mana_ib: Implement DMABUF MR support (git-fixes). - RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes). - RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes). - RDMA/mana_ib: UD/GSI work requests (git-fixes). - RDMA/mana_ib: Use safer allocation function() (git-fixes). - RDMA/mana_ib: add additional port counters (git-fixes). - RDMA/mana_ib: add support of multiple ports (git-fixes). - RDMA/mana_ib: check cqe length for kernel CQs (git-fixes). - RDMA/mana_ib: create kernel-level CQs (git-fixes). - RDMA/mana_ib: create/destroy AH (git-fixes). - RDMA/mana_ib: extend mana QP table (git-fixes). - RDMA/mana_ib: helpers to allocate kernel queues (git-fixes). - RDMA/mana_ib: implement get_dma_mr (git-fixes). - RDMA/mana_ib: implement req_notify_cq (git-fixes). - RDMA/mana_ib: indicate CM support (git-fixes). - RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes). - RDMA/mana_ib: request error CQEs when supported (git-fixes). - RDMA/mana_ib: support of the zero based MRs (git-fixes). - RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes). - Revert 'nfc/nci: Add the inconsistency check between the input data length and count' (git-fixes). - USB: OHCI/UHCI: Add soft dependencies on ehci_platform (stable-fixes). - USB: serial: ftdi_sio: add support for PICAXE AXE027 cable (stable-fixes). - USB: serial: option: add Telit LE910 MBIM composition (stable-fixes). - ata: libata: Add cpr_log to ata_dev_print_features() early return (git-fixes). - bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603). - bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569). - bs-upload-kernel: Fix cve branch uploads. - btrfs: do not strictly require dirty metadata threshold for metadata writepages (stable-fixes). - can: ctucanfd: fix SSP_SRC in cases when bit-rate is higher than 1 MBit (git-fixes). - can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak (git-fixes). - can: etas_es58x: allow partial RX URB allocation to succeed (git-fixes). - can: gs_usb: gs_usb_receive_bulk_callback(): fix error message (git-fixes). - can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error (git-fixes). - can: j1939: make j1939_session_activate() fail if device is no longer registered (stable-fixes). - can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak (git-fixes). - can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak (git-fixes). - can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak (git-fixes). - cifs: Fix copy offload to flush destination region (bsc#1252511). - cifs: Fix flushing, invalidation and file size with copy_file_range() (bsc#1252511). - cifs: add new field to track the last access time of cfid (git-fixes). - cifs: after disabling multichannel, mark tcon for reconnect (git-fixes). - cifs: avoid redundant calls to disable multichannel (git-fixes). - cifs: cifs_pick_channel should try selecting active channels (git-fixes). - cifs: deal with the channel loading lag while picking channels (git-fixes). - cifs: dns resolution is needed only for primary channel (git-fixes). - cifs: do not disable interface polling on failure (git-fixes). - cifs: do not search for channel if server is terminating (git-fixes). - cifs: fix a pending undercount of srv_count (git-fixes). - cifs: fix lock ordering while disabling multichannel (git-fixes). - cifs: fix stray unlock in cifs_chan_skip_or_disable (git-fixes). - cifs: fix use after free for iface while disabling secondary channels (git-fixes). - cifs: handle servers that still advertise multichannel after disabling (git-fixes). - cifs: handle when server starts supporting multichannel (git-fixes). - cifs: handle when server stops supporting multichannel (git-fixes). - cifs: make cifs_chan_update_iface() a void function (git-fixes). - cifs: make sure server interfaces are requested only for SMB3+ (git-fixes). - cifs: make sure that channel scaling is done only once (git-fixes). - cifs: reconnect worker should take reference on server struct unconditionally (git-fixes). - cifs: reset connections for all channels when reconnect requested (git-fixes). - cifs: reset iface weights when we cannot find a candidate (git-fixes). - cifs: serialize other channels when query server interfaces is pending (git-fixes). - cifs: update dstaddr whenever channel iface is updated (git-fixes). - comedi: Fix getting range information for subdevices 16 to 255 (git-fixes). - comedi: dmm32at: serialize use of paged registers (git-fixes). - comedi: fix divide-by-zero in comedi_buf_munge() (stable-fixes). - cpuset: fix warning when disabling remote partition (bsc#1256794). - crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec (git-fixes). - dmaengine: apple-admac: Add 'apple,t8103-admac' compatible (git-fixes). - dmaengine: at_hdmac: fix device leak on of_dma_xlate() (git-fixes). - dmaengine: bcm-sba-raid: fix device leak on probe (git-fixes). - dmaengine: dw: dmamux: fix OF node leak on route allocation failure (git-fixes). - dmaengine: idxd: fix device leaks on compat bind and unbind (git-fixes). - dmaengine: lpc18xx-dmamux: fix device leak on route allocation (git-fixes). - dmaengine: omap-dma: fix dma_pool resource leak in error paths (git-fixes). - dmaengine: qcom: gpi: Fix memory leak in gpi_peripheral_config() (git-fixes). - dmaengine: sh: rz-dmac: Fix rz_dmac_terminate_all() (git-fixes). - dmaengine: tegra-adma: Fix use-after-free (git-fixes). - dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation (git-fixes). - dmaengine: ti: dma-crossbar: fix device leak on dra7x route allocation (git-fixes). - dmaengine: ti: k3-udma: fix device leak on udma lookup (git-fixes). - dmaengine: xilinx: xdma: Fix regmap max_register (git-fixes). - dmaengine: xilinx_dma: Fix uninitialized addr_width when 'xlnx,addrwidth' property is missing (git-fixes). - dpll: Prevent duplicate registrations (git-fixes). - dpll: fix device-id-get and pin-id-get to return errors properly (git-fixes). - dpll: fix return value check for kmemdup (git-fixes). - dpll: indent DPLL option type by a tab (git-fixes). - dpll: spec: add missing module-name and clock-id to pin-get reply (git-fixes). - drm/amd/display: Apply e4479aecf658 to dml (stable-fixes). - drm/amd/display: Bump the HDMI clock to 340MHz (stable-fixes). - drm/amd/display: Fix DP no audio issue (stable-fixes). - drm/amd/display: Initialise backlight level values from hw (git-fixes). - drm/amd/display: Respect user's CONFIG_FRAME_WARN more for dml files (stable-fixes). - drm/amd/display: shrink struct members (stable-fixes). - drm/amd/pm: Don't clear SI SMC table when setting power limit (git-fixes). - drm/amd/pm: Workaround SI powertune issue on Radeon 430 (v2) (git-fixes). - drm/amd/pm: fix race in power state check before mutex lock (git-fixes). - drm/amd/pm: fix smu overdrive data type wrong issue on smu 14.0.2 (git-fixes). - drm/amd: Clean up kfd node on surprise disconnect (stable-fixes). - drm/amdgpu: Fix cond_exec handling in amdgpu_ib_schedule() (git-fixes). - drm/amdgpu: Fix query for VPE block_type and ip_count (stable-fixes). - drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove (git-fixes). - drm/amdgpu: remove frame cntl for gfx v12 (stable-fixes). - drm/amdkfd: Fix improper NULL termination of queue restore SMI event string (stable-fixes). - drm/amdkfd: fix a memory leak in device_queue_manager_init() (git-fixes). - drm/imagination: Wait for FW trace update command completion (git-fixes). - drm/imx/tve: fix probe device leak (git-fixes). - drm/msm/a6xx: fix bogus hwcg register updates (git-fixes). - drm/nouveau/disp/nv50-: Set lock_core in curs507a_prepare (git-fixes). - drm/nouveau/disp: Set drm_mode_config_funcs.atomic_(check|commit) (stable-fixes). - drm/nouveau: add missing DCB connector types (git-fixes). - drm/nouveau: implement missing DCB connector types; gracefully handle unknown connectors (git-fixes). - drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel (git-fixes). - drm/radeon: Remove __counted_by from ClockInfoArray.clockInfo[] (stable-fixes). - drm/vmwgfx: Fix an error return check in vmw_compat_shader_add() (git-fixes). - drm/vmwgfx: Merge vmw_bo_release and vmw_bo_free functions (git-fixes). - exfat: check return value of sb_min_blocksize in exfat_read_boot_sector (git-fixes). - exfat: fix remount failure in different process environments (git-fixes). - gpio: omap: do not register driver in probe() (git-fixes). - gpio: pca953x: Add support for level-triggered interrupts (stable-fixes). - gpio: pca953x: Utilise dev_err_probe() where it makes sense (stable-fixes). - gpio: pca953x: Utilise temporary variable for struct device (stable-fixes). - gpio: pca953x: fix wrong error probe return value (git-fixes). - gpio: pca953x: handle short interrupt pulses on PCAL devices (git-fixes). - gpio: rockchip: Stop calling pinctrl for set_direction (git-fixes). - ice: use netif_get_num_default_rss_queues() (bsc#1247712). - iio: accel: iis328dq: fix gain values (git-fixes). - iio: adc: ad7280a: handle spi_setup() errors in probe() (git-fixes). - iio: adc: ad9467: fix ad9434 vref mask (git-fixes). - iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver (git-fixes). - iio: dac: ad5686: add AD5695R to ad5686_chip_info_tbl (git-fixes). - iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection (git-fixes). - intel_th: fix device leak on output open() (git-fixes). - leds: led-class: Only Add LED to leds_list when it is fully ready (git-fixes). - lib/crypto: aes: Fix missing MMU protection for AES S-box (git-fixes). - mISDN: annotate data-race around dev->work (git-fixes). - mei: me: add nova lake point S DID (stable-fixes). - mei: me: add wildcat lake P DID (stable-fixes). - mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1253087 bsc#1254447). - mmc: rtsx_pci_sdmmc: implement sdmmc_card_busy function (git-fixes). - mmc: sdhci-of-dwcmshc: Prevent illegal clock reduction in HS200/HS400 mode (git-fixes). - net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts (git-fixes). - net: hv_netvsc: reject RSS hash key programming without RX indirection table (bsc#1257473). - net: mana: Add metadata support for xdp mode (git-fixes). - net: mana: Add standard counter rx_missed_errors (git-fixes). - net: mana: Add support for auxiliary device servicing events (git-fixes). - net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690). - net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes). - net: mana: Fix use-after-free in reset service rescan path (git-fixes). - net: mana: Fix warnings for missing export.h header inclusion (git-fixes). - net: mana: Handle Reset Request from MANA NIC (git-fixes). - net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes). - net: mana: Handle hardware recovery events when probing the device (git-fixes). - net: mana: Handle unsupported HWC commands (git-fixes). - net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes). - net: mana: Probe rdma device in mana driver (git-fixes). - net: mana: Reduce waiting time if HWC not responding (git-fixes). - net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes). - net: tcp: allow zero-window ACK update the window (bsc#1254767). - net: usb: dm9601: remove broken SR9700 support (git-fixes). - net: wwan: t7xx: fix potential skb->frags overflow in RX path (git-fixes). - nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame() (git-fixes). - nfc: nci: Fix race between rfkill and nci_unregister_device() (git-fixes). - nfsd: Drop the client reference in client_states_open() (git-fixes). - nvme: nvme-fc: move tagset removal to nvme_fc_delete_ctrl() (git-fixes). - nvmet-auth: update sc_c in host response (git-fixes). - nvmet-auth: update sc_c in target host hash calculation (git-fixes). - of: fix reference count leak in of_alias_scan() (git-fixes). - of: platform: Use default match table for /firmware (git-fixes). - phy: freescale: imx8m-pcie: assert phy reset during power on (stable-fixes). - phy: rockchip: inno-usb2: fix communication disruption in gadget mode (git-fixes). - phy: rockchip: inno-usb2: fix disconnection in gadget mode (git-fixes). - phy: stm32-usphyc: Fix off by one in probe() (git-fixes). - phy: tegra: xusb: Explicitly configure HS_DISCON_LEVEL to 0x7 (git-fixes). - platform/x86/amd: Fix memory leak in wbrf_record() (git-fixes). - platform/x86: hp-bioscfg: Fix automatic module loading (git-fixes). - platform/x86: hp-bioscfg: Fix kernel panic in GET_INSTANCE_ID macro (git-fixes). - platform/x86: hp-bioscfg: Fix kobject warnings for empty attribute names (git-fixes). - pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() (git-fixes). - powercap: fix race condition in register_control_type() (stable-fixes). - powercap: fix sscanf() error return value handling (stable-fixes). - powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199). - regmap: Fix race condition in hwspinlock irqsave routine (git-fixes). - sched/rt: Skip group schedulable check with rt_group_sched=0 (bsc#1256568). - sched: Increase sched_tick_remote timeout (bsc#1254510). - scripts/python/git_sort/git_sort.yaml: add cifs for-next repository. - scripts: obsapi: Support URL trailing / in oscrc. - scripts: teaapi: Add paging. - scripts: uploader: Fix no change condition for _maintainership.json. - scripts: uploader: Handle missing upstream in is_pr_open. - scrits: teaapi: Add list_repos. - scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256861). - scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256861). - scsi: qla2xxx: Add Speed in SFP print information (bsc#1256863). - scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256863). - scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256863). - scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256863). - scsi: qla2xxx: Allow recovery for tape devices (bsc#1256863). - scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256863). - scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256863). - scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256863). - scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256863). - scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256863). - scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256863). - scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256863). - scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296). - selftests/bpf: Fix flaky bpf_cookie selftest (git-fixes). - selftests: net: fib-onlink-tests: Convert to use namespaces by default (bsc#1255346). - serial: 8250_pci: Fix broken RS485 for F81504/508/512 (git-fixes). - slimbus: core: fix OF node leak on registration failure (git-fixes). - slimbus: core: fix device reference leak on report present (git-fixes). - slimbus: core: fix of_slim_get_device() kernel doc (git-fixes). - slimbus: core: fix runtime PM imbalance on report present (git-fixes). - smb3: add missing null server pointer check (git-fixes). - smb: change return type of cached_dir_lease_break() to bool (git-fixes). - smb: client: ensure open_cached_dir_by_dentry() only returns valid cfid (git-fixes). - smb: client: fix cifs_pick_channel when channel needs reconnect (git-fixes). - smb: client: fix warning when reconnecting channel (git-fixes). - smb: client: introduce close_cached_dir_locked() (git-fixes). - smb: client: remove unused fid_lock (git-fixes). - smb: client: short-circuit in open_cached_dir_by_dentry() if !dentry (git-fixes). - smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748 bsc#1257154). - smb: client: update cfid->last_access_time in open_cached_dir_by_dentry() (git-fixes). - smb: improve directory cache reuse for readdir operations (bsc#1252712). - spi: spi-sprd-adi: Fix double free in probe error path (git-fixes). - spi: sprd-adi: switch to use spi_alloc_host() (stable-fixes). - spi: sprd: adi: Use devm_register_restart_handler() (stable-fixes). - svcrdma: return 0 on success from svc_rdma_copy_inline_range (git-fixes). - uacce: ensure safe queue release with state management (git-fixes). - uacce: fix cdev handling in the cleanup path (git-fixes). - uacce: fix isolate sysfs check condition (git-fixes). - uacce: implement mremap in uacce_vm_ops to return -EPERM (git-fixes). - usb: core: add USB_QUIRK_NO_BOS for devices that hang on BOS descriptor (stable-fixes). - usb: dwc3: Check for USB4 IP_NAME (stable-fixes). - usbnet: limit max_mtu based on device's hard_mtu (git-fixes). - w1: fix redundant counter decrement in w1_attach_slave_device() (git-fixes). - w1: therm: Fix off-by-one buffer overflow in alarms_store (git-fixes). - wifi: ath10k: fix dma_free_coherent() pointer (git-fixes). - wifi: ath12k: fix dma_free_coherent() pointer (git-fixes). - wifi: mac80211: correctly decode TTLM with default link map (git-fixes). - wifi: mac80211: don't perform DA check on S1G beacon (git-fixes). - wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes). - wifi: rsi: Fix memory corruption due to not set vif driver data size (git-fixes). - x86/microcode/AMD: Add TSA microcode SHAs (bsc#1256528). - x86/microcode/AMD: Add Zen5 model 0x44, stepping 0x1 minrev (bsc#1256528). - x86/microcode/AMD: Add more known models to entry sign checking (bsc#1256528). - x86/microcode/AMD: Add some forgotten models to the SHA check (bsc#1256528). - x86/microcode/AMD: Clean the cache if update did not load microcode (bsc#1256528). - x86/microcode/AMD: Extend the SHA check to Zen5, block loading of any unreleased standalone Zen5 microcode patches (bsc#1256528). - x86/microcode/AMD: Fix Entrysign revision check for Zen5/Strix Halo (bsc#1256528). - x86/microcode/AMD: Fix __apply_microcode_amd()'s return value (bsc#1256528). - x86/microcode/AMD: Limit Entrysign signature checking to known generations (bsc#1256528). - x86/microcode/AMD: Load only SHA256-checksummed patches (bsc#1256528). - x86/microcode/AMD: Use sha256() instead of init/update/final (bsc#1256528). - x86/microcode: Fix Entrysign revision check for Zen1/Naples (bsc#1256528). - x86: make page fault handling disable interrupts properly (git-fixes). The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-2026-587,SUSE-SLE-Module-Live-Patching-15-SP7-2026-587,SUSE-SLE-Module-RT-15-SP7-2026-587 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ Link for SUSE-SU-2026:0587-1 https://lists.suse.com/pipermail/sle-security-updates/2026-February/024356.html E-Mail link for SUSE-SU-2026:0587-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1205462 SUSE Bug 1205462 https://bugzilla.suse.com/1214285 SUSE Bug 1214285 https://bugzilla.suse.com/1215199 SUSE Bug 1215199 https://bugzilla.suse.com/1223800 SUSE Bug 1223800 https://bugzilla.suse.com/1228490 SUSE Bug 1228490 https://bugzilla.suse.com/1233563 SUSE Bug 1233563 https://bugzilla.suse.com/1234842 SUSE Bug 1234842 https://bugzilla.suse.com/1235566 SUSE Bug 1235566 https://bugzilla.suse.com/1241437 SUSE Bug 1241437 https://bugzilla.suse.com/1242505 SUSE Bug 1242505 https://bugzilla.suse.com/1242909 SUSE Bug 1242909 https://bugzilla.suse.com/1243662 SUSE Bug 1243662 https://bugzilla.suse.com/1243677 SUSE Bug 1243677 https://bugzilla.suse.com/1243678 SUSE Bug 1243678 https://bugzilla.suse.com/1245538 SUSE Bug 1245538 https://bugzilla.suse.com/1246022 SUSE Bug 1246022 https://bugzilla.suse.com/1246184 SUSE Bug 1246184 https://bugzilla.suse.com/1246447 SUSE Bug 1246447 https://bugzilla.suse.com/1247030 SUSE Bug 1247030 https://bugzilla.suse.com/1247712 SUSE Bug 1247712 https://bugzilla.suse.com/1248211 SUSE Bug 1248211 https://bugzilla.suse.com/1249307 SUSE Bug 1249307 https://bugzilla.suse.com/1249904 SUSE Bug 1249904 https://bugzilla.suse.com/1250032 SUSE Bug 1250032 https://bugzilla.suse.com/1250082 SUSE Bug 1250082 https://bugzilla.suse.com/1250388 SUSE Bug 1250388 https://bugzilla.suse.com/1250705 SUSE Bug 1250705 https://bugzilla.suse.com/1250748 SUSE Bug 1250748 https://bugzilla.suse.com/1252511 SUSE Bug 1252511 https://bugzilla.suse.com/1252712 SUSE Bug 1252712 https://bugzilla.suse.com/1252891 SUSE Bug 1252891 https://bugzilla.suse.com/1252900 SUSE Bug 1252900 https://bugzilla.suse.com/1253087 SUSE Bug 1253087 https://bugzilla.suse.com/1253330 SUSE Bug 1253330 https://bugzilla.suse.com/1253340 SUSE Bug 1253340 https://bugzilla.suse.com/1253348 SUSE Bug 1253348 https://bugzilla.suse.com/1253433 SUSE Bug 1253433 https://bugzilla.suse.com/1253443 SUSE Bug 1253443 https://bugzilla.suse.com/1253451 SUSE Bug 1253451 https://bugzilla.suse.com/1253471 SUSE Bug 1253471 https://bugzilla.suse.com/1253739 SUSE Bug 1253739 https://bugzilla.suse.com/1254244 SUSE Bug 1254244 https://bugzilla.suse.com/1254447 SUSE Bug 1254447 https://bugzilla.suse.com/1254465 SUSE Bug 1254465 https://bugzilla.suse.com/1254510 SUSE Bug 1254510 https://bugzilla.suse.com/1254624 SUSE Bug 1254624 https://bugzilla.suse.com/1254767 SUSE Bug 1254767 https://bugzilla.suse.com/1254835 SUSE Bug 1254835 https://bugzilla.suse.com/1254839 SUSE Bug 1254839 https://bugzilla.suse.com/1254842 SUSE Bug 1254842 https://bugzilla.suse.com/1254845 SUSE Bug 1254845 https://bugzilla.suse.com/1254852 SUSE Bug 1254852 https://bugzilla.suse.com/1254871 SUSE Bug 1254871 https://bugzilla.suse.com/1255102 SUSE Bug 1255102 https://bugzilla.suse.com/1255120 SUSE Bug 1255120 https://bugzilla.suse.com/1255128 SUSE Bug 1255128 https://bugzilla.suse.com/1255138 SUSE Bug 1255138 https://bugzilla.suse.com/1255140 SUSE Bug 1255140 https://bugzilla.suse.com/1255157 SUSE Bug 1255157 https://bugzilla.suse.com/1255164 SUSE Bug 1255164 https://bugzilla.suse.com/1255172 SUSE Bug 1255172 https://bugzilla.suse.com/1255216 SUSE Bug 1255216 https://bugzilla.suse.com/1255226 SUSE Bug 1255226 https://bugzilla.suse.com/1255241 SUSE Bug 1255241 https://bugzilla.suse.com/1255255 SUSE Bug 1255255 https://bugzilla.suse.com/1255260 SUSE Bug 1255260 https://bugzilla.suse.com/1255261 SUSE Bug 1255261 https://bugzilla.suse.com/1255266 SUSE Bug 1255266 https://bugzilla.suse.com/1255268 SUSE Bug 1255268 https://bugzilla.suse.com/1255269 SUSE Bug 1255269 https://bugzilla.suse.com/1255327 SUSE Bug 1255327 https://bugzilla.suse.com/1255346 SUSE Bug 1255346 https://bugzilla.suse.com/1255377 SUSE Bug 1255377 https://bugzilla.suse.com/1255401 SUSE Bug 1255401 https://bugzilla.suse.com/1255403 SUSE Bug 1255403 https://bugzilla.suse.com/1255417 SUSE Bug 1255417 https://bugzilla.suse.com/1255482 SUSE Bug 1255482 https://bugzilla.suse.com/1255488 SUSE Bug 1255488 https://bugzilla.suse.com/1255537 SUSE Bug 1255537 https://bugzilla.suse.com/1255539 SUSE Bug 1255539 https://bugzilla.suse.com/1255544 SUSE Bug 1255544 https://bugzilla.suse.com/1255547 SUSE Bug 1255547 https://bugzilla.suse.com/1255548 SUSE Bug 1255548 https://bugzilla.suse.com/1255552 SUSE Bug 1255552 https://bugzilla.suse.com/1255568 SUSE Bug 1255568 https://bugzilla.suse.com/1255569 SUSE Bug 1255569 https://bugzilla.suse.com/1255615 SUSE Bug 1255615 https://bugzilla.suse.com/1255622 SUSE Bug 1255622 https://bugzilla.suse.com/1255695 SUSE Bug 1255695 https://bugzilla.suse.com/1255930 SUSE Bug 1255930 https://bugzilla.suse.com/1256280 SUSE Bug 1256280 https://bugzilla.suse.com/1256528 SUSE Bug 1256528 https://bugzilla.suse.com/1256568 SUSE Bug 1256568 https://bugzilla.suse.com/1256579 SUSE Bug 1256579 https://bugzilla.suse.com/1256582 SUSE Bug 1256582 https://bugzilla.suse.com/1256584 SUSE Bug 1256584 https://bugzilla.suse.com/1256586 SUSE Bug 1256586 https://bugzilla.suse.com/1256591 SUSE Bug 1256591 https://bugzilla.suse.com/1256592 SUSE Bug 1256592 https://bugzilla.suse.com/1256593 SUSE Bug 1256593 https://bugzilla.suse.com/1256594 SUSE Bug 1256594 https://bugzilla.suse.com/1256597 SUSE Bug 1256597 https://bugzilla.suse.com/1256605 SUSE Bug 1256605 https://bugzilla.suse.com/1256606 SUSE Bug 1256606 https://bugzilla.suse.com/1256607 SUSE Bug 1256607 https://bugzilla.suse.com/1256608 SUSE Bug 1256608 https://bugzilla.suse.com/1256609 SUSE Bug 1256609 https://bugzilla.suse.com/1256610 SUSE Bug 1256610 https://bugzilla.suse.com/1256611 SUSE Bug 1256611 https://bugzilla.suse.com/1256612 SUSE Bug 1256612 https://bugzilla.suse.com/1256613 SUSE Bug 1256613 https://bugzilla.suse.com/1256616 SUSE Bug 1256616 https://bugzilla.suse.com/1256617 SUSE Bug 1256617 https://bugzilla.suse.com/1256619 SUSE Bug 1256619 https://bugzilla.suse.com/1256622 SUSE Bug 1256622 https://bugzilla.suse.com/1256623 SUSE Bug 1256623 https://bugzilla.suse.com/1256625 SUSE Bug 1256625 https://bugzilla.suse.com/1256627 SUSE Bug 1256627 https://bugzilla.suse.com/1256628 SUSE Bug 1256628 https://bugzilla.suse.com/1256630 SUSE Bug 1256630 https://bugzilla.suse.com/1256638 SUSE Bug 1256638 https://bugzilla.suse.com/1256641 SUSE Bug 1256641 https://bugzilla.suse.com/1256645 SUSE Bug 1256645 https://bugzilla.suse.com/1256646 SUSE Bug 1256646 https://bugzilla.suse.com/1256650 SUSE Bug 1256650 https://bugzilla.suse.com/1256651 SUSE Bug 1256651 https://bugzilla.suse.com/1256653 SUSE Bug 1256653 https://bugzilla.suse.com/1256654 SUSE Bug 1256654 https://bugzilla.suse.com/1256655 SUSE Bug 1256655 https://bugzilla.suse.com/1256659 SUSE Bug 1256659 https://bugzilla.suse.com/1256660 SUSE Bug 1256660 https://bugzilla.suse.com/1256661 SUSE Bug 1256661 https://bugzilla.suse.com/1256664 SUSE Bug 1256664 https://bugzilla.suse.com/1256665 SUSE Bug 1256665 https://bugzilla.suse.com/1256674 SUSE Bug 1256674 https://bugzilla.suse.com/1256680 SUSE Bug 1256680 https://bugzilla.suse.com/1256682 SUSE Bug 1256682 https://bugzilla.suse.com/1256688 SUSE Bug 1256688 https://bugzilla.suse.com/1256689 SUSE Bug 1256689 https://bugzilla.suse.com/1256690 SUSE Bug 1256690 https://bugzilla.suse.com/1256726 SUSE Bug 1256726 https://bugzilla.suse.com/1256728 SUSE Bug 1256728 https://bugzilla.suse.com/1256730 SUSE Bug 1256730 https://bugzilla.suse.com/1256733 SUSE Bug 1256733 https://bugzilla.suse.com/1256737 SUSE Bug 1256737 https://bugzilla.suse.com/1256741 SUSE Bug 1256741 https://bugzilla.suse.com/1256742 SUSE Bug 1256742 https://bugzilla.suse.com/1256744 SUSE Bug 1256744 https://bugzilla.suse.com/1256748 SUSE Bug 1256748 https://bugzilla.suse.com/1256749 SUSE Bug 1256749 https://bugzilla.suse.com/1256752 SUSE Bug 1256752 https://bugzilla.suse.com/1256754 SUSE Bug 1256754 https://bugzilla.suse.com/1256756 SUSE Bug 1256756 https://bugzilla.suse.com/1256757 SUSE Bug 1256757 https://bugzilla.suse.com/1256759 SUSE Bug 1256759 https://bugzilla.suse.com/1256760 SUSE Bug 1256760 https://bugzilla.suse.com/1256761 SUSE Bug 1256761 https://bugzilla.suse.com/1256763 SUSE Bug 1256763 https://bugzilla.suse.com/1256770 SUSE Bug 1256770 https://bugzilla.suse.com/1256773 SUSE Bug 1256773 https://bugzilla.suse.com/1256774 SUSE Bug 1256774 https://bugzilla.suse.com/1256777 SUSE Bug 1256777 https://bugzilla.suse.com/1256779 SUSE Bug 1256779 https://bugzilla.suse.com/1256781 SUSE Bug 1256781 https://bugzilla.suse.com/1256785 SUSE Bug 1256785 https://bugzilla.suse.com/1256792 SUSE Bug 1256792 https://bugzilla.suse.com/1256794 SUSE Bug 1256794 https://bugzilla.suse.com/1256861 SUSE Bug 1256861 https://bugzilla.suse.com/1256863 SUSE Bug 1256863 https://bugzilla.suse.com/1257035 SUSE Bug 1257035 https://bugzilla.suse.com/1257053 SUSE Bug 1257053 https://bugzilla.suse.com/1257154 SUSE Bug 1257154 https://bugzilla.suse.com/1257155 SUSE Bug 1257155 https://bugzilla.suse.com/1257158 SUSE Bug 1257158 https://bugzilla.suse.com/1257163 SUSE Bug 1257163 https://bugzilla.suse.com/1257164 SUSE Bug 1257164 https://bugzilla.suse.com/1257167 SUSE Bug 1257167 https://bugzilla.suse.com/1257168 SUSE Bug 1257168 https://bugzilla.suse.com/1257180 SUSE Bug 1257180 https://bugzilla.suse.com/1257202 SUSE Bug 1257202 https://bugzilla.suse.com/1257204 SUSE Bug 1257204 https://bugzilla.suse.com/1257207 SUSE Bug 1257207 https://bugzilla.suse.com/1257208 SUSE Bug 1257208 https://bugzilla.suse.com/1257215 SUSE Bug 1257215 https://bugzilla.suse.com/1257217 SUSE Bug 1257217 https://bugzilla.suse.com/1257218 SUSE Bug 1257218 https://bugzilla.suse.com/1257220 SUSE Bug 1257220 https://bugzilla.suse.com/1257221 SUSE Bug 1257221 https://bugzilla.suse.com/1257227 SUSE Bug 1257227 https://bugzilla.suse.com/1257232 SUSE Bug 1257232 https://bugzilla.suse.com/1257234 SUSE Bug 1257234 https://bugzilla.suse.com/1257236 SUSE Bug 1257236 https://bugzilla.suse.com/1257245 SUSE Bug 1257245 https://bugzilla.suse.com/1257277 SUSE Bug 1257277 https://bugzilla.suse.com/1257282 SUSE Bug 1257282 https://bugzilla.suse.com/1257296 SUSE Bug 1257296 https://bugzilla.suse.com/1257473 SUSE Bug 1257473 https://bugzilla.suse.com/1257603 SUSE Bug 1257603 https://www.suse.com/security/cve/CVE-2023-53714/ SUSE CVE CVE-2023-53714 page https://www.suse.com/security/cve/CVE-2023-54013/ SUSE CVE CVE-2023-54013 page https://www.suse.com/security/cve/CVE-2024-27005/ SUSE CVE CVE-2024-27005 page https://www.suse.com/security/cve/CVE-2024-42103/ SUSE CVE CVE-2024-42103 page https://www.suse.com/security/cve/CVE-2024-53070/ SUSE CVE CVE-2024-53070 page https://www.suse.com/security/cve/CVE-2024-53149/ SUSE CVE CVE-2024-53149 page https://www.suse.com/security/cve/CVE-2024-56721/ SUSE CVE CVE-2024-56721 page https://www.suse.com/security/cve/CVE-2025-22047/ SUSE CVE CVE-2025-22047 page https://www.suse.com/security/cve/CVE-2025-37744/ SUSE CVE CVE-2025-37744 page https://www.suse.com/security/cve/CVE-2025-37751/ SUSE CVE CVE-2025-37751 page https://www.suse.com/security/cve/CVE-2025-37813/ SUSE CVE CVE-2025-37813 page https://www.suse.com/security/cve/CVE-2025-38209/ SUSE CVE CVE-2025-38209 page https://www.suse.com/security/cve/CVE-2025-38243/ SUSE CVE CVE-2025-38243 page https://www.suse.com/security/cve/CVE-2025-38322/ SUSE CVE CVE-2025-38322 page https://www.suse.com/security/cve/CVE-2025-38379/ SUSE CVE CVE-2025-38379 page https://www.suse.com/security/cve/CVE-2025-38539/ SUSE CVE CVE-2025-38539 page https://www.suse.com/security/cve/CVE-2025-39689/ SUSE CVE CVE-2025-39689 page https://www.suse.com/security/cve/CVE-2025-39813/ SUSE CVE CVE-2025-39813 page https://www.suse.com/security/cve/CVE-2025-39829/ SUSE CVE CVE-2025-39829 page https://www.suse.com/security/cve/CVE-2025-39836/ SUSE CVE CVE-2025-39836 page https://www.suse.com/security/cve/CVE-2025-39880/ SUSE CVE CVE-2025-39880 page https://www.suse.com/security/cve/CVE-2025-39913/ SUSE CVE CVE-2025-39913 page https://www.suse.com/security/cve/CVE-2025-40097/ SUSE CVE CVE-2025-40097 page https://www.suse.com/security/cve/CVE-2025-40106/ SUSE CVE CVE-2025-40106 page https://www.suse.com/security/cve/CVE-2025-40132/ SUSE CVE CVE-2025-40132 page https://www.suse.com/security/cve/CVE-2025-40136/ SUSE CVE CVE-2025-40136 page https://www.suse.com/security/cve/CVE-2025-40142/ SUSE CVE CVE-2025-40142 page https://www.suse.com/security/cve/CVE-2025-40166/ SUSE CVE CVE-2025-40166 page https://www.suse.com/security/cve/CVE-2025-40177/ SUSE CVE CVE-2025-40177 page https://www.suse.com/security/cve/CVE-2025-40181/ SUSE CVE CVE-2025-40181 page https://www.suse.com/security/cve/CVE-2025-40202/ SUSE CVE CVE-2025-40202 page https://www.suse.com/security/cve/CVE-2025-40238/ SUSE CVE CVE-2025-40238 page https://www.suse.com/security/cve/CVE-2025-40254/ SUSE CVE CVE-2025-40254 page https://www.suse.com/security/cve/CVE-2025-40257/ SUSE CVE CVE-2025-40257 page https://www.suse.com/security/cve/CVE-2025-40259/ SUSE CVE CVE-2025-40259 page https://www.suse.com/security/cve/CVE-2025-40261/ SUSE CVE CVE-2025-40261 page https://www.suse.com/security/cve/CVE-2025-40264/ SUSE CVE CVE-2025-40264 page https://www.suse.com/security/cve/CVE-2025-40328/ SUSE CVE CVE-2025-40328 page https://www.suse.com/security/cve/CVE-2025-40350/ SUSE CVE CVE-2025-40350 page https://www.suse.com/security/cve/CVE-2025-40355/ SUSE CVE CVE-2025-40355 page https://www.suse.com/security/cve/CVE-2025-40363/ SUSE CVE CVE-2025-40363 page https://www.suse.com/security/cve/CVE-2025-68171/ SUSE CVE CVE-2025-68171 page https://www.suse.com/security/cve/CVE-2025-68174/ SUSE CVE CVE-2025-68174 page https://www.suse.com/security/cve/CVE-2025-68178/ SUSE CVE CVE-2025-68178 page https://www.suse.com/security/cve/CVE-2025-68188/ SUSE CVE CVE-2025-68188 page https://www.suse.com/security/cve/CVE-2025-68200/ SUSE CVE CVE-2025-68200 page https://www.suse.com/security/cve/CVE-2025-68215/ SUSE CVE CVE-2025-68215 page https://www.suse.com/security/cve/CVE-2025-68227/ SUSE CVE CVE-2025-68227 page https://www.suse.com/security/cve/CVE-2025-68241/ SUSE CVE CVE-2025-68241 page https://www.suse.com/security/cve/CVE-2025-68245/ SUSE CVE CVE-2025-68245 page https://www.suse.com/security/cve/CVE-2025-68254/ SUSE CVE CVE-2025-68254 page https://www.suse.com/security/cve/CVE-2025-68256/ SUSE CVE CVE-2025-68256 page https://www.suse.com/security/cve/CVE-2025-68261/ SUSE CVE CVE-2025-68261 page https://www.suse.com/security/cve/CVE-2025-68284/ SUSE CVE CVE-2025-68284 page https://www.suse.com/security/cve/CVE-2025-68285/ SUSE CVE CVE-2025-68285 page https://www.suse.com/security/cve/CVE-2025-68296/ SUSE CVE CVE-2025-68296 page https://www.suse.com/security/cve/CVE-2025-68297/ SUSE CVE CVE-2025-68297 page https://www.suse.com/security/cve/CVE-2025-68301/ SUSE CVE CVE-2025-68301 page https://www.suse.com/security/cve/CVE-2025-68320/ SUSE CVE CVE-2025-68320 page https://www.suse.com/security/cve/CVE-2025-68325/ SUSE CVE CVE-2025-68325 page https://www.suse.com/security/cve/CVE-2025-68327/ SUSE CVE CVE-2025-68327 page https://www.suse.com/security/cve/CVE-2025-68337/ SUSE CVE CVE-2025-68337 page https://www.suse.com/security/cve/CVE-2025-68349/ SUSE CVE CVE-2025-68349 page https://www.suse.com/security/cve/CVE-2025-68363/ SUSE CVE CVE-2025-68363 page https://www.suse.com/security/cve/CVE-2025-68365/ SUSE CVE CVE-2025-68365 page https://www.suse.com/security/cve/CVE-2025-68366/ SUSE CVE CVE-2025-68366 page https://www.suse.com/security/cve/CVE-2025-68367/ SUSE CVE CVE-2025-68367 page https://www.suse.com/security/cve/CVE-2025-68372/ SUSE CVE CVE-2025-68372 page https://www.suse.com/security/cve/CVE-2025-68379/ SUSE CVE CVE-2025-68379 page https://www.suse.com/security/cve/CVE-2025-68725/ SUSE CVE CVE-2025-68725 page https://www.suse.com/security/cve/CVE-2025-68727/ SUSE CVE CVE-2025-68727 page https://www.suse.com/security/cve/CVE-2025-68728/ SUSE CVE CVE-2025-68728 page https://www.suse.com/security/cve/CVE-2025-68733/ SUSE CVE CVE-2025-68733 page https://www.suse.com/security/cve/CVE-2025-68764/ SUSE CVE CVE-2025-68764 page https://www.suse.com/security/cve/CVE-2025-68768/ SUSE CVE CVE-2025-68768 page https://www.suse.com/security/cve/CVE-2025-68770/ SUSE CVE CVE-2025-68770 page https://www.suse.com/security/cve/CVE-2025-68771/ SUSE CVE CVE-2025-68771 page https://www.suse.com/security/cve/CVE-2025-68773/ SUSE CVE CVE-2025-68773 page https://www.suse.com/security/cve/CVE-2025-68775/ SUSE CVE CVE-2025-68775 page https://www.suse.com/security/cve/CVE-2025-68776/ SUSE CVE CVE-2025-68776 page https://www.suse.com/security/cve/CVE-2025-68777/ SUSE CVE CVE-2025-68777 page https://www.suse.com/security/cve/CVE-2025-68783/ SUSE CVE CVE-2025-68783 page https://www.suse.com/security/cve/CVE-2025-68788/ SUSE CVE CVE-2025-68788 page https://www.suse.com/security/cve/CVE-2025-68789/ SUSE CVE CVE-2025-68789 page https://www.suse.com/security/cve/CVE-2025-68795/ SUSE CVE CVE-2025-68795 page https://www.suse.com/security/cve/CVE-2025-68797/ SUSE CVE CVE-2025-68797 page https://www.suse.com/security/cve/CVE-2025-68798/ SUSE CVE CVE-2025-68798 page https://www.suse.com/security/cve/CVE-2025-68800/ SUSE CVE CVE-2025-68800 page https://www.suse.com/security/cve/CVE-2025-68801/ SUSE CVE CVE-2025-68801 page https://www.suse.com/security/cve/CVE-2025-68802/ SUSE CVE CVE-2025-68802 page https://www.suse.com/security/cve/CVE-2025-68803/ SUSE CVE CVE-2025-68803 page https://www.suse.com/security/cve/CVE-2025-68804/ SUSE CVE CVE-2025-68804 page https://www.suse.com/security/cve/CVE-2025-68808/ SUSE CVE CVE-2025-68808 page https://www.suse.com/security/cve/CVE-2025-68813/ SUSE CVE CVE-2025-68813 page https://www.suse.com/security/cve/CVE-2025-68814/ SUSE CVE CVE-2025-68814 page https://www.suse.com/security/cve/CVE-2025-68815/ SUSE CVE CVE-2025-68815 page https://www.suse.com/security/cve/CVE-2025-68816/ SUSE CVE CVE-2025-68816 page https://www.suse.com/security/cve/CVE-2025-68819/ SUSE CVE CVE-2025-68819 page https://www.suse.com/security/cve/CVE-2025-68820/ SUSE CVE CVE-2025-68820 page https://www.suse.com/security/cve/CVE-2025-71064/ SUSE CVE CVE-2025-71064 page https://www.suse.com/security/cve/CVE-2025-71066/ SUSE CVE CVE-2025-71066 page https://www.suse.com/security/cve/CVE-2025-71076/ SUSE CVE CVE-2025-71076 page https://www.suse.com/security/cve/CVE-2025-71077/ SUSE CVE CVE-2025-71077 page https://www.suse.com/security/cve/CVE-2025-71078/ SUSE CVE CVE-2025-71078 page https://www.suse.com/security/cve/CVE-2025-71079/ SUSE CVE CVE-2025-71079 page https://www.suse.com/security/cve/CVE-2025-71080/ SUSE CVE CVE-2025-71080 page https://www.suse.com/security/cve/CVE-2025-71081/ SUSE CVE CVE-2025-71081 page https://www.suse.com/security/cve/CVE-2025-71082/ SUSE CVE CVE-2025-71082 page https://www.suse.com/security/cve/CVE-2025-71083/ SUSE CVE CVE-2025-71083 page https://www.suse.com/security/cve/CVE-2025-71084/ SUSE CVE CVE-2025-71084 page https://www.suse.com/security/cve/CVE-2025-71085/ SUSE CVE CVE-2025-71085 page https://www.suse.com/security/cve/CVE-2025-71086/ SUSE CVE CVE-2025-71086 page https://www.suse.com/security/cve/CVE-2025-71087/ SUSE CVE CVE-2025-71087 page https://www.suse.com/security/cve/CVE-2025-71088/ SUSE CVE CVE-2025-71088 page https://www.suse.com/security/cve/CVE-2025-71089/ SUSE CVE CVE-2025-71089 page https://www.suse.com/security/cve/CVE-2025-71091/ SUSE CVE CVE-2025-71091 page https://www.suse.com/security/cve/CVE-2025-71093/ SUSE CVE CVE-2025-71093 page https://www.suse.com/security/cve/CVE-2025-71094/ SUSE CVE CVE-2025-71094 page https://www.suse.com/security/cve/CVE-2025-71095/ SUSE CVE CVE-2025-71095 page https://www.suse.com/security/cve/CVE-2025-71096/ SUSE CVE CVE-2025-71096 page https://www.suse.com/security/cve/CVE-2025-71097/ SUSE CVE CVE-2025-71097 page https://www.suse.com/security/cve/CVE-2025-71098/ SUSE CVE CVE-2025-71098 page https://www.suse.com/security/cve/CVE-2025-71099/ SUSE CVE CVE-2025-71099 page https://www.suse.com/security/cve/CVE-2025-71100/ SUSE CVE CVE-2025-71100 page https://www.suse.com/security/cve/CVE-2025-71101/ SUSE CVE CVE-2025-71101 page https://www.suse.com/security/cve/CVE-2025-71108/ SUSE CVE CVE-2025-71108 page https://www.suse.com/security/cve/CVE-2025-71111/ SUSE CVE CVE-2025-71111 page https://www.suse.com/security/cve/CVE-2025-71112/ SUSE CVE CVE-2025-71112 page https://www.suse.com/security/cve/CVE-2025-71114/ SUSE CVE CVE-2025-71114 page https://www.suse.com/security/cve/CVE-2025-71116/ SUSE CVE CVE-2025-71116 page https://www.suse.com/security/cve/CVE-2025-71118/ SUSE CVE CVE-2025-71118 page https://www.suse.com/security/cve/CVE-2025-71119/ SUSE CVE CVE-2025-71119 page https://www.suse.com/security/cve/CVE-2025-71120/ SUSE CVE CVE-2025-71120 page https://www.suse.com/security/cve/CVE-2025-71123/ SUSE CVE CVE-2025-71123 page https://www.suse.com/security/cve/CVE-2025-71130/ SUSE CVE CVE-2025-71130 page https://www.suse.com/security/cve/CVE-2025-71131/ SUSE CVE CVE-2025-71131 page https://www.suse.com/security/cve/CVE-2025-71132/ SUSE CVE CVE-2025-71132 page https://www.suse.com/security/cve/CVE-2025-71133/ SUSE CVE CVE-2025-71133 page https://www.suse.com/security/cve/CVE-2025-71135/ SUSE CVE CVE-2025-71135 page https://www.suse.com/security/cve/CVE-2025-71136/ SUSE CVE CVE-2025-71136 page https://www.suse.com/security/cve/CVE-2025-71137/ SUSE CVE CVE-2025-71137 page https://www.suse.com/security/cve/CVE-2025-71138/ SUSE CVE CVE-2025-71138 page https://www.suse.com/security/cve/CVE-2025-71141/ SUSE CVE CVE-2025-71141 page https://www.suse.com/security/cve/CVE-2025-71142/ SUSE CVE CVE-2025-71142 page https://www.suse.com/security/cve/CVE-2025-71143/ SUSE CVE CVE-2025-71143 page https://www.suse.com/security/cve/CVE-2025-71145/ SUSE CVE CVE-2025-71145 page https://www.suse.com/security/cve/CVE-2025-71147/ SUSE CVE CVE-2025-71147 page https://www.suse.com/security/cve/CVE-2025-71149/ SUSE CVE CVE-2025-71149 page https://www.suse.com/security/cve/CVE-2025-71154/ SUSE CVE CVE-2025-71154 page https://www.suse.com/security/cve/CVE-2025-71156/ SUSE CVE CVE-2025-71156 page https://www.suse.com/security/cve/CVE-2025-71157/ SUSE CVE CVE-2025-71157 page https://www.suse.com/security/cve/CVE-2025-71162/ SUSE CVE CVE-2025-71162 page https://www.suse.com/security/cve/CVE-2025-71163/ SUSE CVE CVE-2025-71163 page https://www.suse.com/security/cve/CVE-2026-22976/ SUSE CVE CVE-2026-22976 page https://www.suse.com/security/cve/CVE-2026-22977/ SUSE CVE CVE-2026-22977 page https://www.suse.com/security/cve/CVE-2026-22978/ SUSE CVE CVE-2026-22978 page https://www.suse.com/security/cve/CVE-2026-22984/ SUSE CVE CVE-2026-22984 page https://www.suse.com/security/cve/CVE-2026-22985/ SUSE CVE CVE-2026-22985 page https://www.suse.com/security/cve/CVE-2026-22988/ SUSE CVE CVE-2026-22988 page https://www.suse.com/security/cve/CVE-2026-22990/ SUSE CVE CVE-2026-22990 page https://www.suse.com/security/cve/CVE-2026-22991/ SUSE CVE CVE-2026-22991 page https://www.suse.com/security/cve/CVE-2026-22992/ SUSE CVE CVE-2026-22992 page https://www.suse.com/security/cve/CVE-2026-22993/ SUSE CVE CVE-2026-22993 page https://www.suse.com/security/cve/CVE-2026-22996/ SUSE CVE CVE-2026-22996 page https://www.suse.com/security/cve/CVE-2026-22997/ SUSE CVE CVE-2026-22997 page https://www.suse.com/security/cve/CVE-2026-22999/ SUSE CVE CVE-2026-22999 page https://www.suse.com/security/cve/CVE-2026-23000/ SUSE CVE CVE-2026-23000 page https://www.suse.com/security/cve/CVE-2026-23001/ SUSE CVE CVE-2026-23001 page https://www.suse.com/security/cve/CVE-2026-23005/ SUSE CVE CVE-2026-23005 page https://www.suse.com/security/cve/CVE-2026-23006/ SUSE CVE CVE-2026-23006 page https://www.suse.com/security/cve/CVE-2026-23011/ SUSE CVE CVE-2026-23011 page SUSE Linux Enterprise Live Patching 15 SP7 SUSE Real Time Module 15 SP7 cluster-md-kmp-rt-6.4.0-150700.7.31.2 dlm-kmp-rt-6.4.0-150700.7.31.2 gfs2-kmp-rt-6.4.0-150700.7.31.2 kernel-devel-rt-6.4.0-150700.7.31.1 kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 kernel-rt-6.4.0-150700.7.31.2 kernel-rt-devel-6.4.0-150700.7.31.2 kernel-rt-extra-6.4.0-150700.7.31.2 kernel-rt-livepatch-6.4.0-150700.7.31.2 kernel-rt-livepatch-devel-6.4.0-150700.7.31.2 kernel-rt-optional-6.4.0-150700.7.31.2 kernel-rt-vdso-6.4.0-150700.7.31.2 kernel-source-rt-6.4.0-150700.7.31.1 kernel-syms-rt-6.4.0-150700.7.31.1 kselftests-kmp-rt-6.4.0-150700.7.31.2 ocfs2-kmp-rt-6.4.0-150700.7.31.2 reiserfs-kmp-rt-6.4.0-150700.7.31.2 kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 as a component of SUSE Linux Enterprise Live Patching 15 SP7 cluster-md-kmp-rt-6.4.0-150700.7.31.2 as a component of SUSE Real Time Module 15 SP7 dlm-kmp-rt-6.4.0-150700.7.31.2 as a component of SUSE Real Time Module 15 SP7 gfs2-kmp-rt-6.4.0-150700.7.31.2 as a component of SUSE Real Time Module 15 SP7 kernel-devel-rt-6.4.0-150700.7.31.1 as a component of SUSE Real Time Module 15 SP7 kernel-rt-6.4.0-150700.7.31.2 as a component of SUSE Real Time Module 15 SP7 kernel-rt-devel-6.4.0-150700.7.31.2 as a component of SUSE Real Time Module 15 SP7 kernel-source-rt-6.4.0-150700.7.31.1 as a component of SUSE Real Time Module 15 SP7 kernel-syms-rt-6.4.0-150700.7.31.1 as a component of SUSE Real Time Module 15 SP7 ocfs2-kmp-rt-6.4.0-150700.7.31.2 as a component of SUSE Real Time Module 15 SP7 In the Linux kernel, the following vulnerability has been resolved: drm/stm: ltdc: fix late dereference check In ltdc_crtc_set_crc_source(), struct drm_crtc was dereferenced in a container_of() before the pointer check. This could cause a kernel panic. Fix this smatch warning: drivers/gpu/drm/stm/ltdc.c:1124 ltdc_crtc_set_crc_source() warn: variable dereferenced before check 'crtc' (see line 1119) CVE-2023-53714 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2023-53714.html CVE-2023-53714 https://bugzilla.suse.com/1254465 SUSE Bug 1254465 In the Linux kernel, the following vulnerability has been resolved: interconnect: Fix locking for runpm vs reclaim For cases where icc_bw_set() can be called in callbaths that could deadlock against shrinker/reclaim, such as runpm resume, we need to decouple the icc locking. Introduce a new icc_bw_lock for cases where we need to serialize bw aggregation and update to decouple that from paths that require memory allocation such as node/link creation/ destruction. Fixes this lockdep splat: ====================================================== WARNING: possible circular locking dependency detected 6.2.0-rc8-debug+ #554 Not tainted ------------------------------------------------------ ring0/132 is trying to acquire lock: ffffff80871916d0 (&gmu->lock){+.+.}-{3:3}, at: a6xx_pm_resume+0xf0/0x234 but task is already holding lock: ffffffdb5aee57e8 (dma_fence_map){++++}-{0:0}, at: msm_job_run+0x68/0x150 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #4 (dma_fence_map){++++}-{0:0}: __dma_fence_might_wait+0x74/0xc0 dma_resv_lockdep+0x1f4/0x2f4 do_one_initcall+0x104/0x2bc kernel_init_freeable+0x344/0x34c kernel_init+0x30/0x134 ret_from_fork+0x10/0x20 -> #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}: fs_reclaim_acquire+0x80/0xa8 slab_pre_alloc_hook.constprop.0+0x40/0x25c __kmem_cache_alloc_node+0x60/0x1cc __kmalloc+0xd8/0x100 topology_parse_cpu_capacity+0x8c/0x178 get_cpu_for_node+0x88/0xc4 parse_cluster+0x1b0/0x28c parse_cluster+0x8c/0x28c init_cpu_topology+0x168/0x188 smp_prepare_cpus+0x24/0xf8 kernel_init_freeable+0x18c/0x34c kernel_init+0x30/0x134 ret_from_fork+0x10/0x20 -> #2 (fs_reclaim){+.+.}-{0:0}: __fs_reclaim_acquire+0x3c/0x48 fs_reclaim_acquire+0x54/0xa8 slab_pre_alloc_hook.constprop.0+0x40/0x25c __kmem_cache_alloc_node+0x60/0x1cc __kmalloc+0xd8/0x100 kzalloc.constprop.0+0x14/0x20 icc_node_create_nolock+0x4c/0xc4 icc_node_create+0x38/0x58 qcom_icc_rpmh_probe+0x1b8/0x248 platform_probe+0x70/0xc4 really_probe+0x158/0x290 __driver_probe_device+0xc8/0xe0 driver_probe_device+0x44/0x100 __driver_attach+0xf8/0x108 bus_for_each_dev+0x78/0xc4 driver_attach+0x2c/0x38 bus_add_driver+0xd0/0x1d8 driver_register+0xbc/0xf8 __platform_driver_register+0x30/0x3c qnoc_driver_init+0x24/0x30 do_one_initcall+0x104/0x2bc kernel_init_freeable+0x344/0x34c kernel_init+0x30/0x134 ret_from_fork+0x10/0x20 -> #1 (icc_lock){+.+.}-{3:3}: __mutex_lock+0xcc/0x3c8 mutex_lock_nested+0x30/0x44 icc_set_bw+0x88/0x2b4 _set_opp_bw+0x8c/0xd8 _set_opp+0x19c/0x300 dev_pm_opp_set_opp+0x84/0x94 a6xx_gmu_resume+0x18c/0x804 a6xx_pm_resume+0xf8/0x234 adreno_runtime_resume+0x2c/0x38 pm_generic_runtime_resume+0x30/0x44 __rpm_callback+0x15c/0x174 rpm_callback+0x78/0x7c rpm_resume+0x318/0x524 __pm_runtime_resume+0x78/0xbc adreno_load_gpu+0xc4/0x17c msm_open+0x50/0x120 drm_file_alloc+0x17c/0x228 drm_open_helper+0x74/0x118 drm_open+0xa0/0x144 drm_stub_open+0xd4/0xe4 chrdev_open+0x1b8/0x1e4 do_dentry_open+0x2f8/0x38c vfs_open+0x34/0x40 path_openat+0x64c/0x7b4 do_filp_open+0x54/0xc4 do_sys_openat2+0x9c/0x100 do_sys_open+0x50/0x7c __arm64_sys_openat+0x28/0x34 invoke_syscall+0x8c/0x128 el0_svc_common.constprop.0+0xa0/0x11c do_el0_ ---truncated--- CVE-2023-54013 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2023-54013.html CVE-2023-54013 https://bugzilla.suse.com/1256280 SUSE Bug 1256280 In the Linux kernel, the following vulnerability has been resolved: interconnect: Don't access req_list while it's being manipulated The icc_lock mutex was split into separate icc_lock and icc_bw_lock mutexes in [1] to avoid lockdep splats. However, this didn't adequately protect access to icc_node::req_list. The icc_set_bw() function will eventually iterate over req_list while only holding icc_bw_lock, but req_list can be modified while only holding icc_lock. This causes races between icc_set_bw(), of_icc_get(), and icc_put(). Example A: CPU0 CPU1 ---- ---- icc_set_bw(path_a) mutex_lock(&icc_bw_lock); icc_put(path_b) mutex_lock(&icc_lock); aggregate_requests() hlist_for_each_entry(r, ... hlist_del(... <r = invalid pointer> Example B: CPU0 CPU1 ---- ---- icc_set_bw(path_a) mutex_lock(&icc_bw_lock); path_b = of_icc_get() of_icc_get_by_index() mutex_lock(&icc_lock); path_find() path_init() aggregate_requests() hlist_for_each_entry(r, ... hlist_add_head(... <r = invalid pointer> Fix this by ensuring icc_bw_lock is always held before manipulating icc_node::req_list. The additional places icc_bw_lock is held don't perform any memory allocations, so we should still be safe from the original lockdep splats that motivated the separate locks. [1] commit af42269c3523 ("interconnect: Fix locking for runpm vs reclaim") CVE-2024-27005 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2024-27005.html CVE-2024-27005 https://bugzilla.suse.com/1223800 SUSE Bug 1223800 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix adding block group to a reclaim list and the unused list during reclaim There is a potential parallel list adding for retrying in btrfs_reclaim_bgs_work and adding to the unused list. Since the block group is removed from the reclaim list and it is on a relocation work, it can be added into the unused list in parallel. When that happens, adding it to the reclaim list will corrupt the list head and trigger list corruption like below. Fix it by taking fs_info->unused_bgs_lock. [177.504][T2585409] BTRFS error (device nullb1): error relocating ch= unk 2415919104 [177.514][T2585409] list_del corruption. next->prev should be ff1100= 0344b119c0, but was ff11000377e87c70. (next=3Dff110002390cd9c0) [177.529][T2585409] ------------[ cut here ]------------ [177.537][T2585409] kernel BUG at lib/list_debug.c:65! [177.545][T2585409] Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI [177.555][T2585409] CPU: 9 PID: 2585409 Comm: kworker/u128:2 Tainted: G W 6.10.0-rc5-kts #1 [177.568][T2585409] Hardware name: Supermicro SYS-520P-WTR/X12SPW-TF, BIOS 1.2 02/14/2022 [177.579][T2585409] Workqueue: events_unbound btrfs_reclaim_bgs_work[btrfs] [177.589][T2585409] RIP: 0010:__list_del_entry_valid_or_report.cold+0x70/0x72 [177.624][T2585409] RSP: 0018:ff11000377e87a70 EFLAGS: 00010286 [177.633][T2585409] RAX: 000000000000006d RBX: ff11000344b119c0 RCX:0000000000000000 [177.644][T2585409] RDX: 000000000000006d RSI: 0000000000000008 RDI:ffe21c006efd0f40 [177.655][T2585409] RBP: ff110002e0509f78 R08: 0000000000000001 R09:ffe21c006efd0f08 [177.665][T2585409] R10: ff11000377e87847 R11: 0000000000000000 R12:ff110002390cd9c0 [177.676][T2585409] R13: ff11000344b119c0 R14: ff110002e0508000 R15:dffffc0000000000 [177.687][T2585409] FS: 0000000000000000(0000) GS:ff11000fec880000(0000) knlGS:0000000000000000 [177.700][T2585409] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [177.709][T2585409] CR2: 00007f06bc7b1978 CR3: 0000001021e86005 CR4:0000000000771ef0 [177.720][T2585409] DR0: 0000000000000000 DR1: 0000000000000000 DR2:0000000000000000 [177.731][T2585409] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:0000000000000400 [177.742][T2585409] PKRU: 55555554 [177.748][T2585409] Call Trace: [177.753][T2585409] <TASK> [177.759][T2585409] ? __die_body.cold+0x19/0x27 [177.766][T2585409] ? die+0x2e/0x50 [177.772][T2585409] ? do_trap+0x1ea/0x2d0 [177.779][T2585409] ? __list_del_entry_valid_or_report.cold+0x70/0x72 [177.788][T2585409] ? do_error_trap+0xa3/0x160 [177.795][T2585409] ? __list_del_entry_valid_or_report.cold+0x70/0x72 [177.805][T2585409] ? handle_invalid_op+0x2c/0x40 [177.812][T2585409] ? __list_del_entry_valid_or_report.cold+0x70/0x72 [177.820][T2585409] ? exc_invalid_op+0x2d/0x40 [177.827][T2585409] ? asm_exc_invalid_op+0x1a/0x20 [177.834][T2585409] ? __list_del_entry_valid_or_report.cold+0x70/0x72 [177.843][T2585409] btrfs_delete_unused_bgs+0x3d9/0x14c0 [btrfs] There is a similar retry_list code in btrfs_delete_unused_bgs(), but it is safe, AFAICS. Since the block group was in the unused list, the used bytes should be 0 when it was added to the unused list. Then, it checks block_group->{used,reserved,pinned} are still 0 under the block_group->lock. So, they should be still eligible for the unused list, not the reclaim list. The reason it is safe there it's because because we're holding space_info->groups_sem in write mode. That means no other task can allocate from the block group, so while we are at deleted_unused_bgs() it's not possible for other tasks to allocate and deallocate extents from the block group, so it can't be added to the unused list or the reclaim list by anyone else. The bug can be reproduced by btrfs/166 after a few rounds. In practice this can be hit when relocation cannot find more chunk space and ends with ENOSPC. CVE-2024-42103 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2024-42103.html CVE-2024-42103 https://bugzilla.suse.com/1228490 SUSE Bug 1228490 In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: fix fault at system suspend if device was already runtime suspended If the device was already runtime suspended then during system suspend we cannot access the device registers else it will crash. Also we cannot access any registers after dwc3_core_exit() on some platforms so move the dwc3_enable_susphy() call to the top. CVE-2024-53070 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2024-53070.html CVE-2024-53070 https://bugzilla.suse.com/1233563 SUSE Bug 1233563 In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: glink: fix off-by-one in connector_status UCSI connector's indices start from 1 up to 3, PMIC_GLINK_MAX_PORTS. Correct the condition in the pmic_glink_ucsi_connector_status() callback, fixing Type-C orientation reporting for the third USB-C connector. CVE-2024-53149 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2024-53149.html CVE-2024-53149 https://bugzilla.suse.com/1234842 SUSE Bug 1234842 In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Terminate the erratum_1386_microcode array The erratum_1386_microcode array requires an empty entry at the end. Otherwise x86_match_cpu_with_stepping() will continue iterate the array after it ended. Add an empty entry to erratum_1386_microcode to its end. CVE-2024-56721 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2024-56721.html CVE-2024-56721 https://bugzilla.suse.com/1235566 SUSE Bug 1235566 In the Linux kernel, the following vulnerability has been resolved: x86/microcode/AMD: Fix __apply_microcode_amd()'s return value When verify_sha256_digest() fails, __apply_microcode_amd() should propagate the failure by returning false (and not -1 which is promoted to true). CVE-2025-22047 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-22047.html CVE-2025-22047 https://bugzilla.suse.com/1241437 SUSE Bug 1241437 In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix memory leak in ath12k_pci_remove() Kmemleak reported this error: unreferenced object 0xffff1c165cec3060 (size 32): comm "insmod", pid 560, jiffies 4296964570 (age 235.596s) backtrace: [<000000005434db68>] __kmem_cache_alloc_node+0x1f4/0x2c0 [<000000001203b155>] kmalloc_trace+0x40/0x88 [<0000000028adc9c8>] _request_firmware+0xb8/0x608 [<00000000cad1aef7>] firmware_request_nowarn+0x50/0x80 [<000000005011a682>] local_pci_probe+0x48/0xd0 [<00000000077cd295>] pci_device_probe+0xb4/0x200 [<0000000087184c94>] really_probe+0x150/0x2c0 The firmware memory was allocated in ath12k_pci_probe(), but not freed in ath12k_pci_remove() in case ATH12K_FLAG_QMI_FAIL bit is set. So call ath12k_fw_unmap() to free the memory. Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.2.0-02280-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1 CVE-2025-37744 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-37744.html CVE-2025-37744 https://bugzilla.suse.com/1243662 SUSE Bug 1243662 In the Linux kernel, the following vulnerability has been resolved: x86/cpu: Avoid running off the end of an AMD erratum table The NULL array terminator at the end of erratum_1386_microcode was removed during the switch from x86_cpu_desc to x86_cpu_id. This causes readers to run off the end of the array. Replace the NULL. CVE-2025-37751 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-37751.html CVE-2025-37751 https://bugzilla.suse.com/1242505 SUSE Bug 1242505 In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Fix invalid pointer dereference in Etron workaround This check is performed before prepare_transfer() and prepare_ring(), so enqueue can already point at the final link TRB of a segment. And indeed it will, some 0.4% of times this code is called. Then enqueue + 1 is an invalid pointer. It will crash the kernel right away or load some junk which may look like a link TRB and cause the real link TRB to be replaced with a NOOP. This wouldn't end well. Use a functionally equivalent test which doesn't dereference the pointer and always gives correct result. Something has crashed my machine twice in recent days while playing with an Etron HC, and a control transfer stress test ran for confirmation has just crashed it again. The same test passes with this patch applied. CVE-2025-37813 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-37813.html CVE-2025-37813 https://bugzilla.suse.com/1242909 SUSE Bug 1242909 In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: remove tag set when second admin queue config fails Commit 104d0e2f6222 ("nvme-fabrics: reset admin connection for secure concatenation") modified nvme_tcp_setup_ctrl() to call nvme_tcp_configure_admin_queue() twice. The first call prepares for DH-CHAP negotitation, and the second call is required for secure concatenation. However, this change triggered BUG KASAN slab-use-after- free in blk_mq_queue_tag_busy_iter(). This BUG can be recreated by repeating the blktests test case nvme/063 a few times [1]. When the BUG happens, nvme_tcp_create_ctrl() fails in the call chain below: nvme_tcp_create_ctrl() nvme_tcp_alloc_ctrl() new=true ... Alloc nvme_tcp_ctrl and admin_tag_set nvme_tcp_setup_ctrl() new=true nvme_tcp_configure_admin_queue() new=true ... Succeed nvme_alloc_admin_tag_set() ... Alloc the tag set for admin_tag_set nvme_stop_keep_alive() nvme_tcp_teardown_admin_queue() remove=false nvme_tcp_configure_admin_queue() new=false nvme_tcp_alloc_admin_queue() ... Fail, but do not call nvme_remove_admin_tag_set() nvme_uninit_ctrl() nvme_put_ctrl() ... Free up the nvme_tcp_ctrl and admin_tag_set The first call of nvme_tcp_configure_admin_queue() succeeds with new=true argument. The second call fails with new=false argument. This second call does not call nvme_remove_admin_tag_set() on failure, due to the new=false argument. Then the admin tag set is not removed. However, nvme_tcp_create_ctrl() assumes that nvme_tcp_setup_ctrl() would call nvme_remove_admin_tag_set(). Then it frees up struct nvme_tcp_ctrl which has admin_tag_set field. Later on, the timeout handler accesses the admin_tag_set field and causes the BUG KASAN slab-use-after-free. To not leave the admin tag set, call nvme_remove_admin_tag_set() when the second nvme_tcp_configure_admin_queue() call fails. Do not return from nvme_tcp_setup_ctrl() on failure. Instead, jump to "destroy_admin" go-to label to call nvme_tcp_teardown_admin_queue() which calls nvme_remove_admin_tag_set(). CVE-2025-38209 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-38209.html CVE-2025-38209 https://bugzilla.suse.com/1246022 SUSE Bug 1246022 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix invalid inode pointer dereferences during log replay In a few places where we call read_one_inode(), if we get a NULL pointer we end up jumping into an error path, or fallthrough in case of __add_inode_ref(), where we then do something like this: iput(&inode->vfs_inode); which results in an invalid inode pointer that triggers an invalid memory access, resulting in a crash. Fix this by making sure we don't do such dereferences. CVE-2025-38243 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-38243.html CVE-2025-38243 https://bugzilla.suse.com/1246184 SUSE Bug 1246184 In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel: Fix crash in icl_update_topdown_event() The perf_fuzzer found a hard-lockup crash on a RaptorLake machine: Oops: general protection fault, maybe for address 0xffff89aeceab400: 0000 CPU: 23 UID: 0 PID: 0 Comm: swapper/23 Tainted: [W]=WARN Hardware name: Dell Inc. Precision 9660/0VJ762 RIP: 0010:native_read_pmc+0x7/0x40 Code: cc e8 8d a9 01 00 48 89 03 5b cd cc cc cc cc 0f 1f ... RSP: 000:fffb03100273de8 EFLAGS: 00010046 .... Call Trace: <TASK> icl_update_topdown_event+0x165/0x190 ? ktime_get+0x38/0xd0 intel_pmu_read_event+0xf9/0x210 __perf_event_read+0xf9/0x210 CPUs 16-23 are E-core CPUs that don't support the perf metrics feature. The icl_update_topdown_event() should not be invoked on these CPUs. It's a regression of commit: f9bdf1f95339 ("perf/x86/intel: Avoid disable PMU if !cpuc->enabled in sample read") The bug introduced by that commit is that the is_topdown_event() function is mistakenly used to replace the is_topdown_count() call to check if the topdown functions for the perf metrics feature should be invoked. Fix it. CVE-2025-38322 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-38322.html CVE-2025-38322 https://bugzilla.suse.com/1246447 SUSE Bug 1246447 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix warning when reconnecting channel When reconnecting a channel in smb2_reconnect_server(), a dummy tcon is passed down to smb2_reconnect() with ->query_interface uninitialized, so we can't call queue_delayed_work() on it. Fix the following warning by ensuring that we're queueing the delayed worker from correct tcon. WARNING: CPU: 4 PID: 1126 at kernel/workqueue.c:2498 __queue_delayed_work+0x1d2/0x200 Modules linked in: cifs cifs_arc4 nls_ucs2_utils cifs_md4 [last unloaded: cifs] CPU: 4 UID: 0 PID: 1126 Comm: kworker/4:0 Not tainted 6.16.0-rc3 #5 PREEMPT(voluntary) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-4.fc42 04/01/2014 Workqueue: cifsiod smb2_reconnect_server [cifs] RIP: 0010:__queue_delayed_work+0x1d2/0x200 Code: 41 5e 41 5f e9 7f ee ff ff 90 0f 0b 90 e9 5d ff ff ff bf 02 00 00 00 e8 6c f3 07 00 89 c3 eb bd 90 0f 0b 90 e9 57 f> 0b 90 e9 65 fe ff ff 90 0f 0b 90 e9 72 fe ff ff 90 0f 0b 90 e9 RSP: 0018:ffffc900014afad8 EFLAGS: 00010003 RAX: 0000000000000000 RBX: ffff888124d99988 RCX: ffffffff81399cc1 RDX: dffffc0000000000 RSI: ffff888114326e00 RDI: ffff888124d999f0 RBP: 000000000000ea60 R08: 0000000000000001 R09: ffffed10249b3331 R10: ffff888124d9998f R11: 0000000000000004 R12: 0000000000000040 R13: ffff888114326e00 R14: ffff888124d999d8 R15: ffff888114939020 FS: 0000000000000000(0000) GS:ffff88829f7fe000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffe7a2b4038 CR3: 0000000120a6f000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> queue_delayed_work_on+0xb4/0xc0 smb2_reconnect+0xb22/0xf50 [cifs] smb2_reconnect_server+0x413/0xd40 [cifs] ? __pfx_smb2_reconnect_server+0x10/0x10 [cifs] ? local_clock_noinstr+0xd/0xd0 ? local_clock+0x15/0x30 ? lock_release+0x29b/0x390 process_one_work+0x4c5/0xa10 ? __pfx_process_one_work+0x10/0x10 ? __list_add_valid_or_report+0x37/0x120 worker_thread+0x2f1/0x5a0 ? __kthread_parkme+0xde/0x100 ? __pfx_worker_thread+0x10/0x10 kthread+0x1fe/0x380 ? kthread+0x10f/0x380 ? __pfx_kthread+0x10/0x10 ? local_clock_noinstr+0xd/0xd0 ? ret_from_fork+0x1b/0x1f0 ? local_clock+0x15/0x30 ? lock_release+0x29b/0x390 ? rcu_is_watching+0x20/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x15b/0x1f0 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> irq event stamp: 1116206 hardirqs last enabled at (1116205): [<ffffffff8143af42>] __up_console_sem+0x52/0x60 hardirqs last disabled at (1116206): [<ffffffff81399f0e>] queue_delayed_work_on+0x6e/0xc0 softirqs last enabled at (1116138): [<ffffffffc04562fd>] __smb_send_rqst+0x42d/0x950 [cifs] softirqs last disabled at (1116136): [<ffffffff823d35e1>] release_sock+0x21/0xf0 CVE-2025-38379 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-38379.html CVE-2025-38379 https://bugzilla.suse.com/1247030 SUSE Bug 1247030 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_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-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: ftrace: Also allocate and copy hash for reading of filter files Currently the reader of set_ftrace_filter and set_ftrace_notrace just adds the pointer to the global tracer hash to its iterator. Unlike the writer that allocates a copy of the hash, the reader keeps the pointer to the filter hashes. This is problematic because this pointer is static across function calls that release the locks that can update the global tracer hashes. This can cause UAF and similar bugs. Allocate and copy the hash for reading the filter files like it is done for the writers. This not only fixes UAF bugs, but also makes the code a bit simpler as it doesn't have to differentiate when to free the iterator's hash between writers and readers. CVE-2025-39689 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-39689.html CVE-2025-39689 https://bugzilla.suse.com/1249307 SUSE Bug 1249307 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_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-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: trace/fgraph: Fix the warning caused by missing unregister notifier This warning was triggered during testing on v6.16: notifier callback ftrace_suspend_notifier_call already registered WARNING: CPU: 2 PID: 86 at kernel/notifier.c:23 notifier_chain_register+0x44/0xb0 ... Call Trace: <TASK> blocking_notifier_chain_register+0x34/0x60 register_ftrace_graph+0x330/0x410 ftrace_profile_write+0x1e9/0x340 vfs_write+0xf8/0x420 ? filp_flush+0x8a/0xa0 ? filp_close+0x1f/0x30 ? do_dup2+0xaf/0x160 ksys_write+0x65/0xe0 do_syscall_64+0xa4/0x260 entry_SYSCALL_64_after_hwframe+0x77/0x7f When writing to the function_profile_enabled interface, the notifier was not unregistered after start_graph_tracing failed, causing a warning the next time function_profile_enabled was written. Fixed by adding unregister_pm_notifier in the exception path. CVE-2025-39829 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-39829.html CVE-2025-39829 https://bugzilla.suse.com/1250082 SUSE Bug 1250082 In the Linux kernel, the following vulnerability has been resolved: efi: stmm: Fix incorrect buffer allocation method The communication buffer allocated by setup_mm_hdr() is later on passed to tee_shm_register_kernel_buf(). The latter expects those buffers to be contiguous pages, but setup_mm_hdr() just uses kmalloc(). That can cause various corruptions or BUGs, specifically since commit 9aec2fb0fd5e ("slab: allocate frozen pages"), though it was broken before as well. Fix this by using alloc_pages_exact() instead of kmalloc(). CVE-2025-39836 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-39836.html CVE-2025-39836 https://bugzilla.suse.com/1249904 SUSE Bug 1249904 In the Linux kernel, the following vulnerability has been resolved: libceph: fix invalid accesses to ceph_connection_v1_info There is a place where generic code in messenger.c is reading and another place where it is writing to con->v1 union member without checking that the union member is active (i.e. msgr1 is in use). On 64-bit systems, con->v1.auth_retry overlaps with con->v2.out_iter, so such a read is almost guaranteed to return a bogus value instead of 0 when msgr2 is in use. This ends up being fairly benign because the side effect is just the invalidation of the authorizer and successive fetching of new tickets. con->v1.connect_seq overlaps with con->v2.conn_bufs and the fact that it's being written to can cause more serious consequences, but luckily it's not something that happens often. CVE-2025-39880 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-39880.html CVE-2025-39880 https://bugzilla.suse.com/1250388 SUSE Bug 1250388 In the Linux kernel, the following vulnerability has been resolved: tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. syzbot reported the splat below. [0] The repro does the following: 1. Load a sk_msg prog that calls bpf_msg_cork_bytes(msg, cork_bytes) 2. Attach the prog to a SOCKMAP 3. Add a socket to the SOCKMAP 4. Activate fault injection 5. Send data less than cork_bytes At 5., the data is carried over to the next sendmsg() as it is smaller than the cork_bytes specified by bpf_msg_cork_bytes(). Then, tcp_bpf_send_verdict() tries to allocate psock->cork to hold the data, but this fails silently due to fault injection + __GFP_NOWARN. If the allocation fails, we need to revert the sk->sk_forward_alloc change done by sk_msg_alloc(). Let's call sk_msg_free() when tcp_bpf_send_verdict fails to allocate psock->cork. The "*copied" also needs to be updated such that a proper error can be returned to the caller, sendmsg. It fails to allocate psock->cork. Nothing has been corked so far, so this patch simply sets "*copied" to 0. [0]: WARNING: net/ipv4/af_inet.c:156 at inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156, CPU#1: syz-executor/5983 Modules linked in: CPU: 1 UID: 0 PID: 5983 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156 Code: 0f 0b 90 e9 62 fe ff ff e8 7a db b5 f7 90 0f 0b 90 e9 95 fe ff ff e8 6c db b5 f7 90 0f 0b 90 e9 bb fe ff ff e8 5e db b5 f7 90 <0f> 0b 90 e9 e1 fe ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 9f fc RSP: 0018:ffffc90000a08b48 EFLAGS: 00010246 RAX: ffffffff8a09d0b2 RBX: dffffc0000000000 RCX: ffff888024a23c80 RDX: 0000000000000100 RSI: 0000000000000fff RDI: 0000000000000000 RBP: 0000000000000fff R08: ffff88807e07c627 R09: 1ffff1100fc0f8c4 R10: dffffc0000000000 R11: ffffed100fc0f8c5 R12: ffff88807e07c380 R13: dffffc0000000000 R14: ffff88807e07c60c R15: 1ffff1100fc0f872 FS: 00005555604c4500(0000) GS:ffff888125af1000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005555604df5c8 CR3: 0000000032b06000 CR4: 00000000003526f0 Call Trace: <IRQ> __sk_destruct+0x86/0x660 net/core/sock.c:2339 rcu_do_batch kernel/rcu/tree.c:2605 [inline] rcu_core+0xca8/0x1770 kernel/rcu/tree.c:2861 handle_softirqs+0x286/0x870 kernel/softirq.c:579 __do_softirq kernel/softirq.c:613 [inline] invoke_softirq kernel/softirq.c:453 [inline] __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680 irq_exit_rcu+0x9/0x30 kernel/softirq.c:696 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1052 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1052 </IRQ> CVE-2025-39913 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-39913.html CVE-2025-39913 https://bugzilla.suse.com/1250705 SUSE Bug 1250705 In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: Fix missing pointer check in hda_component_manager_init function The __component_match_add function may assign the 'matchptr' pointer the value ERR_PTR(-ENOMEM), which will subsequently be dereferenced. The call stack leading to the error looks like this: hda_component_manager_init |-> component_match_add |-> component_match_add_release |-> __component_match_add ( ... ,**matchptr, ... ) |-> *matchptr = ERR_PTR(-ENOMEM); // assign |-> component_master_add_with_match( ... match) |-> component_match_realloc(match, match->num); // dereference Add IS_ERR() check to prevent the crash. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2025-40097 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40097.html CVE-2025-40097 https://bugzilla.suse.com/1252900 SUSE Bug 1252900 In the Linux kernel, the following vulnerability has been resolved: comedi: fix divide-by-zero in comedi_buf_munge() The comedi_buf_munge() function performs a modulo operation `async->munge_chan %= async->cmd.chanlist_len` without first checking if chanlist_len is zero. If a user program submits a command with chanlist_len set to zero, this causes a divide-by-zero error when the device processes data in the interrupt handler path. Add a check for zero chanlist_len at the beginning of the function, similar to the existing checks for !map and CMDF_RAWDATA flag. When chanlist_len is zero, update munge_count and return early, indicating the data was handled without munging. This prevents potential kernel panics from malformed user commands. CVE-2025-40106 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40106.html CVE-2025-40106 https://bugzilla.suse.com/1252891 SUSE Bug 1252891 In the Linux kernel, the following vulnerability has been resolved: ASoC: Intel: sof_sdw: Prevent jump to NULL add_sidecar callback In create_sdw_dailink() check that sof_end->codec_info->add_sidecar is not NULL before calling it. The original code assumed that if include_sidecar is true, the codec on that link has an add_sidecar callback. But there could be other codecs on the same link that do not have an add_sidecar callback. CVE-2025-40132 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40132.html CVE-2025-40132 https://bugzilla.suse.com/1253330 SUSE Bug 1253330 In the Linux kernel, the following vulnerability has been resolved: crypto: hisilicon/qm - request reserved interrupt for virtual function The device interrupt vector 3 is an error interrupt for physical function and a reserved interrupt for virtual function. However, the driver has not registered the reserved interrupt for virtual function. When allocating interrupts, the number of interrupts is allocated based on powers of two, which includes this interrupt. When the system enables GICv4 and the virtual function passthrough to the virtual machine, releasing the interrupt in the driver triggers a warning. The WARNING report is: WARNING: CPU: 62 PID: 14889 at arch/arm64/kvm/vgic/vgic-its.c:852 its_free_ite+0x94/0xb4 Therefore, register a reserved interrupt for VF and set the IRQF_NO_AUTOEN flag to avoid that warning. CVE-2025-40136 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40136.html CVE-2025-40136 https://bugzilla.suse.com/1253340 SUSE Bug 1253340 In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Disable bottom softirqs as part of spin_lock_irq() on PREEMPT_RT snd_pcm_group_lock_irq() acquires a spinlock_t and disables interrupts via spin_lock_irq(). This also implicitly disables the handling of softirqs such as TIMER_SOFTIRQ. On PREEMPT_RT softirqs are preemptible and spin_lock_irq() does not disable them. That means a timer can be invoked during spin_lock_irq() on the same CPU. Due to synchronisations reasons local_bh_disable() has a per-CPU lock named softirq_ctrl.lock which synchronizes individual softirq against each other. syz-bot managed to trigger a lockdep report where softirq_ctrl.lock is acquired in hrtimer_cancel() in addition to hrtimer_run_softirq(). This is a possible deadlock. The softirq_ctrl.lock can not be made part of spin_lock_irq() as this would lead to too much synchronisation against individual threads on the system. To avoid the possible deadlock, softirqs must be manually disabled before the lock is acquired. Disable softirqs before the lock is acquired on PREEMPT_RT. CVE-2025-40142 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40142.html CVE-2025-40142 https://bugzilla.suse.com/1253348 SUSE Bug 1253348 In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Check GuC running state before deregistering exec queue In normal operation, a registered exec queue is disabled and deregistered through the GuC, and freed only after the GuC confirms completion. However, if the driver is forced to unbind while the exec queue is still running, the user may call exec_destroy() after the GuC has already been stopped and CT communication disabled. In this case, the driver cannot receive a response from the GuC, preventing proper cleanup of exec queue resources. Fix this by directly releasing the resources when GuC is not running. Here is the failure dmesg log: " [ 468.089581] ---[ end trace 0000000000000000 ]--- [ 468.089608] pci 0000:03:00.0: [drm] *ERROR* GT0: GUC ID manager unclean (1/65535) [ 468.090558] pci 0000:03:00.0: [drm] GT0: total 65535 [ 468.090562] pci 0000:03:00.0: [drm] GT0: used 1 [ 468.090564] pci 0000:03:00.0: [drm] GT0: range 1..1 (1) [ 468.092716] ------------[ cut here ]------------ [ 468.092719] WARNING: CPU: 14 PID: 4775 at drivers/gpu/drm/xe/xe_ttm_vram_mgr.c:298 ttm_vram_mgr_fini+0xf8/0x130 [xe] " v2: use xe_uc_fw_is_running() instead of xe_guc_ct_enabled(). As CT may go down and come back during VF migration. (cherry picked from commit 9b42321a02c50a12b2beb6ae9469606257fbecea) CVE-2025-40166 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40166.html CVE-2025-40166 https://bugzilla.suse.com/1253433 SUSE Bug 1253433 In the Linux kernel, the following vulnerability has been resolved: accel/qaic: Fix bootlog initialization ordering As soon as we queue MHI buffers to receive the bootlog from the device, we could be receiving data. Therefore all the resources needed to process that data need to be setup prior to queuing the buffers. We currently initialize some of the resources after queuing the buffers which creates a race between the probe() and any data that comes back from the device. If the uninitialized resources are accessed, we could see page faults. Fix the init ordering to close the race. CVE-2025-40177 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40177.html CVE-2025-40177 https://bugzilla.suse.com/1253443 SUSE Bug 1253443 In the Linux kernel, the following vulnerability has been resolved: x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP When running as an SNP or TDX guest under KVM, force the legacy PCI hole, i.e. memory between Top of Lower Usable DRAM and 4GiB, to be mapped as UC via a forced variable MTRR range. In most KVM-based setups, legacy devices such as the HPET and TPM are enumerated via ACPI. ACPI enumeration includes a Memory32Fixed entry, and optionally a SystemMemory descriptor for an OperationRegion, e.g. if the device needs to be accessed via a Control Method. If a SystemMemory entry is present, then the kernel's ACPI driver will auto-ioremap the region so that it can be accessed at will. However, the ACPI spec doesn't provide a way to enumerate the memory type of SystemMemory regions, i.e. there's no way to tell software that a region must be mapped as UC vs. WB, etc. As a result, Linux's ACPI driver always maps SystemMemory regions using ioremap_cache(), i.e. as WB on x86. The dedicated device drivers however, e.g. the HPET driver and TPM driver, want to map their associated memory as UC or WC, as accessing PCI devices using WB is unsupported. On bare metal and non-CoCO, the conflicting requirements "work" as firmware configures the PCI hole (and other device memory) to be UC in the MTRRs. So even though the ACPI mappings request WB, they are forced to UC- in the kernel's tracking due to the kernel properly handling the MTRR overrides, and thus are compatible with the drivers' requested WC/UC-. With force WB MTRRs on SNP and TDX guests, the ACPI mappings get their requested WB if the ACPI mappings are established before the dedicated driver code attempts to initialize the device. E.g. if acpi_init() runs before the corresponding device driver is probed, ACPI's WB mapping will "win", and result in the driver's ioremap() failing because the existing WB mapping isn't compatible with the requested WC/UC-. E.g. when a TPM is emulated by the hypervisor (ignoring the security implications of relying on what is allegedly an untrusted entity to store measurements), the TPM driver will request UC and fail: [ 1.730459] ioremap error for 0xfed40000-0xfed45000, requested 0x2, got 0x0 [ 1.732780] tpm_tis MSFT0101:00: probe with driver tpm_tis failed with error -12 Note, the '0x2' and '0x0' values refer to "enum page_cache_mode", not x86's memtypes (which frustratingly are an almost pure inversion; 2 == WB, 0 == UC). E.g. tracing mapping requests for TPM TIS yields: Mapping TPM TIS with req_type = 0 WARNING: CPU: 22 PID: 1 at arch/x86/mm/pat/memtype.c:530 memtype_reserve+0x2ab/0x460 Modules linked in: CPU: 22 UID: 0 PID: 1 Comm: swapper/0 Tainted: G W 6.16.0-rc7+ #2 VOLUNTARY Tainted: [W]=WARN Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/29/2025 RIP: 0010:memtype_reserve+0x2ab/0x460 __ioremap_caller+0x16d/0x3d0 ioremap_cache+0x17/0x30 x86_acpi_os_ioremap+0xe/0x20 acpi_os_map_iomem+0x1f3/0x240 acpi_os_map_memory+0xe/0x20 acpi_ex_system_memory_space_handler+0x273/0x440 acpi_ev_address_space_dispatch+0x176/0x4c0 acpi_ex_access_region+0x2ad/0x530 acpi_ex_field_datum_io+0xa2/0x4f0 acpi_ex_extract_from_field+0x296/0x3e0 acpi_ex_read_data_from_field+0xd1/0x460 acpi_ex_resolve_node_to_value+0x2ee/0x530 acpi_ex_resolve_to_value+0x1f2/0x540 acpi_ds_evaluate_name_path+0x11b/0x190 acpi_ds_exec_end_op+0x456/0x960 acpi_ps_parse_loop+0x27a/0xa50 acpi_ps_parse_aml+0x226/0x600 acpi_ps_execute_method+0x172/0x3e0 acpi_ns_evaluate+0x175/0x5f0 acpi_evaluate_object+0x213/0x490 acpi_evaluate_integer+0x6d/0x140 acpi_bus_get_status+0x93/0x150 acpi_add_single_object+0x43a/0x7c0 acpi_bus_check_add+0x149/0x3a0 acpi_bus_check_add_1+0x16/0x30 acpi_ns_walk_namespace+0x22c/0x360 acpi_walk_namespace+0x15c/0x170 acpi_bus_scan+0x1dd/0x200 acpi_scan_init+0xe5/0x2b0 acpi_init+0x264/0x5b0 do_one_i ---truncated--- CVE-2025-40181 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40181.html CVE-2025-40181 https://bugzilla.suse.com/1253471 SUSE Bug 1253471 In the Linux kernel, the following vulnerability has been resolved: ipmi: Rework user message limit handling The limit on the number of user messages had a number of issues, improper counting in some cases and a use after free. Restructure how this is all done to handle more in the receive message allocation routine, so all refcouting and user message limit counts are done in that routine. It's a lot cleaner and safer. CVE-2025-40202 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40202.html CVE-2025-40202 https://bugzilla.suse.com/1253451 SUSE Bug 1253451 In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix IPsec cleanup over MPV device When we do mlx5e_detach_netdev() we eventually disable blocking events notifier, among those events are IPsec MPV events from IB to core. So before disabling those blocking events, make sure to also unregister the devcom device and mark all this device operations as complete, in order to prevent the other device from using invalid netdev during future devcom events which could cause the trace below. BUG: kernel NULL pointer dereference, address: 0000000000000010 PGD 146427067 P4D 146427067 PUD 146488067 PMD 0 Oops: Oops: 0000 [#1] SMP CPU: 1 UID: 0 PID: 7735 Comm: devlink Tainted: GW 6.12.0-rc6_for_upstream_min_debug_2024_11_08_00_46 #1 Tainted: [W]=WARN Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:mlx5_devcom_comp_set_ready+0x5/0x40 [mlx5_core] Code: 00 01 48 83 05 23 32 1e 00 01 41 b8 ed ff ff ff e9 60 ff ff ff 48 83 05 00 32 1e 00 01 eb e3 66 0f 1f 44 00 00 0f 1f 44 00 00 <48> 8b 47 10 48 83 05 5f 32 1e 00 01 48 8b 50 40 48 85 d2 74 05 40 RSP: 0018:ffff88811a5c35f8 EFLAGS: 00010206 RAX: ffff888106e8ab80 RBX: ffff888107d7e200 RCX: ffff88810d6f0a00 RDX: ffff88810d6f0a00 RSI: 0000000000000001 RDI: 0000000000000000 RBP: ffff88811a17e620 R08: 0000000000000040 R09: 0000000000000000 R10: ffff88811a5c3618 R11: 0000000de85d51bd R12: ffff88811a17e600 R13: ffff88810d6f0a00 R14: 0000000000000000 R15: ffff8881034bda80 FS: 00007f27bdf89180(0000) GS:ffff88852c880000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000010 CR3: 000000010f159005 CR4: 0000000000372eb0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? __die+0x20/0x60 ? page_fault_oops+0x150/0x3e0 ? exc_page_fault+0x74/0x130 ? asm_exc_page_fault+0x22/0x30 ? mlx5_devcom_comp_set_ready+0x5/0x40 [mlx5_core] mlx5e_devcom_event_mpv+0x42/0x60 [mlx5_core] mlx5_devcom_send_event+0x8c/0x170 [mlx5_core] blocking_event+0x17b/0x230 [mlx5_core] notifier_call_chain+0x35/0xa0 blocking_notifier_call_chain+0x3d/0x60 mlx5_blocking_notifier_call_chain+0x22/0x30 [mlx5_core] mlx5_core_mp_event_replay+0x12/0x20 [mlx5_core] mlx5_ib_bind_slave_port+0x228/0x2c0 [mlx5_ib] mlx5_ib_stage_init_init+0x664/0x9d0 [mlx5_ib] ? idr_alloc_cyclic+0x50/0xb0 ? __kmalloc_cache_noprof+0x167/0x340 ? __kmalloc_noprof+0x1a7/0x430 __mlx5_ib_add+0x34/0xd0 [mlx5_ib] mlx5r_probe+0xe9/0x310 [mlx5_ib] ? kernfs_add_one+0x107/0x150 ? __mlx5_ib_add+0xd0/0xd0 [mlx5_ib] auxiliary_bus_probe+0x3e/0x90 really_probe+0xc5/0x3a0 ? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 bus_probe_device+0x86/0xa0 device_add+0x62d/0x830 __auxiliary_device_add+0x3b/0xa0 ? auxiliary_device_init+0x41/0x90 add_adev+0xd1/0x150 [mlx5_core] mlx5_rescan_drivers_locked+0x21c/0x300 [mlx5_core] esw_mode_change+0x6c/0xc0 [mlx5_core] mlx5_devlink_eswitch_mode_set+0x21e/0x640 [mlx5_core] devlink_nl_eswitch_set_doit+0x60/0xe0 genl_family_rcv_msg_doit+0xd0/0x120 genl_rcv_msg+0x180/0x2b0 ? devlink_get_from_attrs_lock+0x170/0x170 ? devlink_nl_eswitch_get_doit+0x290/0x290 ? devlink_nl_pre_doit_port_optional+0x50/0x50 ? genl_family_rcv_msg_dumpit+0xf0/0xf0 netlink_rcv_skb+0x54/0x100 genl_rcv+0x24/0x40 netlink_unicast+0x1fc/0x2d0 netlink_sendmsg+0x1e4/0x410 __sock_sendmsg+0x38/0x60 ? sockfd_lookup_light+0x12/0x60 __sys_sendto+0x105/0x160 ? __sys_recvmsg+0x4e/0x90 __x64_sys_sendto+0x20/0x30 do_syscall_64+0x4c/0x100 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f27bc91b13a Code: bb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 8b 05 fa 96 2c 00 45 89 c9 4c 63 d1 48 63 ff 85 c0 75 15 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff ---truncated--- CVE-2025-40238 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40238.html CVE-2025-40238 https://bugzilla.suse.com/1254871 SUSE Bug 1254871 In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: remove never-working support for setting nsh fields The validation of the set(nsh(...)) action is completely wrong. It runs through the nsh_key_put_from_nlattr() function that is the same function that validates NSH keys for the flow match and the push_nsh() action. However, the set(nsh(...)) has a very different memory layout. Nested attributes in there are doubled in size in case of the masked set(). That makes proper validation impossible. There is also confusion in the code between the 'masked' flag, that says that the nested attributes are doubled in size containing both the value and the mask, and the 'is_mask' that says that the value we're parsing is the mask. This is causing kernel crash on trying to write into mask part of the match with SW_FLOW_KEY_PUT() during validation, while validate_nsh() doesn't allocate any memory for it: BUG: kernel NULL pointer dereference, address: 0000000000000018 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 1c2383067 P4D 1c2383067 PUD 20b703067 PMD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 8 UID: 0 Kdump: loaded Not tainted 6.17.0-rc4+ #107 PREEMPT(voluntary) RIP: 0010:nsh_key_put_from_nlattr+0x19d/0x610 [openvswitch] Call Trace: <TASK> validate_nsh+0x60/0x90 [openvswitch] validate_set.constprop.0+0x270/0x3c0 [openvswitch] __ovs_nla_copy_actions+0x477/0x860 [openvswitch] ovs_nla_copy_actions+0x8d/0x100 [openvswitch] ovs_packet_cmd_execute+0x1cc/0x310 [openvswitch] genl_family_rcv_msg_doit+0xdb/0x130 genl_family_rcv_msg+0x14b/0x220 genl_rcv_msg+0x47/0xa0 netlink_rcv_skb+0x53/0x100 genl_rcv+0x24/0x40 netlink_unicast+0x280/0x3b0 netlink_sendmsg+0x1f7/0x430 ____sys_sendmsg+0x36b/0x3a0 ___sys_sendmsg+0x87/0xd0 __sys_sendmsg+0x6d/0xd0 do_syscall_64+0x7b/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The third issue with this process is that while trying to convert the non-masked set into masked one, validate_set() copies and doubles the size of the OVS_KEY_ATTR_NSH as if it didn't have any nested attributes. It should be copying each nested attribute and doubling them in size independently. And the process must be properly reversed during the conversion back from masked to a non-masked variant during the flow dump. In the end, the only two outcomes of trying to use this action are either validation failure or a kernel crash. And if somehow someone manages to install a flow with such an action, it will most definitely not do what it is supposed to, since all the keys and the masks are mixed up. Fixing all the issues is a complex task as it requires re-writing most of the validation code. Given that and the fact that this functionality never worked since introduction, let's just remove it altogether. It's better to re-introduce it later with a proper implementation instead of trying to fix it in stable releases. CVE-2025-40254 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40254.html CVE-2025-40254 https://bugzilla.suse.com/1254852 SUSE Bug 1254852 In the Linux kernel, the following vulnerability has been resolved: mptcp: fix a race in mptcp_pm_del_add_timer() mptcp_pm_del_add_timer() can call sk_stop_timer_sync(sk, &entry->add_timer) while another might have free entry already, as reported by syzbot. Add RCU protection to fix this issue. Also change confusing add_timer variable with stop_timer boolean. syzbot report: BUG: KASAN: slab-use-after-free in __timer_delete_sync+0x372/0x3f0 kernel/time/timer.c:1616 Read of size 4 at addr ffff8880311e4150 by task kworker/1:1/44 CPU: 1 UID: 0 PID: 44 Comm: kworker/1:1 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025 Workqueue: events mptcp_worker 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 __timer_delete_sync+0x372/0x3f0 kernel/time/timer.c:1616 sk_stop_timer_sync+0x1b/0x90 net/core/sock.c:3631 mptcp_pm_del_add_timer+0x283/0x310 net/mptcp/pm.c:362 mptcp_incoming_options+0x1357/0x1f60 net/mptcp/options.c:1174 tcp_data_queue+0xca/0x6450 net/ipv4/tcp_input.c:5361 tcp_rcv_established+0x1335/0x2670 net/ipv4/tcp_input.c:6441 tcp_v4_do_rcv+0x98b/0xbf0 net/ipv4/tcp_ipv4.c:1931 tcp_v4_rcv+0x252a/0x2dc0 net/ipv4/tcp_ipv4.c:2374 ip_protocol_deliver_rcu+0x221/0x440 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x3bb/0x6f0 net/ipv4/ip_input.c:239 NF_HOOK+0x30c/0x3a0 include/linux/netfilter.h:318 NF_HOOK+0x30c/0x3a0 include/linux/netfilter.h:318 __netif_receive_skb_one_core net/core/dev.c:6079 [inline] __netif_receive_skb+0x143/0x380 net/core/dev.c:6192 process_backlog+0x31e/0x900 net/core/dev.c:6544 __napi_poll+0xb6/0x540 net/core/dev.c:7594 napi_poll net/core/dev.c:7657 [inline] net_rx_action+0x5f7/0xda0 net/core/dev.c:7784 handle_softirqs+0x22f/0x710 kernel/softirq.c:622 __do_softirq kernel/softirq.c:656 [inline] __local_bh_enable_ip+0x1a0/0x2e0 kernel/softirq.c:302 mptcp_pm_send_ack net/mptcp/pm.c:210 [inline] mptcp_pm_addr_send_ack+0x41f/0x500 net/mptcp/pm.c:-1 mptcp_pm_worker+0x174/0x320 net/mptcp/pm.c:1002 mptcp_worker+0xd5/0x1170 net/mptcp/protocol.c:2762 process_one_work kernel/workqueue.c:3263 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427 kthread+0x711/0x8a0 kernel/kthread.c:463 ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK> Allocated by task 44: kasan_save_stack mm/kasan/common.c:56 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:77 poison_kmalloc_redzone mm/kasan/common.c:400 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:417 kasan_kmalloc include/linux/kasan.h:262 [inline] __kmalloc_cache_noprof+0x1ef/0x6c0 mm/slub.c:5748 kmalloc_noprof include/linux/slab.h:957 [inline] mptcp_pm_alloc_anno_list+0x104/0x460 net/mptcp/pm.c:385 mptcp_pm_create_subflow_or_signal_addr+0xf9d/0x1360 net/mptcp/pm_kernel.c:355 mptcp_pm_nl_fully_established net/mptcp/pm_kernel.c:409 [inline] __mptcp_pm_kernel_worker+0x417/0x1ef0 net/mptcp/pm_kernel.c:1529 mptcp_pm_worker+0x1ee/0x320 net/mptcp/pm.c:1008 mptcp_worker+0xd5/0x1170 net/mptcp/protocol.c:2762 process_one_work kernel/workqueue.c:3263 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427 kthread+0x711/0x8a0 kernel/kthread.c:463 ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 Freed by task 6630: kasan_save_stack mm/kasan/common.c:56 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:77 __kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:587 kasan_save_free_info mm/kasan/kasan.h:406 [inline] poison_slab_object m ---truncated--- CVE-2025-40257 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40257.html CVE-2025-40257 https://bugzilla.suse.com/1254842 SUSE Bug 1254842 https://bugzilla.suse.com/1257242 SUSE Bug 1257242 In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Do not sleep in atomic context sg_finish_rem_req() calls blk_rq_unmap_user(). The latter function may sleep. Hence, call sg_finish_rem_req() with interrupts enabled instead of disabled. CVE-2025-40259 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40259.html CVE-2025-40259 https://bugzilla.suse.com/1254845 SUSE Bug 1254845 In the Linux kernel, the following vulnerability has been resolved: nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() nvme_fc_delete_assocation() waits for pending I/O to complete before returning, and an error can cause ->ioerr_work to be queued after cancel_work_sync() had been called. Move the call to cancel_work_sync() to be after nvme_fc_delete_association() to ensure ->ioerr_work is not running when the nvme_fc_ctrl object is freed. Otherwise the following can occur: [ 1135.911754] list_del corruption, ff2d24c8093f31f8->next is NULL [ 1135.917705] ------------[ cut here ]------------ [ 1135.922336] kernel BUG at lib/list_debug.c:52! [ 1135.926784] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 1135.931851] CPU: 48 UID: 0 PID: 726 Comm: kworker/u449:23 Kdump: loaded Not tainted 6.12.0 #1 PREEMPT(voluntary) [ 1135.943490] Hardware name: Dell Inc. PowerEdge R660/0HGTK9, BIOS 2.5.4 01/16/2025 [ 1135.950969] Workqueue: 0x0 (nvme-wq) [ 1135.954673] RIP: 0010:__list_del_entry_valid_or_report.cold+0xf/0x6f [ 1135.961041] Code: c7 c7 98 68 72 94 e8 26 45 fe ff 0f 0b 48 c7 c7 70 68 72 94 e8 18 45 fe ff 0f 0b 48 89 fe 48 c7 c7 80 69 72 94 e8 07 45 fe ff <0f> 0b 48 89 d1 48 c7 c7 a0 6a 72 94 48 89 c2 e8 f3 44 fe ff 0f 0b [ 1135.979788] RSP: 0018:ff579b19482d3e50 EFLAGS: 00010046 [ 1135.985015] RAX: 0000000000000033 RBX: ff2d24c8093f31f0 RCX: 0000000000000000 [ 1135.992148] RDX: 0000000000000000 RSI: ff2d24d6bfa1d0c0 RDI: ff2d24d6bfa1d0c0 [ 1135.999278] RBP: ff2d24c8093f31f8 R08: 0000000000000000 R09: ffffffff951e2b08 [ 1136.006413] R10: ffffffff95122ac8 R11: 0000000000000003 R12: ff2d24c78697c100 [ 1136.013546] R13: fffffffffffffff8 R14: 0000000000000000 R15: ff2d24c78697c0c0 [ 1136.020677] FS: 0000000000000000(0000) GS:ff2d24d6bfa00000(0000) knlGS:0000000000000000 [ 1136.028765] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1136.034510] CR2: 00007fd207f90b80 CR3: 000000163ea22003 CR4: 0000000000f73ef0 [ 1136.041641] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1136.048776] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 [ 1136.055910] PKRU: 55555554 [ 1136.058623] Call Trace: [ 1136.061074] <TASK> [ 1136.063179] ? show_trace_log_lvl+0x1b0/0x2f0 [ 1136.067540] ? show_trace_log_lvl+0x1b0/0x2f0 [ 1136.071898] ? move_linked_works+0x4a/0xa0 [ 1136.075998] ? __list_del_entry_valid_or_report.cold+0xf/0x6f [ 1136.081744] ? __die_body.cold+0x8/0x12 [ 1136.085584] ? die+0x2e/0x50 [ 1136.088469] ? do_trap+0xca/0x110 [ 1136.091789] ? do_error_trap+0x65/0x80 [ 1136.095543] ? __list_del_entry_valid_or_report.cold+0xf/0x6f [ 1136.101289] ? exc_invalid_op+0x50/0x70 [ 1136.105127] ? __list_del_entry_valid_or_report.cold+0xf/0x6f [ 1136.110874] ? asm_exc_invalid_op+0x1a/0x20 [ 1136.115059] ? __list_del_entry_valid_or_report.cold+0xf/0x6f [ 1136.120806] move_linked_works+0x4a/0xa0 [ 1136.124733] worker_thread+0x216/0x3a0 [ 1136.128485] ? __pfx_worker_thread+0x10/0x10 [ 1136.132758] kthread+0xfa/0x240 [ 1136.135904] ? __pfx_kthread+0x10/0x10 [ 1136.139657] ret_from_fork+0x31/0x50 [ 1136.143236] ? __pfx_kthread+0x10/0x10 [ 1136.146988] ret_from_fork_asm+0x1a/0x30 [ 1136.150915] </TASK> CVE-2025-40261 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40261.html CVE-2025-40261 https://bugzilla.suse.com/1254839 SUSE Bug 1254839 In the Linux kernel, the following vulnerability has been resolved: be2net: pass wrb_params in case of OS2BMC be_insert_vlan_in_pkt() is called with the wrb_params argument being NULL at be_send_pkt_to_bmc() call site. This may lead to dereferencing a NULL pointer when processing a workaround for specific packet, as commit bc0c3405abbb ("be2net: fix a Tx stall bug caused by a specific ipv6 packet") states. The correct way would be to pass the wrb_params from be_xmit(). CVE-2025-40264 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40264.html CVE-2025-40264 https://bugzilla.suse.com/1254835 SUSE Bug 1254835 In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in smb2_close_cached_fid() find_or_create_cached_dir() could grab a new reference after kref_put() had seen the refcount drop to zero but before cfid_list_lock is acquired in smb2_close_cached_fid(), leading to use-after-free. Switch to kref_put_lock() so cfid_release() is called with cfid_list_lock held, closing that gap. CVE-2025-40328 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40328.html CVE-2025-40328 https://bugzilla.suse.com/1254624 SUSE Bug 1254624 In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ XDP programs can change the layout of an xdp_buff through bpf_xdp_adjust_tail() and bpf_xdp_adjust_head(). Therefore, the driver cannot assume the size of the linear data area nor fragments. Fix the bug in mlx5 by generating skb according to xdp_buff after XDP programs run. Currently, when handling multi-buf XDP, the mlx5 driver assumes the layout of an xdp_buff to be unchanged. That is, the linear data area continues to be empty and fragments remain the same. This may cause the driver to generate erroneous skb or triggering a kernel warning. When an XDP program added linear data through bpf_xdp_adjust_head(), the linear data will be ignored as mlx5e_build_linear_skb() builds an skb without linear data and then pull data from fragments to fill the linear data area. When an XDP program has shrunk the non-linear data through bpf_xdp_adjust_tail(), the delta passed to __pskb_pull_tail() may exceed the actual nonlinear data size and trigger the BUG_ON in it. To fix the issue, first record the original number of fragments. If the number of fragments changes after the XDP program runs, rewind the end fragment pointer by the difference and recalculate the truesize. Then, build the skb with the linear data area matching the xdp_buff. Finally, only pull data in if there is non-linear data and fill the linear part up to 256 bytes. CVE-2025-40350 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40350.html CVE-2025-40350 https://bugzilla.suse.com/1255260 SUSE Bug 1255260 In the Linux kernel, the following vulnerability has been resolved: sysfs: check visibility before changing group attribute ownership Since commit 0c17270f9b92 ("net: sysfs: Implement is_visible for phys_(port_id, port_name, switch_id)"), __dev_change_net_namespace() can hit WARN_ON() when trying to change owner of a file that isn't visible. See the trace below: WARNING: CPU: 6 PID: 2938 at net/core/dev.c:12410 __dev_change_net_namespace+0xb89/0xc30 CPU: 6 UID: 0 PID: 2938 Comm: incusd Not tainted 6.17.1-1-mainline #1 PREEMPT(full) 4b783b4a638669fb644857f484487d17cb45ed1f Hardware name: Framework Laptop 13 (AMD Ryzen 7040Series)/FRANMDCP07, BIOS 03.07 02/19/2025 RIP: 0010:__dev_change_net_namespace+0xb89/0xc30 [...] Call Trace: <TASK> ? if6_seq_show+0x30/0x50 do_setlink.isra.0+0xc7/0x1270 ? __nla_validate_parse+0x5c/0xcc0 ? security_capable+0x94/0x1a0 rtnl_newlink+0x858/0xc20 ? update_curr+0x8e/0x1c0 ? update_entity_lag+0x71/0x80 ? sched_balance_newidle+0x358/0x450 ? psi_task_switch+0x113/0x2a0 ? __pfx_rtnl_newlink+0x10/0x10 rtnetlink_rcv_msg+0x346/0x3e0 ? sched_clock+0x10/0x30 ? __pfx_rtnetlink_rcv_msg+0x10/0x10 netlink_rcv_skb+0x59/0x110 netlink_unicast+0x285/0x3c0 ? __alloc_skb+0xdb/0x1a0 netlink_sendmsg+0x20d/0x430 ____sys_sendmsg+0x39f/0x3d0 ? import_iovec+0x2f/0x40 ___sys_sendmsg+0x99/0xe0 __sys_sendmsg+0x8a/0xf0 do_syscall_64+0x81/0x970 ? __sys_bind+0xe3/0x110 ? syscall_exit_work+0x143/0x1b0 ? do_syscall_64+0x244/0x970 ? sock_alloc_file+0x63/0xc0 ? syscall_exit_work+0x143/0x1b0 ? do_syscall_64+0x244/0x970 ? alloc_fd+0x12e/0x190 ? put_unused_fd+0x2a/0x70 ? do_sys_openat2+0xa2/0xe0 ? syscall_exit_work+0x143/0x1b0 ? do_syscall_64+0x244/0x970 ? exc_page_fault+0x7e/0x1a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e [...] </TASK> Fix this by checking is_visible() before trying to touch the attribute. CVE-2025-40355 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40355.html CVE-2025-40355 https://bugzilla.suse.com/1255261 SUSE Bug 1255261 In the Linux kernel, the following vulnerability has been resolved: net: ipv6: fix field-spanning memcpy warning in AH output Fix field-spanning memcpy warnings in ah6_output() and ah6_output_done() where extension headers are copied to/from IPv6 address fields, triggering fortify-string warnings about writes beyond the 16-byte address fields. memcpy: detected field-spanning write (size 40) of single field "&top_iph->saddr" at net/ipv6/ah6.c:439 (size 16) WARNING: CPU: 0 PID: 8838 at net/ipv6/ah6.c:439 ah6_output+0xe7e/0x14e0 net/ipv6/ah6.c:439 The warnings are false positives as the extension headers are intentionally placed after the IPv6 header in memory. Fix by properly copying addresses and extension headers separately, and introduce helper functions to avoid code duplication. CVE-2025-40363 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-40363.html CVE-2025-40363 https://bugzilla.suse.com/1255102 SUSE Bug 1255102 In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Ensure XFD state on signal delivery Sean reported [1] the following splat when running KVM tests: WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70 Call Trace: <TASK> fpu__clear_user_states+0x9c/0x100 arch_do_signal_or_restart+0x142/0x210 exit_to_user_mode_loop+0x55/0x100 do_syscall_64+0x205/0x2c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 Chao further identified [2] a reproducible scenario involving signal delivery: a non-AMX task is preempted by an AMX-enabled task which modifies the XFD MSR. When the non-AMX task resumes and reloads XSTATE with init values, a warning is triggered due to a mismatch between fpstate::xfd and the CPU's current XFD state. fpu__clear_user_states() does not currently re-synchronize the XFD state after such preemption. Invoke xfd_update_state() which detects and corrects the mismatch if there is a dynamic feature. This also benefits the sigreturn path, as fpu__restore_sig() may call fpu__clear_user_states() when the sigframe is inaccessible. [ dhansen: minor changelog munging ] CVE-2025-68171 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68171.html CVE-2025-68171 https://bugzilla.suse.com/1255255 SUSE Bug 1255255 In the Linux kernel, the following vulnerability has been resolved: amd/amdkfd: enhance kfd process check in switch partition current switch partition only check if kfd_processes_table is empty. kfd_prcesses_table entry is deleted in kfd_process_notifier_release, but kfd_process tear down is in kfd_process_wq_release. consider two processes: Process A (workqueue) -> kfd_process_wq_release -> Access kfd_node member Process B switch partition -> amdgpu_xcp_pre_partition_switch -> amdgpu_amdkfd_device_fini_sw -> kfd_node tear down. Process A and B may trigger a race as shown in dmesg log. This patch is to resolve the race by adding an atomic kfd_process counter kfd_processes_count, it increment as create kfd process, decrement as finish kfd_process_wq_release. v2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds and bug fix. (Philip Yang) [3966658.307702] divide error: 0000 [#1] SMP NOPTI [3966658.350818] i10nm_edac [3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted [3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu] [3966658.362839] nfit [3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu] [3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 <f7> be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00 [3966658.380967] x86_pkg_temp_thermal [3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246 [3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000 [3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00 [3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4 [3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000 [3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800 [3966658.391533] FS: 0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000 [3966658.391534] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0 [3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 [3966658.391536] PKRU: 55555554 [3966658.391536] Call Trace: [3966658.391674] deallocate_sdma_queue+0x38/0xa0 [amdgpu] [3966658.391762] process_termination_cpsch+0x1ed/0x480 [amdgpu] [3966658.399754] intel_powerclamp [3966658.402831] kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu] [3966658.402908] kfd_process_wq_release+0x1a/0x1a0 [amdgpu] [3966658.410516] coretemp [3966658.434016] process_one_work+0x1ad/0x380 [3966658.434021] worker_thread+0x49/0x310 [3966658.438963] kvm_intel [3966658.446041] ? process_one_work+0x380/0x380 [3966658.446045] kthread+0x118/0x140 [3966658.446047] ? __kthread_bind_mask+0x60/0x60 [3966658.446050] ret_from_fork+0x1f/0x30 [3966658.446053] Modules linked in: kpatch_20765354(OEK) [3966658.455310] kvm [3966658.464534] mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK) [3966658.473462] idxd_mdev [3966658.482306] kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo ---truncated--- CVE-2025-68174 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68174.html CVE-2025-68174 https://bugzilla.suse.com/1255327 SUSE Bug 1255327 In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix possible deadlock while configuring policy Following deadlock can be triggered easily by lockdep: WARNING: possible circular locking dependency detected 6.17.0-rc3-00124-ga12c2658ced0 #1665 Not tainted ------------------------------------------------------ check/1334 is trying to acquire lock: ff1100011d9d0678 (&q->sysfs_lock){+.+.}-{4:4}, at: blk_unregister_queue+0x53/0x180 but task is already holding lock: ff1100011d9d00e0 (&q->q_usage_counter(queue)#3){++++}-{0:0}, at: del_gendisk+0xba/0x110 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&q->q_usage_counter(queue)#3){++++}-{0:0}: blk_queue_enter+0x40b/0x470 blkg_conf_prep+0x7b/0x3c0 tg_set_limit+0x10a/0x3e0 cgroup_file_write+0xc6/0x420 kernfs_fop_write_iter+0x189/0x280 vfs_write+0x256/0x490 ksys_write+0x83/0x190 __x64_sys_write+0x21/0x30 x64_sys_call+0x4608/0x4630 do_syscall_64+0xdb/0x6b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e -> #1 (&q->rq_qos_mutex){+.+.}-{4:4}: __mutex_lock+0xd8/0xf50 mutex_lock_nested+0x2b/0x40 wbt_init+0x17e/0x280 wbt_enable_default+0xe9/0x140 blk_register_queue+0x1da/0x2e0 __add_disk+0x38c/0x5d0 add_disk_fwnode+0x89/0x250 device_add_disk+0x18/0x30 virtblk_probe+0x13a3/0x1800 virtio_dev_probe+0x389/0x610 really_probe+0x136/0x620 __driver_probe_device+0xb3/0x230 driver_probe_device+0x2f/0xe0 __driver_attach+0x158/0x250 bus_for_each_dev+0xa9/0x130 driver_attach+0x26/0x40 bus_add_driver+0x178/0x3d0 driver_register+0x7d/0x1c0 __register_virtio_driver+0x2c/0x60 virtio_blk_init+0x6f/0xe0 do_one_initcall+0x94/0x540 kernel_init_freeable+0x56a/0x7b0 kernel_init+0x2b/0x270 ret_from_fork+0x268/0x4c0 ret_from_fork_asm+0x1a/0x30 -> #0 (&q->sysfs_lock){+.+.}-{4:4}: __lock_acquire+0x1835/0x2940 lock_acquire+0xf9/0x450 __mutex_lock+0xd8/0xf50 mutex_lock_nested+0x2b/0x40 blk_unregister_queue+0x53/0x180 __del_gendisk+0x226/0x690 del_gendisk+0xba/0x110 sd_remove+0x49/0xb0 [sd_mod] device_remove+0x87/0xb0 device_release_driver_internal+0x11e/0x230 device_release_driver+0x1a/0x30 bus_remove_device+0x14d/0x220 device_del+0x1e1/0x5a0 __scsi_remove_device+0x1ff/0x2f0 scsi_remove_device+0x37/0x60 sdev_store_delete+0x77/0x100 dev_attr_store+0x1f/0x40 sysfs_kf_write+0x65/0x90 kernfs_fop_write_iter+0x189/0x280 vfs_write+0x256/0x490 ksys_write+0x83/0x190 __x64_sys_write+0x21/0x30 x64_sys_call+0x4608/0x4630 do_syscall_64+0xdb/0x6b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e other info that might help us debug this: Chain exists of: &q->sysfs_lock --> &q->rq_qos_mutex --> &q->q_usage_counter(queue)#3 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&q->q_usage_counter(queue)#3); lock(&q->rq_qos_mutex); lock(&q->q_usage_counter(queue)#3); lock(&q->sysfs_lock); Root cause is that queue_usage_counter is grabbed with rq_qos_mutex held in blkg_conf_prep(), while queue should be freezed before rq_qos_mutex from other context. The blk_queue_enter() from blkg_conf_prep() is used to protect against policy deactivation, which is already protected with blkcg_mutex, hence convert blk_queue_enter() to blkcg_mutex to fix this problem. Meanwhile, consider that blkcg_mutex is held after queue is freezed from policy deactivation, also convert blkg_alloc() to use GFP_NOIO. CVE-2025-68178 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68178.html CVE-2025-68178 https://bugzilla.suse.com/1255266 SUSE Bug 1255266 In the Linux kernel, the following vulnerability has been resolved: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() Use RCU to avoid a pair of atomic operations and a potential UAF on dst_dev()->flags. CVE-2025-68188 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68188.html CVE-2025-68188 https://bugzilla.suse.com/1255269 SUSE Bug 1255269 In the Linux kernel, the following vulnerability has been resolved: bpf: Add bpf_prog_run_data_pointers() syzbot found that cls_bpf_classify() is able to change tc_skb_cb(skb)->drop_reason triggering a warning in sk_skb_reason_drop(). WARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline] WARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214 struct tc_skb_cb has been added in commit ec624fe740b4 ("net/sched: Extend qdisc control block with tc control block"), which added a wrong interaction with db58ba459202 ("bpf: wire in data and data_end for cls_act_bpf"). drop_reason was added later. Add bpf_prog_run_data_pointers() helper to save/restore the net_sched storage colliding with BPF data_meta/data_end. CVE-2025-68200 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68200.html CVE-2025-68200 https://bugzilla.suse.com/1255241 SUSE Bug 1255241 In the Linux kernel, the following vulnerability has been resolved: ice: fix PTP cleanup on driver removal in error path Improve the cleanup on releasing PTP resources in error path. The error case might happen either at the driver probe and PTP feature initialization or on PTP restart (errors in reset handling, NVM update etc). In both cases, calls to PF PTP cleanup (ice_ptp_cleanup_pf function) and 'ps_lock' mutex deinitialization were missed. Additionally, ptp clock was not unregistered in the latter case. Keep PTP state as 'uninitialized' on init to distinguish between error scenarios and to avoid resource release duplication at driver removal. The consequence of missing ice_ptp_cleanup_pf call is the following call trace dumped when ice_adapter object is freed (port list is not empty, as it is required at this stage): [ T93022] ------------[ cut here ]------------ [ T93022] WARNING: CPU: 10 PID: 93022 at ice/ice_adapter.c:67 ice_adapter_put+0xef/0x100 [ice] ... [ T93022] RIP: 0010:ice_adapter_put+0xef/0x100 [ice] ... [ T93022] Call Trace: [ T93022] <TASK> [ T93022] ? ice_adapter_put+0xef/0x100 [ice 33d2647ad4f6d866d41eefff1806df37c68aef0c] [ T93022] ? __warn.cold+0xb0/0x10e [ T93022] ? ice_adapter_put+0xef/0x100 [ice 33d2647ad4f6d866d41eefff1806df37c68aef0c] [ T93022] ? report_bug+0xd8/0x150 [ T93022] ? handle_bug+0xe9/0x110 [ T93022] ? exc_invalid_op+0x17/0x70 [ T93022] ? asm_exc_invalid_op+0x1a/0x20 [ T93022] ? ice_adapter_put+0xef/0x100 [ice 33d2647ad4f6d866d41eefff1806df37c68aef0c] [ T93022] pci_device_remove+0x42/0xb0 [ T93022] device_release_driver_internal+0x19f/0x200 [ T93022] driver_detach+0x48/0x90 [ T93022] bus_remove_driver+0x70/0xf0 [ T93022] pci_unregister_driver+0x42/0xb0 [ T93022] ice_module_exit+0x10/0xdb0 [ice 33d2647ad4f6d866d41eefff1806df37c68aef0c] ... [ T93022] ---[ end trace 0000000000000000 ]--- [ T93022] ice: module unloaded CVE-2025-68215 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68215.html CVE-2025-68215 https://bugzilla.suse.com/1255226 SUSE Bug 1255226 In the Linux kernel, the following vulnerability has been resolved: mptcp: Fix proto fallback detection with BPF The sockmap feature allows bpf syscall from userspace, or based on bpf sockops, replacing the sk_prot of sockets during protocol stack processing with sockmap's custom read/write interfaces. ''' tcp_rcv_state_process() syn_recv_sock()/subflow_syn_recv_sock() tcp_init_transfer(BPF_SOCK_OPS_PASSIVE_ESTABLISHED_CB) bpf_skops_established <== sockops bpf_sock_map_update(sk) <== call bpf helper tcp_bpf_update_proto() <== update sk_prot ''' When the server has MPTCP enabled but the client sends a TCP SYN without MPTCP, subflow_syn_recv_sock() performs a fallback on the subflow, replacing the subflow sk's sk_prot with the native sk_prot. ''' subflow_syn_recv_sock() subflow_ulp_fallback() subflow_drop_ctx() mptcp_subflow_ops_undo_override() ''' Then, this subflow can be normally used by sockmap, which replaces the native sk_prot with sockmap's custom sk_prot. The issue occurs when the user executes accept::mptcp_stream_accept::mptcp_fallback_tcp_ops(). Here, it uses sk->sk_prot to compare with the native sk_prot, but this is incorrect when sockmap is used, as we may incorrectly set sk->sk_socket->ops. This fix uses the more generic sk_family for the comparison instead. Additionally, this also prevents a WARNING from occurring: result from ./scripts/decode_stacktrace.sh: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 337 at net/mptcp/protocol.c:68 mptcp_stream_accept \ (net/mptcp/protocol.c:4005) Modules linked in: ... PKRU: 55555554 Call Trace: <TASK> do_accept (net/socket.c:1989) __sys_accept4 (net/socket.c:2028 net/socket.c:2057) __x64_sys_accept (net/socket.c:2067) x64_sys_call (arch/x86/entry/syscall_64.c:41) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) RIP: 0033:0x7f87ac92b83d ---[ end trace 0000000000000000 ]--- CVE-2025-68227 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68227.html CVE-2025-68227 https://bugzilla.suse.com/1255216 SUSE Bug 1255216 In the Linux kernel, the following vulnerability has been resolved: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe The sit driver's packet transmission path calls: sit_tunnel_xmit() -> update_or_create_fnhe(), which lead to fnhe_remove_oldest() being called to delete entries exceeding FNHE_RECLAIM_DEPTH+random. The race window is between fnhe_remove_oldest() selecting fnheX for deletion and the subsequent kfree_rcu(). During this time, the concurrent path's __mkroute_output() -> find_exception() can fetch the soon-to-be-deleted fnheX, and rt_bind_exception() then binds it with a new dst using a dst_hold(). When the original fnheX is freed via RCU, the dst reference remains permanently leaked. CPU 0 CPU 1 __mkroute_output() find_exception() [fnheX] update_or_create_fnhe() fnhe_remove_oldest() [fnheX] rt_bind_exception() [bind dst] RCU callback [fnheX freed, dst leak] This issue manifests as a device reference count leak and a warning in dmesg when unregistering the net device: unregister_netdevice: waiting for sitX to become free. Usage count = N Ido Schimmel provided the simple test validation method [1]. The fix clears 'oldest->fnhe_daddr' before calling fnhe_flush_routes(). Since rt_bind_exception() checks this field, setting it to zero prevents the stale fnhe from being reused and bound to a new dst just before it is freed. [1] ip netns add ns1 ip -n ns1 link set dev lo up ip -n ns1 address add 192.0.2.1/32 dev lo ip -n ns1 link add name dummy1 up type dummy ip -n ns1 route add 192.0.2.2/32 dev dummy1 ip -n ns1 link add name gretap1 up arp off type gretap \ local 192.0.2.1 remote 192.0.2.2 ip -n ns1 route add 198.51.0.0/16 dev gretap1 taskset -c 0 ip netns exec ns1 mausezahn gretap1 \ -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q & taskset -c 2 ip netns exec ns1 mausezahn gretap1 \ -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q & sleep 10 ip netns pids ns1 | xargs kill ip netns del ns1 CVE-2025-68241 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68241.html CVE-2025-68241 https://bugzilla.suse.com/1255157 SUSE Bug 1255157 In the Linux kernel, the following vulnerability has been resolved: net: netpoll: fix incorrect refcount handling causing incorrect cleanup commit efa95b01da18 ("netpoll: fix use after free") incorrectly ignored the refcount and prematurely set dev->npinfo to NULL during netpoll cleanup, leading to improper behavior and memory leaks. Scenario causing lack of proper cleanup: 1) A netpoll is associated with a NIC (e.g., eth0) and netdev->npinfo is allocated, and refcnt = 1 - Keep in mind that npinfo is shared among all netpoll instances. In this case, there is just one. 2) Another netpoll is also associated with the same NIC and npinfo->refcnt += 1. - Now dev->npinfo->refcnt = 2; - There is just one npinfo associated to the netdev. 3) When the first netpolls goes to clean up: - The first cleanup succeeds and clears np->dev->npinfo, ignoring refcnt. - It basically calls `RCU_INIT_POINTER(np->dev->npinfo, NULL);` - Set dev->npinfo = NULL, without proper cleanup - No ->ndo_netpoll_cleanup() is either called 4) Now the second target tries to clean up - The second cleanup fails because np->dev->npinfo is already NULL. * In this case, ops->ndo_netpoll_cleanup() was never called, and the skb pool is not cleaned as well (for the second netpoll instance) - This leaks npinfo and skbpool skbs, which is clearly reported by kmemleak. Revert commit efa95b01da18 ("netpoll: fix use after free") and adds clarifying comments emphasizing that npinfo cleanup should only happen once the refcount reaches zero, ensuring stable and correct netpoll behavior. CVE-2025-68245 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68245.html CVE-2025-68245 https://bugzilla.suse.com/1255268 SUSE Bug 1255268 In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix out-of-bounds read in OnBeacon ESR IE parsing The Extended Supported Rates (ESR) IE handling in OnBeacon accessed *(p + 1 + ielen) and *(p + 2 + ielen) without verifying that these offsets lie within the received frame buffer. A malformed beacon with an ESR IE positioned at the end of the buffer could cause an out-of-bounds read, potentially triggering a kernel panic. Add a boundary check to ensure that the ESR IE body and the subsequent bytes are within the limits of the frame before attempting to access them. This prevents OOB reads caused by malformed beacon frames. CVE-2025-68254 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68254.html CVE-2025-68254 https://bugzilla.suse.com/1255140 SUSE Bug 1255140 In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix out-of-bounds read in rtw_get_ie() parser The Information Element (IE) parser rtw_get_ie() trusted the length byte of each IE without validating that the IE body (len bytes after the 2-byte header) fits inside the remaining frame buffer. A malformed frame can advertise an IE length larger than the available data, causing the parser to increment its pointer beyond the buffer end. This results in out-of-bounds reads or, depending on the pattern, an infinite loop. Fix by validating that (offset + 2 + len) does not exceed the limit before accepting the IE or advancing to the next element. This prevents OOB reads and ensures the parser terminates safely on malformed frames. CVE-2025-68256 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68256.html CVE-2025-68256 https://bugzilla.suse.com/1255138 SUSE Bug 1255138 In the Linux kernel, the following vulnerability has been resolved: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() Fix a race between inline data destruction and block mapping. The function ext4_destroy_inline_data_nolock() changes the inode data layout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS. At the same time, another thread may execute ext4_map_blocks(), which tests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks() or ext4_ind_map_blocks(). Without i_data_sem protection, ext4_ind_map_blocks() may receive inode with EXT4_INODE_EXTENTS flag and triggering assert. kernel BUG at fs/ext4/indirect.c:546! EXT4-fs (loop2): unmounting filesystem. invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 RIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546 Call Trace: <TASK> ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681 _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822 ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124 ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255 ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000 generic_perform_write+0x259/0x5d0 mm/filemap.c:3846 ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285 ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679 call_write_iter include/linux/fs.h:2271 [inline] do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735 do_iter_write+0x186/0x710 fs/read_write.c:861 vfs_iter_write+0x70/0xa0 fs/read_write.c:902 iter_file_splice_write+0x73b/0xc90 fs/splice.c:685 do_splice_from fs/splice.c:763 [inline] direct_splice_actor+0x10f/0x170 fs/splice.c:950 splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896 do_splice_direct+0x1a9/0x280 fs/splice.c:1002 do_sendfile+0xb13/0x12c0 fs/read_write.c:1255 __do_sys_sendfile64 fs/read_write.c:1323 [inline] __se_sys_sendfile64 fs/read_write.c:1309 [inline] __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 CVE-2025-68261 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68261.html CVE-2025-68261 https://bugzilla.suse.com/1255164 SUSE Bug 1255164 In the Linux kernel, the following vulnerability has been resolved: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() The len field originates from untrusted network packets. Boundary checks have been added to prevent potential out-of-bounds writes when decrypting the connection secret or processing service tickets. [ idryomov: changelog ] CVE-2025-68284 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68284.html CVE-2025-68284 https://bugzilla.suse.com/1255377 SUSE Bug 1255377 https://bugzilla.suse.com/1255378 SUSE Bug 1255378 In the Linux kernel, the following vulnerability has been resolved: libceph: fix potential use-after-free in have_mon_and_osd_map() The wait loop in __ceph_open_session() can race with the client receiving a new monmap or osdmap shortly after the initial map is received. Both ceph_monc_handle_map() and handle_one_map() install a new map immediately after freeing the old one kfree(monc->monmap); monc->monmap = monmap; ceph_osdmap_destroy(osdc->osdmap); osdc->osdmap = newmap; under client->monc.mutex and client->osdc.lock respectively, but because neither is taken in have_mon_and_osd_map() it's possible for client->monc.monmap->epoch and client->osdc.osdmap->epoch arms in client->monc.monmap && client->monc.monmap->epoch && client->osdc.osdmap && client->osdc.osdmap->epoch; condition to dereference an already freed map. This happens to be reproducible with generic/395 and generic/397 with KASAN enabled: BUG: KASAN: slab-use-after-free in have_mon_and_osd_map+0x56/0x70 Read of size 4 at addr ffff88811012d810 by task mount.ceph/13305 CPU: 2 UID: 0 PID: 13305 Comm: mount.ceph Not tainted 6.14.0-rc2-build2+ #1266 ... Call Trace: <TASK> have_mon_and_osd_map+0x56/0x70 ceph_open_session+0x182/0x290 ceph_get_tree+0x333/0x680 vfs_get_tree+0x49/0x180 do_new_mount+0x1a3/0x2d0 path_mount+0x6dd/0x730 do_mount+0x99/0xe0 __do_sys_mount+0x141/0x180 do_syscall_64+0x9f/0x100 entry_SYSCALL_64_after_hwframe+0x76/0x7e </TASK> Allocated by task 13305: ceph_osdmap_alloc+0x16/0x130 ceph_osdc_init+0x27a/0x4c0 ceph_create_client+0x153/0x190 create_fs_client+0x50/0x2a0 ceph_get_tree+0xff/0x680 vfs_get_tree+0x49/0x180 do_new_mount+0x1a3/0x2d0 path_mount+0x6dd/0x730 do_mount+0x99/0xe0 __do_sys_mount+0x141/0x180 do_syscall_64+0x9f/0x100 entry_SYSCALL_64_after_hwframe+0x76/0x7e Freed by task 9475: kfree+0x212/0x290 handle_one_map+0x23c/0x3b0 ceph_osdc_handle_map+0x3c9/0x590 mon_dispatch+0x655/0x6f0 ceph_con_process_message+0xc3/0xe0 ceph_con_v1_try_read+0x614/0x760 ceph_con_workfn+0x2de/0x650 process_one_work+0x486/0x7c0 process_scheduled_works+0x73/0x90 worker_thread+0x1c8/0x2a0 kthread+0x2ec/0x300 ret_from_fork+0x24/0x40 ret_from_fork_asm+0x1a/0x30 Rewrite the wait loop to check the above condition directly with client->monc.mutex and client->osdc.lock taken as appropriate. While at it, improve the timeout handling (previously mount_timeout could be exceeded in case wait_event_interruptible_timeout() slept more than once) and access client->auth_err under client->monc.mutex to match how it's set in finish_auth(). monmap_show() and osdmap_show() now take the respective lock before accessing the map as well. CVE-2025-68285 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68285.html CVE-2025-68285 https://bugzilla.suse.com/1255401 SUSE Bug 1255401 https://bugzilla.suse.com/1255402 SUSE Bug 1255402 In the Linux kernel, the following vulnerability has been resolved: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup Protect vga_switcheroo_client_fb_set() with console lock. Avoids OOB access in fbcon_remap_all(). Without holding the console lock the call races with switching outputs. VGA switcheroo calls fbcon_remap_all() when switching clients. The fbcon function uses struct fb_info.node, which is set by register_framebuffer(). As the fb-helper code currently sets up VGA switcheroo before registering the framebuffer, the value of node is -1 and therefore not a legal value. For example, fbcon uses the value within set_con2fb_map() [1] as an index into an array. Moving vga_switcheroo_client_fb_set() after register_framebuffer() can result in VGA switching that does not switch fbcon correctly. Therefore move vga_switcheroo_client_fb_set() under fbcon_fb_registered(), which already holds the console lock. Fbdev calls fbcon_fb_registered() from within register_framebuffer(). Serializes the helper with VGA switcheroo's call to fbcon_remap_all(). Although vga_switcheroo_client_fb_set() takes an instance of struct fb_info as parameter, it really only needs the contained fbcon state. Moving the call to fbcon initialization is therefore cleaner than before. Only amdgpu, i915, nouveau and radeon support vga_switcheroo. For all other drivers, this change does nothing. CVE-2025-68296 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68296.html CVE-2025-68296 https://bugzilla.suse.com/1255128 SUSE Bug 1255128 In the Linux kernel, the following vulnerability has been resolved: ceph: fix crash in process_v2_sparse_read() for encrypted directories The crash in process_v2_sparse_read() for fscrypt-encrypted directories has been reported. Issue takes place for Ceph msgr2 protocol in secure mode. It can be reproduced by the steps: sudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure (1) mkdir /mnt/cephfs/fscrypt-test-3 (2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3 (3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3 (4) fscrypt lock /mnt/cephfs/fscrypt-test-3 (5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3 (6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar (7) Issue has been triggered [ 408.072247] ------------[ cut here ]------------ [ 408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865 ceph_con_v2_try_read+0x4b39/0x72f0 [ 408.072267] Modules linked in: intel_rapl_msr intel_rapl_common intel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery pmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass polyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse serio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg pata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore [ 408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+ [ 408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-5.fc42 04/01/2014 [ 408.072310] Workqueue: ceph-msgr ceph_con_workfn [ 408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0 [ 408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8 8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff <0f> 0b e9 06 fe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85 [ 408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246 [ 408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38 [ 408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8 [ 408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8 [ 408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000 [ 408.072329] FS: 0000000000000000(0000) GS:ffff88823eadf000(0000) knlGS:0000000000000000 [ 408.072331] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0 [ 408.072336] PKRU: 55555554 [ 408.072337] Call Trace: [ 408.072338] <TASK> [ 408.072340] ? sched_clock_noinstr+0x9/0x10 [ 408.072344] ? __pfx_ceph_con_v2_try_read+0x10/0x10 [ 408.072347] ? _raw_spin_unlock+0xe/0x40 [ 408.072349] ? finish_task_switch.isra.0+0x15d/0x830 [ 408.072353] ? __kasan_check_write+0x14/0x30 [ 408.072357] ? mutex_lock+0x84/0xe0 [ 408.072359] ? __pfx_mutex_lock+0x10/0x10 [ 408.072361] ceph_con_workfn+0x27e/0x10e0 [ 408.072364] ? metric_delayed_work+0x311/0x2c50 [ 408.072367] process_one_work+0x611/0xe20 [ 408.072371] ? __kasan_check_write+0x14/0x30 [ 408.072373] worker_thread+0x7e3/0x1580 [ 408.072375] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 408.072378] ? __pfx_worker_thread+0x10/0x10 [ 408.072381] kthread+0x381/0x7a0 [ 408.072383] ? __pfx__raw_spin_lock_irq+0x10/0x10 [ 408.072385] ? __pfx_kthread+0x10/0x10 [ 408.072387] ? __kasan_check_write+0x14/0x30 [ 408.072389] ? recalc_sigpending+0x160/0x220 [ 408.072392] ? _raw_spin_unlock_irq+0xe/0x50 [ 408.072394] ? calculate_sigpending+0x78/0xb0 [ 408.072395] ? __pfx_kthread+0x10/0x10 [ 408.072397] ret_from_fork+0x2b6/0x380 [ 408.072400] ? __pfx_kthread+0x10/0x10 [ 408.072402] ret_from_fork_asm+0x1a/0x30 [ 408.072406] </TASK> [ 408.072407] ---[ end trace 0000000000000000 ]--- [ 408.072418] Oops: general protection fault, probably for non-canonical address 0xdffffc00000000 ---truncated--- CVE-2025-68297 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68297.html CVE-2025-68297 https://bugzilla.suse.com/1255403 SUSE Bug 1255403 In the Linux kernel, the following vulnerability has been resolved: net: atlantic: fix fragment overflow handling in RX path The atlantic driver can receive packets with more than MAX_SKB_FRAGS (17) fragments when handling large multi-descriptor packets. This causes an out-of-bounds write in skb_add_rx_frag_netmem() leading to kernel panic. The issue occurs because the driver doesn't check the total number of fragments before calling skb_add_rx_frag(). When a packet requires more than MAX_SKB_FRAGS fragments, the fragment index exceeds the array bounds. Fix by assuming there will be an extra frag if buff->len > AQ_CFG_RX_HDR_SIZE, then all fragments are accounted for. And reusing the existing check to prevent the overflow earlier in the code path. This crash occurred in production with an Aquantia AQC113 10G NIC. Stack trace from production environment: ``` RIP: 0010:skb_add_rx_frag_netmem+0x29/0xd0 Code: 90 f3 0f 1e fa 0f 1f 44 00 00 48 89 f8 41 89 ca 48 89 d7 48 63 ce 8b 90 c0 00 00 00 48 c1 e1 04 48 01 ca 48 03 90 c8 00 00 00 <48> 89 7a 30 44 89 52 3c 44 89 42 38 40 f6 c7 01 75 74 48 89 fa 83 RSP: 0018:ffffa9bec02a8d50 EFLAGS: 00010287 RAX: ffff925b22e80a00 RBX: ffff925ad38d2700 RCX: fffffffe0a0c8000 RDX: ffff9258ea95bac0 RSI: ffff925ae0a0c800 RDI: 0000000000037a40 RBP: 0000000000000024 R08: 0000000000000000 R09: 0000000000000021 R10: 0000000000000848 R11: 0000000000000000 R12: ffffa9bec02a8e24 R13: ffff925ad8615570 R14: 0000000000000000 R15: ffff925b22e80a00 FS: 0000000000000000(0000) GS:ffff925e47880000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff9258ea95baf0 CR3: 0000000166022004 CR4: 0000000000f72ef0 PKRU: 55555554 Call Trace: <IRQ> aq_ring_rx_clean+0x175/0xe60 [atlantic] ? aq_ring_rx_clean+0x14d/0xe60 [atlantic] ? aq_ring_tx_clean+0xdf/0x190 [atlantic] ? kmem_cache_free+0x348/0x450 ? aq_vec_poll+0x81/0x1d0 [atlantic] ? __napi_poll+0x28/0x1c0 ? net_rx_action+0x337/0x420 ``` Changes in v4: - Add Fixes: tag to satisfy patch validation requirements. Changes in v3: - Fix by assuming there will be an extra frag if buff->len > AQ_CFG_RX_HDR_SIZE, then all fragments are accounted for. CVE-2025-68301 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68301.html CVE-2025-68301 https://bugzilla.suse.com/1255120 SUSE Bug 1255120 In the Linux kernel, the following vulnerability has been resolved: lan966x: Fix sleeping in atomic context The following warning was seen when we try to connect using ssh to the device. BUG: sleeping function called from invalid context at kernel/locking/mutex.c:575 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 104, name: dropbear preempt_count: 1, expected: 0 INFO: lockdep is turned off. CPU: 0 UID: 0 PID: 104 Comm: dropbear Tainted: G W 6.18.0-rc2-00399-g6f1ab1b109b9-dirty #530 NONE Tainted: [W]=WARN Hardware name: Generic DT based system Call trace: unwind_backtrace from show_stack+0x10/0x14 show_stack from dump_stack_lvl+0x7c/0xac dump_stack_lvl from __might_resched+0x16c/0x2b0 __might_resched from __mutex_lock+0x64/0xd34 __mutex_lock from mutex_lock_nested+0x1c/0x24 mutex_lock_nested from lan966x_stats_get+0x5c/0x558 lan966x_stats_get from dev_get_stats+0x40/0x43c dev_get_stats from dev_seq_printf_stats+0x3c/0x184 dev_seq_printf_stats from dev_seq_show+0x10/0x30 dev_seq_show from seq_read_iter+0x350/0x4ec seq_read_iter from seq_read+0xfc/0x194 seq_read from proc_reg_read+0xac/0x100 proc_reg_read from vfs_read+0xb0/0x2b0 vfs_read from ksys_read+0x6c/0xec ksys_read from ret_fast_syscall+0x0/0x1c Exception stack(0xf0b11fa8 to 0xf0b11ff0) 1fa0: 00000001 00001000 00000008 be9048d8 00001000 00000001 1fc0: 00000001 00001000 00000008 00000003 be905920 0000001e 00000000 00000001 1fe0: 0005404c be9048c0 00018684 b6ec2cd8 It seems that we are using a mutex in a atomic context which is wrong. Change the mutex with a spinlock. CVE-2025-68320 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68320.html CVE-2025-68320 https://bugzilla.suse.com/1255172 SUSE Bug 1255172 In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop In cake_drop(), qdisc_tree_reduce_backlog() is used to update the qlen and backlog of the qdisc hierarchy. Its caller, cake_enqueue(), assumes that the parent qdisc will enqueue the current packet. However, this assumption breaks when cake_enqueue() returns NET_XMIT_CN: the parent qdisc stops enqueuing current packet, leaving the tree qlen/backlog accounting inconsistent. This mismatch can lead to a NULL dereference (e.g., when the parent Qdisc is qfq_qdisc). This patch computes the qlen/backlog delta in a more robust way by observing the difference before and after the series of cake_drop() calls, and then compensates the qdisc tree accounting if cake_enqueue() returns NET_XMIT_CN. To ensure correct compensation when ACK thinning is enabled, a new variable is introduced to keep qlen unchanged. CVE-2025-68325 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68325.html CVE-2025-68325 https://bugzilla.suse.com/1255417 SUSE Bug 1255417 In the Linux kernel, the following vulnerability has been resolved: usb: renesas_usbhs: Fix synchronous external abort on unbind A synchronous external abort occurs on the Renesas RZ/G3S SoC if unbind is executed after the configuration sequence described above: modprobe usb_f_ecm modprobe libcomposite modprobe configfs cd /sys/kernel/config/usb_gadget mkdir -p g1 cd g1 echo "0x1d6b" > idVendor echo "0x0104" > idProduct mkdir -p strings/0x409 echo "0123456789" > strings/0x409/serialnumber echo "Renesas." > strings/0x409/manufacturer echo "Ethernet Gadget" > strings/0x409/product mkdir -p functions/ecm.usb0 mkdir -p configs/c.1 mkdir -p configs/c.1/strings/0x409 echo "ECM" > configs/c.1/strings/0x409/configuration if [ ! -L configs/c.1/ecm.usb0 ]; then ln -s functions/ecm.usb0 configs/c.1 fi echo 11e20000.usb > UDC echo 11e20000.usb > /sys/bus/platform/drivers/renesas_usbhs/unbind The displayed trace is as follows: Internal error: synchronous external abort: 0000000096000010 [#1] SMP CPU: 0 UID: 0 PID: 188 Comm: sh Tainted: G M 6.17.0-rc7-next-20250922-00010-g41050493b2bd #55 PREEMPT Tainted: [M]=MACHINE_CHECK Hardware name: Renesas SMARC EVK version 2 based on r9a08g045s33 (DT) pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : usbhs_sys_function_pullup+0x10/0x40 [renesas_usbhs] lr : usbhsg_update_pullup+0x3c/0x68 [renesas_usbhs] sp : ffff8000838b3920 x29: ffff8000838b3920 x28: ffff00000d585780 x27: 0000000000000000 x26: 0000000000000000 x25: 0000000000000000 x24: ffff00000c3e3810 x23: ffff00000d5e5c80 x22: ffff00000d5e5d40 x21: 0000000000000000 x20: 0000000000000000 x19: ffff00000d5e5c80 x18: 0000000000000020 x17: 2e30303230316531 x16: 312d7968703a7968 x15: 3d454d414e5f4344 x14: 000000000000002c x13: 0000000000000000 x12: 0000000000000000 x11: ffff00000f358f38 x10: ffff00000f358db0 x9 : ffff00000b41f418 x8 : 0101010101010101 x7 : 7f7f7f7f7f7f7f7f x6 : fefefeff6364626d x5 : 8080808000000000 x4 : 000000004b5ccb9d x3 : 0000000000000000 x2 : 0000000000000000 x1 : ffff800083790000 x0 : ffff00000d5e5c80 Call trace: usbhs_sys_function_pullup+0x10/0x40 [renesas_usbhs] (P) usbhsg_pullup+0x4c/0x7c [renesas_usbhs] usb_gadget_disconnect_locked+0x48/0xd4 gadget_unbind_driver+0x44/0x114 device_remove+0x4c/0x80 device_release_driver_internal+0x1c8/0x224 device_release_driver+0x18/0x24 bus_remove_device+0xcc/0x10c device_del+0x14c/0x404 usb_del_gadget+0x88/0xc0 usb_del_gadget_udc+0x18/0x30 usbhs_mod_gadget_remove+0x24/0x44 [renesas_usbhs] usbhs_mod_remove+0x20/0x30 [renesas_usbhs] usbhs_remove+0x98/0xdc [renesas_usbhs] platform_remove+0x20/0x30 device_remove+0x4c/0x80 device_release_driver_internal+0x1c8/0x224 device_driver_detach+0x18/0x24 unbind_store+0xb4/0xb8 drv_attr_store+0x24/0x38 sysfs_kf_write+0x7c/0x94 kernfs_fop_write_iter+0x128/0x1b8 vfs_write+0x2ac/0x350 ksys_write+0x68/0xfc __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x110 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x34/0xf0 el0t_64_sync_handler+0xa0/0xe4 el0t_64_sync+0x198/0x19c Code: 7100003f 1a9f07e1 531c6c22 f9400001 (79400021) ---[ end trace 0000000000000000 ]--- note: sh[188] exited with irqs disabled note: sh[188] exited with preempt_count 1 The issue occurs because usbhs_sys_function_pullup(), which accesses the IP registers, is executed after the USBHS clocks have been disabled. The problem is reproducible on the Renesas RZ/G3S SoC starting with the addition of module stop in the clock enable/disable APIs. With module stop functionality enabled, a bus error is expected if a master accesses a module whose clock has been stopped and module stop activated. Disable the IP clocks at the end of remove. CVE-2025-68327 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68327.html CVE-2025-68327 https://bugzilla.suse.com/1255488 SUSE Bug 1255488 In the Linux kernel, the following vulnerability has been resolved: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted There's issue when file system corrupted: ------------[ cut here ]------------ kernel BUG at fs/jbd2/transaction.c:1289! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next RIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0 RSP: 0018:ffff888117aafa30 EFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534 RDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010 RBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028 R10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000 R13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0 Call Trace: <TASK> __ext4_journal_get_create_access+0x42/0x170 ext4_getblk+0x319/0x6f0 ext4_bread+0x11/0x100 ext4_append+0x1e6/0x4a0 ext4_init_new_dir+0x145/0x1d0 ext4_mkdir+0x326/0x920 vfs_mkdir+0x45c/0x740 do_mkdirat+0x234/0x2f0 __x64_sys_mkdir+0xd6/0x120 do_syscall_64+0x5f/0xfa0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The above issue occurs with us in errors=continue mode when accompanied by storage failures. There have been many inconsistencies in the file system data. In the case of file system data inconsistency, for example, if the block bitmap of a referenced block is not set, it can lead to the situation where a block being committed is allocated and used again. As a result, the following condition will not be satisfied then trigger BUG_ON. Of course, it is entirely possible to construct a problematic image that can trigger this BUG_ON through specific operations. In fact, I have constructed such an image and easily reproduced this issue. Therefore, J_ASSERT() holds true only under ideal conditions, but it may not necessarily be satisfied in exceptional scenarios. Using J_ASSERT() directly in abnormal situations would cause the system to crash, which is clearly not what we want. So here we directly trigger a JBD abort instead of immediately invoking BUG_ON. CVE-2025-68337 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68337.html CVE-2025-68337 https://bugzilla.suse.com/1255482 SUSE Bug 1255482 In the Linux kernel, the following vulnerability has been resolved: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid Fixes a crash when layout is null during this call stack: write_inode -> nfs4_write_inode -> pnfs_layoutcommit_inode pnfs_set_layoutcommit relies on the lseg refcount to keep the layout around. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt to reference a null layout. CVE-2025-68349 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68349.html CVE-2025-68349 https://bugzilla.suse.com/1255544 SUSE Bug 1255544 In the Linux kernel, the following vulnerability has been resolved: bpf: Check skb->transport_header is set in bpf_skb_check_mtu The bpf_skb_check_mtu helper needs to use skb->transport_header when the BPF_MTU_CHK_SEGS flag is used: bpf_skb_check_mtu(skb, ifindex, &mtu_len, 0, BPF_MTU_CHK_SEGS) The transport_header is not always set. There is a WARN_ON_ONCE report when CONFIG_DEBUG_NET is enabled + skb->gso_size is set + bpf_prog_test_run is used: WARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071 skb_gso_validate_network_len bpf_skb_check_mtu bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch bpf_test_run bpf_prog_test_run_skb For a normal ingress skb (not test_run), skb_reset_transport_header is performed but there is plan to avoid setting it as described in commit 2170a1f09148 ("net: no longer reset transport_header in __netif_receive_skb_core()"). This patch fixes the bpf helper by checking skb_transport_header_was_set(). The check is done just before skb->transport_header is used, to avoid breaking the existing bpf prog. The WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next. CVE-2025-68363 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68363.html CVE-2025-68363 https://bugzilla.suse.com/1255552 SUSE Bug 1255552 In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Initialize allocated memory before use KMSAN reports: Multiple uninitialized values detected: - KMSAN: uninit-value in ntfs_read_hdr (3) - KMSAN: uninit-value in bcmp (3) Memory is allocated by __getname(), which is a wrapper for kmem_cache_alloc(). This memory is used before being properly cleared. Change kmem_cache_alloc() to kmem_cache_zalloc() to properly allocate and clear memory before use. CVE-2025-68365 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68365.html CVE-2025-68365 https://bugzilla.suse.com/1255548 SUSE Bug 1255548 In the Linux kernel, the following vulnerability has been resolved: nbd: defer config unlock in nbd_genl_connect There is one use-after-free warning when running NBD_CMD_CONNECT and NBD_CLEAR_SOCK: nbd_genl_connect nbd_alloc_and_init_config // config_refs=1 nbd_start_device // config_refs=2 set NBD_RT_HAS_CONFIG_REF open nbd // config_refs=3 recv_work done // config_refs=2 NBD_CLEAR_SOCK // config_refs=1 close nbd // config_refs=0 refcount_inc -> uaf ------------[ cut here ]------------ refcount_t: addition on 0; use-after-free. WARNING: CPU: 24 PID: 1014 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x290 nbd_genl_connect+0x16d0/0x1ab0 genl_family_rcv_msg_doit+0x1f3/0x310 genl_rcv_msg+0x44a/0x790 The issue can be easily reproduced by adding a small delay before refcount_inc(&nbd->config_refs) in nbd_genl_connect(): mutex_unlock(&nbd->config_lock); if (!ret) { set_bit(NBD_RT_HAS_CONFIG_REF, &config->runtime_flags); + printk("before sleep\n"); + mdelay(5 * 1000); + printk("after sleep\n"); refcount_inc(&nbd->config_refs); nbd_connect_reply(info, nbd->index); } CVE-2025-68366 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68366.html CVE-2025-68366 https://bugzilla.suse.com/1255622 SUSE Bug 1255622 In the Linux kernel, the following vulnerability has been resolved: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse The following warning appears when running syzkaller, and this issue also exists in the mainline code. ------------[ cut here ]------------ list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100. WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130 Modules linked in: CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:__list_add_valid_or_report+0xf7/0x130 RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817 RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001 RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100 R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48 FS: 00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 80000000 Call Trace: <TASK> input_register_handler+0xb3/0x210 mac_hid_start_emulation+0x1c5/0x290 mac_hid_toggle_emumouse+0x20a/0x240 proc_sys_call_handler+0x4c2/0x6e0 new_sync_write+0x1b1/0x2d0 vfs_write+0x709/0x950 ksys_write+0x12a/0x250 do_syscall_64+0x5a/0x110 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The WARNING occurs when two processes concurrently write to the mac-hid emulation sysctl, causing a race condition in mac_hid_toggle_emumouse(). Both processes read old_val=0, then both try to register the input handler, leading to a double list_add of the same handler. CPU0 CPU1 ------------------------- ------------------------- vfs_write() //write 1 vfs_write() //write 1 proc_sys_write() proc_sys_write() mac_hid_toggle_emumouse() mac_hid_toggle_emumouse() old_val = *valp // old_val=0 old_val = *valp // old_val=0 mutex_lock_killable() proc_dointvec() // *valp=1 mac_hid_start_emulation() input_register_handler() mutex_unlock() mutex_lock_killable() proc_dointvec() mac_hid_start_emulation() input_register_handler() //Trigger Warning mutex_unlock() Fix this by moving the old_val read inside the mutex lock region. CVE-2025-68367 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68367.html CVE-2025-68367 https://bugzilla.suse.com/1255547 SUSE Bug 1255547 In the Linux kernel, the following vulnerability has been resolved: nbd: defer config put in recv_work There is one uaf issue in recv_work when running NBD_CLEAR_SOCK and NBD_CMD_RECONFIGURE: nbd_genl_connect // conf_ref=2 (connect and recv_work A) nbd_open // conf_ref=3 recv_work A done // conf_ref=2 NBD_CLEAR_SOCK // conf_ref=1 nbd_genl_reconfigure // conf_ref=2 (trigger recv_work B) close nbd // conf_ref=1 recv_work B config_put // conf_ref=0 atomic_dec(&config->recv_threads); -> UAF Or only running NBD_CLEAR_SOCK: nbd_genl_connect // conf_ref=2 nbd_open // conf_ref=3 NBD_CLEAR_SOCK // conf_ref=2 close nbd nbd_release config_put // conf_ref=1 recv_work config_put // conf_ref=0 atomic_dec(&config->recv_threads); -> UAF Commit 87aac3a80af5 ("nbd: call nbd_config_put() before notifying the waiter") moved nbd_config_put() to run before waking up the waiter in recv_work, in order to ensure that nbd_start_device_ioctl() would not be woken up while nbd->task_recv was still uncleared. However, in nbd_start_device_ioctl(), after being woken up it explicitly calls flush_workqueue() to make sure all current works are finished. Therefore, there is no need to move the config put ahead of the wakeup. Move nbd_config_put() to the end of recv_work, so that the reference is held for the whole lifetime of the worker thread. This makes sure the config cannot be freed while recv_work is still running, even if clear + reconfigure interleave. In addition, we don't need to worry about recv_work dropping the last nbd_put (which causes deadlock): path A (netlink with NBD_CFLAG_DESTROY_ON_DISCONNECT): connect // nbd_refs=1 (trigger recv_work) open nbd // nbd_refs=2 NBD_CLEAR_SOCK close nbd nbd_release nbd_disconnect_and_put flush_workqueue // recv_work done nbd_config_put nbd_put // nbd_refs=1 nbd_put // nbd_refs=0 queue_work path B (netlink without NBD_CFLAG_DESTROY_ON_DISCONNECT): connect // nbd_refs=2 (trigger recv_work) open nbd // nbd_refs=3 NBD_CLEAR_SOCK // conf_refs=2 close nbd nbd_release nbd_config_put // conf_refs=1 nbd_put // nbd_refs=2 recv_work done // conf_refs=0, nbd_refs=1 rmmod // nbd_refs=0 Depends-on: e2daec488c57 ("nbd: Fix hungtask when nbd_config_put") CVE-2025-68372 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68372.html CVE-2025-68372 https://bugzilla.suse.com/1255537 SUSE Bug 1255537 In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix null deref on srq->rq.queue after resize failure A NULL pointer dereference can occur in rxe_srq_chk_attr() when ibv_modify_srq() is invoked twice in succession under certain error conditions. The first call may fail in rxe_queue_resize(), which leads rxe_srq_from_attr() to set srq->rq.queue = NULL. The second call then triggers a crash (null deref) when accessing srq->rq.queue->buf->index_mask. Call Trace: <TASK> rxe_modify_srq+0x170/0x480 [rdma_rxe] ? __pfx_rxe_modify_srq+0x10/0x10 [rdma_rxe] ? uverbs_try_lock_object+0x4f/0xa0 [ib_uverbs] ? rdma_lookup_get_uobject+0x1f0/0x380 [ib_uverbs] ib_uverbs_modify_srq+0x204/0x290 [ib_uverbs] ? __pfx_ib_uverbs_modify_srq+0x10/0x10 [ib_uverbs] ? tryinc_node_nr_active+0xe6/0x150 ? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs] ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x2c0/0x470 [ib_uverbs] ? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs] ? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs] ib_uverbs_run_method+0x55a/0x6e0 [ib_uverbs] ? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs] ib_uverbs_cmd_verbs+0x54d/0x800 [ib_uverbs] ? __pfx_ib_uverbs_cmd_verbs+0x10/0x10 [ib_uverbs] ? __pfx___raw_spin_lock_irqsave+0x10/0x10 ? __pfx_do_vfs_ioctl+0x10/0x10 ? ioctl_has_perm.constprop.0.isra.0+0x2c7/0x4c0 ? __pfx_ioctl_has_perm.constprop.0.isra.0+0x10/0x10 ib_uverbs_ioctl+0x13e/0x220 [ib_uverbs] ? __pfx_ib_uverbs_ioctl+0x10/0x10 [ib_uverbs] __x64_sys_ioctl+0x138/0x1c0 do_syscall_64+0x82/0x250 ? fdget_pos+0x58/0x4c0 ? ksys_write+0xf3/0x1c0 ? __pfx_ksys_write+0x10/0x10 ? do_syscall_64+0xc8/0x250 ? __pfx_vm_mmap_pgoff+0x10/0x10 ? fget+0x173/0x230 ? fput+0x2a/0x80 ? ksys_mmap_pgoff+0x224/0x4c0 ? do_syscall_64+0xc8/0x250 ? do_user_addr_fault+0x37b/0xfe0 ? clear_bhb_loop+0x50/0xa0 ? clear_bhb_loop+0x50/0xa0 ? clear_bhb_loop+0x50/0xa0 entry_SYSCALL_64_after_hwframe+0x76/0x7e CVE-2025-68379 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68379.html CVE-2025-68379 https://bugzilla.suse.com/1255695 SUSE Bug 1255695 In the Linux kernel, the following vulnerability has been resolved: bpf: Do not let BPF test infra emit invalid GSO types to stack Yinhao et al. reported that their fuzzer tool was able to trigger a skb_warn_bad_offload() from netif_skb_features() -> gso_features_check(). When a BPF program - triggered via BPF test infra - pushes the packet to the loopback device via bpf_clone_redirect() then mentioned offload warning can be seen. GSO-related features are then rightfully disabled. We get into this situation due to convert___skb_to_skb() setting gso_segs and gso_size but not gso_type. Technically, it makes sense that this warning triggers since the GSO properties are malformed due to the gso_type. Potentially, the gso_type could be marked non-trustworthy through setting it at least to SKB_GSO_DODGY without any other specific assumptions, but that also feels wrong given we should not go further into the GSO engine in the first place. The checks were added in 121d57af308d ("gso: validate gso_type in GSO handlers") because there were malicious (syzbot) senders that combine a protocol with a non-matching gso_type. If we would want to drop such packets, gso_features_check() currently only returns feature flags via netif_skb_features(), so one location for potentially dropping such skbs could be validate_xmit_unreadable_skb(), but then otoh it would be an additional check in the fast-path for a very corner case. Given bpf_clone_redirect() is the only place where BPF test infra could emit such packets, lets reject them right there. CVE-2025-68725 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68725.html CVE-2025-68725 https://bugzilla.suse.com/1255569 SUSE Bug 1255569 In the Linux kernel, the following vulnerability has been resolved: ntfs3: Fix uninit buffer allocated by __getname() Fix uninit errors caused after buffer allocation given to 'de'; by initializing the buffer with zeroes. The fix was found by using KMSAN. CVE-2025-68727 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68727.html CVE-2025-68727 https://bugzilla.suse.com/1255568 SUSE Bug 1255568 In the Linux kernel, the following vulnerability has been resolved: ntfs3: fix uninit memory after failed mi_read in mi_format_new Fix a KMSAN un-init bug found by syzkaller. ntfs_get_bh() expects a buffer from sb_getblk(), that buffer may not be uptodate. We do not bring the buffer uptodate before setting it as uptodate. If the buffer were to not be uptodate, it could mean adding a buffer with un-init data to the mi record. Attempting to load that record will trigger KMSAN. Avoid this by setting the buffer as uptodate, if it's not already, by overwriting it. CVE-2025-68728 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68728.html CVE-2025-68728 https://bugzilla.suse.com/1255539 SUSE Bug 1255539 In the Linux kernel, the following vulnerability has been resolved: smack: fix bug: unprivileged task can create labels If an unprivileged task is allowed to relabel itself (/smack/relabel-self is not empty), it can freely create new labels by writing their names into own /proc/PID/attr/smack/current This occurs because do_setattr() imports the provided label in advance, before checking "relabel-self" list. This change ensures that the "relabel-self" list is checked before importing the label. CVE-2025-68733 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68733.html CVE-2025-68733 https://bugzilla.suse.com/1255615 SUSE Bug 1255615 In the Linux kernel, the following vulnerability has been resolved: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags When a filesystem is being automounted, it needs to preserve the user-set superblock mount options, such as the "ro" flag. CVE-2025-68764 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68764.html CVE-2025-68764 https://bugzilla.suse.com/1255930 SUSE Bug 1255930 In the Linux kernel, the following vulnerability has been resolved: inet: frags: flush pending skbs in fqdir_pre_exit() We have been seeing occasional deadlocks on pernet_ops_rwsem since September in NIPA. The stuck task was usually modprobe (often loading a driver like ipvlan), trying to take the lock as a Writer. lockdep does not track readers for rwsems so the read wasn't obvious from the reports. On closer inspection the Reader holding the lock was conntrack looping forever in nf_conntrack_cleanup_net_list(). Based on past experience with occasional NIPA crashes I looked thru the tests which run before the crash and noticed that the crash follows ip_defrag.sh. An immediate red flag. Scouring thru (de)fragmentation queues reveals skbs sitting around, holding conntrack references. The problem is that since conntrack depends on nf_defrag_ipv6, nf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its netns exit hooks run _after_ conntrack's netns exit hook. Flush all fragment queue SKBs during fqdir_pre_exit() to release conntrack references before conntrack cleanup runs. Also flush the queues in timer expiry handlers when they discover fqdir->dead is set, in case packet sneaks in while we're running the pre_exit flush. The commit under Fixes is not exactly the culprit, but I think previously the timer firing would eventually unblock the spinning conntrack. CVE-2025-68768 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68768.html CVE-2025-68768 https://bugzilla.suse.com/1256579 SUSE Bug 1256579 In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix XDP_TX path For XDP_TX action in bnxt_rx_xdp(), clearing of the event flags is not correct. __bnxt_poll_work() -> bnxt_rx_pkt() -> bnxt_rx_xdp() may be looping within NAPI and some event flags may be set in earlier iterations. In particular, if BNXT_TX_EVENT is set earlier indicating some XDP_TX packets are ready and pending, it will be cleared if it is XDP_TX action again. Normally, we will set BNXT_TX_EVENT again when we successfully call __bnxt_xmit_xdp(). But if the TX ring has no more room, the flag will not be set. This will cause the TX producer to be ahead but the driver will not hit the TX doorbell. For multi-buf XDP_TX, there is no need to clear the event flags and set BNXT_AGG_EVENT. The BNXT_AGG_EVENT flag should have been set earlier in bnxt_rx_pkt(). The visible symptom of this is that the RX ring associated with the TX XDP ring will eventually become empty and all packets will be dropped. Because this condition will cause the driver to not refill the RX ring seeing that the TX ring has forever pending XDP_TX packets. The fix is to only clear BNXT_RX_EVENT when we have successfully called __bnxt_xmit_xdp(). CVE-2025-68770 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68770.html CVE-2025-68770 https://bugzilla.suse.com/1256584 SUSE Bug 1256584 In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix kernel BUG in ocfs2_find_victim_chain syzbot reported a kernel BUG in ocfs2_find_victim_chain() because the `cl_next_free_rec` field of the allocation chain list (next free slot in the chain list) is 0, triggring the BUG_ON(!cl->cl_next_free_rec) condition in ocfs2_find_victim_chain() and panicking the kernel. To fix this, an if condition is introduced in ocfs2_claim_suballoc_bits(), just before calling ocfs2_find_victim_chain(), the code block in it being executed when either of the following conditions is true: 1. `cl_next_free_rec` is equal to 0, indicating that there are no free chains in the allocation chain list 2. `cl_next_free_rec` is greater than `cl_count` (the total number of chains in the allocation chain list) Either of them being true is indicative of the fact that there are no chains left for usage. This is addressed using ocfs2_error(), which prints the error log for debugging purposes, rather than panicking the kernel. CVE-2025-68771 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68771.html CVE-2025-68771 https://bugzilla.suse.com/1256582 SUSE Bug 1256582 In the Linux kernel, the following vulnerability has been resolved: spi: fsl-cpm: Check length parity before switching to 16 bit mode Commit fc96ec826bce ("spi: fsl-cpm: Use 16 bit mode for large transfers with even size") failed to make sure that the size is really even before switching to 16 bit mode. Until recently the problem went unnoticed because kernfs uses a pre-allocated bounce buffer of size PAGE_SIZE for reading EEPROM. But commit 8ad6249c51d0 ("eeprom: at25: convert to spi-mem API") introduced an additional dynamically allocated bounce buffer whose size is exactly the size of the transfer, leading to a buffer overrun in the fsl-cpm driver when that size is odd. Add the missing length parity verification and remain in 8 bit mode when the length is not even. CVE-2025-68773 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68773.html CVE-2025-68773 https://bugzilla.suse.com/1256586 SUSE Bug 1256586 In the Linux kernel, the following vulnerability has been resolved: net/handshake: duplicate handshake cancellations leak socket When a handshake request is cancelled it is removed from the handshake_net->hn_requests list, but it is still present in the handshake_rhashtbl until it is destroyed. If a second cancellation request arrives for the same handshake request, then remove_pending() will return false... and assuming HANDSHAKE_F_REQ_COMPLETED isn't set in req->hr_flags, we'll continue processing through the out_true label, where we put another reference on the sock and a refcount underflow occurs. This can happen for example if a handshake times out - particularly if the SUNRPC client sends the AUTH_TLS probe to the server but doesn't follow it up with the ClientHello due to a problem with tlshd. When the timeout is hit on the server, the server will send a FIN, which triggers a cancellation request via xs_reset_transport(). When the timeout is hit on the client, another cancellation request happens via xs_tls_handshake_sync(). Add a test_and_set_bit(HANDSHAKE_F_REQ_COMPLETED) in the pending cancel path so duplicate cancels can be detected. CVE-2025-68775 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68775.html CVE-2025-68775 https://bugzilla.suse.com/1256665 SUSE Bug 1256665 https://bugzilla.suse.com/1256666 SUSE Bug 1256666 In the Linux kernel, the following vulnerability has been resolved: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() prp_get_untagged_frame() calls __pskb_copy() to create frame->skb_std but doesn't check if the allocation failed. If __pskb_copy() returns NULL, skb_clone() is called with a NULL pointer, causing a crash: Oops: general protection fault, probably for non-canonical address 0xdffffc000000000f: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000078-0x000000000000007f] CPU: 0 UID: 0 PID: 5625 Comm: syz.1.18 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 RIP: 0010:skb_clone+0xd7/0x3a0 net/core/skbuff.c:2041 Code: 03 42 80 3c 20 00 74 08 4c 89 f7 e8 23 29 05 f9 49 83 3e 00 0f 85 a0 01 00 00 e8 94 dd 9d f8 48 8d 6b 7e 49 89 ee 49 c1 ee 03 <43> 0f b6 04 26 84 c0 0f 85 d1 01 00 00 44 0f b6 7d 00 41 83 e7 0c RSP: 0018:ffffc9000d00f200 EFLAGS: 00010207 RAX: ffffffff892235a1 RBX: 0000000000000000 RCX: ffff88803372a480 RDX: 0000000000000000 RSI: 0000000000000820 RDI: 0000000000000000 RBP: 000000000000007e R08: ffffffff8f7d0f77 R09: 1ffffffff1efa1ee R10: dffffc0000000000 R11: fffffbfff1efa1ef R12: dffffc0000000000 R13: 0000000000000820 R14: 000000000000000f R15: ffff88805144cc00 FS: 0000555557f6d500(0000) GS:ffff88808d72f000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000555581d35808 CR3: 000000005040e000 CR4: 0000000000352ef0 Call Trace: <TASK> hsr_forward_do net/hsr/hsr_forward.c:-1 [inline] hsr_forward_skb+0x1013/0x2860 net/hsr/hsr_forward.c:741 hsr_handle_frame+0x6ce/0xa70 net/hsr/hsr_slave.c:84 __netif_receive_skb_core+0x10b9/0x4380 net/core/dev.c:5966 __netif_receive_skb_one_core net/core/dev.c:6077 [inline] __netif_receive_skb+0x72/0x380 net/core/dev.c:6192 netif_receive_skb_internal net/core/dev.c:6278 [inline] netif_receive_skb+0x1cb/0x790 net/core/dev.c:6337 tun_rx_batched+0x1b9/0x730 drivers/net/tun.c:1485 tun_get_user+0x2b65/0x3e90 drivers/net/tun.c:1953 tun_chr_write_iter+0x113/0x200 drivers/net/tun.c:1999 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/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f0449f8e1ff Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 f9 92 02 00 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 4c 93 02 00 48 RSP: 002b:00007ffd7ad94c90 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f044a1e5fa0 RCX: 00007f0449f8e1ff RDX: 000000000000003e RSI: 0000200000000500 RDI: 00000000000000c8 RBP: 00007ffd7ad94d20 R08: 0000000000000000 R09: 0000000000000000 R10: 000000000000003e R11: 0000000000000293 R12: 0000000000000001 R13: 00007f044a1e5fa0 R14: 00007f044a1e5fa0 R15: 0000000000000003 </TASK> Add a NULL check immediately after __pskb_copy() to handle allocation failures gracefully. CVE-2025-68776 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68776.html CVE-2025-68776 https://bugzilla.suse.com/1256659 SUSE Bug 1256659 In the Linux kernel, the following vulnerability has been resolved: Input: ti_am335x_tsc - fix off-by-one error in wire_order validation The current validation 'wire_order[i] > ARRAY_SIZE(config_pins)' allows wire_order[i] to equal ARRAY_SIZE(config_pins), which causes out-of-bounds access when used as index in 'config_pins[wire_order[i]]'. Since config_pins has 4 elements (indices 0-3), the valid range for wire_order should be 0-3. Fix the off-by-one error by using >= instead of > in the validation check. CVE-2025-68777 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68777.html CVE-2025-68777 https://bugzilla.suse.com/1256655 SUSE Bug 1256655 In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-mixer: us16x08: validate meter packet indices get_meter_levels_from_urb() parses the 64-byte meter packets sent by the device and fills the per-channel arrays meter_level[], comp_level[] and master_level[] in struct snd_us16x08_meter_store. Currently the function derives the channel index directly from the meter packet (MUB2(meter_urb, s) - 1) and uses it to index those arrays without validating the range. If the packet contains a negative or out-of-range channel number, the driver may write past the end of these arrays. Introduce a local channel variable and validate it before updating the arrays. We reject negative indices, limit meter_level[] and comp_level[] to SND_US16X08_MAX_CHANNELS, and guard master_level[] updates with ARRAY_SIZE(master_level). CVE-2025-68783 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68783.html CVE-2025-68783 https://bugzilla.suse.com/1256650 SUSE Bug 1256650 In the Linux kernel, the following vulnerability has been resolved: fsnotify: do not generate ACCESS/MODIFY events on child for special files inotify/fanotify do not allow users with no read access to a file to subscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the same user to subscribe for watching events on children when the user has access to the parent directory (e.g. /dev). Users with no read access to a file but with read access to its parent directory can still stat the file and see if it was accessed/modified via atime/mtime change. The same is not true for special files (e.g. /dev/null). Users will not generally observe atime/mtime changes when other users read/write to special files, only when someone sets atime/mtime via utimensat(). Align fsnotify events with this stat behavior and do not generate ACCESS/MODIFY events to parent watchers on read/write of special files. The events are still generated to parent watchers on utimensat(). This closes some side-channels that could be possibly used for information exfiltration [1]. [1] https://snee.la/pdf/pubs/file-notification-attacks.pdf CVE-2025-68788 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68788.html CVE-2025-68788 https://bugzilla.suse.com/1256638 SUSE Bug 1256638 This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. CVE-2025-68789 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68789.html CVE-2025-68789 https://bugzilla.suse.com/1256781 SUSE Bug 1256781 In the Linux kernel, the following vulnerability has been resolved: ethtool: Avoid overflowing userspace buffer on stats query The ethtool -S command operates across three ioctl calls: ETHTOOL_GSSET_INFO for the size, ETHTOOL_GSTRINGS for the names, and ETHTOOL_GSTATS for the values. If the number of stats changes between these calls (e.g., due to device reconfiguration), userspace's buffer allocation will be incorrect, potentially leading to buffer overflow. Drivers are generally expected to maintain stable stat counts, but some drivers (e.g., mlx5, bnx2x, bna, ksz884x) use dynamic counters, making this scenario possible. Some drivers try to handle this internally: - bnad_get_ethtool_stats() returns early in case stats.n_stats is not equal to the driver's stats count. - micrel/ksz884x also makes sure not to write anything beyond stats.n_stats and overflow the buffer. However, both use stats.n_stats which is already assigned with the value returned from get_sset_count(), hence won't solve the issue described here. Change ethtool_get_strings(), ethtool_get_stats(), ethtool_get_phy_stats() to not return anything in case of a mismatch between userspace's size and get_sset_size(), to prevent buffer overflow. The returned n_stats value will be equal to zero, to reflect that nothing has been returned. This could result in one of two cases when using upstream ethtool, depending on when the size change is detected: 1. When detected in ethtool_get_strings(): # ethtool -S eth2 no stats available 2. When detected in get stats, all stats will be reported as zero. Both cases are presumably transient, and a subsequent ethtool call should succeed. Other than the overflow avoidance, these two cases are very evident (no output/cleared stats), which is arguably better than presenting incorrect/shifted stats. I also considered returning an error instead of a "silent" response, but that seems more destructive towards userspace apps. Notes: - This patch does not claim to fix the inherent race, it only makes sure that we do not overflow the userspace buffer, and makes for a more predictable behavior. - RTNL lock is held during each ioctl, the race window exists between the separate ioctl calls when the lock is released. - Userspace ethtool always fills stats.n_stats, but it is likely that these stats ioctls are implemented in other userspace applications which might not fill it. The added code checks that it's not zero, to prevent any regressions. CVE-2025-68795 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68795.html CVE-2025-68795 https://bugzilla.suse.com/1256688 SUSE Bug 1256688 In the Linux kernel, the following vulnerability has been resolved: char: applicom: fix NULL pointer dereference in ac_ioctl Discovered by Atuin - Automated Vulnerability Discovery Engine. In ac_ioctl, the validation of IndexCard and the check for a valid RamIO pointer are skipped when cmd is 6. However, the function unconditionally executes readb(apbs[IndexCard].RamIO + VERS) at the end. If cmd is 6, IndexCard may reference a board that does not exist (where RamIO is NULL), leading to a NULL pointer dereference. Fix this by skipping the readb access when cmd is 6, as this command is a global information query and does not target a specific board context. CVE-2025-68797 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68797.html CVE-2025-68797 https://bugzilla.suse.com/1256660 SUSE Bug 1256660 In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd: Check event before enable to avoid GPF On AMD machines cpuc->events[idx] can become NULL in a subtle race condition with NMI->throttle->x86_pmu_stop(). Check event for NULL in amd_pmu_enable_all() before enable to avoid a GPF. This appears to be an AMD only issue. Syzkaller reported a GPF in amd_pmu_enable_all. INFO: NMI handler (perf_event_nmi_handler) took too long to run: 13.143 msecs Oops: general protection fault, probably for non-canonical address 0xdffffc0000000034: 0000 PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x00000000000001a0-0x00000000000001a7] CPU: 0 UID: 0 PID: 328415 Comm: repro_36674776 Not tainted 6.12.0-rc1-syzk RIP: 0010:x86_pmu_enable_event (arch/x86/events/perf_event.h:1195 arch/x86/events/core.c:1430) RSP: 0018:ffff888118009d60 EFLAGS: 00010012 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000034 RSI: 0000000000000000 RDI: 00000000000001a0 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002 R13: ffff88811802a440 R14: ffff88811802a240 R15: ffff8881132d8601 FS: 00007f097dfaa700(0000) GS:ffff888118000000(0000) GS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200001c0 CR3: 0000000103d56000 CR4: 00000000000006f0 Call Trace: <IRQ> amd_pmu_enable_all (arch/x86/events/amd/core.c:760 (discriminator 2)) x86_pmu_enable (arch/x86/events/core.c:1360) event_sched_out (kernel/events/core.c:1191 kernel/events/core.c:1186 kernel/events/core.c:2346) __perf_remove_from_context (kernel/events/core.c:2435) event_function (kernel/events/core.c:259) remote_function (kernel/events/core.c:92 (discriminator 1) kernel/events/core.c:72 (discriminator 1)) __flush_smp_call_function_queue (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/csd.h:64 kernel/smp.c:135 kernel/smp.c:540) __sysvec_call_function_single (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./arch/x86/include/asm/trace/irq_vectors.h:99 arch/x86/kernel/smp.c:272) sysvec_call_function_single (arch/x86/kernel/smp.c:266 (discriminator 47) arch/x86/kernel/smp.c:266 (discriminator 47)) </IRQ> CVE-2025-68798 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68798.html CVE-2025-68798 https://bugzilla.suse.com/1256689 SUSE Bug 1256689 In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats Cited commit added a dedicated mutex (instead of RTNL) to protect the multicast route list, so that it will not change while the driver periodically traverses it in order to update the kernel about multicast route stats that were queried from the device. One instance of list entry deletion (during route replace) was missed and it can result in a use-after-free [1]. Fix by acquiring the mutex before deleting the entry from the list and releasing it afterwards. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum] Read of size 8 at addr ffff8881523c2fa8 by task kworker/2:5/22043 CPU: 2 UID: 0 PID: 22043 Comm: kworker/2:5 Not tainted 6.18.0-rc1-custom-g1a3d6d7cd014 #1 PREEMPT(full) Hardware name: Mellanox Technologies Ltd. MSN2010/SA002610, BIOS 5.6.5 08/24/2017 Workqueue: mlxsw_core mlxsw_sp_mr_stats_update [mlxsw_spectrum] Call Trace: <TASK> dump_stack_lvl+0xba/0x110 print_report+0x174/0x4f5 kasan_report+0xdf/0x110 mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum] process_one_work+0x9cc/0x18e0 worker_thread+0x5df/0xe40 kthread+0x3b8/0x730 ret_from_fork+0x3e9/0x560 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 29933: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x8f/0xa0 mlxsw_sp_mr_route_add+0xd8/0x4770 [mlxsw_spectrum] mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum] process_one_work+0x9cc/0x18e0 worker_thread+0x5df/0xe40 kthread+0x3b8/0x730 ret_from_fork+0x3e9/0x560 ret_from_fork_asm+0x1a/0x30 Freed by task 29933: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_save_free_info+0x3b/0x70 __kasan_slab_free+0x43/0x70 kfree+0x14e/0x700 mlxsw_sp_mr_route_add+0x2dea/0x4770 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:444 [mlxsw_spectrum] mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum] process_one_work+0x9cc/0x18e0 worker_thread+0x5df/0xe40 kthread+0x3b8/0x730 ret_from_fork+0x3e9/0x560 ret_from_fork_asm+0x1a/0x30 CVE-2025-68800 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68800.html CVE-2025-68800 https://bugzilla.suse.com/1256646 SUSE Bug 1256646 In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_router: Fix neighbour use-after-free We sometimes observe use-after-free when dereferencing a neighbour [1]. The problem seems to be that the driver stores a pointer to the neighbour, but without holding a reference on it. A reference is only taken when the neighbour is used by a nexthop. Fix by simplifying the reference counting scheme. Always take a reference when storing a neighbour pointer in a neighbour entry. Avoid taking a referencing when the neighbour is used by a nexthop as the neighbour entry associated with the nexthop already holds a reference. Tested by running the test that uncovered the problem over 300 times. Without this patch the problem was reproduced after a handful of iterations. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310 Read of size 8 at addr ffff88817f8e3420 by task ip/3929 CPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full) Hardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023 Call Trace: <TASK> dump_stack_lvl+0x6f/0xa0 print_address_description.constprop.0+0x6e/0x300 print_report+0xfc/0x1fb kasan_report+0xe4/0x110 mlxsw_sp_neigh_entry_update+0x2d4/0x310 mlxsw_sp_router_rif_gone_sync+0x35f/0x510 mlxsw_sp_rif_destroy+0x1ea/0x730 mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0 __mlxsw_sp_inetaddr_lag_event+0xcc/0x130 __mlxsw_sp_inetaddr_event+0xf5/0x3c0 mlxsw_sp_router_netdevice_event+0x1015/0x1580 notifier_call_chain+0xcc/0x150 call_netdevice_notifiers_info+0x7e/0x100 __netdev_upper_dev_unlink+0x10b/0x210 netdev_upper_dev_unlink+0x79/0xa0 vrf_del_slave+0x18/0x50 do_set_master+0x146/0x7d0 do_setlink.isra.0+0x9a0/0x2880 rtnl_newlink+0x637/0xb20 rtnetlink_rcv_msg+0x6fe/0xb90 netlink_rcv_skb+0x123/0x380 netlink_unicast+0x4a3/0x770 netlink_sendmsg+0x75b/0xc90 __sock_sendmsg+0xbe/0x160 ____sys_sendmsg+0x5b2/0x7d0 ___sys_sendmsg+0xfd/0x180 __sys_sendmsg+0x124/0x1c0 do_syscall_64+0xbb/0xfd0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 [...] Allocated by task 109: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7b/0x90 __kmalloc_noprof+0x2c1/0x790 neigh_alloc+0x6af/0x8f0 ___neigh_create+0x63/0xe90 mlxsw_sp_nexthop_neigh_init+0x430/0x7e0 mlxsw_sp_nexthop_type_init+0x212/0x960 mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280 mlxsw_sp_nexthop6_group_get+0x392/0x6a0 mlxsw_sp_fib6_entry_create+0x46a/0xfd0 mlxsw_sp_router_fib6_replace+0x1ed/0x5f0 mlxsw_sp_router_fib6_event_work+0x10a/0x2a0 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40 kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 Freed by task 154: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x43/0x70 kmem_cache_free_bulk.part.0+0x1eb/0x5e0 kvfree_rcu_bulk+0x1f2/0x260 kfree_rcu_work+0x130/0x1b0 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40 kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 Last potentially related work creation: kasan_save_stack+0x30/0x50 kasan_record_aux_stack+0x8c/0xa0 kvfree_call_rcu+0x93/0x5b0 mlxsw_sp_router_neigh_event_work+0x67d/0x860 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40 kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 CVE-2025-68801 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68801.html CVE-2025-68801 https://bugzilla.suse.com/1256653 SUSE Bug 1256653 In the Linux kernel, the following vulnerability has been resolved: drm/xe: Limit num_syncs to prevent oversized allocations The exec and vm_bind ioctl allow userspace to specify an arbitrary num_syncs value. Without bounds checking, a very large num_syncs can force an excessively large allocation, leading to kernel warnings from the page allocator as below. Introduce DRM_XE_MAX_SYNCS (set to 1024) and reject any request exceeding this limit. " ------------[ cut here ]------------ WARNING: CPU: 0 PID: 1217 at mm/page_alloc.c:5124 __alloc_frozen_pages_noprof+0x2f8/0x2180 mm/page_alloc.c:5124 ... Call Trace: <TASK> alloc_pages_mpol+0xe4/0x330 mm/mempolicy.c:2416 ___kmalloc_large_node+0xd8/0x110 mm/slub.c:4317 __kmalloc_large_node_noprof+0x18/0xe0 mm/slub.c:4348 __do_kmalloc_node mm/slub.c:4364 [inline] __kmalloc_noprof+0x3d4/0x4b0 mm/slub.c:4388 kmalloc_noprof include/linux/slab.h:909 [inline] kmalloc_array_noprof include/linux/slab.h:948 [inline] xe_exec_ioctl+0xa47/0x1e70 drivers/gpu/drm/xe/xe_exec.c:158 drm_ioctl_kernel+0x1f1/0x3e0 drivers/gpu/drm/drm_ioctl.c:797 drm_ioctl+0x5e7/0xc50 drivers/gpu/drm/drm_ioctl.c:894 xe_drm_ioctl+0x10b/0x170 drivers/gpu/drm/xe/xe_device.c:224 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:598 [inline] __se_sys_ioctl fs/ioctl.c:584 [inline] __x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:584 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xbb/0x380 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f ... " v2: Add "Reported-by" and Cc stable kernels. v3: Change XE_MAX_SYNCS from 64 to 1024. (Matt & Ashutosh) v4: s/XE_MAX_SYNCS/DRM_XE_MAX_SYNCS/ (Matt) v5: Do the check at the top of the exec func. (Matt) (cherry picked from commit b07bac9bd708ec468cd1b8a5fe70ae2ac9b0a11c) CVE-2025-68802 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68802.html CVE-2025-68802 https://bugzilla.suse.com/1256661 SUSE Bug 1256661 In the Linux kernel, the following vulnerability has been resolved: NFSD: NFSv4 file creation neglects setting ACL An NFSv4 client that sets an ACL with a named principal during file creation retrieves the ACL afterwards, and finds that it is only a default ACL (based on the mode bits) and not the ACL that was requested during file creation. This violates RFC 8881 section 6.4.1.3: "the ACL attribute is set as given". The issue occurs in nfsd_create_setattr(), which calls nfsd_attrs_valid() to determine whether to call nfsd_setattr(). However, nfsd_attrs_valid() checks only for iattr changes and security labels, but not POSIX ACLs. When only an ACL is present, the function returns false, nfsd_setattr() is skipped, and the POSIX ACL is never applied to the inode. Subsequently, when the client retrieves the ACL, the server finds no POSIX ACL on the inode and returns one generated from the file's mode bits rather than returning the originally-specified ACL. CVE-2025-68803 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68803.html CVE-2025-68803 https://bugzilla.suse.com/1256770 SUSE Bug 1256770 In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_ishtp: Fix UAF after unbinding driver After unbinding the driver, another kthread `cros_ec_console_log_work` is still accessing the device, resulting an UAF and crash. The driver doesn't unregister the EC device in .remove() which should shutdown sub-devices synchronously. Fix it. CVE-2025-68804 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68804.html CVE-2025-68804 https://bugzilla.suse.com/1256617 SUSE Bug 1256617 https://bugzilla.suse.com/1256618 SUSE Bug 1256618 In the Linux kernel, the following vulnerability has been resolved: media: vidtv: initialize local pointers upon transfer of memory ownership vidtv_channel_si_init() creates a temporary list (program, service, event) and ownership of the memory itself is transferred to the PAT/SDT/EIT tables through vidtv_psi_pat_program_assign(), vidtv_psi_sdt_service_assign(), vidtv_psi_eit_event_assign(). The problem here is that the local pointer where the memory ownership transfer was completed is not initialized to NULL. This causes the vidtv_psi_pmt_create_sec_for_each_pat_entry() function to fail, and in the flow that jumps to free_eit, the memory that was freed by vidtv_psi_*_table_destroy() can be accessed again by vidtv_psi_*_event_destroy() due to the uninitialized local pointer, so it is freed once again. Therefore, to prevent use-after-free and double-free vulnerability, local pointers must be initialized to NULL when transferring memory ownership. CVE-2025-68808 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68808.html CVE-2025-68808 https://bugzilla.suse.com/1256682 SUSE Bug 1256682 In the Linux kernel, the following vulnerability has been resolved: ipvs: fix ipv4 null-ptr-deref in route error path The IPv4 code path in __ip_vs_get_out_rt() calls dst_link_failure() without ensuring skb->dev is set, leading to a NULL pointer dereference in fib_compute_spec_dst() when ipv4_link_failure() attempts to send ICMP destination unreachable messages. The issue emerged after commit ed0de45a1008 ("ipv4: recompile ip options in ipv4_link_failure") started calling __ip_options_compile() from ipv4_link_failure(). This code path eventually calls fib_compute_spec_dst() which dereferences skb->dev. An attempt was made to fix the NULL skb->dev dereference in commit 0113d9c9d1cc ("ipv4: fix null-deref in ipv4_link_failure"), but it only addressed the immediate dev_net(skb->dev) dereference by using a fallback device. The fix was incomplete because fib_compute_spec_dst() later in the call chain still accesses skb->dev directly, which remains NULL when IPVS calls dst_link_failure(). The crash occurs when: 1. IPVS processes a packet in NAT mode with a misconfigured destination 2. Route lookup fails in __ip_vs_get_out_rt() before establishing a route 3. The error path calls dst_link_failure(skb) with skb->dev == NULL 4. ipv4_link_failure() -> ipv4_send_dest_unreach() -> __ip_options_compile() -> fib_compute_spec_dst() 5. fib_compute_spec_dst() dereferences NULL skb->dev Apply the same fix used for IPv6 in commit 326bf17ea5d4 ("ipvs: fix ipv6 route unreach panic"): set skb->dev from skb_dst(skb)->dev before calling dst_link_failure(). KASAN: null-ptr-deref in range [0x0000000000000328-0x000000000000032f] CPU: 1 PID: 12732 Comm: syz.1.3469 Not tainted 6.6.114 #2 RIP: 0010:__in_dev_get_rcu include/linux/inetdevice.h:233 RIP: 0010:fib_compute_spec_dst+0x17a/0x9f0 net/ipv4/fib_frontend.c:285 Call Trace: <TASK> spec_dst_fill net/ipv4/ip_options.c:232 spec_dst_fill net/ipv4/ip_options.c:229 __ip_options_compile+0x13a1/0x17d0 net/ipv4/ip_options.c:330 ipv4_send_dest_unreach net/ipv4/route.c:1252 ipv4_link_failure+0x702/0xb80 net/ipv4/route.c:1265 dst_link_failure include/net/dst.h:437 __ip_vs_get_out_rt+0x15fd/0x19e0 net/netfilter/ipvs/ip_vs_xmit.c:412 ip_vs_nat_xmit+0x1d8/0xc80 net/netfilter/ipvs/ip_vs_xmit.c:764 CVE-2025-68813 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68813.html CVE-2025-68813 https://bugzilla.suse.com/1256641 SUSE Bug 1256641 https://bugzilla.suse.com/1256644 SUSE Bug 1256644 In the Linux kernel, the following vulnerability has been resolved: io_uring: fix filename leak in __io_openat_prep() __io_openat_prep() allocates a struct filename using getname(). However, for the condition of the file being installed in the fixed file table as well as having O_CLOEXEC flag set, the function returns early. At that point, the request doesn't have REQ_F_NEED_CLEANUP flag set. Due to this, the memory for the newly allocated struct filename is not cleaned up, causing a memory leak. Fix this by setting the REQ_F_NEED_CLEANUP for the request just after the successful getname() call, so that when the request is torn down, the filename will be cleaned up, along with other resources needing cleanup. CVE-2025-68814 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68814.html CVE-2025-68814 https://bugzilla.suse.com/1256651 SUSE Bug 1256651 In the Linux kernel, the following vulnerability has been resolved: net/sched: ets: Remove drr class from the active list if it changes to strict Whenever a user issues an ets qdisc change command, transforming a drr class into a strict one, the ets code isn't checking whether that class was in the active list and removing it. This means that, if a user changes a strict class (which was in the active list) back to a drr one, that class will be added twice to the active list [1]. Doing so with the following commands: tc qdisc add dev lo root handle 1: ets bands 2 strict 1 tc qdisc add dev lo parent 1:2 handle 20: \ tbf rate 8bit burst 100b latency 1s tc filter add dev lo parent 1: basic classid 1:2 ping -c1 -W0.01 -s 56 127.0.0.1 tc qdisc change dev lo root handle 1: ets bands 2 strict 2 tc qdisc change dev lo root handle 1: ets bands 2 strict 1 ping -c1 -W0.01 -s 56 127.0.0.1 Will trigger the following splat with list debug turned on: [ 59.279014][ T365] ------------[ cut here ]------------ [ 59.279452][ T365] list_add double add: new=ffff88801d60e350, prev=ffff88801d60e350, next=ffff88801d60e2c0. [ 59.280153][ T365] WARNING: CPU: 3 PID: 365 at lib/list_debug.c:35 __list_add_valid_or_report+0x17f/0x220 [ 59.280860][ T365] Modules linked in: [ 59.281165][ T365] CPU: 3 UID: 0 PID: 365 Comm: tc Not tainted 6.18.0-rc7-00105-g7e9f13163c13-dirty #239 PREEMPT(voluntary) [ 59.281977][ T365] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 59.282391][ T365] RIP: 0010:__list_add_valid_or_report+0x17f/0x220 [ 59.282842][ T365] Code: 89 c6 e8 d4 b7 0d ff 90 0f 0b 90 90 31 c0 e9 31 ff ff ff 90 48 c7 c7 e0 a0 22 9f 48 89 f2 48 89 c1 4c 89 c6 e8 b2 b7 0d ff 90 <0f> 0b 90 90 31 c0 e9 0f ff ff ff 48 89 f7 48 89 44 24 10 4c 89 44 ... [ 59.288812][ T365] Call Trace: [ 59.289056][ T365] <TASK> [ 59.289224][ T365] ? srso_alias_return_thunk+0x5/0xfbef5 [ 59.289546][ T365] ets_qdisc_change+0xd2b/0x1e80 [ 59.289891][ T365] ? __lock_acquire+0x7e7/0x1be0 [ 59.290223][ T365] ? __pfx_ets_qdisc_change+0x10/0x10 [ 59.290546][ T365] ? srso_alias_return_thunk+0x5/0xfbef5 [ 59.290898][ T365] ? __mutex_trylock_common+0xda/0x240 [ 59.291228][ T365] ? __pfx___mutex_trylock_common+0x10/0x10 [ 59.291655][ T365] ? srso_alias_return_thunk+0x5/0xfbef5 [ 59.291993][ T365] ? srso_alias_return_thunk+0x5/0xfbef5 [ 59.292313][ T365] ? trace_contention_end+0xc8/0x110 [ 59.292656][ T365] ? srso_alias_return_thunk+0x5/0xfbef5 [ 59.293022][ T365] ? srso_alias_return_thunk+0x5/0xfbef5 [ 59.293351][ T365] tc_modify_qdisc+0x63a/0x1cf0 Fix this by always checking and removing an ets class from the active list when changing it to strict. [1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/tree/net/sched/sch_ets.c?id=ce052b9402e461a9aded599f5b47e76bc727f7de#n663 CVE-2025-68815 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68815.html CVE-2025-68815 https://bugzilla.suse.com/1256680 SUSE Bug 1256680 In the Linux kernel, the following vulnerability has been resolved: net/mlx5: fw_tracer, Validate format string parameters Add validation for format string parameters in the firmware tracer to prevent potential security vulnerabilities and crashes from malformed format strings received from firmware. The firmware tracer receives format strings from the device firmware and uses them to format trace messages. Without proper validation, bad firmware could provide format strings with invalid format specifiers (e.g., %s, %p, %n) that could lead to crashes, or other undefined behavior. Add mlx5_tracer_validate_params() to validate that all format specifiers in trace strings are limited to safe integer/hex formats (%x, %d, %i, %u, %llx, %lx, etc.). Reject strings containing other format types that could be used to access arbitrary memory or cause crashes. Invalid format strings are added to the trace output for visibility with "BAD_FORMAT: " prefix. CVE-2025-68816 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68816.html CVE-2025-68816 https://bugzilla.suse.com/1256674 SUSE Bug 1256674 In the Linux kernel, the following vulnerability has been resolved: media: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg() rlen value is a user-controlled value, but dtv5100_i2c_msg() does not check the size of the rlen value. Therefore, if it is set to a value larger than sizeof(st->data), an out-of-bounds vuln occurs for st->data. Therefore, we need to add proper range checking to prevent this vuln. CVE-2025-68819 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68819.html CVE-2025-68819 https://bugzilla.suse.com/1256664 SUSE Bug 1256664 In the Linux kernel, the following vulnerability has been resolved: ext4: xattr: fix null pointer deref in ext4_raw_inode() If ext4_get_inode_loc() fails (e.g. if it returns -EFSCORRUPTED), iloc.bh will remain set to NULL. Since ext4_xattr_inode_dec_ref_all() lacks error checking, this will lead to a null pointer dereference in ext4_raw_inode(), called right after ext4_get_inode_loc(). Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2025-68820 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-68820.html CVE-2025-68820 https://bugzilla.suse.com/1256754 SUSE Bug 1256754 In the Linux kernel, the following vulnerability has been resolved: net: hns3: using the num_tqps in the vf driver to apply for resources Currently, hdev->htqp is allocated using hdev->num_tqps, and kinfo->tqp is allocated using kinfo->num_tqps. However, kinfo->num_tqps is set to min(new_tqps, hdev->num_tqps); Therefore, kinfo->num_tqps may be smaller than hdev->num_tqps, which causes some hdev->htqp[i] to remain uninitialized in hclgevf_knic_setup(). Thus, this patch allocates hdev->htqp and kinfo->tqp using hdev->num_tqps, ensuring that the lengths of hdev->htqp and kinfo->tqp are consistent and that all elements are properly initialized. CVE-2025-71064 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71064.html CVE-2025-71064 https://bugzilla.suse.com/1256654 SUSE Bug 1256654 In the Linux kernel, the following vulnerability has been resolved: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change zdi-disclosures@trendmicro.com says: The vulnerability is a race condition between `ets_qdisc_dequeue` and `ets_qdisc_change`. It leads to UAF on `struct Qdisc` object. Attacker requires the capability to create new user and network namespace in order to trigger the bug. See my additional commentary at the end of the analysis. Analysis: static int ets_qdisc_change(struct Qdisc *sch, struct nlattr *opt, struct netlink_ext_ack *extack) { ... // (1) this lock is preventing .change handler (`ets_qdisc_change`) //to race with .dequeue handler (`ets_qdisc_dequeue`) sch_tree_lock(sch); for (i = nbands; i < oldbands; i++) { if (i >= q->nstrict && q->classes[i].qdisc->q.qlen) list_del_init(&q->classes[i].alist); qdisc_purge_queue(q->classes[i].qdisc); } WRITE_ONCE(q->nbands, nbands); for (i = nstrict; i < q->nstrict; i++) { if (q->classes[i].qdisc->q.qlen) { // (2) the class is added to the q->active list_add_tail(&q->classes[i].alist, &q->active); q->classes[i].deficit = quanta[i]; } } WRITE_ONCE(q->nstrict, nstrict); memcpy(q->prio2band, priomap, sizeof(priomap)); for (i = 0; i < q->nbands; i++) WRITE_ONCE(q->classes[i].quantum, quanta[i]); for (i = oldbands; i < q->nbands; i++) { q->classes[i].qdisc = queues[i]; if (q->classes[i].qdisc != &noop_qdisc) qdisc_hash_add(q->classes[i].qdisc, true); } // (3) the qdisc is unlocked, now dequeue can be called in parallel // to the rest of .change handler sch_tree_unlock(sch); ets_offload_change(sch); for (i = q->nbands; i < oldbands; i++) { // (4) we're reducing the refcount for our class's qdisc and // freeing it qdisc_put(q->classes[i].qdisc); // (5) If we call .dequeue between (4) and (5), we will have // a strong UAF and we can control RIP q->classes[i].qdisc = NULL; WRITE_ONCE(q->classes[i].quantum, 0); q->classes[i].deficit = 0; gnet_stats_basic_sync_init(&q->classes[i].bstats); memset(&q->classes[i].qstats, 0, sizeof(q->classes[i].qstats)); } return 0; } Comment: This happens because some of the classes have their qdiscs assigned to NULL, but remain in the active list. This commit fixes this issue by always removing the class from the active list before deleting and freeing its associated qdisc Reproducer Steps (trimmed version of what was sent by zdi-disclosures@trendmicro.com) ``` DEV="${DEV:-lo}" ROOT_HANDLE="${ROOT_HANDLE:-1:}" BAND2_HANDLE="${BAND2_HANDLE:-20:}" # child under 1:2 PING_BYTES="${PING_BYTES:-48}" PING_COUNT="${PING_COUNT:-200000}" PING_DST="${PING_DST:-127.0.0.1}" SLOW_TBF_RATE="${SLOW_TBF_RATE:-8bit}" SLOW_TBF_BURST="${SLOW_TBF_BURST:-100b}" SLOW_TBF_LAT="${SLOW_TBF_LAT:-1s}" cleanup() { tc qdisc del dev "$DEV" root 2>/dev/null } trap cleanup EXIT ip link set "$DEV" up tc qdisc del dev "$DEV" root 2>/dev/null || true tc qdisc add dev "$DEV" root handle "$ROOT_HANDLE" ets bands 2 strict 2 tc qdisc add dev "$DEV" parent 1:2 handle "$BAND2_HANDLE" \ tbf rate "$SLOW_TBF_RATE" burst "$SLOW_TBF_BURST" latency "$SLOW_TBF_LAT" tc filter add dev "$DEV" parent 1: protocol all prio 1 u32 match u32 0 0 flowid 1:2 tc -s qdisc ls dev $DEV ping -I "$DEV" -f -c "$PING_COUNT" -s "$PING_BYTES" -W 0.001 "$PING_DST" \ >/dev/null 2>&1 & tc qdisc change dev "$DEV" root handle "$ROOT_HANDLE" ets bands 2 strict 0 tc qdisc change dev "$DEV" root handle "$ROOT_HANDLE" ets bands 2 strict 2 tc -s qdisc ls dev $DEV tc qdisc del dev "$DEV" parent ---truncated--- CVE-2025-71066 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71066.html CVE-2025-71066 https://bugzilla.suse.com/1256645 SUSE Bug 1256645 In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Limit num_syncs to prevent oversized allocations The OA open parameters did not validate num_syncs, allowing userspace to pass arbitrarily large values, potentially leading to excessive allocations. Add check to ensure that num_syncs does not exceed DRM_XE_MAX_SYNCS, returning -EINVAL when the limit is violated. v2: use XE_IOCTL_DBG() and drop duplicated check. (Ashutosh) (cherry picked from commit e057b2d2b8d815df3858a87dffafa2af37e5945b) CVE-2025-71076 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71076.html CVE-2025-71076 https://bugzilla.suse.com/1256627 SUSE Bug 1256627 In the Linux kernel, the following vulnerability has been resolved: tpm: Cap the number of PCR banks tpm2_get_pcr_allocation() does not cap any upper limit for the number of banks. Cap the limit to eight banks so that out of bounds values coming from external I/O cause on only limited harm. CVE-2025-71077 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71077.html CVE-2025-71077 https://bugzilla.suse.com/1256613 SUSE Bug 1256613 In the Linux kernel, the following vulnerability has been resolved: powerpc/64s/slb: Fix SLB multihit issue during SLB preload On systems using the hash MMU, there is a software SLB preload cache that mirrors the entries loaded into the hardware SLB buffer. This preload cache is subject to periodic eviction - typically after every 256 context switches - to remove old entry. To optimize performance, the kernel skips switch_mmu_context() in switch_mm_irqs_off() when the prev and next mm_struct are the same. However, on hash MMU systems, this can lead to inconsistencies between the hardware SLB and the software preload cache. If an SLB entry for a process is evicted from the software cache on one CPU, and the same process later runs on another CPU without executing switch_mmu_context(), the hardware SLB may retain stale entries. If the kernel then attempts to reload that entry, it can trigger an SLB multi-hit error. The following timeline shows how stale SLB entries are created and can cause a multi-hit error when a process moves between CPUs without a MMU context switch. CPU 0 CPU 1 ----- ----- Process P exec swapper/1 load_elf_binary begin_new_exc activate_mm switch_mm_irqs_off switch_mmu_context switch_slb /* * This invalidates all * the entries in the HW * and setup the new HW * SLB entries as per the * preload cache. */ context_switch sched_migrate_task migrates process P to cpu-1 Process swapper/0 context switch (to process P) (uses mm_struct of Process P) switch_mm_irqs_off() switch_slb load_slb++ /* * load_slb becomes 0 here * and we evict an entry from * the preload cache with * preload_age(). We still * keep HW SLB and preload * cache in sync, that is * because all HW SLB entries * anyways gets evicted in * switch_slb during SLBIA. * We then only add those * entries back in HW SLB, * which are currently * present in preload_cache * (after eviction). */ load_elf_binary continues... setup_new_exec() slb_setup_new_exec() sched_switch event sched_migrate_task migrates process P to cpu-0 context_switch from swapper/0 to Process P switch_mm_irqs_off() /* * Since both prev and next mm struct are same we don't call * switch_mmu_context(). This will cause the HW SLB and SW preload * cache to go out of sync in preload_new_slb_context. Because there * was an SLB entry which was evicted from both HW and preload cache * on cpu-1. Now later in preload_new_slb_context(), when we will try * to add the same preload entry again, we will add this to the SW * preload cache and then will add it to the HW SLB. Since on cpu-0 * this entry was never invalidated, hence adding this entry to the HW * SLB will cause a SLB multi-hit error. */ load_elf_binary cont ---truncated--- CVE-2025-71078 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71078.html CVE-2025-71078 https://bugzilla.suse.com/1256616 SUSE Bug 1256616 In the Linux kernel, the following vulnerability has been resolved: net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write A deadlock can occur between nfc_unregister_device() and rfkill_fop_write() due to lock ordering inversion between device_lock and rfkill_global_mutex. The problematic lock order is: Thread A (rfkill_fop_write): rfkill_fop_write() mutex_lock(&rfkill_global_mutex) rfkill_set_block() nfc_rfkill_set_block() nfc_dev_down() device_lock(&dev->dev) <- waits for device_lock Thread B (nfc_unregister_device): nfc_unregister_device() device_lock(&dev->dev) rfkill_unregister() mutex_lock(&rfkill_global_mutex) <- waits for rfkill_global_mutex This creates a classic ABBA deadlock scenario. Fix this by moving rfkill_unregister() and rfkill_destroy() outside the device_lock critical section. Store the rfkill pointer in a local variable before releasing the lock, then call rfkill_unregister() after releasing device_lock. This change is safe because rfkill_fop_write() holds rfkill_global_mutex while calling the rfkill callbacks, and rfkill_unregister() also acquires rfkill_global_mutex before cleanup. Therefore, rfkill_unregister() will wait for any ongoing callback to complete before proceeding, and device_del() is only called after rfkill_unregister() returns, preventing any use-after-free. The similar lock ordering in nfc_register_device() (device_lock -> rfkill_global_mutex via rfkill_register) is safe because during registration the device is not yet in rfkill_list, so no concurrent rfkill operations can occur on this device. CVE-2025-71079 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71079.html CVE-2025-71079 https://bugzilla.suse.com/1256619 SUSE Bug 1256619 In the Linux kernel, the following vulnerability has been resolved: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT On PREEMPT_RT kernels, after rt6_get_pcpu_route() returns NULL, the current task can be preempted. Another task running on the same CPU may then execute rt6_make_pcpu_route() and successfully install a pcpu_rt entry. When the first task resumes execution, its cmpxchg() in rt6_make_pcpu_route() will fail because rt6i_pcpu is no longer NULL, triggering the BUG_ON(prev). It's easy to reproduce it by adding mdelay() after rt6_get_pcpu_route(). Using preempt_disable/enable is not appropriate here because ip6_rt_pcpu_alloc() may sleep. Fix this by handling the cmpxchg() failure gracefully on PREEMPT_RT: free our allocation and return the existing pcpu_rt installed by another task. The BUG_ON is replaced by WARN_ON_ONCE for non-PREEMPT_RT kernels where such races should not occur. CVE-2025-71080 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71080.html CVE-2025-71080 https://bugzilla.suse.com/1256608 SUSE Bug 1256608 In the Linux kernel, the following vulnerability has been resolved: ASoC: stm32: sai: fix OF node leak on probe The reference taken to the sync provider OF node when probing the platform device is currently only dropped if the set_sync() callback fails during DAI probe. Make sure to drop the reference on platform probe failures (e.g. probe deferral) and on driver unbind. This also avoids a potential use-after-free in case the DAI is ever reprobed without first rebinding the platform driver. CVE-2025-71081 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71081.html CVE-2025-71081 https://bugzilla.suse.com/1256609 SUSE Bug 1256609 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: revert use of devm_kzalloc in btusb This reverts commit 98921dbd00c4e ("Bluetooth: Use devm_kzalloc in btusb.c file"). In btusb_probe(), we use devm_kzalloc() to allocate the btusb data. This ties the lifetime of all the btusb data to the binding of a driver to one interface, INTF. In a driver that binds to other interfaces, ISOC and DIAG, this is an accident waiting to happen. The issue is revealed in btusb_disconnect(), where calling usb_driver_release_interface(&btusb_driver, data->intf) will have devm free the data that is also being used by the other interfaces of the driver that may not be released yet. To fix this, revert the use of devm and go back to freeing memory explicitly. CVE-2025-71082 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71082.html CVE-2025-71082 https://bugzilla.suse.com/1256611 SUSE Bug 1256611 In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Avoid NULL pointer deref for evicted BOs It is possible for a BO to exist that is not currently associated with a resource, e.g. because it has been evicted. When devcoredump tries to read the contents of all BOs for dumping, we need to expect this as well -- in this case, ENODATA is recorded instead of the buffer contents. CVE-2025-71083 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71083.html CVE-2025-71083 https://bugzilla.suse.com/1256610 SUSE Bug 1256610 In the Linux kernel, the following vulnerability has been resolved: RDMA/cm: Fix leaking the multicast GID table reference If the CM ID is destroyed while the CM event for multicast creating is still queued the cancel_work_sync() will prevent the work from running which also prevents destroying the ah_attr. This leaks a refcount and triggers a WARN: GID entry ref leak for dev syz1 index 2 ref=573 WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline] WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886 Destroy the ah_attr after canceling the work, it is safe to call this twice. CVE-2025-71084 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71084.html CVE-2025-71084 https://bugzilla.suse.com/1256622 SUSE Bug 1256622 In the Linux kernel, the following vulnerability has been resolved: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() There exists a kernel oops caused by a BUG_ON(nhead < 0) at net/core/skbuff.c:2232 in pskb_expand_head(). This bug is triggered as part of the calipso_skbuff_setattr() routine when skb_cow() is passed headroom > INT_MAX (i.e. (int)(skb_headroom(skb) + len_delta) < 0). The root cause of the bug is due to an implicit integer cast in __skb_cow(). The check (headroom > skb_headroom(skb)) is meant to ensure that delta = headroom - skb_headroom(skb) is never negative, otherwise we will trigger a BUG_ON in pskb_expand_head(). However, if headroom > INT_MAX and delta <= -NET_SKB_PAD, the check passes, delta becomes negative, and pskb_expand_head() is passed a negative value for nhead. Fix the trigger condition in calipso_skbuff_setattr(). Avoid passing "negative" headroom sizes to skb_cow() within calipso_skbuff_setattr() by only using skb_cow() to grow headroom. PoC: Using `netlabelctl` tool: netlabelctl map del default netlabelctl calipso add pass doi:7 netlabelctl map add default address:0::1/128 protocol:calipso,7 Then run the following PoC: int fd = socket(AF_INET6, SOCK_DGRAM, IPPROTO_UDP); // setup msghdr int cmsg_size = 2; int cmsg_len = 0x60; struct msghdr msg; struct sockaddr_in6 dest_addr; struct cmsghdr * cmsg = (struct cmsghdr *) calloc(1, sizeof(struct cmsghdr) + cmsg_len); msg.msg_name = &dest_addr; msg.msg_namelen = sizeof(dest_addr); msg.msg_iov = NULL; msg.msg_iovlen = 0; msg.msg_control = cmsg; msg.msg_controllen = cmsg_len; msg.msg_flags = 0; // setup sockaddr dest_addr.sin6_family = AF_INET6; dest_addr.sin6_port = htons(31337); dest_addr.sin6_flowinfo = htonl(31337); dest_addr.sin6_addr = in6addr_loopback; dest_addr.sin6_scope_id = 31337; // setup cmsghdr cmsg->cmsg_len = cmsg_len; cmsg->cmsg_level = IPPROTO_IPV6; cmsg->cmsg_type = IPV6_HOPOPTS; char * hop_hdr = (char *)cmsg + sizeof(struct cmsghdr); hop_hdr[1] = 0x9; //set hop size - (0x9 + 1) * 8 = 80 sendmsg(fd, &msg, 0); CVE-2025-71085 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71085.html CVE-2025-71085 https://bugzilla.suse.com/1256623 SUSE Bug 1256623 https://bugzilla.suse.com/1256624 SUSE Bug 1256624 In the Linux kernel, the following vulnerability has been resolved: net: rose: fix invalid array index in rose_kill_by_device() rose_kill_by_device() collects sockets into a local array[] and then iterates over them to disconnect sockets bound to a device being brought down. The loop mistakenly indexes array[cnt] instead of array[i]. For cnt < ARRAY_SIZE(array), this reads an uninitialized entry; for cnt == ARRAY_SIZE(array), it is an out-of-bounds read. Either case can lead to an invalid socket pointer dereference and also leaks references taken via sock_hold(). Fix the index to use i. CVE-2025-71086 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71086.html CVE-2025-71086 https://bugzilla.suse.com/1256625 SUSE Bug 1256625 In the Linux kernel, the following vulnerability has been resolved: iavf: fix off-by-one issues in iavf_config_rss_reg() There are off-by-one bugs when configuring RSS hash key and lookup table, causing out-of-bounds reads to memory [1] and out-of-bounds writes to device registers. Before commit 43a3d9ba34c9 ("i40evf: Allow PF driver to configure RSS"), the loop upper bounds were: i <= I40E_VFQF_{HKEY,HLUT}_MAX_INDEX which is safe since the value is the last valid index. That commit changed the bounds to: i <= adapter->rss_{key,lut}_size / 4 where `rss_{key,lut}_size / 4` is the number of dwords, so the last valid index is `(rss_{key,lut}_size / 4) - 1`. Therefore, using `<=` accesses one element past the end. Fix the issues by using `<` instead of `<=`, ensuring we do not exceed the bounds. [1] KASAN splat about rss_key_size off-by-one BUG: KASAN: slab-out-of-bounds in iavf_config_rss+0x619/0x800 Read of size 4 at addr ffff888102c50134 by task kworker/u8:6/63 CPU: 0 UID: 0 PID: 63 Comm: kworker/u8:6 Not tainted 6.18.0-rc2-enjuk-tnguy-00378-g3005f5b77652-dirty #156 PREEMPT(voluntary) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Workqueue: iavf iavf_watchdog_task Call Trace: <TASK> dump_stack_lvl+0x6f/0xb0 print_report+0x170/0x4f3 kasan_report+0xe1/0x1a0 iavf_config_rss+0x619/0x800 iavf_watchdog_task+0x2be7/0x3230 process_one_work+0x7fd/0x1420 worker_thread+0x4d1/0xd40 kthread+0x344/0x660 ret_from_fork+0x249/0x320 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 63: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7f/0x90 __kmalloc_noprof+0x246/0x6f0 iavf_watchdog_task+0x28fc/0x3230 process_one_work+0x7fd/0x1420 worker_thread+0x4d1/0xd40 kthread+0x344/0x660 ret_from_fork+0x249/0x320 ret_from_fork_asm+0x1a/0x30 The buggy address belongs to the object at ffff888102c50100 which belongs to the cache kmalloc-64 of size 64 The buggy address is located 0 bytes to the right of allocated 52-byte region [ffff888102c50100, ffff888102c50134) The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x102c50 flags: 0x200000000000000(node=0|zone=2) page_type: f5(slab) raw: 0200000000000000 ffff8881000418c0 dead000000000122 0000000000000000 raw: 0000000000000000 0000000080200020 00000000f5000000 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888102c50000: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc ffff888102c50080: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc >ffff888102c50100: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc ^ ffff888102c50180: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc ffff888102c50200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc CVE-2025-71087 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71087.html CVE-2025-71087 https://bugzilla.suse.com/1256628 SUSE Bug 1256628 In the Linux kernel, the following vulnerability has been resolved: mptcp: fallback earlier on simult connection Syzkaller reports a simult-connect race leading to inconsistent fallback status: WARNING: CPU: 3 PID: 33 at net/mptcp/subflow.c:1515 subflow_data_ready+0x40b/0x7c0 net/mptcp/subflow.c:1515 Modules linked in: CPU: 3 UID: 0 PID: 33 Comm: ksoftirqd/3 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 RIP: 0010:subflow_data_ready+0x40b/0x7c0 net/mptcp/subflow.c:1515 Code: 89 ee e8 78 61 3c f6 40 84 ed 75 21 e8 8e 66 3c f6 44 89 fe bf 07 00 00 00 e8 c1 61 3c f6 41 83 ff 07 74 09 e8 76 66 3c f6 90 <0f> 0b 90 e8 6d 66 3c f6 48 89 df e8 e5 ad ff ff 31 ff 89 c5 89 c6 RSP: 0018:ffffc900006cf338 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff888031acd100 RCX: ffffffff8b7f2abf RDX: ffff88801e6ea440 RSI: ffffffff8b7f2aca RDI: 0000000000000005 RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000007 R10: 0000000000000004 R11: 0000000000002c10 R12: ffff88802ba69900 R13: 1ffff920000d9e67 R14: ffff888046f81800 R15: 0000000000000004 FS: 0000000000000000(0000) GS:ffff8880d69bc000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000560fc0ca1670 CR3: 0000000032c3a000 CR4: 0000000000352ef0 Call Trace: <TASK> tcp_data_queue+0x13b0/0x4f90 net/ipv4/tcp_input.c:5197 tcp_rcv_state_process+0xfdf/0x4ec0 net/ipv4/tcp_input.c:6922 tcp_v6_do_rcv+0x492/0x1740 net/ipv6/tcp_ipv6.c:1672 tcp_v6_rcv+0x2976/0x41e0 net/ipv6/tcp_ipv6.c:1918 ip6_protocol_deliver_rcu+0x188/0x1520 net/ipv6/ip6_input.c:438 ip6_input_finish+0x1e4/0x4b0 net/ipv6/ip6_input.c:489 NF_HOOK include/linux/netfilter.h:318 [inline] NF_HOOK include/linux/netfilter.h:312 [inline] ip6_input+0x105/0x2f0 net/ipv6/ip6_input.c:500 dst_input include/net/dst.h:471 [inline] ip6_rcv_finish net/ipv6/ip6_input.c:79 [inline] NF_HOOK include/linux/netfilter.h:318 [inline] NF_HOOK include/linux/netfilter.h:312 [inline] ipv6_rcv+0x264/0x650 net/ipv6/ip6_input.c:311 __netif_receive_skb_one_core+0x12d/0x1e0 net/core/dev.c:5979 __netif_receive_skb+0x1d/0x160 net/core/dev.c:6092 process_backlog+0x442/0x15e0 net/core/dev.c:6444 __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7494 napi_poll net/core/dev.c:7557 [inline] net_rx_action+0xa9f/0xfe0 net/core/dev.c:7684 handle_softirqs+0x216/0x8e0 kernel/softirq.c:579 run_ksoftirqd kernel/softirq.c:968 [inline] run_ksoftirqd+0x3a/0x60 kernel/softirq.c:960 smpboot_thread_fn+0x3f7/0xae0 kernel/smpboot.c:160 kthread+0x3c2/0x780 kernel/kthread.c:463 ret_from_fork+0x5d7/0x6f0 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK> The TCP subflow can process the simult-connect syn-ack packet after transitioning to TCP_FIN1 state, bypassing the MPTCP fallback check, as the sk_state_change() callback is not invoked for * -> FIN_WAIT1 transitions. That will move the msk socket to an inconsistent status and the next incoming data will hit the reported splat. Close the race moving the simult-fallback check at the earliest possible stage - that is at syn-ack generation time. About the fixes tags: [2] was supposed to also fix this issue introduced by [3]. [1] is required as a dependence: it was not explicitly marked as a fix, but it is one and it has already been backported before [3]. In other words, this commit should be backported up to [3], including [2] and [1] if that's not already there. CVE-2025-71088 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71088.html CVE-2025-71088 https://bugzilla.suse.com/1256630 SUSE Bug 1256630 In the Linux kernel, the following vulnerability has been resolved: iommu: disable SVA when CONFIG_X86 is set Patch series "Fix stale IOTLB entries for kernel address space", v7. This proposes a fix for a security vulnerability related to IOMMU Shared Virtual Addressing (SVA). In an SVA context, an IOMMU can cache kernel page table entries. When a kernel page table page is freed and reallocated for another purpose, the IOMMU might still hold stale, incorrect entries. This can be exploited to cause a use-after-free or write-after-free condition, potentially leading to privilege escalation or data corruption. This solution introduces a deferred freeing mechanism for kernel page table pages, which provides a safe window to notify the IOMMU to invalidate its caches before the page is reused. This patch (of 8): In the IOMMU Shared Virtual Addressing (SVA) context, the IOMMU hardware shares and walks the CPU's page tables. The x86 architecture maps the kernel's virtual address space into the upper portion of every process's page table. Consequently, in an SVA context, the IOMMU hardware can walk and cache kernel page table entries. The Linux kernel currently lacks a notification mechanism for kernel page table changes, specifically when page table pages are freed and reused. The IOMMU driver is only notified of changes to user virtual address mappings. This can cause the IOMMU's internal caches to retain stale entries for kernel VA. Use-After-Free (UAF) and Write-After-Free (WAF) conditions arise when kernel page table pages are freed and later reallocated. The IOMMU could misinterpret the new data as valid page table entries. The IOMMU might then walk into attacker-controlled memory, leading to arbitrary physical memory DMA access or privilege escalation. This is also a Write-After-Free issue, as the IOMMU will potentially continue to write Accessed and Dirty bits to the freed memory while attempting to walk the stale page tables. Currently, SVA contexts are unprivileged and cannot access kernel mappings. However, the IOMMU will still walk kernel-only page tables all the way down to the leaf entries, where it realizes the mapping is for the kernel and errors out. This means the IOMMU still caches these intermediate page table entries, making the described vulnerability a real concern. Disable SVA on x86 architecture until the IOMMU can receive notification to flush the paging cache before freeing the CPU kernel page table pages. CVE-2025-71089 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71089.html CVE-2025-71089 https://bugzilla.suse.com/1256612 SUSE Bug 1256612 https://bugzilla.suse.com/1256615 SUSE Bug 1256615 In the Linux kernel, the following vulnerability has been resolved: team: fix check for port enabled in team_queue_override_port_prio_changed() There has been a syzkaller bug reported recently with the following trace: list_del corruption, ffff888058bea080->prev is LIST_POISON2 (dead000000000122) ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:59! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 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 RIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59 Code: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 <0f> 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff RSP: 0018:ffffc9000d49f370 EFLAGS: 00010286 RAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000 RDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005 RBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000 R10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230 R13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480 FS: 00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0 Call Trace: <TASK> __list_del_entry_valid include/linux/list.h:132 [inline] __list_del_entry include/linux/list.h:223 [inline] list_del_rcu include/linux/rculist.h:178 [inline] __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline] __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline] team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline] team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534 team_option_set drivers/net/team/team_core.c:376 [inline] team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653 genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115 genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline] genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210 netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552 genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219 netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline] netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346 netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg net/socket.c:742 [inline] ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630 ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684 __sys_sendmsg+0x16d/0x220 net/socket.c:2716 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f The problem is in this flow: 1) Port is enabled, queue_id != 0, in qom_list 2) Port gets disabled -> team_port_disable() -> team_queue_override_port_del() -> del (removed from list) 3) Port is disabled, queue_id != 0, not in any list 4) Priority changes -> team_queue_override_port_prio_changed() -> checks: port disabled && queue_id != 0 -> calls del - hits the BUG as it is removed already To fix this, change the check in team_queue_override_port_prio_changed() so it returns early if port is not enabled. CVE-2025-71091 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71091.html CVE-2025-71091 https://bugzilla.suse.com/1256773 SUSE Bug 1256773 In the Linux kernel, the following vulnerability has been resolved: e1000: fix OOB in e1000_tbi_should_accept() In e1000_tbi_should_accept() we read the last byte of the frame via 'data[length - 1]' to evaluate the TBI workaround. If the descriptor- reported length is zero or larger than the actual RX buffer size, this read goes out of bounds and can hit unrelated slab objects. The issue is observed from the NAPI receive path (e1000_clean_rx_irq): ================================================================== BUG: KASAN: slab-out-of-bounds in e1000_tbi_should_accept+0x610/0x790 Read of size 1 at addr ffff888014114e54 by task sshd/363 CPU: 0 PID: 363 Comm: sshd Not tainted 5.18.0-rc1 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014 Call Trace: <IRQ> dump_stack_lvl+0x5a/0x74 print_address_description+0x7b/0x440 print_report+0x101/0x200 kasan_report+0xc1/0xf0 e1000_tbi_should_accept+0x610/0x790 e1000_clean_rx_irq+0xa8c/0x1110 e1000_clean+0xde2/0x3c10 __napi_poll+0x98/0x380 net_rx_action+0x491/0xa20 __do_softirq+0x2c9/0x61d do_softirq+0xd1/0x120 </IRQ> <TASK> __local_bh_enable_ip+0xfe/0x130 ip_finish_output2+0x7d5/0xb00 __ip_queue_xmit+0xe24/0x1ab0 __tcp_transmit_skb+0x1bcb/0x3340 tcp_write_xmit+0x175d/0x6bd0 __tcp_push_pending_frames+0x7b/0x280 tcp_sendmsg_locked+0x2e4f/0x32d0 tcp_sendmsg+0x24/0x40 sock_write_iter+0x322/0x430 vfs_write+0x56c/0xa60 ksys_write+0xd1/0x190 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f511b476b10 Code: 73 01 c3 48 8b 0d 88 d3 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d f9 2b 2c 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 8e 9b 01 00 48 89 04 24 RSP: 002b:00007ffc9211d4e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000004024 RCX: 00007f511b476b10 RDX: 0000000000004024 RSI: 0000559a9385962c RDI: 0000000000000003 RBP: 0000559a9383a400 R08: fffffffffffffff0 R09: 0000000000004f00 R10: 0000000000000070 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc9211d57f R14: 0000559a9347bde7 R15: 0000000000000003 </TASK> Allocated by task 1: __kasan_krealloc+0x131/0x1c0 krealloc+0x90/0xc0 add_sysfs_param+0xcb/0x8a0 kernel_add_sysfs_param+0x81/0xd4 param_sysfs_builtin+0x138/0x1a6 param_sysfs_init+0x57/0x5b do_one_initcall+0x104/0x250 do_initcall_level+0x102/0x132 do_initcalls+0x46/0x74 kernel_init_freeable+0x28f/0x393 kernel_init+0x14/0x1a0 ret_from_fork+0x22/0x30 The buggy address belongs to the object at ffff888014114000 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 1620 bytes to the right of 2048-byte region [ffff888014114000, ffff888014114800] The buggy address belongs to the physical page: page:ffffea0000504400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14110 head:ffffea0000504400 order:3 compound_mapcount:0 compound_pincount:0 flags: 0x100000000010200(slab|head|node=0|zone=1) raw: 0100000000010200 0000000000000000 dead000000000001 ffff888013442000 raw: 0000000000000000 0000000000080008 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected ================================================================== This happens because the TBI check unconditionally dereferences the last byte without validating the reported length first: u8 last_byte = *(data + length - 1); Fix by rejecting the frame early if the length is zero, or if it exceeds adapter->rx_buffer_len. This preserves the TBI workaround semantics for valid frames and prevents touching memory beyond the RX buffer. CVE-2025-71093 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71093.html CVE-2025-71093 https://bugzilla.suse.com/1256777 SUSE Bug 1256777 In the Linux kernel, the following vulnerability has been resolved: net: usb: asix: validate PHY address before use The ASIX driver reads the PHY address from the USB device via asix_read_phy_addr(). A malicious or faulty device can return an invalid address (>= PHY_MAX_ADDR), which causes a warning in mdiobus_get_phy(): addr 207 out of range WARNING: drivers/net/phy/mdio_bus.c:76 Validate the PHY address in asix_read_phy_addr() and remove the now-redundant check in ax88172a.c. CVE-2025-71094 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71094.html CVE-2025-71094 https://bugzilla.suse.com/1256597 SUSE Bug 1256597 In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix the crash issue for zero copy XDP_TX action There is a crash issue when running zero copy XDP_TX action, the crash log is shown below. [ 216.122464] Unable to handle kernel paging request at virtual address fffeffff80000000 [ 216.187524] Internal error: Oops: 0000000096000144 [#1] SMP [ 216.301694] Call trace: [ 216.304130] dcache_clean_poc+0x20/0x38 (P) [ 216.308308] __dma_sync_single_for_device+0x1bc/0x1e0 [ 216.313351] stmmac_xdp_xmit_xdpf+0x354/0x400 [ 216.317701] __stmmac_xdp_run_prog+0x164/0x368 [ 216.322139] stmmac_napi_poll_rxtx+0xba8/0xf00 [ 216.326576] __napi_poll+0x40/0x218 [ 216.408054] Kernel panic - not syncing: Oops: Fatal exception in interrupt For XDP_TX action, the xdp_buff is converted to xdp_frame by xdp_convert_buff_to_frame(). The memory type of the resulting xdp_frame depends on the memory type of the xdp_buff. For page pool based xdp_buff it produces xdp_frame with memory type MEM_TYPE_PAGE_POOL. For zero copy XSK pool based xdp_buff it produces xdp_frame with memory type MEM_TYPE_PAGE_ORDER0. However, stmmac_xdp_xmit_back() does not check the memory type and always uses the page pool type, this leads to invalid mappings and causes the crash. Therefore, check the xdp_buff memory type in stmmac_xdp_xmit_back() to fix this issue. CVE-2025-71095 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71095.html CVE-2025-71095 https://bugzilla.suse.com/1256605 SUSE Bug 1256605 In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly The netlink response for RDMA_NL_LS_OP_IP_RESOLVE should always have a LS_NLA_TYPE_DGID attribute, it is invalid if it does not. Use the nl parsing logic properly and call nla_parse_deprecated() to fill the nlattrs array and then directly index that array to get the data for the DGID. Just fail if it is NULL. Remove the for loop searching for the nla, and squash the validation and parsing into one function. Fixes an uninitialized read from the stack triggered by userspace if it does not provide the DGID to a kernel initiated RDMA_NL_LS_OP_IP_RESOLVE query. BUG: KMSAN: uninit-value in hex_byte_pack include/linux/hex.h:13 [inline] BUG: KMSAN: uninit-value in ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490 hex_byte_pack include/linux/hex.h:13 [inline] ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490 ip6_addr_string+0x18a/0x3e0 lib/vsprintf.c:1509 ip_addr_string+0x245/0xee0 lib/vsprintf.c:1633 pointer+0xc09/0x1bd0 lib/vsprintf.c:2542 vsnprintf+0xf8a/0x1bd0 lib/vsprintf.c:2930 vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2279 vprintk_emit+0x307/0xcd0 kernel/printk/printk.c:2426 vprintk_default+0x3f/0x50 kernel/printk/printk.c:2465 vprintk+0x36/0x50 kernel/printk/printk_safe.c:82 _printk+0x17e/0x1b0 kernel/printk/printk.c:2475 ib_nl_process_good_ip_rsep drivers/infiniband/core/addr.c:128 [inline] ib_nl_handle_ip_res_resp+0x963/0x9d0 drivers/infiniband/core/addr.c:141 rdma_nl_rcv_msg drivers/infiniband/core/netlink.c:-1 [inline] rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline] rdma_nl_rcv+0xefa/0x11c0 drivers/infiniband/core/netlink.c:259 netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline] netlink_unicast+0xf04/0x12b0 net/netlink/af_netlink.c:1346 netlink_sendmsg+0x10b3/0x1250 net/netlink/af_netlink.c:1896 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg+0x333/0x3d0 net/socket.c:729 ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2617 ___sys_sendmsg+0x271/0x3b0 net/socket.c:2671 __sys_sendmsg+0x1aa/0x300 net/socket.c:2703 __compat_sys_sendmsg net/compat.c:346 [inline] __do_compat_sys_sendmsg net/compat.c:353 [inline] __se_compat_sys_sendmsg net/compat.c:350 [inline] __ia32_compat_sys_sendmsg+0xa4/0x100 net/compat.c:350 ia32_sys_call+0x3f6c/0x4310 arch/x86/include/generated/asm/syscalls_32.h:371 do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline] __do_fast_syscall_32+0xb0/0x150 arch/x86/entry/syscall_32.c:306 do_fast_syscall_32+0x38/0x80 arch/x86/entry/syscall_32.c:331 do_SYSENTER_32+0x1f/0x30 arch/x86/entry/syscall_32.c:3 CVE-2025-71096 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71096.html CVE-2025-71096 https://bugzilla.suse.com/1256606 SUSE Bug 1256606 In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix reference count leak when using error routes with nexthop objects When a nexthop object is deleted, it is marked as dead and then fib_table_flush() is called to flush all the routes that are using the dead nexthop. The current logic in fib_table_flush() is to only flush error routes (e.g., blackhole) when it is called as part of network namespace dismantle (i.e., with flush_all=true). Therefore, error routes are not flushed when their nexthop object is deleted: # ip link add name dummy1 up type dummy # ip nexthop add id 1 dev dummy1 # ip route add 198.51.100.1/32 nhid 1 # ip route add blackhole 198.51.100.2/32 nhid 1 # ip nexthop del id 1 # ip route show blackhole 198.51.100.2 nhid 1 dev dummy1 As such, they keep holding a reference on the nexthop object which in turn holds a reference on the nexthop device, resulting in a reference count leak: # ip link del dev dummy1 [ 70.516258] unregister_netdevice: waiting for dummy1 to become free. Usage count = 2 Fix by flushing error routes when their nexthop is marked as dead. IPv6 does not suffer from this problem. CVE-2025-71097 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71097.html CVE-2025-71097 https://bugzilla.suse.com/1256607 SUSE Bug 1256607 In the Linux kernel, the following vulnerability has been resolved: ip6_gre: make ip6gre_header() robust Over the years, syzbot found many ways to crash the kernel in ip6gre_header() [1]. This involves team or bonding drivers ability to dynamically change their dev->needed_headroom and/or dev->hard_header_len In this particular crash mld_newpack() allocated an skb with a too small reserve/headroom, and by the time mld_sendpack() was called, syzbot managed to attach an ip6gre device. [1] skbuff: skb_under_panic: text:ffffffff8a1d69a8 len:136 put:40 head:ffff888059bc7000 data:ffff888059bc6fe8 tail:0x70 end:0x6c0 dev:team0 ------------[ cut here ]------------ kernel BUG at net/core/skbuff.c:213 ! <TASK> skb_under_panic net/core/skbuff.c:223 [inline] skb_push+0xc3/0xe0 net/core/skbuff.c:2641 ip6gre_header+0xc8/0x790 net/ipv6/ip6_gre.c:1371 dev_hard_header include/linux/netdevice.h:3436 [inline] neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618 neigh_output include/net/neighbour.h:556 [inline] ip6_finish_output2+0xfb3/0x1480 net/ipv6/ip6_output.c:136 __ip6_finish_output net/ipv6/ip6_output.c:-1 [inline] ip6_finish_output+0x234/0x7d0 net/ipv6/ip6_output.c:220 NF_HOOK_COND include/linux/netfilter.h:307 [inline] ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247 NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318 mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855 mld_send_cr net/ipv6/mcast.c:2154 [inline] mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693 CVE-2025-71098 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71098.html CVE-2025-71098 https://bugzilla.suse.com/1256591 SUSE Bug 1256591 In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl() In xe_oa_add_config_ioctl(), we accessed oa_config->id after dropping metrics_lock. Since this lock protects the lifetime of oa_config, an attacker could guess the id and call xe_oa_remove_config_ioctl() with perfect timing, freeing oa_config before we dereference it, leading to a potential use-after-free. Fix this by caching the id in a local variable while holding the lock. v2: (Matt A) - Dropped mutex_unlock(&oa->metrics_lock) ordering change from xe_oa_remove_config_ioctl() (cherry picked from commit 28aeaed130e8e587fd1b73b6d66ca41ccc5a1a31) CVE-2025-71099 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71099.html CVE-2025-71099 https://bugzilla.suse.com/1256592 SUSE Bug 1256592 In the Linux kernel, the following vulnerability has been resolved: wifi: rtlwifi: 8192cu: fix tid out of range in rtl92cu_tx_fill_desc() TID getting from ieee80211_get_tid() might be out of range of array size of sta_entry->tids[], so check TID is less than MAX_TID_COUNT. Othwerwise, UBSAN warn: UBSAN: array-index-out-of-bounds in drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c:514:30 index 10 is out of range for type 'rtl_tid_data [9]' CVE-2025-71100 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71100.html CVE-2025-71100 https://bugzilla.suse.com/1256593 SUSE Bug 1256593 In the Linux kernel, the following vulnerability has been resolved: platform/x86: hp-bioscfg: Fix out-of-bounds array access in ACPI package parsing The hp_populate_*_elements_from_package() functions in the hp-bioscfg driver contain out-of-bounds array access vulnerabilities. These functions parse ACPI packages into internal data structures using a for loop with index variable 'elem' that iterates through enum_obj/integer_obj/order_obj/password_obj/string_obj arrays. When processing multi-element fields like PREREQUISITES and ENUM_POSSIBLE_VALUES, these functions read multiple consecutive array elements using expressions like 'enum_obj[elem + reqs]' and 'enum_obj[elem + pos_values]' within nested loops. The bug is that the bounds check only validated elem, but did not consider the additional offset when accessing elem + reqs or elem + pos_values. The fix changes the bounds check to validate the actual accessed index. CVE-2025-71101 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71101.html CVE-2025-71101 https://bugzilla.suse.com/1256594 SUSE Bug 1256594 In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: Handle incorrect num_connectors capability The UCSI spec states that the num_connectors field is 7 bits, and the 8th bit is reserved and should be set to zero. Some buggy FW has been known to set this bit, and it can lead to a system not booting. Flag that the FW is not behaving correctly, and auto-fix the value so that the system boots correctly. Found on Lenovo P1 G8 during Linux enablement program. The FW will be fixed, but seemed worth addressing in case it hit platforms that aren't officially Linux supported. CVE-2025-71108 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71108.html CVE-2025-71108 https://bugzilla.suse.com/1256774 SUSE Bug 1256774 In the Linux kernel, the following vulnerability has been resolved: hwmon: (w83791d) Convert macros to functions to avoid TOCTOU The macro FAN_FROM_REG evaluates its arguments multiple times. When used in lockless contexts involving shared driver data, this leads to Time-of-Check to Time-of-Use (TOCTOU) race conditions, potentially causing divide-by-zero errors. Convert the macro to a static function. This guarantees that arguments are evaluated only once (pass-by-value), preventing the race conditions. Additionally, in store_fan_div, move the calculation of the minimum limit inside the update lock. This ensures that the read-modify-write sequence operates on consistent data. Adhere to the principle of minimal changes by only converting macros that evaluate arguments multiple times and are used in lockless contexts. CVE-2025-71111 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71111.html CVE-2025-71111 https://bugzilla.suse.com/1256728 SUSE Bug 1256728 In the Linux kernel, the following vulnerability has been resolved: net: hns3: add VLAN id validation before using Currently, the VLAN id may be used without validation when receive a VLAN configuration mailbox from VF. The length of vlan_del_fail_bmap is BITS_TO_LONGS(VLAN_N_VID). It may cause out-of-bounds memory access once the VLAN id is bigger than or equal to VLAN_N_VID. Therefore, VLAN id needs to be checked to ensure it is within the range of VLAN_N_VID. CVE-2025-71112 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71112.html CVE-2025-71112 https://bugzilla.suse.com/1256726 SUSE Bug 1256726 https://bugzilla.suse.com/1256727 SUSE Bug 1256727 In the Linux kernel, the following vulnerability has been resolved: via_wdt: fix critical boot hang due to unnamed resource allocation The VIA watchdog driver uses allocate_resource() to reserve a MMIO region for the watchdog control register. However, the allocated resource was not given a name, which causes the kernel resource tree to contain an entry marked as "<BAD>" under /proc/iomem on x86 platforms. During boot, this unnamed resource can lead to a critical hang because subsequent resource lookups and conflict checks fail to handle the invalid entry properly. CVE-2025-71114 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71114.html CVE-2025-71114 https://bugzilla.suse.com/1256752 SUSE Bug 1256752 In the Linux kernel, the following vulnerability has been resolved: libceph: make decode_pool() more resilient against corrupted osdmaps If the osdmap is (maliciously) corrupted such that the encoded length of ceph_pg_pool envelope is less than what is expected for a particular encoding version, out-of-bounds reads may ensue because the only bounds check that is there is based on that length value. This patch adds explicit bounds checks for each field that is decoded or skipped. CVE-2025-71116 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71116.html CVE-2025-71116 https://bugzilla.suse.com/1256744 SUSE Bug 1256744 In the Linux kernel, the following vulnerability has been resolved: ACPICA: Avoid walking the Namespace if start_node is NULL Although commit 0c9992315e73 ("ACPICA: Avoid walking the ACPI Namespace if it is not there") fixed the situation when both start_node and acpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed on Honor Magicbook 14 Pro [1]. That happens due to the access to the member of parent_node in acpi_ns_get_next_node(). The NULL pointer dereference will always happen, no matter whether or not the start_node is equal to ACPI_ROOT_OBJECT, so move the check of start_node being NULL out of the if block. Unfortunately, all the attempts to contact Honor have failed, they refused to provide any technical support for Linux. The bad DSDT table's dump could be found on GitHub [2]. DMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025 [ rjw: Subject adjustment, changelog edits ] CVE-2025-71118 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71118.html CVE-2025-71118 https://bugzilla.suse.com/1256763 SUSE Bug 1256763 In the Linux kernel, the following vulnerability has been resolved: powerpc/kexec: Enable SMT before waking offline CPUs If SMT is disabled or a partial SMT state is enabled, when a new kernel image is loaded for kexec, on reboot the following warning is observed: kexec: Waking offline cpu 228. WARNING: CPU: 0 PID: 9062 at arch/powerpc/kexec/core_64.c:223 kexec_prepare_cpus+0x1b0/0x1bc [snip] NIP kexec_prepare_cpus+0x1b0/0x1bc LR kexec_prepare_cpus+0x1a0/0x1bc Call Trace: kexec_prepare_cpus+0x1a0/0x1bc (unreliable) default_machine_kexec+0x160/0x19c machine_kexec+0x80/0x88 kernel_kexec+0xd0/0x118 __do_sys_reboot+0x210/0x2c4 system_call_exception+0x124/0x320 system_call_vectored_common+0x15c/0x2ec This occurs as add_cpu() fails due to cpu_bootable() returning false for CPUs that fail the cpu_smt_thread_allowed() check or non primary threads if SMT is disabled. Fix the issue by enabling SMT and resetting the number of SMT threads to the number of threads per core, before attempting to wake up all present CPUs. CVE-2025-71119 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71119.html CVE-2025-71119 https://bugzilla.suse.com/1256730 SUSE Bug 1256730 In the Linux kernel, the following vulnerability has been resolved: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf A zero length gss_token results in pages == 0 and in_token->pages[0] is NULL. The code unconditionally evaluates page_address(in_token->pages[0]) for the initial memcpy, which can dereference NULL even when the copy length is 0. Guard the first memcpy so it only runs when length > 0. CVE-2025-71120 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71120.html CVE-2025-71120 https://bugzilla.suse.com/1256779 SUSE Bug 1256779 https://bugzilla.suse.com/1256780 SUSE Bug 1256780 In the Linux kernel, the following vulnerability has been resolved: ext4: fix string copying in parse_apply_sb_mount_options() strscpy_pad() can't be used to copy a non-NUL-term string into a NUL-term string of possibly bigger size. Commit 0efc5990bca5 ("string.h: Introduce memtostr() and memtostr_pad()") provides additional information in that regard. So if this happens, the following warning is observed: strnlen: detected buffer overflow: 65 byte read of buffer size 64 WARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032 Modules linked in: CPU: 0 UID: 0 PID: 28655 Comm: syz-executor.3 Not tainted 6.12.54-syzkaller-00144-g5f0270f1ba00 #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__fortify_report+0x96/0xc0 lib/string_helpers.c:1032 Call Trace: <TASK> __fortify_panic+0x1f/0x30 lib/string_helpers.c:1039 strnlen include/linux/fortify-string.h:235 [inline] sized_strscpy include/linux/fortify-string.h:309 [inline] parse_apply_sb_mount_options fs/ext4/super.c:2504 [inline] __ext4_fill_super fs/ext4/super.c:5261 [inline] ext4_fill_super+0x3c35/0xad00 fs/ext4/super.c:5706 get_tree_bdev_flags+0x387/0x620 fs/super.c:1636 vfs_get_tree+0x93/0x380 fs/super.c:1814 do_new_mount fs/namespace.c:3553 [inline] path_mount+0x6ae/0x1f70 fs/namespace.c:3880 do_mount fs/namespace.c:3893 [inline] __do_sys_mount fs/namespace.c:4103 [inline] __se_sys_mount fs/namespace.c:4080 [inline] __x64_sys_mount+0x280/0x300 fs/namespace.c:4080 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x64/0x140 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x76/0x7e Since userspace is expected to provide s_mount_opts field to be at most 63 characters long with the ending byte being NUL-term, use a 64-byte buffer which matches the size of s_mount_opts, so that strscpy_pad() does its job properly. Return with error if the user still managed to provide a non-NUL-term string here. Found by Linux Verification Center (linuxtesting.org) with Syzkaller. CVE-2025-71123 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71123.html CVE-2025-71123 https://bugzilla.suse.com/1256757 SUSE Bug 1256757 In the Linux kernel, the following vulnerability has been resolved: drm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer Initialize the eb.vma array with values of 0 when the eb structure is first set up. In particular, this sets the eb->vma[i].vma pointers to NULL, simplifying cleanup and getting rid of the bug described below. During the execution of eb_lookup_vmas(), the eb->vma array is successively filled up with struct eb_vma objects. This process includes calling eb_add_vma(), which might fail; however, even in the event of failure, eb->vma[i].vma is set for the currently processed buffer. If eb_add_vma() fails, eb_lookup_vmas() returns with an error, which prompts a call to eb_release_vmas() to clean up the mess. Since eb_lookup_vmas() might fail during processing any (possibly not first) buffer, eb_release_vmas() checks whether a buffer's vma is NULL to know at what point did the lookup function fail. In eb_lookup_vmas(), eb->vma[i].vma is set to NULL if either the helper function eb_lookup_vma() or eb_validate_vma() fails. eb->vma[i+1].vma is set to NULL in case i915_gem_object_userptr_submit_init() fails; the current one needs to be cleaned up by eb_release_vmas() at this point, so the next one is set. If eb_add_vma() fails, neither the current nor the next vma is set to NULL, which is a source of a NULL deref bug described in the issue linked in the Closes tag. When entering eb_lookup_vmas(), the vma pointers are set to the slab poison value, instead of NULL. This doesn't matter for the actual lookup, since it gets overwritten anyway, however the eb_release_vmas() function only recognizes NULL as the stopping value, hence the pointers are being set to NULL as they go in case of intermediate failure. This patch changes the approach to filling them all with NULL at the start instead, rather than handling that manually during failure. (cherry picked from commit 08889b706d4f0b8d2352b7ca29c2d8df4d0787cd) CVE-2025-71130 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71130.html CVE-2025-71130 https://bugzilla.suse.com/1256741 SUSE Bug 1256741 In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Do not use req->iv after crypto_aead_encrypt As soon as crypto_aead_encrypt is called, the underlying request may be freed by an asynchronous completion. Thus dereferencing req->iv after it returns is invalid. Instead of checking req->iv against info, create a new variable unaligned_info and use it for that purpose instead. CVE-2025-71131 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71131.html CVE-2025-71131 https://bugzilla.suse.com/1256742 SUSE Bug 1256742 In the Linux kernel, the following vulnerability has been resolved: smc91x: fix broken irq-context in PREEMPT_RT When smc91x.c is built with PREEMPT_RT, the following splat occurs in FVP_RevC: [ 13.055000] smc91x LNRO0003:00 eth0: link up, 10Mbps, half-duplex, lpa 0x0000 [ 13.062137] BUG: workqueue leaked atomic, lock or RCU: kworker/2:1[106] [ 13.062137] preempt=0x00000000 lock=0->0 RCU=0->1 workfn=mld_ifc_work [ 13.062266] C ** replaying previous printk message ** [ 13.062266] CPU: 2 UID: 0 PID: 106 Comm: kworker/2:1 Not tainted 6.18.0-dirty #179 PREEMPT_{RT,(full)} [ 13.062353] Hardware name: , BIOS [ 13.062382] Workqueue: mld mld_ifc_work [ 13.062469] Call trace: [ 13.062494] show_stack+0x24/0x40 (C) [ 13.062602] __dump_stack+0x28/0x48 [ 13.062710] dump_stack_lvl+0x7c/0xb0 [ 13.062818] dump_stack+0x18/0x34 [ 13.062926] process_scheduled_works+0x294/0x450 [ 13.063043] worker_thread+0x260/0x3d8 [ 13.063124] kthread+0x1c4/0x228 [ 13.063235] ret_from_fork+0x10/0x20 This happens because smc_special_trylock() disables IRQs even on PREEMPT_RT, but smc_special_unlock() does not restore IRQs on PREEMPT_RT. The reason is that smc_special_unlock() calls spin_unlock_irqrestore(), and rcu_read_unlock_bh() in __dev_queue_xmit() cannot invoke rcu_read_unlock() through __local_bh_enable_ip() when current->softirq_disable_cnt becomes zero. To address this issue, replace smc_special_trylock() with spin_trylock_irqsave(). CVE-2025-71132 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71132.html CVE-2025-71132 https://bugzilla.suse.com/1256737 SUSE Bug 1256737 In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: avoid invalid read in irdma_net_event irdma_net_event() should not dereference anything from "neigh" (alias "ptr") until it has checked that the event is NETEVENT_NEIGH_UPDATE. Other events come with different structures pointed to by "ptr" and they may be smaller than struct neighbour. Move the read of neigh->dev under the NETEVENT_NEIGH_UPDATE case. The bug is mostly harmless, but it triggers KASAN on debug kernels: BUG: KASAN: stack-out-of-bounds in irdma_net_event+0x32e/0x3b0 [irdma] Read of size 8 at addr ffffc900075e07f0 by task kworker/27:2/542554 CPU: 27 PID: 542554 Comm: kworker/27:2 Kdump: loaded Not tainted 5.14.0-630.el9.x86_64+debug #1 Hardware name: [...] Workqueue: events rt6_probe_deferred Call Trace: <IRQ> dump_stack_lvl+0x60/0xb0 print_address_description.constprop.0+0x2c/0x3f0 print_report+0xb4/0x270 kasan_report+0x92/0xc0 irdma_net_event+0x32e/0x3b0 [irdma] notifier_call_chain+0x9e/0x180 atomic_notifier_call_chain+0x5c/0x110 rt6_do_redirect+0xb91/0x1080 tcp_v6_err+0xe9b/0x13e0 icmpv6_notify+0x2b2/0x630 ndisc_redirect_rcv+0x328/0x530 icmpv6_rcv+0xc16/0x1360 ip6_protocol_deliver_rcu+0xb84/0x12e0 ip6_input_finish+0x117/0x240 ip6_input+0xc4/0x370 ipv6_rcv+0x420/0x7d0 __netif_receive_skb_one_core+0x118/0x1b0 process_backlog+0xd1/0x5d0 __napi_poll.constprop.0+0xa3/0x440 net_rx_action+0x78a/0xba0 handle_softirqs+0x2d4/0x9c0 do_softirq+0xad/0xe0 </IRQ> CVE-2025-71133 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71133.html CVE-2025-71133 https://bugzilla.suse.com/1256733 SUSE Bug 1256733 In the Linux kernel, the following vulnerability has been resolved: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() The variable mddev->private is first assigned to conf and then checked: conf = mddev->private; if (!conf) ... If conf is NULL, then mddev->private is also NULL. In this case, null-pointer dereferences can occur when calling raid5_quiesce(): raid5_quiesce(mddev, true); raid5_quiesce(mddev, false); since mddev->private is assigned to conf again in raid5_quiesce(), and conf is dereferenced in several places, for example: conf->quiesce = 0; wake_up(&conf->wait_for_quiescent); To fix this issue, the function should unlock mddev and return before invoking raid5_quiesce() when conf is NULL, following the existing pattern in raid5_change_consistency_policy(). CVE-2025-71135 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71135.html CVE-2025-71135 https://bugzilla.suse.com/1256761 SUSE Bug 1256761 In the Linux kernel, the following vulnerability has been resolved: media: adv7842: Avoid possible out-of-bounds array accesses in adv7842_cp_log_status() It's possible for cp_read() and hdmi_read() to return -EIO. Those values are further used as indexes for accessing arrays. Fix that by checking return values where it's needed. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2025-71136 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71136.html CVE-2025-71136 https://bugzilla.suse.com/1256759 SUSE Bug 1256759 In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: fix "UBSAN: shift-out-of-bounds error" This patch ensures that the RX ring size (rx_pending) is not set below the permitted length. This avoids UBSAN shift-out-of-bounds errors when users passes small or zero ring sizes via ethtool -G. CVE-2025-71137 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71137.html CVE-2025-71137 https://bugzilla.suse.com/1256760 SUSE Bug 1256760 In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: Add missing NULL pointer check for pingpong interface It is checked almost always in dpu_encoder_phys_wb_setup_ctl(), but in a single place the check is missing. Also use convenient locals instead of phys_enc->* where available. Patchwork: https://patchwork.freedesktop.org/patch/693860/ CVE-2025-71138 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71138.html CVE-2025-71138 https://bugzilla.suse.com/1256785 SUSE Bug 1256785 In the Linux kernel, the following vulnerability has been resolved: drm/tilcdc: Fix removal actions in case of failed probe The drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers should only be called when the device has been successfully registered. Currently, these functions are called unconditionally in tilcdc_fini(), which causes warnings during probe deferral scenarios. [ 7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68 ... [ 8.005820] drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108 [ 8.005858] drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8 [ 8.005885] drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144 [ 8.005911] drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc] [ 8.005957] tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc] Fix this by rewriting the failed probe cleanup path using the standard goto error handling pattern, which ensures that cleanup functions are only called on successfully initialized resources. Additionally, remove the now-unnecessary is_registered flag. CVE-2025-71141 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71141.html CVE-2025-71141 https://bugzilla.suse.com/1256756 SUSE Bug 1256756 In the Linux kernel, the following vulnerability has been resolved: cpuset: fix warning when disabling remote partition A warning was triggered as follows: WARNING: kernel/cgroup/cpuset.c:1651 at remote_partition_disable+0xf7/0x110 RIP: 0010:remote_partition_disable+0xf7/0x110 RSP: 0018:ffffc90001947d88 EFLAGS: 00000206 RAX: 0000000000007fff RBX: ffff888103b6e000 RCX: 0000000000006f40 RDX: 0000000000006f00 RSI: ffffc90001947da8 RDI: ffff888103b6e000 RBP: ffff888103b6e000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: ffff88810b2e2728 R12: ffffc90001947da8 R13: 0000000000000000 R14: ffffc90001947da8 R15: ffff8881081f1c00 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f55c8bbe0b2 CR3: 000000010b14c000 CR4: 00000000000006f0 Call Trace: <TASK> update_prstate+0x2d3/0x580 cpuset_partition_write+0x94/0xf0 kernfs_fop_write_iter+0x147/0x200 vfs_write+0x35d/0x500 ksys_write+0x66/0xe0 do_syscall_64+0x6b/0x390 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f55c8cd4887 Reproduction steps (on a 16-CPU machine): # cd /sys/fs/cgroup/ # mkdir A1 # echo +cpuset > A1/cgroup.subtree_control # echo "0-14" > A1/cpuset.cpus.exclusive # mkdir A1/A2 # echo "0-14" > A1/A2/cpuset.cpus.exclusive # echo "root" > A1/A2/cpuset.cpus.partition # echo 0 > /sys/devices/system/cpu/cpu15/online # echo member > A1/A2/cpuset.cpus.partition When CPU 15 is offlined, subpartitions_cpus gets cleared because no CPUs remain available for the top_cpuset, forcing partitions to share CPUs with the top_cpuset. In this scenario, disabling the remote partition triggers a warning stating that effective_xcpus is not a subset of subpartitions_cpus. Partitions should be invalidated in this case to inform users that the partition is now invalid(cpus are shared with top_cpuset). To fix this issue: 1. Only emit the warning only if subpartitions_cpus is not empty and the effective_xcpus is not a subset of subpartitions_cpus. 2. During the CPU hotplug process, invalidate partitions if subpartitions_cpus is empty. CVE-2025-71142 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71142.html CVE-2025-71142 https://bugzilla.suse.com/1256748 SUSE Bug 1256748 In the Linux kernel, the following vulnerability has been resolved: clk: samsung: exynos-clkout: Assign .num before accessing .hws Commit f316cdff8d67 ("clk: Annotate struct clk_hw_onecell_data with __counted_by") annotated the hws member of 'struct clk_hw_onecell_data' with __counted_by, which informs the bounds sanitizer (UBSAN_BOUNDS) about the number of elements in .hws[], so that it can warn when .hws[] is accessed out of bounds. As noted in that change, the __counted_by member must be initialized with the number of elements before the first array access happens, otherwise there will be a warning from each access prior to the initialization because the number of elements is zero. This occurs in exynos_clkout_probe() due to .num being assigned after .hws[] has been accessed: UBSAN: array-index-out-of-bounds in drivers/clk/samsung/clk-exynos-clkout.c:178:18 index 0 is out of range for type 'clk_hw *[*]' Move the .num initialization to before the first access of .hws[], clearing up the warning. CVE-2025-71143 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71143.html CVE-2025-71143 https://bugzilla.suse.com/1256749 SUSE Bug 1256749 In the Linux kernel, the following vulnerability has been resolved: usb: phy: isp1301: fix non-OF device reference imbalance A recent change fixing a device reference leak in a UDC driver introduced a potential use-after-free in the non-OF case as the isp1301_get_client() helper only increases the reference count for the returned I2C device in the OF case. Increment the reference count also for non-OF so that the caller can decrement it unconditionally. Note that this is inherently racy just as using the returned I2C device is since nothing is preventing the PHY driver from being unbound while in use. CVE-2025-71145 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71145.html CVE-2025-71145 https://bugzilla.suse.com/1257155 SUSE Bug 1257155 https://bugzilla.suse.com/1257156 SUSE Bug 1257156 In the Linux kernel, the following vulnerability has been resolved: KEYS: trusted: Fix a memory leak in tpm2_load_cmd 'tpm2_load_cmd' allocates a tempoary blob indirectly via 'tpm2_key_decode' but it is not freed in the failure paths. Address this by wrapping the blob into with a cleanup helper. CVE-2025-71147 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71147.html CVE-2025-71147 https://bugzilla.suse.com/1257158 SUSE Bug 1257158 In the Linux kernel, the following vulnerability has been resolved: io_uring/poll: correctly handle io_poll_add() return value on update When the core of io_uring was updated to handle completions consistently and with fixed return codes, the POLL_REMOVE opcode with updates got slightly broken. If a POLL_ADD is pending and then POLL_REMOVE is used to update the events of that request, if that update causes the POLL_ADD to now trigger, then that completion is lost and a CQE is never posted. Additionally, ensure that if an update does cause an existing POLL_ADD to complete, that the completion value isn't always overwritten with -ECANCELED. For that case, whatever io_poll_add() set the value to should just be retained. CVE-2025-71149 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71149.html CVE-2025-71149 https://bugzilla.suse.com/1257164 SUSE Bug 1257164 In the Linux kernel, the following vulnerability has been resolved: net: usb: rtl8150: fix memory leak on usb_submit_urb() failure In async_set_registers(), when usb_submit_urb() fails, the allocated async_req structure and URB are not freed, causing a memory leak. The completion callback async_set_reg_cb() is responsible for freeing these allocations, but it is only called after the URB is successfully submitted and completes (successfully or with error). If submission fails, the callback never runs and the memory is leaked. Fix this by freeing both the URB and the request structure in the error path when usb_submit_urb() fails. CVE-2025-71154 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71154.html CVE-2025-71154 https://bugzilla.suse.com/1257163 SUSE Bug 1257163 In the Linux kernel, the following vulnerability has been resolved: gve: defer interrupt enabling until NAPI registration Currently, interrupts are automatically enabled immediately upon request. This allows interrupt to fire before the associated NAPI context is fully initialized and cause failures like below: [ 0.946369] Call Trace: [ 0.946369] <IRQ> [ 0.946369] __napi_poll+0x2a/0x1e0 [ 0.946369] net_rx_action+0x2f9/0x3f0 [ 0.946369] handle_softirqs+0xd6/0x2c0 [ 0.946369] ? handle_edge_irq+0xc1/0x1b0 [ 0.946369] __irq_exit_rcu+0xc3/0xe0 [ 0.946369] common_interrupt+0x81/0xa0 [ 0.946369] </IRQ> [ 0.946369] <TASK> [ 0.946369] asm_common_interrupt+0x22/0x40 [ 0.946369] RIP: 0010:pv_native_safe_halt+0xb/0x10 Use the `IRQF_NO_AUTOEN` flag when requesting interrupts to prevent auto enablement and explicitly enable the interrupt in NAPI initialization path (and disable it during NAPI teardown). This ensures that interrupt lifecycle is strictly coupled with readiness of NAPI context. CVE-2025-71156 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71156.html CVE-2025-71156 https://bugzilla.suse.com/1257167 SUSE Bug 1257167 In the Linux kernel, the following vulnerability has been resolved: RDMA/core: always drop device refcount in ib_del_sub_device_and_put() Since nldev_deldev() (introduced by commit 060c642b2ab8 ("RDMA/nldev: Add support to add/delete a sub IB device through netlink") grabs a reference using ib_device_get_by_index() before calling ib_del_sub_device_and_put(), we need to drop that reference before returning -EOPNOTSUPP error. CVE-2025-71157 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71157.html CVE-2025-71157 https://bugzilla.suse.com/1257168 SUSE Bug 1257168 In the Linux kernel, the following vulnerability has been resolved: dmaengine: tegra-adma: Fix use-after-free A use-after-free bug exists in the Tegra ADMA driver when audio streams are terminated, particularly during XRUN conditions. The issue occurs when the DMA buffer is freed by tegra_adma_terminate_all() before the vchan completion tasklet finishes accessing it. The race condition follows this sequence: 1. DMA transfer completes, triggering an interrupt that schedules the completion tasklet (tasklet has not executed yet) 2. Audio playback stops, calling tegra_adma_terminate_all() which frees the DMA buffer memory via kfree() 3. The scheduled tasklet finally executes, calling vchan_complete() which attempts to access the already-freed memory Since tasklets can execute at any time after being scheduled, there is no guarantee that the buffer will remain valid when vchan_complete() runs. Fix this by properly synchronizing the virtual channel completion: - Calling vchan_terminate_vdesc() in tegra_adma_stop() to mark the descriptors as terminated instead of freeing the descriptor. - Add the callback tegra_adma_synchronize() that calls vchan_synchronize() which kills any pending tasklets and frees any terminated descriptors. Crash logs: [ 337.427523] BUG: KASAN: use-after-free in vchan_complete+0x124/0x3b0 [ 337.427544] Read of size 8 at addr ffff000132055428 by task swapper/0/0 [ 337.427562] Call trace: [ 337.427564] dump_backtrace+0x0/0x320 [ 337.427571] show_stack+0x20/0x30 [ 337.427575] dump_stack_lvl+0x68/0x84 [ 337.427584] print_address_description.constprop.0+0x74/0x2b8 [ 337.427590] kasan_report+0x1f4/0x210 [ 337.427598] __asan_load8+0xa0/0xd0 [ 337.427603] vchan_complete+0x124/0x3b0 [ 337.427609] tasklet_action_common.constprop.0+0x190/0x1d0 [ 337.427617] tasklet_action+0x30/0x40 [ 337.427623] __do_softirq+0x1a0/0x5c4 [ 337.427628] irq_exit+0x110/0x140 [ 337.427633] handle_domain_irq+0xa4/0xe0 [ 337.427640] gic_handle_irq+0x64/0x160 [ 337.427644] call_on_irq_stack+0x20/0x4c [ 337.427649] do_interrupt_handler+0x7c/0x90 [ 337.427654] el1_interrupt+0x30/0x80 [ 337.427659] el1h_64_irq_handler+0x18/0x30 [ 337.427663] el1h_64_irq+0x7c/0x80 [ 337.427667] cpuidle_enter_state+0xe4/0x540 [ 337.427674] cpuidle_enter+0x54/0x80 [ 337.427679] do_idle+0x2e0/0x380 [ 337.427685] cpu_startup_entry+0x2c/0x70 [ 337.427690] rest_init+0x114/0x130 [ 337.427695] arch_call_rest_init+0x18/0x24 [ 337.427702] start_kernel+0x380/0x3b4 [ 337.427706] __primary_switched+0xc0/0xc8 CVE-2025-71162 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71162.html CVE-2025-71162 https://bugzilla.suse.com/1257204 SUSE Bug 1257204 In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: fix device leaks on compat bind and unbind Make sure to drop the reference taken when looking up the idxd device as part of the compat bind and unbind sysfs interface. CVE-2025-71163 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2025-71163.html CVE-2025-71163 https://bugzilla.suse.com/1257215 SUSE Bug 1257215 In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset `qfq_class->leaf_qdisc->q.qlen > 0` does not imply that the class itself is active. Two qfq_class objects may point to the same leaf_qdisc. This happens when: 1. one QFQ qdisc is attached to the dev as the root qdisc, and 2. another QFQ qdisc is temporarily referenced (e.g., via qdisc_get() / qdisc_put()) and is pending to be destroyed, as in function tc_new_tfilter. When packets are enqueued through the root QFQ qdisc, the shared leaf_qdisc->q.qlen increases. At the same time, the second QFQ qdisc triggers qdisc_put and qdisc_destroy: the qdisc enters qfq_reset() with its own q->q.qlen == 0, but its class's leaf qdisc->q.qlen > 0. Therefore, the qfq_reset would wrongly deactivate an inactive aggregate and trigger a null-deref in qfq_deactivate_agg: [ 0.903172] BUG: kernel NULL pointer dereference, address: 0000000000000000 [ 0.903571] #PF: supervisor write access in kernel mode [ 0.903860] #PF: error_code(0x0002) - not-present page [ 0.904177] PGD 10299b067 P4D 10299b067 PUD 10299c067 PMD 0 [ 0.904502] Oops: Oops: 0002 [#1] SMP NOPTI [ 0.904737] CPU: 0 UID: 0 PID: 135 Comm: exploit Not tainted 6.19.0-rc3+ #2 NONE [ 0.905157] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 [ 0.905754] RIP: 0010:qfq_deactivate_agg (include/linux/list.h:992 (discriminator 2) include/linux/list.h:1006 (discriminator 2) net/sched/sch_qfq.c:1367 (discriminator 2) net/sched/sch_qfq.c:1393 (discriminator 2)) [ 0.906046] Code: 0f 84 4d 01 00 00 48 89 70 18 8b 4b 10 48 c7 c2 ff ff ff ff 48 8b 78 08 48 d3 e2 48 21 f2 48 2b 13 48 8b 30 48 d3 ea 8b 4b 18 0 Code starting with the faulting instruction =========================================== 0: 0f 84 4d 01 00 00 je 0x153 6: 48 89 70 18 mov %rsi,0x18(%rax) a: 8b 4b 10 mov 0x10(%rbx),%ecx d: 48 c7 c2 ff ff ff ff mov $0xffffffffffffffff,%rdx 14: 48 8b 78 08 mov 0x8(%rax),%rdi 18: 48 d3 e2 shl %cl,%rdx 1b: 48 21 f2 and %rsi,%rdx 1e: 48 2b 13 sub (%rbx),%rdx 21: 48 8b 30 mov (%rax),%rsi 24: 48 d3 ea shr %cl,%rdx 27: 8b 4b 18 mov 0x18(%rbx),%ecx ... [ 0.907095] RSP: 0018:ffffc900004a39a0 EFLAGS: 00010246 [ 0.907368] RAX: ffff8881043a0880 RBX: ffff888102953340 RCX: 0000000000000000 [ 0.907723] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 0.908100] RBP: ffff888102952180 R08: 0000000000000000 R09: 0000000000000000 [ 0.908451] R10: ffff8881043a0000 R11: 0000000000000000 R12: ffff888102952000 [ 0.908804] R13: ffff888102952180 R14: ffff8881043a0ad8 R15: ffff8881043a0880 [ 0.909179] FS: 000000002a1a0380(0000) GS:ffff888196d8d000(0000) knlGS:0000000000000000 [ 0.909572] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 0.909857] CR2: 0000000000000000 CR3: 0000000102993002 CR4: 0000000000772ef0 [ 0.910247] PKRU: 55555554 [ 0.910391] Call Trace: [ 0.910527] <TASK> [ 0.910638] qfq_reset_qdisc (net/sched/sch_qfq.c:357 net/sched/sch_qfq.c:1485) [ 0.910826] qdisc_reset (include/linux/skbuff.h:2195 include/linux/skbuff.h:2501 include/linux/skbuff.h:3424 include/linux/skbuff.h:3430 net/sched/sch_generic.c:1036) [ 0.911040] __qdisc_destroy (net/sched/sch_generic.c:1076) [ 0.911236] tc_new_tfilter (net/sched/cls_api.c:2447) [ 0.911447] rtnetlink_rcv_msg (net/core/rtnetlink.c:6958) [ 0.911663] ? __pfx_rtnetlink_rcv_msg (net/core/rtnetlink.c:6861) [ 0.911894] netlink_rcv_skb (net/netlink/af_netlink.c:2550) [ 0.912100] netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344) [ 0.912296] ? __alloc_skb (net/core/skbuff.c:706) [ 0.912484] netlink_sendmsg (net/netlink/af ---truncated--- CVE-2026-22976 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22976.html CVE-2026-22976 https://bugzilla.suse.com/1257035 SUSE Bug 1257035 In the Linux kernel, the following vulnerability has been resolved: net: sock: fix hardened usercopy panic in sock_recv_errqueue skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is enabled and the kernel attempts to copy sk_buff.cb data to userspace via sock_recv_errqueue() -> put_cmsg(). The crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone() (from skbuff_fclone_cache) [1] 2. The skb is cloned via skb_clone() using the pre-allocated fclone [3] 3. The cloned skb is queued to sk_error_queue for timestamp reporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE) 5. sock_recv_errqueue() calls put_cmsg() to copy serr->ee from skb->cb [4] 6. __check_heap_object() fails because skbuff_fclone_cache has no usercopy whitelist [5] When cloned skbs allocated from skbuff_fclone_cache are used in the socket error queue, accessing the sock_exterr_skb structure in skb->cb via put_cmsg() triggers a usercopy hardening violation: [ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object 'skbuff_fclone_cache' (offset 296, size 16)! [ 5.382796] kernel BUG at mm/usercopy.c:102! [ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7 [ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80 [ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff <0f> 0b 490 [ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246 [ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74 [ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0 [ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74 [ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001 [ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00 [ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000 [ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0 [ 5.384903] PKRU: 55555554 [ 5.384903] Call Trace: [ 5.384903] <TASK> [ 5.384903] __check_heap_object+0x9a/0xd0 [ 5.384903] __check_object_size+0x46c/0x690 [ 5.384903] put_cmsg+0x129/0x5e0 [ 5.384903] sock_recv_errqueue+0x22f/0x380 [ 5.384903] tls_sw_recvmsg+0x7ed/0x1960 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? schedule+0x6d/0x270 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? mutex_unlock+0x81/0xd0 [ 5.384903] ? __pfx_mutex_unlock+0x10/0x10 [ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10 [ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0 [ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 The crash offset 296 corresponds to skb2->cb within skbuff_fclones: - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 - offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 = 272 + 24 (inside sock_exterr_skb.ee) This patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure. [1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885 [2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104 [3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566 [4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491 [5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719 CVE-2026-22977 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22977.html CVE-2026-22977 https://bugzilla.suse.com/1257053 SUSE Bug 1257053 In the Linux kernel, the following vulnerability has been resolved: wifi: avoid kernel-infoleak from struct iw_point struct iw_point has a 32bit hole on 64bit arches. struct iw_point { void __user *pointer; /* Pointer to the data (in user space) */ __u16 length; /* number of fields or size in bytes */ __u16 flags; /* Optional params */ }; Make sure to zero the structure to avoid disclosing 32bits of kernel data to user space. CVE-2026-22978 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22978.html CVE-2026-22978 https://bugzilla.suse.com/1257227 SUSE Bug 1257227 In the Linux kernel, the following vulnerability has been resolved: libceph: prevent potential out-of-bounds reads in handle_auth_done() Perform an explicit bounds check on payload_len to avoid a possible out-of-bounds access in the callout. [ idryomov: changelog ] CVE-2026-22984 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22984.html CVE-2026-22984 https://bugzilla.suse.com/1257217 SUSE Bug 1257217 In the Linux kernel, the following vulnerability has been resolved: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations The RSS LUT is not initialized until the interface comes up, causing the following NULL pointer crash when ethtool operations like rxhash on/off are performed before the interface is brought up for the first time. Move RSS LUT initialization from ndo_open to vport creation to ensure LUT is always available. This enables RSS configuration via ethtool before bringing the interface up. Simplify LUT management by maintaining all changes in the driver's soft copy and programming zeros to the indirection table when rxhash is disabled. Defer HW programming until the interface comes up if it is down during rxhash and LUT configuration changes. Steps to reproduce: ** Load idpf driver; interfaces will be created modprobe idpf ** Before bringing the interfaces up, turn rxhash off ethtool -K eth2 rxhash off [89408.371875] BUG: kernel NULL pointer dereference, address: 0000000000000000 [89408.371908] #PF: supervisor read access in kernel mode [89408.371924] #PF: error_code(0x0000) - not-present page [89408.371940] PGD 0 P4D 0 [89408.371953] Oops: Oops: 0000 [#1] SMP NOPTI <snip> [89408.372052] RIP: 0010:memcpy_orig+0x16/0x130 [89408.372310] Call Trace: [89408.372317] <TASK> [89408.372326] ? idpf_set_features+0xfc/0x180 [idpf] [89408.372363] __netdev_update_features+0x295/0xde0 [89408.372384] ethnl_set_features+0x15e/0x460 [89408.372406] genl_family_rcv_msg_doit+0x11f/0x180 [89408.372429] genl_rcv_msg+0x1ad/0x2b0 [89408.372446] ? __pfx_ethnl_set_features+0x10/0x10 [89408.372465] ? __pfx_genl_rcv_msg+0x10/0x10 [89408.372482] netlink_rcv_skb+0x58/0x100 [89408.372502] genl_rcv+0x2c/0x50 [89408.372516] netlink_unicast+0x289/0x3e0 [89408.372533] netlink_sendmsg+0x215/0x440 [89408.372551] __sys_sendto+0x234/0x240 [89408.372571] __x64_sys_sendto+0x28/0x30 [89408.372585] x64_sys_call+0x1909/0x1da0 [89408.372604] do_syscall_64+0x7a/0xfa0 [89408.373140] ? clear_bhb_loop+0x60/0xb0 [89408.373647] entry_SYSCALL_64_after_hwframe+0x76/0x7e [89408.378887] </TASK> <snip> CVE-2026-22985 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22985.html CVE-2026-22985 https://bugzilla.suse.com/1257277 SUSE Bug 1257277 In the Linux kernel, the following vulnerability has been resolved: arp: do not assume dev_hard_header() does not change skb->head arp_create() is the only dev_hard_header() caller making assumption about skb->head being unchanged. A recent commit broke this assumption. Initialize @arp pointer after dev_hard_header() call. CVE-2026-22988 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22988.html CVE-2026-22988 https://bugzilla.suse.com/1257282 SUSE Bug 1257282 In the Linux kernel, the following vulnerability has been resolved: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() If the osdmap is (maliciously) corrupted such that the incremental osdmap epoch is different from what is expected, there is no need to BUG. Instead, just declare the incremental osdmap to be invalid. CVE-2026-22990 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22990.html CVE-2026-22990 https://bugzilla.suse.com/1257221 SUSE Bug 1257221 In the Linux kernel, the following vulnerability has been resolved: libceph: make free_choose_arg_map() resilient to partial allocation free_choose_arg_map() may dereference a NULL pointer if its caller fails after a partial allocation. For example, in decode_choose_args(), if allocation of arg_map->args fails, execution jumps to the fail label and free_choose_arg_map() is called. Since arg_map->size is updated to a non-zero value before memory allocation, free_choose_arg_map() will iterate over arg_map->args and dereference a NULL pointer. To prevent this potential NULL pointer dereference and make free_choose_arg_map() more resilient, add checks for pointers before iterating. CVE-2026-22991 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22991.html CVE-2026-22991 https://bugzilla.suse.com/1257220 SUSE Bug 1257220 In the Linux kernel, the following vulnerability has been resolved: libceph: return the handler error from mon_handle_auth_done() Currently any error from ceph_auth_handle_reply_done() is propagated via finish_auth() but isn't returned from mon_handle_auth_done(). This results in higher layers learning that (despite the monitor considering us to be successfully authenticated) something went wrong in the authentication phase and reacting accordingly, but msgr2 still trying to proceed with establishing the session in the background. In the case of secure mode this can trigger a WARN in setup_crypto() and later lead to a NULL pointer dereference inside of prepare_auth_signature(). CVE-2026-22992 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22992.html CVE-2026-22992 https://bugzilla.suse.com/1257218 SUSE Bug 1257218 In the Linux kernel, the following vulnerability has been resolved: idpf: Fix RSS LUT NULL ptr issue after soft reset During soft reset, the RSS LUT is freed and not restored unless the interface is up. If an ethtool command that accesses the rss lut is attempted immediately after reset, it will result in NULL ptr dereference. Also, there is no need to reset the rss lut if the soft reset does not involve queue count change. After soft reset, set the RSS LUT to default values based on the updated queue count only if the reset was a result of a queue count change and the LUT was not configured by the user. In all other cases, don't touch the LUT. Steps to reproduce: ** Bring the interface down (if up) ifconfig eth1 down ** update the queue count (eg., 27->20) ethtool -L eth1 combined 20 ** display the RSS LUT ethtool -x eth1 [82375.558338] BUG: kernel NULL pointer dereference, address: 0000000000000000 [82375.558373] #PF: supervisor read access in kernel mode [82375.558391] #PF: error_code(0x0000) - not-present page [82375.558408] PGD 0 P4D 0 [82375.558421] Oops: Oops: 0000 [#1] SMP NOPTI <snip> [82375.558516] RIP: 0010:idpf_get_rxfh+0x108/0x150 [idpf] [82375.558786] Call Trace: [82375.558793] <TASK> [82375.558804] rss_prepare.isra.0+0x187/0x2a0 [82375.558827] rss_prepare_data+0x3a/0x50 [82375.558845] ethnl_default_doit+0x13d/0x3e0 [82375.558863] genl_family_rcv_msg_doit+0x11f/0x180 [82375.558886] genl_rcv_msg+0x1ad/0x2b0 [82375.558902] ? __pfx_ethnl_default_doit+0x10/0x10 [82375.558920] ? __pfx_genl_rcv_msg+0x10/0x10 [82375.558937] netlink_rcv_skb+0x58/0x100 [82375.558957] genl_rcv+0x2c/0x50 [82375.558971] netlink_unicast+0x289/0x3e0 [82375.558988] netlink_sendmsg+0x215/0x440 [82375.559005] __sys_sendto+0x234/0x240 [82375.559555] __x64_sys_sendto+0x28/0x30 [82375.560068] x64_sys_call+0x1909/0x1da0 [82375.560576] do_syscall_64+0x7a/0xfa0 [82375.561076] ? clear_bhb_loop+0x60/0xb0 [82375.561567] entry_SYSCALL_64_after_hwframe+0x76/0x7e <snip> CVE-2026-22993 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22993.html CVE-2026-22993 https://bugzilla.suse.com/1257180 SUSE Bug 1257180 In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv mlx5e_priv is an unstable structure that can be memset(0) if profile attaching fails, mlx5e_priv in mlx5e_dev devlink private is used to reference the netdev and mdev associated with that struct. Instead, store netdev directly into mlx5e_dev and get mdev from the containing mlx5_adev aux device structure. This fixes a kernel oops in mlx5e_remove when switchdev mode fails due to change profile failure. $ devlink dev eswitch set pci/0000:00:03.0 mode switchdev Error: mlx5_core: Failed setting eswitch to offloads. dmesg: workqueue: Failed to create a rescuer kthread for wq "mlx5e": -EINTR mlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12 mlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12 workqueue: Failed to create a rescuer kthread for wq "mlx5e": -EINTR mlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12 mlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12 $ devlink dev reload pci/0000:00:03.0 ==> oops BUG: kernel NULL pointer dereference, address: 0000000000000520 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 RIP: 0010:mlx5e_remove+0x68/0x130 RSP: 0018:ffffc900034838f0 EFLAGS: 00010246 RAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000 RBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10 R10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0 R13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400 FS: 00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0 Call Trace: <TASK> device_release_driver_internal+0x19c/0x200 bus_remove_device+0xc6/0x130 device_del+0x160/0x3d0 ? devl_param_driverinit_value_get+0x2d/0x90 mlx5_detach_device+0x89/0xe0 mlx5_unload_one_devl_locked+0x3a/0x70 mlx5_devlink_reload_down+0xc8/0x220 devlink_reload+0x7d/0x260 devlink_nl_reload_doit+0x45b/0x5a0 genl_family_rcv_msg_doit+0xe8/0x140 CVE-2026-22996 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22996.html CVE-2026-22996 https://bugzilla.suse.com/1257203 SUSE Bug 1257203 In the Linux kernel, the following vulnerability has been resolved: net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts Since j1939_session_deactivate_activate_next() in j1939_tp_rxtimer() is called only when the timer is enabled, we need to call j1939_session_deactivate_activate_next() if we cancelled the timer. Otherwise, refcount for j1939_session leaks, which will later appear as | unregister_netdevice: waiting for vcan0 to become free. Usage count = 2. problem. CVE-2026-22997 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22997.html CVE-2026-22997 https://bugzilla.suse.com/1257202 SUSE Bug 1257202 In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_qfq: do not free existing class in qfq_change_class() Fixes qfq_change_class() error case. cl->qdisc and cl should only be freed if a new class and qdisc were allocated, or we risk various UAF. CVE-2026-22999 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-22999.html CVE-2026-22999 https://bugzilla.suse.com/1257236 SUSE Bug 1257236 https://bugzilla.suse.com/1257238 SUSE Bug 1257238 In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix crash on profile change rollback failure mlx5e_netdev_change_profile can fail to attach a new profile and can fail to rollback to old profile, in such case, we could end up with a dangling netdev with a fully reset netdev_priv. A retry to change profile, e.g. another attempt to call mlx5e_netdev_change_profile via switchdev mode change, will crash trying to access the now NULL priv->mdev. This fix allows mlx5e_netdev_change_profile() to handle previous failures and an empty priv, by not assuming priv is valid. Pass netdev and mdev to all flows requiring mlx5e_netdev_change_profile() and avoid passing priv. In mlx5e_netdev_change_profile() check if current priv is valid, and if not, just attach the new profile without trying to access the old one. This fixes the following oops, when enabling switchdev mode for the 2nd time after first time failure: ## Enabling switchdev mode first time: mlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload workqueue: Failed to create a rescuer kthread for wq "mlx5e": -EINTR mlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12 mlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12 workqueue: Failed to create a rescuer kthread for wq "mlx5e": -EINTR mlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12 mlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12 ^^^^^^^^ mlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0) ## retry: Enabling switchdev mode 2nd time: mlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload BUG: kernel NULL pointer dereference, address: 0000000000000038 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 RIP: 0010:mlx5e_detach_netdev+0x3c/0x90 Code: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 <48> 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07 RSP: 0018:ffffc90000673890 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000 RDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000 RBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000 R10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000 R13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000 FS: 00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0 Call Trace: <TASK> mlx5e_netdev_change_profile+0x45/0xb0 mlx5e_vport_rep_load+0x27b/0x2d0 mlx5_esw_offloads_rep_load+0x72/0xf0 esw_offloads_enable+0x5d0/0x970 mlx5_eswitch_enable_locked+0x349/0x430 ? is_mp_supported+0x57/0xb0 mlx5_devlink_eswitch_mode_set+0x26b/0x430 devlink_nl_eswitch_set_doit+0x6f/0xf0 genl_family_rcv_msg_doit+0xe8/0x140 genl_rcv_msg+0x18b/0x290 ? __pfx_devlink_nl_pre_doit+0x10/0x10 ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10 ? __pfx_devlink_nl_post_doit+0x10/0x10 ? __pfx_genl_rcv_msg+0x10/0x10 netlink_rcv_skb+0x52/0x100 genl_rcv+0x28/0x40 netlink_unicast+0x282/0x3e0 ? __alloc_skb+0xd6/0x190 netlink_sendmsg+0x1f7/0x430 __sys_sendto+0x213/0x220 ? __sys_recvmsg+0x6a/0xd0 __x64_sys_sendto+0x24/0x30 do_syscall_64+0x50/0x1f0 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7fdfb8495047 CVE-2026-23000 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-23000.html CVE-2026-23000 https://bugzilla.suse.com/1257234 SUSE Bug 1257234 In the Linux kernel, the following vulnerability has been resolved: macvlan: fix possible UAF in macvlan_forward_source() Add RCU protection on (struct macvlan_source_entry)->vlan. Whenever macvlan_hash_del_source() is called, we must clear entry->vlan pointer before RCU grace period starts. This allows macvlan_forward_source() to skip over entries queued for freeing. Note that macvlan_dev are already RCU protected, as they are embedded in a standard netdev (netdev_priv(ndev)). https: //lore.kernel.org/netdev/695fb1e8.050a0220.1c677c.039f.GAE@google.com/T/#u CVE-2026-23001 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-23001.html CVE-2026-23001 https://bugzilla.suse.com/1257232 SUSE Bug 1257232 https://bugzilla.suse.com/1257233 SUSE Bug 1257233 In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1 When loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in response to a guest WRMSR, clear XFD-disabled features in the saved (or to be restored) XSTATE_BV to ensure KVM doesn't attempt to load state for features that are disabled via the guest's XFD. Because the kernel executes XRSTOR with the guest's XFD, saving XSTATE_BV[i]=1 with XFD[i]=1 will cause XRSTOR to #NM and panic the kernel. E.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV: ------------[ cut here ]------------ WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848 Modules linked in: kvm_intel kvm irqbypass CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:exc_device_not_available+0x101/0x110 Call Trace: <TASK> asm_exc_device_not_available+0x1a/0x20 RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90 switch_fpu_return+0x4a/0xb0 kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm] kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm] __x64_sys_ioctl+0x8f/0xd0 do_syscall_64+0x62/0x940 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> ---[ end trace 0000000000000000 ]--- This can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1, and a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler's call to fpu_update_guest_xfd(). and if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE: ------------[ cut here ]------------ WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867 Modules linked in: kvm_intel kvm irqbypass CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:exc_device_not_available+0x101/0x110 Call Trace: <TASK> asm_exc_device_not_available+0x1a/0x20 RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90 fpu_swap_kvm_fpstate+0x6b/0x120 kvm_load_guest_fpu+0x30/0x80 [kvm] kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm] kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm] __x64_sys_ioctl+0x8f/0xd0 do_syscall_64+0x62/0x940 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> ---[ end trace 0000000000000000 ]--- The new behavior is consistent with the AMX architecture. Per Intel's SDM, XSAVE saves XSTATE_BV as '0' for components that are disabled via XFD (and non-compacted XSAVE saves the initial configuration of the state component): If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i, the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1; instead, it operates as if XINUSE[i] = 0 (and the state component was in its initial state): it saves bit i of XSTATE_BV field of the XSAVE header as 0; in addition, XSAVE saves the initial configuration of the state component (the other instructions do not save state component i). Alternatively, KVM could always do XRSTOR with XFD=0, e.g. by using a constant XFD based on the set of enabled features when XSAVEing for a struct fpu_guest. However, having XSTATE_BV[i]=1 for XFD-disabled features can only happen in the above interrupt case, or in similar scenarios involving preemption on preemptible kernels, because fpu_swap_kvm_fpstate()'s call to save_fpregs_to_fpstate() saves the outgoing FPU state with the current XFD; and that is (on all but the first WRMSR to XFD) the guest XFD. Therefore, XFD can only go out of sync with XSTATE_BV in the above interrupt case, or in similar scenarios involving preemption on preemptible kernels, and it we can consider it (de facto) part of KVM ABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features. [Move clea ---truncated--- CVE-2026-23005 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-23005.html CVE-2026-23005 https://bugzilla.suse.com/1257245 SUSE Bug 1257245 In the Linux kernel, the following vulnerability has been resolved: ASoC: tlv320adcx140: fix null pointer The "snd_soc_component" in "adcx140_priv" was only used once but never set. It was only used for reaching "dev" which is already present in "adcx140_priv". CVE-2026-23006 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-23006.html CVE-2026-23006 https://bugzilla.suse.com/1257208 SUSE Bug 1257208 In the Linux kernel, the following vulnerability has been resolved: ipv4: ip_gre: make ipgre_header() robust Analog to commit db5b4e39c4e6 ("ip6_gre: make ip6gre_header() robust") Over the years, syzbot found many ways to crash the kernel in ipgre_header() [1]. This involves team or bonding drivers ability to dynamically change their dev->needed_headroom and/or dev->hard_header_len In this particular crash mld_newpack() allocated an skb with a too small reserve/headroom, and by the time mld_sendpack() was called, syzbot managed to attach an ipgre device. [1] skbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0 kernel BUG at net/core/skbuff.c:213 ! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Workqueue: mld mld_ifc_work RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213 Call Trace: <TASK> skb_under_panic net/core/skbuff.c:223 [inline] skb_push+0xc3/0xe0 net/core/skbuff.c:2641 ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897 dev_hard_header include/linux/netdevice.h:3436 [inline] neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618 NF_HOOK_COND include/linux/netfilter.h:307 [inline] ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247 NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318 mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855 mld_send_cr net/ipv6/mcast.c:2154 [inline] mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693 process_one_work kernel/workqueue.c:3257 [inline] process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421 kthread+0x711/0x8a0 kernel/kthread.c:463 ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 CVE-2026-23011 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_31-rt-1-150700.1.3.2 SUSE Real Time Module 15 SP7:cluster-md-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:dlm-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:gfs2-kmp-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-devel-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-rt-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-rt-devel-6.4.0-150700.7.31.2 SUSE Real Time Module 15 SP7:kernel-source-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:kernel-syms-rt-6.4.0-150700.7.31.1 SUSE Real Time Module 15 SP7:ocfs2-kmp-rt-6.4.0-150700.7.31.2 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/ https://www.suse.com/security/cve/CVE-2026-23011.html CVE-2026-23011 https://bugzilla.suse.com/1257207 SUSE Bug 1257207