Security update for the Linux Kernel SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2025:20653-1 Final 1 1 2025-09-05T12:02:35Z current 2025-09-05T12:02:35Z 2025-09-05T12:02:35Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for the Linux Kernel The SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes. The following security bugs were fixed: - CVE-2024-46733: btrfs: fix qgroup reserve leaks in cow_file_range (bsc#1230708). - CVE-2025-38006: net: mctp: Do not access ifa_index when missing (bsc#1244930). - CVE-2025-38075: scsi: target: iscsi: Fix timeout on deleted connection (bsc#1244734). - CVE-2025-38103: HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() (bsc#1245663). - CVE-2025-38125: net: stmmac: make sure that ptp_rate is not 0 before configuring EST (bsc#1245710). - CVE-2025-38146: net: openvswitch: Fix the dead loop of MPLS parse (bsc#1245767). - CVE-2025-38160: clk: bcm: rpi: Add NULL check in raspberrypi_clk_register() (bsc#1245780). - CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956). - CVE-2025-38185: atm: atmtcp: Free invalid length skb in atmtcp_c_send() (bsc#1246012). - CVE-2025-38190: atm: Revert atm_account_tx() if copy_from_iter_full() fails (bsc#1245973). - CVE-2025-38201: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX (bsc#1245977). - CVE-2025-38205: drm/amd/display: Avoid divide by zero by initializing dummy pitch to 1 (bsc#1246005). - CVE-2025-38208: smb: client: add NULL check in automount_fullpath (bsc#1245815). - CVE-2025-38245: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister() (bsc#1246193). - CVE-2025-38251: atm: clip: prevent NULL deref in clip_push() (bsc#1246181). - CVE-2025-38360: drm/amd/display: Add more checks for DSC / HUBP ONO guarantees (bsc#1247078). - CVE-2025-38439: bnxt_en: Set DMA unmap len correctly for XDP_REDIRECT (bsc#1247155). - CVE-2025-38441: netfilter: flowtable: account for Ethernet header in nf_flow_pppoe_proto() (bsc#1247167). - CVE-2025-38444: raid10: cleanup memleak at raid10_make_request (bsc#1247162). - CVE-2025-38445: md/raid1: Fix stack memory use after return in raid1_reshape (bsc#1247229). - CVE-2025-38458: atm: clip: Fix NULL pointer dereference in vcc_sendmsg() (bsc#1247116). - CVE-2025-38459: atm: clip: Fix infinite recursive call of clip_push() (bsc#1247119). - CVE-2025-38464: tipc: Fix use-after-free in tipc_conn_close() (bsc#1247112). - CVE-2025-38472: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry (bsc#1247313). - CVE-2025-38490: net: libwx: remove duplicate page_pool_put_full_page() (bsc#1247243). - CVE-2025-38491: mptcp: make fallback action and fallback decision atomic (bsc#1247280). - CVE-2025-38499: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns (bsc#1247976). - CVE-2025-38500: xfrm: interface: fix use-after-free after changing collect_md xfrm interface (bsc#1248088). - CVE-2025-38506: KVM: Allow CPU to reschedule while setting per-page memory attributes (bsc#1248186). - CVE-2025-38520: drm/amdkfd: Do not call mmput from MMU notifier callback (bsc#1248217). - CVE-2025-38524: rxrpc: Fix recv-recv race of completed call (bsc#1248194). - CVE-2025-38528: bpf: Reject %p% format string in bprintf-like helpers (bsc#1248198). - CVE-2025-38531: iio: common: st_sensors: Fix use of uninitialize device structs (bsc#1248205). - CVE-2025-38546: atm: clip: Fix memory leak of struct clip_vcc (bsc#1248223). - CVE-2025-38560: x86/sev: Evict cache lines during SNP memory validation (bsc#1248312). - CVE-2025-38585: staging: media: atomisp: Fix stack buffer overflow in gmin_get_var_int() (bsc#1248355). - CVE-2025-38591: bpf: Reject narrower access to pointer ctx fields (bsc#1248363). - CVE-2025-38608: bpf, ktls: Fix data corruption when using bpf_msg_pop_data() in ktls (bsc#1248338). - CVE-2025-38618: vsock: Do not allow binding to VMADDR_PORT_ANY (bsc#1248511). The following non-security bugs were fixed: - ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered (stable-fixes). - ACPI: pfr_update: Fix the driver update version check (git-fixes). - ACPI: processor: fix acpi_object initialization (stable-fixes). - ACPI: processor: perflib: Move problematic pr->performance check (git-fixes). - ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (stable-fixes). - ALSA: hda/realtek: Add Framework Laptop 13 (AMD Ryzen AI 300) to quirks (stable-fixes). - ALSA: hda/realtek: Add support for HP EliteBook x360 830 G6 and EliteBook 830 G6 (stable-fixes). - ALSA: hda/realtek: Audio disappears on HP 15-fc000 after warm boot again (git-fixes). - ALSA: hda/realtek: Fix headset mic on ASUS Zenbook 14 (git-fixes). - ALSA: hda/realtek: Fix headset mic on HONOR BRB-X (stable-fixes). - ALSA: hda: Disable jack polling at shutdown (stable-fixes). - ALSA: hda: Handle the jack polling always via a work (stable-fixes). - ALSA: intel8x0: Fix incorrect codec index usage in mixer for ICH4 (stable-fixes). - ALSA: pcm: Rewrite recalculate_boundary() to avoid costly loop (stable-fixes). - ALSA: scarlett2: Add retry on -EPROTO from scarlett2_usb_tx() (git-fixes). - ALSA: usb-audio: Avoid precedence issues in mixer_quirks macros (stable-fixes). - ALSA: usb-audio: Fix size validation in convert_chmap_v3() (git-fixes). - ALSA: usb-audio: Use correct sub-type for UAC3 feature unit validation (git-fixes). - ALSA: usb-audio: Validate UAC3 cluster segment descriptors (git-fixes). - ALSA: usb-audio: Validate UAC3 power domain descriptors, too (git-fixes). - ASoC: Intel: avs: Fix uninitialized pointer error in probe() (stable-fixes). - ASoC: Intel: fix SND_SOC_SOF dependencies (stable-fixes). - ASoC: amd: yc: Add DMI entries to support HP 15-fb1xxx (stable-fixes). - ASoC: amd: yc: Add DMI quirk for HP Laptop 17 cp-2033dx (stable-fixes). - ASoC: amd: yc: add DMI quirk for ASUS M6501RM (stable-fixes). - ASoC: codecs: rt5640: Retry DEVICE_ID verification (stable-fixes). - ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() (stable-fixes). - ASoC: hdac_hdmi: Rate limit logging on connection and disconnection (stable-fixes). - ASoC: soc-dapm: set bias_level if snd_soc_dapm_set_bias_level() was successed (stable-fixes). - Bluetooth: btusb: Add USB ID 3625:010b for TP-LINK Archer TX10UB Nano (stable-fixes). - Bluetooth: hci_conn: do return error from hci_enhanced_setup_sync() (git-fixes). - Bluetooth: hci_event: Detect if HCI_EV_NUM_COMP_PKTS is unbalanced (git-fixes). - Bluetooth: hci_event: Mark connection as closed during suspend disconnect (git-fixes). - Bluetooth: hci_event: Treat UNKNOWN_CONN_ID on disconnect as success (git-fixes). - Bluetooth: hci_event: fix MTU for BN == 0 in CIS Established (git-fixes). - Bluetooth: hci_sock: Reset cookie to zero in hci_sock_free_cookie() (stable-fixes). - Bluetooth: hci_sync: fix set_local_name race condition (git-fixes). - HID: asus: fix UAF via HID_CLAIMED_INPUT validation (git-fixes). - HID: multitouch: fix slab out-of-bounds access in mt_report_fixup() (git-fixes). - Move pesign-obs-integration requirement from kernel-syms to kernel devel subpackage (bsc#1248108). - PCI/ACPI: Fix runtime PM ref imbalance on Hot-Plug Capable ports (git-fixes). - PCI/portdrv: Use is_pciehp instead of is_hotplug_bridge (git-fixes). - PCI: Add ACS quirk for Loongson PCIe (git-fixes). - PCI: Support Immediate Readiness on devices without PM capabilities (git-fixes). - PCI: apple: Fix missing OF node reference in apple_pcie_setup_port (git-fixes). - PCI: imx6: Add IMX8MM_EP and IMX8MP_EP fixed 256-byte BAR 4 in epc_features (git-fixes). - PCI: imx6: Delay link start until configfs 'start' written (git-fixes). - PCI: imx6: Remove apps_reset toggling from imx_pcie_{assert/deassert}_core_reset (git-fixes). - PCI: pnv_php: Clean up allocated IRQs on unplug (bsc#1215199). - PCI: pnv_php: Work around switches with broken presence detection (bsc#1215199). - PCI: rockchip: Set Target Link Speed to 5.0 GT/s before retraining (git-fixes). - PCI: rockchip: Use standard PCIe definitions (git-fixes). - PM / devfreq: governor: Replace sscanf() with kstrtoul() in set_freq_store() (stable-fixes). - PM: runtime: Clear power.needs_force_resume in pm_runtime_reinit() (stable-fixes). - PM: sleep: console: Fix the black screen issue (stable-fixes). - RAS/AMD/ATL: Include row bit in row retirement (bsc#1242034). - RAS/AMD/FMPM: Get masked address (bsc#1242034). - RAS/AMD/FMPM: Use atl internal.h for INVALID_SPA (bsc#1242034). - RDMA/bnxt_re: Fix a possible memory leak in the driver (git-fixes) - RDMA/bnxt_re: Fix to do SRQ armena by default (git-fixes) - RDMA/bnxt_re: Fix to initialize the PBL array (git-fixes) - RDMA/bnxt_re: Fix to remove workload check in SRQ limit path (git-fixes) - RDMA/core: reduce stack using in nldev_stat_get_doit() (git-fixes) - RDMA/erdma: Fix ignored return value of init_kernel_qp (git-fixes) - RDMA/hns: Fix dip entries leak on devices newer than hip09 (git-fixes) - RDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask() (git-fixes) - Revert "gpio: mlxbf3: only get IRQ for device instance 0" (git-fixes). - USB: serial: option: add Foxconn T99W709 (stable-fixes). - USB: storage: Add unusual-devs entry for Novatek NTK96550-based camera (stable-fixes). - USB: storage: Ignore driver CD mode for Realtek multi-mode Wi-Fi dongles (stable-fixes). - aoe: defer rexmit timer downdev work to workqueue (git-fixes). - arch/powerpc: Remove .interp section in vmlinux (bsc#1215199). - arm64/cpufeatures/kvm: Add ARMv8.9 FEAT_ECBHB bits in ID_AA64MMFR1 (git-fixes) - arm64/entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack() (git-fixes) - arm64/mm: Check PUD_TYPE_TABLE in pud_bad() (git-fixes) - arm64: Add support for HIP09 Spectre-BHB mitigation (git-fixes) - arm64: Filter out SME hwcaps when FEAT_SME isn't implemented (git-fixes) - arm64: Restrict pagetable teardown to avoid false warning (git-fixes) - arm64: dts: apple: t8103: Fix PCIe BCM4377 nodename (git-fixes) - arm64: dts: freescale: imx8mm-verdin: Keep LDO5 always on (git-fixes) - arm64: dts: imx8mm-beacon: Fix HS400 USDHC clock speed (git-fixes) - arm64: dts: imx8mm-beacon: Fix RTC capacitive load (git-fixes) - arm64: dts: imx8mm-venice-gw700x: Increase HS400 USDHC clock speed (git-fixes) - arm64: dts: imx8mm-venice-gw7901: Increase HS400 USDHC clock speed (git-fixes) - arm64: dts: imx8mm-venice-gw7902: Increase HS400 USDHC clock speed (git-fixes) - arm64: dts: imx8mm-venice-gw7903: Increase HS400 USDHC clock speed (git-fixes) - arm64: dts: imx8mm-venice-gw7904: Increase HS400 USDHC clock speed (git-fixes) - arm64: dts: imx8mn-beacon: Fix HS400 USDHC clock speed (git-fixes) - arm64: dts: imx8mn-beacon: Fix RTC capacitive load (git-fixes) - arm64: dts: imx8mn-venice-gw7902: Increase HS400 USDHC clock speed (git-fixes) - arm64: dts: imx8mp-beacon: Fix RTC capacitive load (git-fixes) - arm64: dts: rockchip: Update eMMC for NanoPi R5 series (git-fixes) - arm64: dts: rockchip: fix endpoint dtc warning for PX30 ISP (git-fixes) - arm64: tegra: Drop remaining serial clock-names and reset-names (git-fixes) - arm64: tegra: p2597: Fix gpio for vdd-1v8-dis regulator (git-fixes) - arm64: zynqmp: add clock-output-names property in clock nodes (git-fixes) - ata: libata-scsi: Fix CDL control (git-fixes). - block: fix kobject leak in blk_unregister_queue (git-fixes). - block: mtip32xx: Fix usage of dma_map_sg() (git-fixes). - bpf: fix kfunc btf caching for modules (git-fixes). - bpf: use kvzmalloc to allocate BPF verifier environment (git-fixes). - btrfs: convert BUG_ON in btrfs_reloc_cow_block() to proper error handling (git-fixes). - btrfs: correctly escape subvol in btrfs_show_options() (git-fixes). - btrfs: fix adding block group to a reclaim list and the unused list during reclaim (git-fixes). - btrfs: fix bitmap leak when loading free space cache on duplicate entry (git-fixes). - btrfs: fix data race when accessing the inode's disk_i_size at btrfs_drop_extents() (git-fixes). - btrfs: fix the length of reserved qgroup to free (bsc#1240708) - btrfs: retry block group reclaim without infinite loop (git-fixes). - btrfs: return accurate error code on open failure in open_fs_devices() (bsc#1233120) - btrfs: run delayed iputs when flushing delalloc (git-fixes). - btrfs: update target inode's ctime on unlink (git-fixes). - cdx: Fix off-by-one error in cdx_rpmsg_probe() (git-fixes). - char: misc: Fix improper and inaccurate error code returned by misc_init() (stable-fixes). - comedi: Fix use of uninitialized memory in do_insn_ioctl() and do_insnlist_ioctl() (git-fixes). - comedi: Make insn_rw_emulate_bits() do insn->n samples (git-fixes). - comedi: fix race between polling and detaching (git-fixes). - comedi: pcl726: Prevent invalid irq number (git-fixes). - crypto: hisilicon/hpre - fix dma unmap sequence (stable-fixes). - crypto: jitter - fix intermediary handling (stable-fixes). - crypto: octeontx2 - add timeout for load_fvc completion poll (stable-fixes). - crypto: qat - lower priority for skcipher and aead algorithms (stable-fixes). - drm/amd/display: Add null pointer check in mod_hdcp_hdcp1_create_session() (git-fixes). - drm/amd/display: Add primary plane to commits for correct VRR handling (stable-fixes). - drm/amd/display: Adjust DCE 8-10 clock, do not overclock by 15% (git-fixes). - drm/amd/display: Avoid a NULL pointer dereference (stable-fixes). - drm/amd/display: Avoid configuring PSR granularity if PSR-SU not supported (stable-fixes). - drm/amd/display: Avoid trying AUX transactions on disconnected ports (stable-fixes). - drm/amd/display: Do not overclock DCE 6 by 15% (git-fixes). - drm/amd/display: Fill display clock and vblank time in dce110_fill_display_configs (stable-fixes). - drm/amd/display: Find first CRTC and its line time in dce110_fill_display_configs (stable-fixes). - drm/amd/display: Fix 'failed to blank crtc!' (stable-fixes). - drm/amd/display: Fix DP audio DTO1 clock source on DCE 6 (stable-fixes). - drm/amd/display: Fix fractional fb divider in set_pixel_clock_v3 (git-fixes). - drm/amd/display: Only finalize atomic_obj if it was initialized (stable-fixes). - drm/amd/display: Separate set_gsl from set_gsl_source_select (stable-fixes). - drm/amd: Allow printing VanGogh OD SCLK levels without setting dpm to manual (stable-fixes). - drm/amd: Restore cached power limit during resume (stable-fixes). - drm/amdgpu: Avoid extra evict-restore process (stable-fixes). - drm/amdgpu: fix incorrect vm flags to map bo (git-fixes). - drm/amdgpu: fix task hang from failed job submission during process kill (git-fixes). - drm/amdgpu: update mmhub 3.0.1 client id mappings (stable-fixes). - drm/amdkfd: Destroy KFD debugfs after destroy KFD wq (stable-fixes). - drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS (stable-fixes). - drm/hisilicon/hibmc: fix the hibmc loaded failed bug (git-fixes). - drm/mediatek: Fix device/node reference count leaks in mtk_drm_get_all_drm_priv (git-fixes). - drm/msm/kms: move snapshot init earlier in KMS init (git-fixes). - drm/msm: Defer fd_install in SUBMIT ioctl (git-fixes). - drm/msm: use trylock for debugfs (stable-fixes). - drm/nouveau/disp: Always accept linear modifier (git-fixes). - drm/nouveau/nvif: Fix potential memory leak in nvif_vmm_ctor() (git-fixes). - drm/nouveau: fix error path in nvkm_gsp_fwsec_v2 (git-fixes). - drm/nouveau: fix typos in comments (git-fixes). - drm/nouveau: remove unused increment in gm200_flcn_pio_imem_wr (git-fixes). - drm/nouveau: remove unused memory target test (git-fixes). - drm/ttm: Respect the shrinker core free target (stable-fixes). - drm/ttm: Should to return the evict error (stable-fixes). - et131x: Add missing check after DMA map (stable-fixes). - exfat: add cluster chain loop check for dir (git-fixes). - fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (stable-fixes). - fbdev: fix potential buffer overflow in do_register_framebuffer() (stable-fixes). - fs/mnt_idmapping.c: Return -EINVAL when no map is written (bsc#1233120) - fs/orangefs: use snprintf() instead of sprintf() (git-fixes). - gpio: mlxbf3: use platform_get_irq_optional() (git-fixes). - gpio: tps65912: check the return value of regmap_update_bits() (stable-fixes). - gpio: wcd934x: check the return value of regmap_update_bits() (stable-fixes). - hfs: fix not erasing deleted b-tree node issue (git-fixes). - hfs: fix slab-out-of-bounds in hfs_bnode_read() (git-fixes). - hfsplus: do not use BUG_ON() in hfsplus_create_attributes_file() (git-fixes). - hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() (git-fixes). - hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (git-fixes). - hwmon: (emc2305) Set initial PWM minimum value during probe based on thermal state (stable-fixes). - i2c: Force DLL0945 touchpad i2c freq to 100khz (stable-fixes). - i3c: do not fail if GETHDRCAP is unsupported (stable-fixes). - i3c: master: Initialize ret in i3c_i2c_notifier_call() (stable-fixes). - ice, irdma: fix an off by one in error handling code (bsc#1247712). - ice, irdma: move interrupts code to irdma (bsc#1247712). - ice: Fix signedness bug in ice_init_interrupt_scheme() (bsc#1247712). - ice: count combined queues using Rx/Tx count (bsc#1247712). - ice: devlink PF MSI-X max and min parameter (bsc#1247712). - ice: enable_rdma devlink param (bsc#1247712). - ice: get rid of num_lan_msix field (bsc#1247712). - ice: init flow director before RDMA (bsc#1247712). - ice: remove splitting MSI-X between features (bsc#1247712). - ice: simplify VF MSI-X managing (bsc#1247712). - ice: treat dyn_allowed only as suggestion (bsc#1247712). - iio: adc: ad7768-1: Ensure SYNC_IN pulse minimum timing requirement (stable-fixes). - iio: adc: ad_sigma_delta: do not overallocate scan buffer (stable-fixes). - iio: imu: inv_icm42600: switch timestamp type from int64_t __aligned(8) to aligned_s64 (stable-fixes). - iio: imu: inv_icm42600: use = { } instead of memset() (stable-fixes). - iio: pressure: bmp280: Use IS_ERR() in bmp280_common_probe() (git-fixes). - iio: proximity: isl29501: fix buffered read on big-endian systems (git-fixes). - integrity/platform_certs: Allow loading of keys in the static key management mode (jsc#PED-13345 jsc#PED-13343). - iosys-map: Fix undefined behavior in iosys_map_clear() (git-fixes). - ipmi: Fix strcpy source and destination the same (stable-fixes). - ipmi: Use dev_warn_ratelimited() for incorrect message warnings (stable-fixes). - irdma: free iwdev->rf after removing MSI-X (bsc#1247712). - jfs: Regular file corruption check (git-fixes). - jfs: truncate good inode pages when hard link is 0 (git-fixes). - jfs: upper bound check of tree index in dbAllocAG (git-fixes). - kABI: PCI/ACPI: Fix runtime PM ref imbalance on Hot-Plug Capable ports (git-fixes). - kselftest/arm64: Fix check for setting new VLs in sve-ptrace (git-fixes). - leds: leds-lp50xx: Handle reg to get correct multi_index (stable-fixes). - loop: use kiocb helpers to fix lockdep warning (git-fixes). - mISDN: hfcpci: Fix warning when deleting uninitialized timer (git-fixes). - md/md-cluster: handle REMOVE message earlier (bsc#1247057). - md/raid1,raid10: strip REQ_NOWAIT from member bios (git-fixes). - md: allow removing faulty rdev during resync (git-fixes). - md: make rdev_addable usable for rcu mode (git-fixes). - media: dvb-frontends: dib7090p: fix null-ptr-deref in dib7090p_rw_on_apb() (stable-fixes). - media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and w7090p_tuner_read_serpar (stable-fixes). - media: tc358743: Check I2C succeeded during probe (stable-fixes). - media: tc358743: Increase FIFO trigger level to 374 (stable-fixes). - media: tc358743: Return an appropriate colorspace from tc358743_set_fmt (stable-fixes). - media: usb: hdpvr: disable zero-length read messages (stable-fixes). - media: uvcvideo: Fix bandwidth issue for Alcor camera (stable-fixes). - media: v4l2-common: Reduce warnings about missing V4L2_CID_LINK_FREQ control (stable-fixes). - mei: bus: Check for still connected devices in mei_cl_bus_dev_release() (stable-fixes). - memstick: Fix deadlock by moving removing flag earlier (git-fixes). - mm/ptdump: take the memory hotplug lock inside ptdump_walk_pgd() (git-fixes) - mmc: rtsx_usb_sdmmc: Fix error-path in sd_set_power_mode() (stable-fixes). - mmc: sdhci-msm: Ensure SD card power isn't ON when card removed (stable-fixes). - mmc: sdhci-pci-gli: GL9763e: Rename the gli_set_gl9763e() for consistency (git-fixes). - most: core: Drop device reference after usage in get_channel() (git-fixes). - mptcp: fallback when MPTCP opts are dropped after 1st data (git-fixes). - mptcp: reset when MPTCP opts are dropped after join (git-fixes). - net: phy: micrel: Add ksz9131_resume() (stable-fixes). - net: phy: smsc: add proper reset flags for LAN8710A (stable-fixes). - net: thunderbolt: Enable end-to-end flow control also in transmit (stable-fixes). - net: thunderbolt: Fix the parameter passing of tb_xdomain_enable_paths()/tb_xdomain_disable_paths() (stable-fixes). - net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization (git-fixes). - net: usb: asix_devices: add phy_mask for ax88772 mdio bus (git-fixes). - pNFS: Fix disk addr range check in block/scsi layout (git-fixes). - pNFS: Fix stripe mapping in block/scsi layout (git-fixes). - pNFS: Fix uninited ptr deref in block/scsi layout (git-fixes). - pNFS: Handle RPC size limit for layoutcommits (git-fixes). - phy: mscc: Fix parsing of unicast frames (git-fixes). - phy: rockchip-pcie: Properly disable TEST_WRITE strobe signal (stable-fixes). - pinctrl: STMFX: add missing HAS_IOMEM dependency (git-fixes). - pinctrl: stm32: Manage irq affinity settings (stable-fixes). - platform/chrome: cros_ec_typec: Defer probe on missing EC parent (stable-fixes). - platform/x86/amd: pmc: Add Lenovo Yoga 6 13ALC6 to pmc quirk list (stable-fixes). - pm: cpupower: Fix the snapshot-order of tsc,mperf, clock in mperf_stop() (stable-fixes). - power: supply: qcom_battmgr: Add lithium-polymer entry (stable-fixes). - powerpc/eeh: Export eeh_unfreeze_pe() (bsc#1215199). - powerpc/eeh: Make EEH driver device hotplug safe (bsc#1215199). - powerpc/eeh: Rely on dev->link_active_reporting (bsc#1215199). - powerpc/kernel: Fix ppc_save_regs inclusion in build (bsc#1215199). - powerpc/pseries: Correct secvar format representation for static key management (jsc#PED-13345 jsc#PED-13343). - powerpc/secvar: Expose secvars relevant to the key management mode (jsc#PED-13345 jsc#PED-13343). - powerpc: do not build ppc_save_regs.o always (bsc#1215199). - pwm: mediatek: Fix duty and period setting (git-fixes). - pwm: mediatek: Handle hardware enable and clock enable separately (stable-fixes). - reset: brcmstb: Enable reset drivers for ARCH_BCM2835 (stable-fixes). - rpm/config.sh: Update Leap project - rtc: ds1307: handle oscillator stop flag (OSF) for ds1341 (stable-fixes). - rtc: ds1307: remove clear of oscillator stop flag (OSF) in probe (stable-fixes). - samples/bpf: Fix compilation errors with cf-protection option (git-fixes). - scsi: Revert "scsi: iscsi: Fix HW conn removal use after free" (git-fixes). - scsi: core: Fix kernel doc for scsi_track_queue_full() (git-fixes). - scsi: elx: efct: Fix dma_unmap_sg() nents value (git-fixes). - scsi: ibmvscsi_tgt: Fix dma_unmap_sg() nents value (git-fixes). - scsi: isci: Fix dma_unmap_sg() nents value (git-fixes). - scsi: mpi3mr: Fix kernel-doc issues in mpi3mr_app.c (git-fixes). - scsi: mpi3mr: Fix race between config read submit and interrupt completion (git-fixes). - scsi: mpi3mr: Serialize admin queue BAR writes on 32-bit systems (git-fixes). - scsi: mpt3sas: Fix a fw_event memory leak (git-fixes). - scsi: mvsas: Fix dma_unmap_sg() nents value (git-fixes). - scsi: sd: Make sd shutdown issue START STOP UNIT appropriately (git-fixes). - selftests/bpf: fexit_sleep: Fix stack allocation for arm64 (git-fixes). - selftests/tracing: Fix false failure of subsystem event test (git-fixes). - selftests: Fix errno checking in syscall_user_dispatch test (git-fixes). - selftests: rtnetlink.sh: remove esp4_offload after test (git-fixes). - serial: 8250: fix panic due to PSLVERR (git-fixes). - slab: Decouple slab_debug and no_hash_pointers (bsc#1249022). - smb: client: fix parsing of device numbers (git-fixes). - soc/tegra: pmc: Ensure power-domains are in a known state (git-fixes). - soundwire: amd: serialize amd manager resume sequence during pm_prepare (stable-fixes). - squashfs: fix memory leak in squashfs_fill_super (git-fixes). - sunrpc: fix handling of server side tls alerts (git-fixes). - sunvdc: Balance device refcount in vdc_port_mpgroup_check (git-fixes). - thermal/drivers/qcom-spmi-temp-alarm: Enable stage 2 shutdown when required (stable-fixes). - thermal: sysfs: Return ENODATA instead of EAGAIN for reads (stable-fixes). - ublk: sanity check add_dev input for underflow (git-fixes). - ublk: use vmalloc for ublk_device's __queues (git-fixes). - usb: core: config: Prevent OOB read in SS endpoint companion parsing (stable-fixes). - usb: core: hcd: fix accessing unmapped memory in SINGLE_STEP_SET_FEATURE test (git-fixes). - usb: core: usb_submit_urb: downgrade type check (stable-fixes). - usb: dwc3: Ignore late xferNotReady event to prevent halt timeout (git-fixes). - usb: dwc3: Remove WARN_ON for device endpoint command timeouts (stable-fixes). - usb: dwc3: core: Fix system suspend on TI AM62 platforms (git-fixes). - usb: dwc3: fix fault at system suspend if device was already runtime suspended (git-fixes). - usb: dwc3: pci: add support for the Intel Wildcat Lake (stable-fixes). - usb: quirks: Add DELAY_INIT quick for another SanDisk 3.2Gen1 Flash Drive (stable-fixes). - usb: renesas-xhci: Fix External ROM access timeouts (git-fixes). - usb: storage: realtek_cr: Use correct byte order for bcs->Residue (git-fixes). - usb: typec: intel_pmc_mux: Defer probe if SCU IPC isn't present (stable-fixes). - usb: typec: ucsi: psy: Set current max to 100mA for BC 1.2 and Default (stable-fixes). - usb: xhci: Avoid showing errors during surprise removal (stable-fixes). - usb: xhci: Avoid showing warnings for dying controller (stable-fixes). - usb: xhci: Fix slot_id resource race conflict (git-fixes). - usb: xhci: Set avg_trb_len = 8 for EP0 during Address Device Command (stable-fixes). - usb: xhci: print xhci->xhc_state when queue_command failed (stable-fixes). - vfs: Add a sysctl for automated deletion of dentry (bsc#1240890). - watchdog: dw_wdt: Fix default timeout (stable-fixes). - watchdog: iTCO_wdt: Report error if timeout configuration fails (stable-fixes). - watchdog: sbsa: Adjust keepalive timeout to avoid MediaTek WS0 race condition (stable-fixes). - wifi: ath12k: Add memset and update default rate value in wmi tx completion (stable-fixes). - wifi: ath12k: Correct tid cleanup when tid setup fails (stable-fixes). - wifi: ath12k: Decrement TID on RX peer frag setup error handling (stable-fixes). - wifi: ath12k: Enable REO queue lookup table feature on QCN9274 hw2.0 (stable-fixes). - wifi: cfg80211: Fix interface type validation (stable-fixes). - wifi: cfg80211: reject HTC bit for management frames (stable-fixes). - wifi: iwlegacy: Check rate_idx range after addition (stable-fixes). - wifi: iwlwifi: dvm: fix potential overflow in rs_fill_link_cmd() (stable-fixes). - wifi: iwlwifi: fw: Fix possible memory leak in iwl_fw_dbg_collect (stable-fixes). - wifi: iwlwifi: mvm: fix scan request validation (stable-fixes). - wifi: iwlwifi: mvm: set gtk id also in older FWs (stable-fixes). - wifi: mac80211: do not complete management TX on SAE commit (stable-fixes). - wifi: mac80211: fix rx link assignment for non-MLO stations (stable-fixes). - wifi: mac80211: update radar_required in channel context after channel switch (stable-fixes). - wifi: mt76: mt7915: mcu: re-init MCU before loading FW patch (stable-fixes). - wifi: rtlwifi: fix possible skb memory leak in _rtl_pci_init_one_rxdesc() (stable-fixes). - wifi: rtlwifi: fix possible skb memory leak in `_rtl_pci_rx_interrupt()` (stable-fixes). - wifi: rtw89: Disable deep power saving for USB/SDIO (stable-fixes). - wifi: rtw89: Fix rtw89_mac_power_switch() for USB (stable-fixes). - wifi: rtw89: Lower the timeout in rtw89_fw_read_c2h_reg() for USB (stable-fixes). The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-SLE-Micro-6.0-kernel-101 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ Link for SUSE-SU-2025:20653-1 https://lists.suse.com/pipermail/sle-updates/2025-September/041572.html E-Mail link for SUSE-SU-2025:20653-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1012628 SUSE Bug 1012628 https://bugzilla.suse.com/1213545 SUSE Bug 1213545 https://bugzilla.suse.com/1215199 SUSE Bug 1215199 https://bugzilla.suse.com/1221858 SUSE Bug 1221858 https://bugzilla.suse.com/1222323 SUSE Bug 1222323 https://bugzilla.suse.com/1230557 SUSE Bug 1230557 https://bugzilla.suse.com/1230708 SUSE Bug 1230708 https://bugzilla.suse.com/1233120 SUSE Bug 1233120 https://bugzilla.suse.com/1240708 SUSE Bug 1240708 https://bugzilla.suse.com/1240890 SUSE Bug 1240890 https://bugzilla.suse.com/1242034 SUSE Bug 1242034 https://bugzilla.suse.com/1242754 SUSE Bug 1242754 https://bugzilla.suse.com/1244734 SUSE Bug 1244734 https://bugzilla.suse.com/1244930 SUSE Bug 1244930 https://bugzilla.suse.com/1245663 SUSE Bug 1245663 https://bugzilla.suse.com/1245710 SUSE Bug 1245710 https://bugzilla.suse.com/1245767 SUSE Bug 1245767 https://bugzilla.suse.com/1245780 SUSE Bug 1245780 https://bugzilla.suse.com/1245815 SUSE Bug 1245815 https://bugzilla.suse.com/1245956 SUSE Bug 1245956 https://bugzilla.suse.com/1245973 SUSE Bug 1245973 https://bugzilla.suse.com/1245977 SUSE Bug 1245977 https://bugzilla.suse.com/1246005 SUSE Bug 1246005 https://bugzilla.suse.com/1246012 SUSE Bug 1246012 https://bugzilla.suse.com/1246181 SUSE Bug 1246181 https://bugzilla.suse.com/1246193 SUSE Bug 1246193 https://bugzilla.suse.com/1247057 SUSE Bug 1247057 https://bugzilla.suse.com/1247078 SUSE Bug 1247078 https://bugzilla.suse.com/1247112 SUSE Bug 1247112 https://bugzilla.suse.com/1247116 SUSE Bug 1247116 https://bugzilla.suse.com/1247119 SUSE Bug 1247119 https://bugzilla.suse.com/1247155 SUSE Bug 1247155 https://bugzilla.suse.com/1247162 SUSE Bug 1247162 https://bugzilla.suse.com/1247167 SUSE Bug 1247167 https://bugzilla.suse.com/1247229 SUSE Bug 1247229 https://bugzilla.suse.com/1247243 SUSE Bug 1247243 https://bugzilla.suse.com/1247280 SUSE Bug 1247280 https://bugzilla.suse.com/1247313 SUSE Bug 1247313 https://bugzilla.suse.com/1247712 SUSE Bug 1247712 https://bugzilla.suse.com/1247976 SUSE Bug 1247976 https://bugzilla.suse.com/1248088 SUSE Bug 1248088 https://bugzilla.suse.com/1248108 SUSE Bug 1248108 https://bugzilla.suse.com/1248164 SUSE Bug 1248164 https://bugzilla.suse.com/1248166 SUSE Bug 1248166 https://bugzilla.suse.com/1248178 SUSE Bug 1248178 https://bugzilla.suse.com/1248179 SUSE Bug 1248179 https://bugzilla.suse.com/1248180 SUSE Bug 1248180 https://bugzilla.suse.com/1248183 SUSE Bug 1248183 https://bugzilla.suse.com/1248186 SUSE Bug 1248186 https://bugzilla.suse.com/1248194 SUSE Bug 1248194 https://bugzilla.suse.com/1248196 SUSE Bug 1248196 https://bugzilla.suse.com/1248198 SUSE Bug 1248198 https://bugzilla.suse.com/1248205 SUSE Bug 1248205 https://bugzilla.suse.com/1248206 SUSE Bug 1248206 https://bugzilla.suse.com/1248208 SUSE Bug 1248208 https://bugzilla.suse.com/1248209 SUSE Bug 1248209 https://bugzilla.suse.com/1248212 SUSE Bug 1248212 https://bugzilla.suse.com/1248213 SUSE Bug 1248213 https://bugzilla.suse.com/1248214 SUSE Bug 1248214 https://bugzilla.suse.com/1248216 SUSE Bug 1248216 https://bugzilla.suse.com/1248217 SUSE Bug 1248217 https://bugzilla.suse.com/1248223 SUSE Bug 1248223 https://bugzilla.suse.com/1248227 SUSE Bug 1248227 https://bugzilla.suse.com/1248228 SUSE Bug 1248228 https://bugzilla.suse.com/1248229 SUSE Bug 1248229 https://bugzilla.suse.com/1248240 SUSE Bug 1248240 https://bugzilla.suse.com/1248255 SUSE Bug 1248255 https://bugzilla.suse.com/1248297 SUSE Bug 1248297 https://bugzilla.suse.com/1248306 SUSE Bug 1248306 https://bugzilla.suse.com/1248312 SUSE Bug 1248312 https://bugzilla.suse.com/1248333 SUSE Bug 1248333 https://bugzilla.suse.com/1248337 SUSE Bug 1248337 https://bugzilla.suse.com/1248338 SUSE Bug 1248338 https://bugzilla.suse.com/1248340 SUSE Bug 1248340 https://bugzilla.suse.com/1248341 SUSE Bug 1248341 https://bugzilla.suse.com/1248345 SUSE Bug 1248345 https://bugzilla.suse.com/1248349 SUSE Bug 1248349 https://bugzilla.suse.com/1248350 SUSE Bug 1248350 https://bugzilla.suse.com/1248354 SUSE Bug 1248354 https://bugzilla.suse.com/1248355 SUSE Bug 1248355 https://bugzilla.suse.com/1248361 SUSE Bug 1248361 https://bugzilla.suse.com/1248363 SUSE Bug 1248363 https://bugzilla.suse.com/1248368 SUSE Bug 1248368 https://bugzilla.suse.com/1248374 SUSE Bug 1248374 https://bugzilla.suse.com/1248377 SUSE Bug 1248377 https://bugzilla.suse.com/1248386 SUSE Bug 1248386 https://bugzilla.suse.com/1248390 SUSE Bug 1248390 https://bugzilla.suse.com/1248395 SUSE Bug 1248395 https://bugzilla.suse.com/1248399 SUSE Bug 1248399 https://bugzilla.suse.com/1248401 SUSE Bug 1248401 https://bugzilla.suse.com/1248511 SUSE Bug 1248511 https://bugzilla.suse.com/1248573 SUSE Bug 1248573 https://bugzilla.suse.com/1248575 SUSE Bug 1248575 https://bugzilla.suse.com/1248577 SUSE Bug 1248577 https://bugzilla.suse.com/1248609 SUSE Bug 1248609 https://bugzilla.suse.com/1248614 SUSE Bug 1248614 https://bugzilla.suse.com/1248617 SUSE Bug 1248617 https://bugzilla.suse.com/1248621 SUSE Bug 1248621 https://bugzilla.suse.com/1248636 SUSE Bug 1248636 https://bugzilla.suse.com/1248643 SUSE Bug 1248643 https://bugzilla.suse.com/1248648 SUSE Bug 1248648 https://bugzilla.suse.com/1248652 SUSE Bug 1248652 https://bugzilla.suse.com/1248655 SUSE Bug 1248655 https://bugzilla.suse.com/1248666 SUSE Bug 1248666 https://bugzilla.suse.com/1248669 SUSE Bug 1248669 https://bugzilla.suse.com/1248746 SUSE Bug 1248746 https://bugzilla.suse.com/1248748 SUSE Bug 1248748 https://bugzilla.suse.com/1249022 SUSE Bug 1249022 https://www.suse.com/security/cve/CVE-2023-3867/ SUSE CVE CVE-2023-3867 page https://www.suse.com/security/cve/CVE-2023-4130/ SUSE CVE CVE-2023-4130 page https://www.suse.com/security/cve/CVE-2023-4515/ SUSE CVE CVE-2023-4515 page https://www.suse.com/security/cve/CVE-2024-26661/ SUSE CVE CVE-2024-26661 page https://www.suse.com/security/cve/CVE-2024-46733/ SUSE CVE CVE-2024-46733 page https://www.suse.com/security/cve/CVE-2024-58238/ SUSE CVE CVE-2024-58238 page https://www.suse.com/security/cve/CVE-2024-58239/ SUSE CVE CVE-2024-58239 page https://www.suse.com/security/cve/CVE-2025-38006/ SUSE CVE CVE-2025-38006 page https://www.suse.com/security/cve/CVE-2025-38075/ SUSE CVE CVE-2025-38075 page https://www.suse.com/security/cve/CVE-2025-38103/ SUSE CVE CVE-2025-38103 page https://www.suse.com/security/cve/CVE-2025-38125/ SUSE CVE CVE-2025-38125 page https://www.suse.com/security/cve/CVE-2025-38146/ SUSE CVE CVE-2025-38146 page https://www.suse.com/security/cve/CVE-2025-38160/ SUSE CVE CVE-2025-38160 page https://www.suse.com/security/cve/CVE-2025-38184/ SUSE CVE CVE-2025-38184 page https://www.suse.com/security/cve/CVE-2025-38185/ SUSE CVE CVE-2025-38185 page https://www.suse.com/security/cve/CVE-2025-38190/ SUSE CVE CVE-2025-38190 page https://www.suse.com/security/cve/CVE-2025-38201/ SUSE CVE CVE-2025-38201 page https://www.suse.com/security/cve/CVE-2025-38205/ SUSE CVE CVE-2025-38205 page https://www.suse.com/security/cve/CVE-2025-38208/ SUSE CVE CVE-2025-38208 page https://www.suse.com/security/cve/CVE-2025-38245/ SUSE CVE CVE-2025-38245 page https://www.suse.com/security/cve/CVE-2025-38251/ SUSE CVE CVE-2025-38251 page https://www.suse.com/security/cve/CVE-2025-38360/ SUSE CVE CVE-2025-38360 page https://www.suse.com/security/cve/CVE-2025-38439/ SUSE CVE CVE-2025-38439 page https://www.suse.com/security/cve/CVE-2025-38441/ SUSE CVE CVE-2025-38441 page https://www.suse.com/security/cve/CVE-2025-38444/ SUSE CVE CVE-2025-38444 page https://www.suse.com/security/cve/CVE-2025-38445/ SUSE CVE CVE-2025-38445 page https://www.suse.com/security/cve/CVE-2025-38458/ SUSE CVE CVE-2025-38458 page https://www.suse.com/security/cve/CVE-2025-38459/ SUSE CVE CVE-2025-38459 page https://www.suse.com/security/cve/CVE-2025-38464/ SUSE CVE CVE-2025-38464 page https://www.suse.com/security/cve/CVE-2025-38472/ SUSE CVE CVE-2025-38472 page https://www.suse.com/security/cve/CVE-2025-38490/ SUSE CVE CVE-2025-38490 page https://www.suse.com/security/cve/CVE-2025-38491/ SUSE CVE CVE-2025-38491 page https://www.suse.com/security/cve/CVE-2025-38499/ SUSE CVE CVE-2025-38499 page https://www.suse.com/security/cve/CVE-2025-38500/ SUSE CVE CVE-2025-38500 page https://www.suse.com/security/cve/CVE-2025-38503/ SUSE CVE CVE-2025-38503 page https://www.suse.com/security/cve/CVE-2025-38506/ SUSE CVE CVE-2025-38506 page https://www.suse.com/security/cve/CVE-2025-38510/ SUSE CVE CVE-2025-38510 page https://www.suse.com/security/cve/CVE-2025-38512/ SUSE CVE CVE-2025-38512 page https://www.suse.com/security/cve/CVE-2025-38513/ SUSE CVE CVE-2025-38513 page https://www.suse.com/security/cve/CVE-2025-38515/ SUSE CVE CVE-2025-38515 page https://www.suse.com/security/cve/CVE-2025-38516/ SUSE CVE CVE-2025-38516 page https://www.suse.com/security/cve/CVE-2025-38520/ SUSE CVE CVE-2025-38520 page https://www.suse.com/security/cve/CVE-2025-38524/ SUSE CVE CVE-2025-38524 page https://www.suse.com/security/cve/CVE-2025-38528/ SUSE CVE CVE-2025-38528 page https://www.suse.com/security/cve/CVE-2025-38529/ SUSE CVE CVE-2025-38529 page https://www.suse.com/security/cve/CVE-2025-38530/ SUSE CVE CVE-2025-38530 page https://www.suse.com/security/cve/CVE-2025-38531/ SUSE CVE CVE-2025-38531 page https://www.suse.com/security/cve/CVE-2025-38535/ SUSE CVE CVE-2025-38535 page https://www.suse.com/security/cve/CVE-2025-38537/ SUSE CVE CVE-2025-38537 page https://www.suse.com/security/cve/CVE-2025-38538/ SUSE CVE CVE-2025-38538 page https://www.suse.com/security/cve/CVE-2025-38540/ SUSE CVE CVE-2025-38540 page https://www.suse.com/security/cve/CVE-2025-38541/ SUSE CVE CVE-2025-38541 page https://www.suse.com/security/cve/CVE-2025-38543/ SUSE CVE CVE-2025-38543 page https://www.suse.com/security/cve/CVE-2025-38546/ SUSE CVE CVE-2025-38546 page https://www.suse.com/security/cve/CVE-2025-38548/ SUSE CVE CVE-2025-38548 page https://www.suse.com/security/cve/CVE-2025-38550/ SUSE CVE CVE-2025-38550 page https://www.suse.com/security/cve/CVE-2025-38553/ SUSE CVE CVE-2025-38553 page https://www.suse.com/security/cve/CVE-2025-38555/ SUSE CVE CVE-2025-38555 page https://www.suse.com/security/cve/CVE-2025-38560/ SUSE CVE CVE-2025-38560 page https://www.suse.com/security/cve/CVE-2025-38563/ SUSE CVE CVE-2025-38563 page https://www.suse.com/security/cve/CVE-2025-38565/ SUSE CVE CVE-2025-38565 page https://www.suse.com/security/cve/CVE-2025-38566/ SUSE CVE CVE-2025-38566 page https://www.suse.com/security/cve/CVE-2025-38568/ SUSE CVE CVE-2025-38568 page https://www.suse.com/security/cve/CVE-2025-38571/ SUSE CVE CVE-2025-38571 page https://www.suse.com/security/cve/CVE-2025-38572/ SUSE CVE CVE-2025-38572 page https://www.suse.com/security/cve/CVE-2025-38576/ SUSE CVE CVE-2025-38576 page https://www.suse.com/security/cve/CVE-2025-38581/ SUSE CVE CVE-2025-38581 page https://www.suse.com/security/cve/CVE-2025-38582/ SUSE CVE CVE-2025-38582 page https://www.suse.com/security/cve/CVE-2025-38583/ SUSE CVE CVE-2025-38583 page https://www.suse.com/security/cve/CVE-2025-38585/ SUSE CVE CVE-2025-38585 page https://www.suse.com/security/cve/CVE-2025-38587/ SUSE CVE CVE-2025-38587 page https://www.suse.com/security/cve/CVE-2025-38588/ SUSE CVE CVE-2025-38588 page https://www.suse.com/security/cve/CVE-2025-38591/ SUSE CVE CVE-2025-38591 page https://www.suse.com/security/cve/CVE-2025-38601/ SUSE CVE CVE-2025-38601 page https://www.suse.com/security/cve/CVE-2025-38602/ SUSE CVE CVE-2025-38602 page https://www.suse.com/security/cve/CVE-2025-38604/ SUSE CVE CVE-2025-38604 page https://www.suse.com/security/cve/CVE-2025-38608/ SUSE CVE CVE-2025-38608 page https://www.suse.com/security/cve/CVE-2025-38609/ SUSE CVE CVE-2025-38609 page https://www.suse.com/security/cve/CVE-2025-38610/ SUSE CVE CVE-2025-38610 page https://www.suse.com/security/cve/CVE-2025-38612/ SUSE CVE CVE-2025-38612 page https://www.suse.com/security/cve/CVE-2025-38617/ SUSE CVE CVE-2025-38617 page https://www.suse.com/security/cve/CVE-2025-38618/ SUSE CVE CVE-2025-38618 page https://www.suse.com/security/cve/CVE-2025-38621/ SUSE CVE CVE-2025-38621 page https://www.suse.com/security/cve/CVE-2025-38624/ SUSE CVE CVE-2025-38624 page https://www.suse.com/security/cve/CVE-2025-38630/ SUSE CVE CVE-2025-38630 page https://www.suse.com/security/cve/CVE-2025-38632/ SUSE CVE CVE-2025-38632 page https://www.suse.com/security/cve/CVE-2025-38634/ SUSE CVE CVE-2025-38634 page https://www.suse.com/security/cve/CVE-2025-38635/ SUSE CVE CVE-2025-38635 page https://www.suse.com/security/cve/CVE-2025-38644/ SUSE CVE CVE-2025-38644 page https://www.suse.com/security/cve/CVE-2025-38646/ SUSE CVE CVE-2025-38646 page https://www.suse.com/security/cve/CVE-2025-38650/ SUSE CVE CVE-2025-38650 page https://www.suse.com/security/cve/CVE-2025-38656/ SUSE CVE CVE-2025-38656 page https://www.suse.com/security/cve/CVE-2025-38663/ SUSE CVE CVE-2025-38663 page https://www.suse.com/security/cve/CVE-2025-38665/ SUSE CVE CVE-2025-38665 page https://www.suse.com/security/cve/CVE-2025-38670/ SUSE CVE CVE-2025-38670 page https://www.suse.com/security/cve/CVE-2025-38671/ SUSE CVE CVE-2025-38671 page SUSE Linux Micro 6.0 kernel-default-6.4.0-34.1 kernel-default-base-6.4.0-34.1.21.11 kernel-default-livepatch-6.4.0-34.1 kernel-devel-6.4.0-34.1 kernel-kvmsmall-6.4.0-34.1 kernel-macros-6.4.0-34.1 kernel-source-6.4.0-34.1 kernel-default-6.4.0-34.1 as a component of SUSE Linux Micro 6.0 kernel-default-base-6.4.0-34.1.21.11 as a component of SUSE Linux Micro 6.0 kernel-default-livepatch-6.4.0-34.1 as a component of SUSE Linux Micro 6.0 kernel-devel-6.4.0-34.1 as a component of SUSE Linux Micro 6.0 kernel-kvmsmall-6.4.0-34.1 as a component of SUSE Linux Micro 6.0 kernel-macros-6.4.0-34.1 as a component of SUSE Linux Micro 6.0 kernel-source-6.4.0-34.1 as a component of SUSE Linux Micro 6.0 In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix out of bounds read in smb2_sess_setup ksmbd does not consider the case of that smb2 session setup is in compound request. If this is the second payload of the compound, OOB read issue occurs while processing the first payload in the smb2_sess_setup(). CVE-2023-3867 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2023-3867.html CVE-2023-3867 https://bugzilla.suse.com/1213545 SUSE Bug 1213545 In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using ->NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea. CVE-2023-4130 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2023-4130.html CVE-2023-4130 https://bugzilla.suse.com/1248164 SUSE Bug 1248164 In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate command request size In commit 2b9b8f3b68ed ("ksmbd: validate command payload size"), except for SMB2_OPLOCK_BREAK_HE command, the request size of other commands is not checked, it's not expected. Fix it by add check for request size of other commands. CVE-2023-4515 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2023-4515.html CVE-2023-4515 https://bugzilla.suse.com/1248180 SUSE Bug 1248180 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add NULL test for 'timing generator' in 'dcn21_set_pipe()' In "u32 otg_inst = pipe_ctx->stream_res.tg->inst;" pipe_ctx->stream_res.tg could be NULL, it is relying on the caller to ensure the tg is not NULL. CVE-2024-26661 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2024-26661.html CVE-2024-26661 https://bugzilla.suse.com/1222323 SUSE Bug 1222323 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve leaks in cow_file_range In the buffered write path, the dirty page owns the qgroup reserve until it creates an ordered_extent. Therefore, any errors that occur before the ordered_extent is created must free that reservation, or else the space is leaked. The fstest generic/475 exercises various IO error paths, and is able to trigger errors in cow_file_range where we fail to get to allocating the ordered extent. Note that because we *do* clear delalloc, we are likely to remove the inode from the delalloc list, so the inodes/pages to not have invalidate/launder called on them in the commit abort path. This results in failures at the unmount stage of the test that look like: BTRFS: error (device dm-8 state EA) in cleanup_transaction:2018: errno=-5 IO failure BTRFS: error (device dm-8 state EA) in btrfs_replace_file_extents:2416: errno=-5 IO failure BTRFS warning (device dm-8 state EA): qgroup 0/5 has unreleased space, type 0 rsv 28672 ------------[ cut here ]------------ WARNING: CPU: 3 PID: 22588 at fs/btrfs/disk-io.c:4333 close_ctree+0x222/0x4d0 [btrfs] Modules linked in: btrfs blake2b_generic libcrc32c xor zstd_compress raid6_pq CPU: 3 PID: 22588 Comm: umount Kdump: loaded Tainted: G W 6.10.0-rc7-gab56fde445b8 #21 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 RIP: 0010:close_ctree+0x222/0x4d0 [btrfs] RSP: 0018:ffffb4465283be00 EFLAGS: 00010202 RAX: 0000000000000001 RBX: ffffa1a1818e1000 RCX: 0000000000000001 RDX: 0000000000000000 RSI: ffffb4465283bbe0 RDI: ffffa1a19374fcb8 RBP: ffffa1a1818e13c0 R08: 0000000100028b16 R09: 0000000000000000 R10: 0000000000000003 R11: 0000000000000003 R12: ffffa1a18ad7972c R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f9168312b80(0000) GS:ffffa1a4afcc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f91683c9140 CR3: 000000010acaa000 CR4: 00000000000006f0 Call Trace: <TASK> ? close_ctree+0x222/0x4d0 [btrfs] ? __warn.cold+0x8e/0xea ? close_ctree+0x222/0x4d0 [btrfs] ? report_bug+0xff/0x140 ? handle_bug+0x3b/0x70 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? close_ctree+0x222/0x4d0 [btrfs] generic_shutdown_super+0x70/0x160 kill_anon_super+0x11/0x40 btrfs_kill_super+0x11/0x20 [btrfs] deactivate_locked_super+0x2e/0xa0 cleanup_mnt+0xb5/0x150 task_work_run+0x57/0x80 syscall_exit_to_user_mode+0x121/0x130 do_syscall_64+0xab/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f916847a887 ---[ end trace 0000000000000000 ]--- BTRFS error (device dm-8 state EA): qgroup reserved space leaked Cases 2 and 3 in the out_reserve path both pertain to this type of leak and must free the reserved qgroup data. Because it is already an error path, I opted not to handle the possible errors in btrfs_free_qgroup_data. CVE-2024-46733 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2024-46733.html CVE-2024-46733 https://bugzilla.suse.com/1230708 SUSE Bug 1230708 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Resolve TX timeout error in power save stress test This fixes the tx timeout issue seen while running a stress test on btnxpuart for couple of hours, such that the interval between two HCI commands coincide with the power save timeout value of 2 seconds. Test procedure using bash script: <load btnxpuart.ko> hciconfig hci0 up //Enable Power Save feature hcitool -i hci0 cmd 3f 23 02 00 00 while (true) do hciconfig hci0 leadv sleep 2 hciconfig hci0 noleadv sleep 2 done Error log, after adding few more debug prints: Bluetooth: btnxpuart_queue_skb(): 01 0A 20 01 00 Bluetooth: hci0: Set UART break: on, status=0 Bluetooth: hci0: btnxpuart_tx_wakeup() tx_work scheduled Bluetooth: hci0: btnxpuart_tx_work() dequeue: 01 0A 20 01 00 Can't set advertise mode on hci0: Connection timed out (110) Bluetooth: hci0: command 0x200a tx timeout When the power save mechanism turns on UART break, and btnxpuart_tx_work() is scheduled simultaneously, psdata->ps_state is read as PS_STATE_AWAKE, which prevents the psdata->work from being scheduled, which is responsible to turn OFF UART break. This issue is fixed by adding a ps_lock mutex around UART break on/off as well as around ps_state read/write. btnxpuart_tx_wakeup() will now read updated ps_state value. If ps_state is PS_STATE_SLEEP, it will first schedule psdata->work, and then it will reschedule itself once UART break has been turned off and ps_state is PS_STATE_AWAKE. Tested above script for 50,000 iterations and TX timeout error was not observed anymore. CVE-2024-58238 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2024-58238.html CVE-2024-58238 https://bugzilla.suse.com/1242754 SUSE Bug 1242754 In the Linux kernel, the following vulnerability has been resolved: tls: stop recv() if initial process_rx_list gave us non-DATA If we have a non-DATA record on the rx_list and another record of the same type still on the queue, we will end up merging them: - process_rx_list copies the non-DATA record - we start the loop and process the first available record since it's of the same type - we break out of the loop since the record was not DATA Just check the record type and jump to the end in case process_rx_list did some work. CVE-2024-58239 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2024-58239.html CVE-2024-58239 https://bugzilla.suse.com/1248614 SUSE Bug 1248614 https://bugzilla.suse.com/1248615 SUSE Bug 1248615 In the Linux kernel, the following vulnerability has been resolved: net: mctp: Don't access ifa_index when missing In mctp_dump_addrinfo, ifa_index can be used to filter interfaces, but only when the struct ifaddrmsg is provided. Otherwise it will be comparing to uninitialised memory - reproducible in the syzkaller case from dhcpd, or busybox "ip addr show". The kernel MCTP implementation has always filtered by ifa_index, so existing userspace programs expecting to dump MCTP addresses must already be passing a valid ifa_index value (either 0 or a real index). BUG: KMSAN: uninit-value in mctp_dump_addrinfo+0x208/0xac0 net/mctp/device.c:128 mctp_dump_addrinfo+0x208/0xac0 net/mctp/device.c:128 rtnl_dump_all+0x3ec/0x5b0 net/core/rtnetlink.c:4380 rtnl_dumpit+0xd5/0x2f0 net/core/rtnetlink.c:6824 netlink_dump+0x97b/0x1690 net/netlink/af_netlink.c:2309 CVE-2025-38006 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38006.html CVE-2025-38006 https://bugzilla.suse.com/1244930 SUSE Bug 1244930 In the Linux kernel, the following vulnerability has been resolved: scsi: target: iscsi: Fix timeout on deleted connection NOPIN response timer may expire on a deleted connection and crash with such logs: Did not receive response to NOPIN on CID: 0, failing connection for I_T Nexus (null),i,0x00023d000125,iqn.2017-01.com.iscsi.target,t,0x3d BUG: Kernel NULL pointer dereference on read at 0x00000000 NIP strlcpy+0x8/0xb0 LR iscsit_fill_cxn_timeout_err_stats+0x5c/0xc0 [iscsi_target_mod] Call Trace: iscsit_handle_nopin_response_timeout+0xfc/0x120 [iscsi_target_mod] call_timer_fn+0x58/0x1f0 run_timer_softirq+0x740/0x860 __do_softirq+0x16c/0x420 irq_exit+0x188/0x1c0 timer_interrupt+0x184/0x410 That is because nopin response timer may be re-started on nopin timer expiration. Stop nopin timer before stopping the nopin response timer to be sure that no one of them will be re-started. CVE-2025-38075 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38075.html CVE-2025-38075 https://bugzilla.suse.com/1244734 SUSE Bug 1244734 In the Linux kernel, the following vulnerability has been resolved: HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() Update struct hid_descriptor to better reflect the mandatory and optional parts of the HID Descriptor as per USB HID 1.11 specification. Note: the kernel currently does not parse any optional HID class descriptors, only the mandatory report descriptor. Update all references to member element desc[0] to rpt_desc. Add test to verify bLength and bNumDescriptors values are valid. Replace the for loop with direct access to the mandatory HID class descriptor member for the report descriptor. This eliminates the possibility of getting an out-of-bounds fault. Add a warning message if the HID descriptor contains any unsupported optional HID class descriptors. CVE-2025-38103 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38103.html CVE-2025-38103 https://bugzilla.suse.com/1245663 SUSE Bug 1245663 In the Linux kernel, the following vulnerability has been resolved: net: stmmac: make sure that ptp_rate is not 0 before configuring EST If the ptp_rate recorded earlier in the driver happens to be 0, this bogus value will propagate up to EST configuration, where it will trigger a division by 0. Prevent this division by 0 by adding the corresponding check and error code. CVE-2025-38125 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38125.html CVE-2025-38125 https://bugzilla.suse.com/1245710 SUSE Bug 1245710 In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: Fix the dead loop of MPLS parse The unexpected MPLS packet may not end with the bottom label stack. When there are many stacks, The label count value has wrapped around. A dead loop occurs, soft lockup/CPU stuck finally. stack backtrace: UBSAN: array-index-out-of-bounds in /build/linux-0Pa0xK/linux-5.15.0/net/openvswitch/flow.c:662:26 index -1 is out of range for type '__be32 [3]' CPU: 34 PID: 0 Comm: swapper/34 Kdump: loaded Tainted: G OE 5.15.0-121-generic #131-Ubuntu Hardware name: Dell Inc. PowerEdge C6420/0JP9TF, BIOS 2.12.2 07/14/2021 Call Trace: <IRQ> show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x36 __ubsan_handle_out_of_bounds.cold+0x44/0x49 key_extract_l3l4+0x82a/0x840 [openvswitch] ? kfree_skbmem+0x52/0xa0 key_extract+0x9c/0x2b0 [openvswitch] ovs_flow_key_extract+0x124/0x350 [openvswitch] ovs_vport_receive+0x61/0xd0 [openvswitch] ? kernel_init_free_pages.part.0+0x4a/0x70 ? get_page_from_freelist+0x353/0x540 netdev_port_receive+0xc4/0x180 [openvswitch] ? netdev_port_receive+0x180/0x180 [openvswitch] netdev_frame_hook+0x1f/0x40 [openvswitch] __netif_receive_skb_core.constprop.0+0x23a/0xf00 __netif_receive_skb_list_core+0xfa/0x240 netif_receive_skb_list_internal+0x18e/0x2a0 napi_complete_done+0x7a/0x1c0 bnxt_poll+0x155/0x1c0 [bnxt_en] __napi_poll+0x30/0x180 net_rx_action+0x126/0x280 ? bnxt_msix+0x67/0x80 [bnxt_en] handle_softirqs+0xda/0x2d0 irq_exit_rcu+0x96/0xc0 common_interrupt+0x8e/0xa0 </IRQ> CVE-2025-38146 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38146.html CVE-2025-38146 https://bugzilla.suse.com/1245767 SUSE Bug 1245767 In the Linux kernel, the following vulnerability has been resolved: clk: bcm: rpi: Add NULL check in raspberrypi_clk_register() devm_kasprintf() returns NULL when memory allocation fails. Currently, raspberrypi_clk_register() does not check for this case, which results in a NULL pointer dereference. Add NULL check after devm_kasprintf() to prevent this issue. CVE-2025-38160 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38160.html CVE-2025-38160 https://bugzilla.suse.com/1245780 SUSE Bug 1245780 In the Linux kernel, the following vulnerability has been resolved: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer The reproduction steps: 1. create a tun interface 2. enable l2 bearer 3. TIPC_NL_UDP_GET_REMOTEIP with media name set to tun tipc: Started in network mode tipc: Node identity 8af312d38a21, cluster identity 4711 tipc: Enabled bearer <eth:syz_tun>, priority 1 Oops: general protection fault KASAN: null-ptr-deref in range CPU: 1 UID: 1000 PID: 559 Comm: poc Not tainted 6.16.0-rc1+ #117 PREEMPT Hardware name: QEMU Ubuntu 24.04 PC RIP: 0010:tipc_udp_nl_dump_remoteip+0x4a4/0x8f0 the ub was in fact a struct dev. when bid != 0 && skip_cnt != 0, bearer_list[bid] may be NULL or other media when other thread changes it. fix this by checking media_id. CVE-2025-38184 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38184.html CVE-2025-38184 https://bugzilla.suse.com/1245956 SUSE Bug 1245956 In the Linux kernel, the following vulnerability has been resolved: atm: atmtcp: Free invalid length skb in atmtcp_c_send(). syzbot reported the splat below. [0] vcc_sendmsg() copies data passed from userspace to skb and passes it to vcc->dev->ops->send(). atmtcp_c_send() accesses skb->data as struct atmtcp_hdr after checking if skb->len is 0, but it's not enough. Also, when skb->len == 0, skb and sk (vcc) were leaked because dev_kfree_skb() is not called and sk_wmem_alloc adjustment is missing to revert atm_account_tx() in vcc_sendmsg(), which is expected to be done in atm_pop_raw(). Let's properly free skb with an invalid length in atmtcp_c_send(). [0]: BUG: KMSAN: uninit-value in atmtcp_c_send+0x255/0xed0 drivers/atm/atmtcp.c:294 atmtcp_c_send+0x255/0xed0 drivers/atm/atmtcp.c:294 vcc_sendmsg+0xd7c/0xff0 net/atm/common.c:644 sock_sendmsg_nosec net/socket.c:712 [inline] __sock_sendmsg+0x330/0x3d0 net/socket.c:727 ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2566 ___sys_sendmsg+0x271/0x3b0 net/socket.c:2620 __sys_sendmsg net/socket.c:2652 [inline] __do_sys_sendmsg net/socket.c:2657 [inline] __se_sys_sendmsg net/socket.c:2655 [inline] __x64_sys_sendmsg+0x211/0x3e0 net/socket.c:2655 x64_sys_call+0x32fb/0x3db0 arch/x86/include/generated/asm/syscalls_64.h:47 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4154 [inline] slab_alloc_node mm/slub.c:4197 [inline] kmem_cache_alloc_node_noprof+0x818/0xf00 mm/slub.c:4249 kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:579 __alloc_skb+0x347/0x7d0 net/core/skbuff.c:670 alloc_skb include/linux/skbuff.h:1336 [inline] vcc_sendmsg+0xb40/0xff0 net/atm/common.c:628 sock_sendmsg_nosec net/socket.c:712 [inline] __sock_sendmsg+0x330/0x3d0 net/socket.c:727 ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2566 ___sys_sendmsg+0x271/0x3b0 net/socket.c:2620 __sys_sendmsg net/socket.c:2652 [inline] __do_sys_sendmsg net/socket.c:2657 [inline] __se_sys_sendmsg net/socket.c:2655 [inline] __x64_sys_sendmsg+0x211/0x3e0 net/socket.c:2655 x64_sys_call+0x32fb/0x3db0 arch/x86/include/generated/asm/syscalls_64.h:47 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 1 UID: 0 PID: 5798 Comm: syz-executor192 Not tainted 6.16.0-rc1-syzkaller-00010-g2c4a1f3fe03e #0 PREEMPT(undef) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 CVE-2025-38185 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38185.html CVE-2025-38185 https://bugzilla.suse.com/1246012 SUSE Bug 1246012 In the Linux kernel, the following vulnerability has been resolved: atm: Revert atm_account_tx() if copy_from_iter_full() fails. In vcc_sendmsg(), we account skb->truesize to sk->sk_wmem_alloc by atm_account_tx(). It is expected to be reverted by atm_pop_raw() later called by vcc->dev->ops->send(vcc, skb). However, vcc_sendmsg() misses the same revert when copy_from_iter_full() fails, and then we will leak a socket. Let's factorise the revert part as atm_return_tx() and call it in the failure path. Note that the corresponding sk_wmem_alloc operation can be found in alloc_tx() as of the blamed commit. $ git blame -L:alloc_tx net/atm/common.c c55fa3cccbc2c~ CVE-2025-38190 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38190.html CVE-2025-38190 https://bugzilla.suse.com/1245973 SUSE Bug 1245973 In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX Otherwise, it is possible to hit WARN_ON_ONCE in __kvmalloc_node_noprof() when resizing hashtable because __GFP_NOWARN is unset. Similar to: b541ba7d1f5a ("netfilter: conntrack: clamp maximum hashtable size to INT_MAX") CVE-2025-38201 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38201.html CVE-2025-38201 https://bugzilla.suse.com/1245977 SUSE Bug 1245977 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid divide by zero by initializing dummy pitch to 1 [Why] If the dummy values in `populate_dummy_dml_surface_cfg()` aren't updated then they can lead to a divide by zero in downstream callers like CalculateVMAndRowBytes() [How] Initialize dummy value to a value to avoid divide by zero. CVE-2025-38205 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38205.html CVE-2025-38205 https://bugzilla.suse.com/1246005 SUSE Bug 1246005 In the Linux kernel, the following vulnerability has been resolved: smb: client: add NULL check in automount_fullpath page is checked for null in __build_path_from_dentry_optional_prefix when tcon->origin_fullpath is not set. However, the check is missing when it is set. Add a check to prevent a potential NULL pointer dereference. CVE-2025-38208 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38208.html CVE-2025-38208 https://bugzilla.suse.com/1245815 SUSE Bug 1245815 In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). syzbot reported a warning below during atm_dev_register(). [0] Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated device by __atm_dev_lookup(). These operations are done under atm_dev_mutex. However, when removing a device in atm_dev_deregister(), it releases the mutex just after removing the device from the list that __atm_dev_lookup() iterates over. So, there will be a small race window where the device does not exist on the device list but procfs/sysfs are still not removed, triggering the splat. Let's hold the mutex until procfs/sysfs are removed in atm_dev_deregister(). [0]: proc_dir_entry 'atm/atmtcp:0' already registered WARNING: CPU: 0 PID: 5919 at fs/proc/generic.c:377 proc_register+0x455/0x5f0 fs/proc/generic.c:377 Modules linked in: CPU: 0 UID: 0 PID: 5919 Comm: syz-executor284 Not tainted 6.16.0-rc2-syzkaller-00047-g52da431bf03b #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 RIP: 0010:proc_register+0x455/0x5f0 fs/proc/generic.c:377 Code: 48 89 f9 48 c1 e9 03 80 3c 01 00 0f 85 a2 01 00 00 48 8b 44 24 10 48 c7 c7 20 c0 c2 8b 48 8b b0 d8 00 00 00 e8 0c 02 1c ff 90 <0f> 0b 90 90 48 c7 c7 80 f2 82 8e e8 0b de 23 09 48 8b 4c 24 28 48 RSP: 0018:ffffc9000466fa30 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff817ae248 RDX: ffff888026280000 RSI: ffffffff817ae255 RDI: 0000000000000001 RBP: ffff8880232bed48 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000001 R12: ffff888076ed2140 R13: dffffc0000000000 R14: ffff888078a61340 R15: ffffed100edda444 FS: 00007f38b3b0c6c0(0000) GS:ffff888124753000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f38b3bdf953 CR3: 0000000076d58000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> proc_create_data+0xbe/0x110 fs/proc/generic.c:585 atm_proc_dev_register+0x112/0x1e0 net/atm/proc.c:361 atm_dev_register+0x46d/0x890 net/atm/resources.c:113 atmtcp_create+0x77/0x210 drivers/atm/atmtcp.c:369 atmtcp_attach drivers/atm/atmtcp.c:403 [inline] atmtcp_ioctl+0x2f9/0xd60 drivers/atm/atmtcp.c:464 do_vcc_ioctl+0x12c/0x930 net/atm/ioctl.c:159 sock_do_ioctl+0x115/0x280 net/socket.c:1190 sock_ioctl+0x227/0x6b0 net/socket.c:1311 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f38b3b74459 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f38b3b0c198 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f38b3bfe318 RCX: 00007f38b3b74459 RDX: 0000000000000000 RSI: 0000000000006180 RDI: 0000000000000005 RBP: 00007f38b3bfe310 R08: 65732f636f72702f R09: 65732f636f72702f R10: 65732f636f72702f R11: 0000000000000246 R12: 00007f38b3bcb0ac R13: 00007f38b3b0c1a0 R14: 0000200000000200 R15: 00007f38b3bcb03b </TASK> CVE-2025-38245 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38245.html CVE-2025-38245 https://bugzilla.suse.com/1246193 SUSE Bug 1246193 In the Linux kernel, the following vulnerability has been resolved: atm: clip: prevent NULL deref in clip_push() Blamed commit missed that vcc_destroy_socket() calls clip_push() with a NULL skb. If clip_devs is NULL, clip_push() then crashes when reading skb->truesize. CVE-2025-38251 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38251.html CVE-2025-38251 https://bugzilla.suse.com/1246181 SUSE Bug 1246181 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add more checks for DSC / HUBP ONO guarantees [WHY] For non-zero DSC instances it's possible that the HUBP domain required to drive it for sequential ONO ASICs isn't met, potentially causing the logic to the tile to enter an undefined state leading to a system hang. [HOW] Add more checks to ensure that the HUBP domain matching the DSC instance is appropriately powered. (cherry picked from commit da63df07112e5a9857a8d2aaa04255c4206754ec) CVE-2025-38360 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38360.html CVE-2025-38360 https://bugzilla.suse.com/1247078 SUSE Bug 1247078 In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Set DMA unmap len correctly for XDP_REDIRECT When transmitting an XDP_REDIRECT packet, call dma_unmap_len_set() with the proper length instead of 0. This bug triggers this warning on a system with IOMMU enabled: WARNING: CPU: 36 PID: 0 at drivers/iommu/dma-iommu.c:842 __iommu_dma_unmap+0x159/0x170 RIP: 0010:__iommu_dma_unmap+0x159/0x170 Code: a8 00 00 00 00 48 c7 45 b0 00 00 00 00 48 c7 45 c8 00 00 00 00 48 c7 45 a0 ff ff ff ff 4c 89 45 b8 4c 89 45 c0 e9 77 ff ff ff <0f> 0b e9 60 ff ff ff e8 8b bf 6a 00 66 66 2e 0f 1f 84 00 00 00 00 RSP: 0018:ff22d31181150c88 EFLAGS: 00010206 RAX: 0000000000002000 RBX: 00000000e13a0000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ff22d31181150cf0 R08: ff22d31181150ca8 R09: 0000000000000000 R10: 0000000000000000 R11: ff22d311d36c9d80 R12: 0000000000001000 R13: ff13544d10645010 R14: ff22d31181150c90 R15: ff13544d0b2bac00 FS: 0000000000000000(0000) GS:ff13550908a00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005be909dacff8 CR3: 0008000173408003 CR4: 0000000000f71ef0 PKRU: 55555554 Call Trace: <IRQ> ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? __iommu_dma_unmap+0x159/0x170 ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? __iommu_dma_unmap+0x159/0x170 ? __iommu_dma_unmap+0xb3/0x170 iommu_dma_unmap_page+0x4f/0x100 dma_unmap_page_attrs+0x52/0x220 ? srso_alias_return_thunk+0x5/0xfbef5 ? xdp_return_frame+0x2e/0xd0 bnxt_tx_int_xdp+0xdf/0x440 [bnxt_en] __bnxt_poll_work_done+0x81/0x1e0 [bnxt_en] bnxt_poll+0xd3/0x1e0 [bnxt_en] CVE-2025-38439 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38439.html CVE-2025-38439 https://bugzilla.suse.com/1247155 SUSE Bug 1247155 In the Linux kernel, the following vulnerability has been resolved: netfilter: flowtable: account for Ethernet header in nf_flow_pppoe_proto() syzbot found a potential access to uninit-value in nf_flow_pppoe_proto() Blamed commit forgot the Ethernet header. BUG: KMSAN: uninit-value in nf_flow_offload_inet_hook+0x7e4/0x940 net/netfilter/nf_flow_table_inet.c:27 nf_flow_offload_inet_hook+0x7e4/0x940 net/netfilter/nf_flow_table_inet.c:27 nf_hook_entry_hookfn include/linux/netfilter.h:157 [inline] nf_hook_slow+0xe1/0x3d0 net/netfilter/core.c:623 nf_hook_ingress include/linux/netfilter_netdev.h:34 [inline] nf_ingress net/core/dev.c:5742 [inline] __netif_receive_skb_core+0x4aff/0x70c0 net/core/dev.c:5837 __netif_receive_skb_one_core net/core/dev.c:5975 [inline] __netif_receive_skb+0xcc/0xac0 net/core/dev.c:6090 netif_receive_skb_internal net/core/dev.c:6176 [inline] netif_receive_skb+0x57/0x630 net/core/dev.c:6235 tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485 tun_get_user+0x4ee0/0x6b40 drivers/net/tun.c:1938 tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1984 new_sync_write fs/read_write.c:593 [inline] vfs_write+0xb4b/0x1580 fs/read_write.c:686 ksys_write fs/read_write.c:738 [inline] __do_sys_write fs/read_write.c:749 [inline] CVE-2025-38441 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38441.html CVE-2025-38441 https://bugzilla.suse.com/1247167 SUSE Bug 1247167 In the Linux kernel, the following vulnerability has been resolved: raid10: cleanup memleak at raid10_make_request If raid10_read_request or raid10_write_request registers a new request and the REQ_NOWAIT flag is set, the code does not free the malloc from the mempool. unreferenced object 0xffff8884802c3200 (size 192): comm "fio", pid 9197, jiffies 4298078271 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 88 41 02 00 00 00 00 00 .........A...... 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc c1a049a2): __kmalloc+0x2bb/0x450 mempool_alloc+0x11b/0x320 raid10_make_request+0x19e/0x650 [raid10] md_handle_request+0x3b3/0x9e0 __submit_bio+0x394/0x560 __submit_bio_noacct+0x145/0x530 submit_bio_noacct_nocheck+0x682/0x830 __blkdev_direct_IO_async+0x4dc/0x6b0 blkdev_read_iter+0x1e5/0x3b0 __io_read+0x230/0x1110 io_read+0x13/0x30 io_issue_sqe+0x134/0x1180 io_submit_sqes+0x48c/0xe90 __do_sys_io_uring_enter+0x574/0x8b0 do_syscall_64+0x5c/0xe0 entry_SYSCALL_64_after_hwframe+0x76/0x7e V4: changing backing tree to see if CKI tests will pass. The patch code has not changed between any versions. CVE-2025-38444 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38444.html CVE-2025-38444 https://bugzilla.suse.com/1247162 SUSE Bug 1247162 In the Linux kernel, the following vulnerability has been resolved: md/raid1: Fix stack memory use after return in raid1_reshape In the raid1_reshape function, newpool is allocated on the stack and assigned to conf->r1bio_pool. This results in conf->r1bio_pool.wait.head pointing to a stack address. Accessing this address later can lead to a kernel panic. Example access path: raid1_reshape() { // newpool is on the stack mempool_t newpool, oldpool; // initialize newpool.wait.head to stack address mempool_init(&newpool, ...); conf->r1bio_pool = newpool; } raid1_read_request() or raid1_write_request() { alloc_r1bio() { mempool_alloc() { // if pool->alloc fails remove_element() { --pool->curr_nr; } } } } mempool_free() { if (pool->curr_nr < pool->min_nr) { // pool->wait.head is a stack address // wake_up() will try to access this invalid address // which leads to a kernel panic return; wake_up(&pool->wait); } } Fix: reinit conf->r1bio_pool.wait after assigning newpool. CVE-2025-38445 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38445.html CVE-2025-38445 https://bugzilla.suse.com/1247229 SUSE Bug 1247229 In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix NULL pointer dereference in vcc_sendmsg() atmarpd_dev_ops does not implement the send method, which may cause crash as bellow. BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: Oops: 0010 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 5324 Comm: syz.0.0 Not tainted 6.15.0-rc6-syzkaller-00346-g5723cc3450bc #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:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. RSP: 0018:ffffc9000d3cf778 EFLAGS: 00010246 RAX: 1ffffffff1910dd1 RBX: 00000000000000c0 RCX: dffffc0000000000 RDX: ffffc9000dc82000 RSI: ffff88803e4c4640 RDI: ffff888052cd0000 RBP: ffffc9000d3cf8d0 R08: ffff888052c9143f R09: 1ffff1100a592287 R10: dffffc0000000000 R11: 0000000000000000 R12: 1ffff92001a79f00 R13: ffff888052cd0000 R14: ffff88803e4c4640 R15: ffffffff8c886e88 FS: 00007fbc762566c0(0000) GS:ffff88808d6c2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffffffffd6 CR3: 0000000041f1b000 CR4: 0000000000352ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> vcc_sendmsg+0xa10/0xc50 net/atm/common.c:644 sock_sendmsg_nosec net/socket.c:712 [inline] __sock_sendmsg+0x219/0x270 net/socket.c:727 ____sys_sendmsg+0x52d/0x830 net/socket.c:2566 ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2620 __sys_sendmmsg+0x227/0x430 net/socket.c:2709 __do_sys_sendmmsg net/socket.c:2736 [inline] __se_sys_sendmmsg net/socket.c:2733 [inline] __x64_sys_sendmmsg+0xa0/0xc0 net/socket.c:2733 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f CVE-2025-38458 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38458.html CVE-2025-38458 https://bugzilla.suse.com/1247116 SUSE Bug 1247116 In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix infinite recursive call of clip_push(). syzbot reported the splat below. [0] This happens if we call ioctl(ATMARP_MKIP) more than once. During the first call, clip_mkip() sets clip_push() to vcc->push(), and the second call copies it to clip_vcc->old_push(). Later, when the socket is close()d, vcc_destroy_socket() passes NULL skb to clip_push(), which calls clip_vcc->old_push(), triggering the infinite recursion. Let's prevent the second ioctl(ATMARP_MKIP) by checking vcc->user_back, which is allocated by the first call as clip_vcc. Note also that we use lock_sock() to prevent racy calls. [0]: BUG: TASK stack guard page was hit at ffffc9000d66fff8 (stack is ffffc9000d670000..ffffc9000d678000) Oops: stack guard page: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 5322 Comm: syz.0.0 Not tainted 6.16.0-rc4-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:clip_push+0x5/0x720 net/atm/clip.c:191 Code: e0 8f aa 8c e8 1c ad 5b fa eb ae 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 55 <41> 57 41 56 41 55 41 54 53 48 83 ec 20 48 89 f3 49 89 fd 48 bd 00 RSP: 0018:ffffc9000d670000 EFLAGS: 00010246 RAX: 1ffff1100235a4a5 RBX: ffff888011ad2508 RCX: ffff8880003c0000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888037f01000 RBP: dffffc0000000000 R08: ffffffff8fa104f7 R09: 1ffffffff1f4209e R10: dffffc0000000000 R11: ffffffff8a99b300 R12: ffffffff8a99b300 R13: ffff888037f01000 R14: ffff888011ad2500 R15: ffff888037f01578 FS: 000055557ab6d500(0000) GS:ffff88808d250000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc9000d66fff8 CR3: 0000000043172000 CR4: 0000000000352ef0 Call Trace: <TASK> clip_push+0x6dc/0x720 net/atm/clip.c:200 clip_push+0x6dc/0x720 net/atm/clip.c:200 clip_push+0x6dc/0x720 net/atm/clip.c:200 ... clip_push+0x6dc/0x720 net/atm/clip.c:200 clip_push+0x6dc/0x720 net/atm/clip.c:200 clip_push+0x6dc/0x720 net/atm/clip.c:200 vcc_destroy_socket net/atm/common.c:183 [inline] vcc_release+0x157/0x460 net/atm/common.c:205 __sock_release net/socket.c:647 [inline] sock_close+0xc0/0x240 net/socket.c:1391 __fput+0x449/0xa70 fs/file_table.c:465 task_work_run+0x1d1/0x260 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xec/0x110 kernel/entry/common.c:114 exit_to_user_mode_prepare include/linux/entry-common.h:330 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:414 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:449 [inline] do_syscall_64+0x2bd/0x3b0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff31c98e929 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fffb5aa1f78 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: 0000000000000000 RBX: 0000000000012747 RCX: 00007ff31c98e929 RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003 RBP: 00007ff31cbb7ba0 R08: 0000000000000001 R09: 0000000db5aa226f R10: 00007ff31c7ff030 R11: 0000000000000246 R12: 00007ff31cbb608c R13: 00007ff31cbb6080 R14: ffffffffffffffff R15: 00007fffb5aa2090 </TASK> Modules linked in: CVE-2025-38459 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38459.html CVE-2025-38459 https://bugzilla.suse.com/1247119 SUSE Bug 1247119 In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each tipc_conn. The problem is that tipc_conn_close() is called after releasing the IDR lock. At the same time, there might be tipc_conn_recv_work() running and it could call tipc_conn_close() for the same tipc_conn and release its last ->kref. Once we release the IDR lock in tipc_topsrv_stop(), there is no guarantee that the tipc_conn is alive. Let's hold the ref before releasing the lock and put the ref after tipc_conn_close() in tipc_topsrv_stop(). [0]: BUG: KASAN: use-after-free in tipc_conn_close+0x122/0x140 net/tipc/topsrv.c:165 Read of size 8 at addr ffff888099305a08 by task kworker/u4:3/435 CPU: 0 PID: 435 Comm: kworker/u4:3 Not tainted 4.19.204-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: netns cleanup_net Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_address_description.cold+0x54/0x219 mm/kasan/report.c:256 kasan_report_error.cold+0x8a/0x1b9 mm/kasan/report.c:354 kasan_report mm/kasan/report.c:412 [inline] __asan_report_load8_noabort+0x88/0x90 mm/kasan/report.c:433 tipc_conn_close+0x122/0x140 net/tipc/topsrv.c:165 tipc_topsrv_stop net/tipc/topsrv.c:701 [inline] tipc_topsrv_exit_net+0x27b/0x5c0 net/tipc/topsrv.c:722 ops_exit_list+0xa5/0x150 net/core/net_namespace.c:153 cleanup_net+0x3b4/0x8b0 net/core/net_namespace.c:553 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 Allocated by task 23: kmem_cache_alloc_trace+0x12f/0x380 mm/slab.c:3625 kmalloc include/linux/slab.h:515 [inline] kzalloc include/linux/slab.h:709 [inline] tipc_conn_alloc+0x43/0x4f0 net/tipc/topsrv.c:192 tipc_topsrv_accept+0x1b5/0x280 net/tipc/topsrv.c:470 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 Freed by task 23: __cache_free mm/slab.c:3503 [inline] kfree+0xcc/0x210 mm/slab.c:3822 tipc_conn_kref_release net/tipc/topsrv.c:150 [inline] kref_put include/linux/kref.h:70 [inline] conn_put+0x2cd/0x3a0 net/tipc/topsrv.c:155 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 The buggy address belongs to the object at ffff888099305a00 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 8 bytes inside of 512-byte region [ffff888099305a00, ffff888099305c00) The buggy address belongs to the page: page:ffffea000264c140 count:1 mapcount:0 mapping:ffff88813bff0940 index:0x0 flags: 0xfff00000000100(slab) raw: 00fff00000000100 ffffea00028b6b88 ffffea0002cd2b08 ffff88813bff0940 raw: 0000000000000000 ffff888099305000 0000000100000006 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888099305900: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888099305980: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff888099305a00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888099305a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888099305b00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb CVE-2025-38464 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38464.html CVE-2025-38464 https://bugzilla.suse.com/1247112 SUSE Bug 1247112 In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry A crash in conntrack was reported while trying to unlink the conntrack entry from the hash bucket list: [exception RIP: __nf_ct_delete_from_lists+172] [..] #7 [ff539b5a2b043aa0] nf_ct_delete at ffffffffc124d421 [nf_conntrack] #8 [ff539b5a2b043ad0] nf_ct_gc_expired at ffffffffc124d999 [nf_conntrack] #9 [ff539b5a2b043ae0] __nf_conntrack_find_get at ffffffffc124efbc [nf_conntrack] [..] The nf_conn struct is marked as allocated from slab but appears to be in a partially initialised state: ct hlist pointer is garbage; looks like the ct hash value (hence crash). ct->status is equal to IPS_CONFIRMED|IPS_DYING, which is expected ct->timeout is 30000 (=30s), which is unexpected. Everything else looks like normal udp conntrack entry. If we ignore ct->status and pretend its 0, the entry matches those that are newly allocated but not yet inserted into the hash: - ct hlist pointers are overloaded and store/cache the raw tuple hash - ct->timeout matches the relative time expected for a new udp flow rather than the absolute 'jiffies' value. If it were not for the presence of IPS_CONFIRMED, __nf_conntrack_find_get() would have skipped the entry. Theory is that we did hit following race: cpu x cpu y cpu z found entry E found entry E E is expired <preemption> nf_ct_delete() return E to rcu slab init_conntrack E is re-inited, ct->status set to 0 reply tuplehash hnnode.pprev stores hash value. cpu y found E right before it was deleted on cpu x. E is now re-inited on cpu z. cpu y was preempted before checking for expiry and/or confirm bit. ->refcnt set to 1 E now owned by skb ->timeout set to 30000 If cpu y were to resume now, it would observe E as expired but would skip E due to missing CONFIRMED bit. nf_conntrack_confirm gets called sets: ct->status |= CONFIRMED This is wrong: E is not yet added to hashtable. cpu y resumes, it observes E as expired but CONFIRMED: <resumes> nf_ct_expired() -> yes (ct->timeout is 30s) confirmed bit set. cpu y will try to delete E from the hashtable: nf_ct_delete() -> set DYING bit __nf_ct_delete_from_lists Even this scenario doesn't guarantee a crash: cpu z still holds the table bucket lock(s) so y blocks: wait for spinlock held by z CONFIRMED is set but there is no guarantee ct will be added to hash: "chaintoolong" or "clash resolution" logic both skip the insert step. reply hnnode.pprev still stores the hash value. unlocks spinlock return NF_DROP <unblocks, then crashes on hlist_nulls_del_rcu pprev> In case CPU z does insert the entry into the hashtable, cpu y will unlink E again right away but no crash occurs. Without 'cpu y' race, 'garbage' hlist is of no consequence: ct refcnt remains at 1, eventually skb will be free'd and E gets destroyed via: nf_conntrack_put -> nf_conntrack_destroy -> nf_ct_destroy. To resolve this, move the IPS_CONFIRMED assignment after the table insertion but before the unlock. Pablo points out that the confirm-bit-store could be reordered to happen before hlist add resp. the timeout fixup, so switch to set_bit and before_atomic memory barrier to prevent this. It doesn't matter if other CPUs can observe a newly inserted entry right before the CONFIRMED bit was set: Such event cannot be distinguished from above "E is the old incarnation" case: the entry will be skipped. Also change nf_ct_should_gc() to first check the confirmed bit. The gc sequence is: 1. Check if entry has expired, if not skip to next entry 2. Obtain a reference to the expired entry. 3. Call nf_ct_should_gc() to double-check step 1. nf_ct_should_gc() is thus called only for entries that already failed an expiry check. After this patch, once the confirmed bit check pas ---truncated--- CVE-2025-38472 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38472.html CVE-2025-38472 https://bugzilla.suse.com/1247313 SUSE Bug 1247313 In the Linux kernel, the following vulnerability has been resolved: net: libwx: remove duplicate page_pool_put_full_page() page_pool_put_full_page() should only be invoked when freeing Rx buffers or building a skb if the size is too short. At other times, the pages need to be reused. So remove the redundant page put. In the original code, double free pages cause kernel panic: [ 876.949834] __irq_exit_rcu+0xc7/0x130 [ 876.949836] common_interrupt+0xb8/0xd0 [ 876.949838] </IRQ> [ 876.949838] <TASK> [ 876.949840] asm_common_interrupt+0x22/0x40 [ 876.949841] RIP: 0010:cpuidle_enter_state+0xc2/0x420 [ 876.949843] Code: 00 00 e8 d1 1d 5e ff e8 ac f0 ff ff 49 89 c5 0f 1f 44 00 00 31 ff e8 cd fc 5c ff 45 84 ff 0f 85 40 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 84 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d [ 876.949844] RSP: 0018:ffffaa7340267e78 EFLAGS: 00000246 [ 876.949845] RAX: ffff9e3f135be000 RBX: 0000000000000002 RCX: 0000000000000000 [ 876.949846] RDX: 000000cc2dc4cb7c RSI: ffffffff89ee49ae RDI: ffffffff89ef9f9e [ 876.949847] RBP: ffff9e378f940800 R08: 0000000000000002 R09: 00000000000000ed [ 876.949848] R10: 000000000000afc8 R11: ffff9e3e9e5a9b6c R12: ffffffff8a6d8580 [ 876.949849] R13: 000000cc2dc4cb7c R14: 0000000000000002 R15: 0000000000000000 [ 876.949852] ? cpuidle_enter_state+0xb3/0x420 [ 876.949855] cpuidle_enter+0x29/0x40 [ 876.949857] cpuidle_idle_call+0xfd/0x170 [ 876.949859] do_idle+0x7a/0xc0 [ 876.949861] cpu_startup_entry+0x25/0x30 [ 876.949862] start_secondary+0x117/0x140 [ 876.949864] common_startup_64+0x13e/0x148 [ 876.949867] </TASK> [ 876.949868] ---[ end trace 0000000000000000 ]--- [ 876.949869] ------------[ cut here ]------------ [ 876.949870] list_del corruption, ffffead40445a348->next is NULL [ 876.949873] WARNING: CPU: 14 PID: 0 at lib/list_debug.c:52 __list_del_entry_valid_or_report+0x67/0x120 [ 876.949875] Modules linked in: snd_hrtimer(E) bnep(E) binfmt_misc(E) amdgpu(E) squashfs(E) vfat(E) loop(E) fat(E) amd_atl(E) snd_hda_codec_realtek(E) intel_rapl_msr(E) snd_hda_codec_generic(E) intel_rapl_common(E) snd_hda_scodec_component(E) snd_hda_codec_hdmi(E) snd_hda_intel(E) edac_mce_amd(E) snd_intel_dspcfg(E) snd_hda_codec(E) snd_hda_core(E) amdxcp(E) kvm_amd(E) snd_hwdep(E) gpu_sched(E) drm_panel_backlight_quirks(E) cec(E) snd_pcm(E) drm_buddy(E) snd_seq_dummy(E) drm_ttm_helper(E) btusb(E) kvm(E) snd_seq_oss(E) btrtl(E) ttm(E) btintel(E) snd_seq_midi(E) btbcm(E) drm_exec(E) snd_seq_midi_event(E) i2c_algo_bit(E) snd_rawmidi(E) bluetooth(E) drm_suballoc_helper(E) irqbypass(E) snd_seq(E) ghash_clmulni_intel(E) sha512_ssse3(E) drm_display_helper(E) aesni_intel(E) snd_seq_device(E) rfkill(E) snd_timer(E) gf128mul(E) drm_client_lib(E) drm_kms_helper(E) snd(E) i2c_piix4(E) joydev(E) soundcore(E) wmi_bmof(E) ccp(E) k10temp(E) i2c_smbus(E) gpio_amdpt(E) i2c_designware_platform(E) gpio_generic(E) sg(E) [ 876.949914] i2c_designware_core(E) sch_fq_codel(E) parport_pc(E) drm(E) ppdev(E) lp(E) parport(E) fuse(E) nfnetlink(E) ip_tables(E) ext4 crc16 mbcache jbd2 sd_mod sfp mdio_i2c i2c_core txgbe ahci ngbe pcs_xpcs libahci libwx r8169 phylink libata realtek ptp pps_core video wmi [ 876.949933] CPU: 14 UID: 0 PID: 0 Comm: swapper/14 Kdump: loaded Tainted: G W E 6.16.0-rc2+ #20 PREEMPT(voluntary) [ 876.949935] Tainted: [W]=WARN, [E]=UNSIGNED_MODULE [ 876.949936] Hardware name: Micro-Star International Co., Ltd. MS-7E16/X670E GAMING PLUS WIFI (MS-7E16), BIOS 1.90 12/31/2024 [ 876.949936] RIP: 0010:__list_del_entry_valid_or_report+0x67/0x120 [ 876.949938] Code: 00 00 00 48 39 7d 08 0f 85 a6 00 00 00 5b b8 01 00 00 00 5d 41 5c e9 73 0d 93 ff 48 89 fe 48 c7 c7 a0 31 e8 89 e8 59 7c b3 ff <0f> 0b 31 c0 5b 5d 41 5c e9 57 0d 93 ff 48 89 fe 48 c7 c7 c8 31 e8 [ 876.949940] RSP: 0018:ffffaa73405d0c60 EFLAGS: 00010282 [ 876.949941] RAX: 0000000000000000 RBX: ffffead40445a348 RCX: 0000000000000000 [ 876.949942] RDX: 0000000000000105 RSI: 00000 ---truncated--- CVE-2025-38490 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38490.html CVE-2025-38490 https://bugzilla.suse.com/1247243 SUSE Bug 1247243 https://bugzilla.suse.com/1247384 SUSE Bug 1247384 In the Linux kernel, the following vulnerability has been resolved: mptcp: make fallback action and fallback decision atomic Syzkaller reported the following splat: WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Modules linked in: CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary) Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline] RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 <0f> 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00 RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45 RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001 RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000 FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0 Call Trace: <IRQ> tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432 tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975 tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166 tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925 tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363 ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233 NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254 dst_input include/net/dst.h:469 [inline] ip_rcv_finish net/ipv4/ip_input.c:447 [inline] NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567 __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975 __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088 process_backlog+0x301/0x1360 net/core/dev.c:6440 __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453 napi_poll net/core/dev.c:7517 [inline] net_rx_action+0xb44/0x1010 net/core/dev.c:7644 handle_softirqs+0x1d0/0x770 kernel/softirq.c:579 do_softirq+0x3f/0x90 kernel/softirq.c:480 </IRQ> <TASK> __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407 local_bh_enable include/linux/bottom_half.h:33 [inline] inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524 mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985 mptcp_check_listen_stop net/mptcp/mib.h:118 [inline] __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000 mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066 inet_release+0xed/0x200 net/ipv4/af_inet.c:435 inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x402/0xb70 fs/file_table.c:465 task_work_run+0x150/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xd4 ---truncated--- CVE-2025-38491 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38491.html CVE-2025-38491 https://bugzilla.suse.com/1247280 SUSE Bug 1247280 In the Linux kernel, the following vulnerability has been resolved: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns What we want is to verify there is that clone won't expose something hidden by a mount we wouldn't be able to undo. "Wouldn't be able to undo" may be a result of MNT_LOCKED on a child, but it may also come from lacking admin rights in the userns of the namespace mount belongs to. clone_private_mnt() checks the former, but not the latter. There's a number of rather confusing CAP_SYS_ADMIN checks in various userns during the mount, especially with the new mount API; they serve different purposes and in case of clone_private_mnt() they usually, but not always end up covering the missing check mentioned above. CVE-2025-38499 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38499.html CVE-2025-38499 https://bugzilla.suse.com/1247976 SUSE Bug 1247976 https://bugzilla.suse.com/1248673 SUSE Bug 1248673 In the Linux kernel, the following vulnerability has been resolved: xfrm: interface: fix use-after-free after changing collect_md xfrm interface collect_md property on xfrm interfaces can only be set on device creation, thus xfrmi_changelink() should fail when called on such interfaces. The check to enforce this was done only in the case where the xi was returned from xfrmi_locate() which doesn't look for the collect_md interface, and thus the validation was never reached. Calling changelink would thus errornously place the special interface xi in the xfrmi_net->xfrmi hash, but since it also exists in the xfrmi_net->collect_md_xfrmi pointer it would lead to a double free when the net namespace was taken down [1]. Change the check to use the xi from netdev_priv which is available earlier in the function to prevent changes in xfrm collect_md interfaces. [1] resulting oops: [ 8.516540] kernel BUG at net/core/dev.c:12029! [ 8.516552] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 8.516559] CPU: 0 UID: 0 PID: 12 Comm: kworker/u80:0 Not tainted 6.15.0-virtme #5 PREEMPT(voluntary) [ 8.516565] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 8.516569] Workqueue: netns cleanup_net [ 8.516579] RIP: 0010:unregister_netdevice_many_notify+0x101/0xab0 [ 8.516590] Code: 90 0f 0b 90 48 8b b0 78 01 00 00 48 8b 90 80 01 00 00 48 89 56 08 48 89 32 4c 89 80 78 01 00 00 48 89 b8 80 01 00 00 eb ac 90 <0f> 0b 48 8b 45 00 4c 8d a0 88 fe ff ff 48 39 c5 74 5c 41 80 bc 24 [ 8.516593] RSP: 0018:ffffa93b8006bd30 EFLAGS: 00010206 [ 8.516598] RAX: ffff98fe4226e000 RBX: ffffa93b8006bd58 RCX: ffffa93b8006bc60 [ 8.516601] RDX: 0000000000000004 RSI: 0000000000000000 RDI: dead000000000122 [ 8.516603] RBP: ffffa93b8006bdd8 R08: dead000000000100 R09: ffff98fe4133c100 [ 8.516605] R10: 0000000000000000 R11: 00000000000003d2 R12: ffffa93b8006be00 [ 8.516608] R13: ffffffff96c1a510 R14: ffffffff96c1a510 R15: ffffa93b8006be00 [ 8.516615] FS: 0000000000000000(0000) GS:ffff98fee73b7000(0000) knlGS:0000000000000000 [ 8.516619] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 8.516622] CR2: 00007fcd2abd0700 CR3: 000000003aa40000 CR4: 0000000000752ef0 [ 8.516625] PKRU: 55555554 [ 8.516627] Call Trace: [ 8.516632] <TASK> [ 8.516635] ? rtnl_is_locked+0x15/0x20 [ 8.516641] ? unregister_netdevice_queue+0x29/0xf0 [ 8.516650] ops_undo_list+0x1f2/0x220 [ 8.516659] cleanup_net+0x1ad/0x2e0 [ 8.516664] process_one_work+0x160/0x380 [ 8.516673] worker_thread+0x2aa/0x3c0 [ 8.516679] ? __pfx_worker_thread+0x10/0x10 [ 8.516686] kthread+0xfb/0x200 [ 8.516690] ? __pfx_kthread+0x10/0x10 [ 8.516693] ? __pfx_kthread+0x10/0x10 [ 8.516697] ret_from_fork+0x82/0xf0 [ 8.516705] ? __pfx_kthread+0x10/0x10 [ 8.516709] ret_from_fork_asm+0x1a/0x30 [ 8.516718] </TASK> CVE-2025-38500 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38500.html CVE-2025-38500 https://bugzilla.suse.com/1248088 SUSE Bug 1248088 https://bugzilla.suse.com/1248672 SUSE Bug 1248672 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix assertion when building free space tree When building the free space tree with the block group tree feature enabled, we can hit an assertion failure like this: BTRFS info (device loop0 state M): rebuilding free space tree assertion failed: ret == 0, in fs/btrfs/free-space-tree.c:1102 ------------[ cut here ]------------ kernel BUG at fs/btrfs/free-space-tree.c:1102! Internal error: Oops - BUG: 00000000f2000800 [#1] SMP Modules linked in: CPU: 1 UID: 0 PID: 6592 Comm: syz-executor322 Not tainted 6.15.0-rc7-syzkaller-gd7fa1af5b33e #0 PREEMPT Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : populate_free_space_tree+0x514/0x518 fs/btrfs/free-space-tree.c:1102 lr : populate_free_space_tree+0x514/0x518 fs/btrfs/free-space-tree.c:1102 sp : ffff8000a4ce7600 x29: ffff8000a4ce76e0 x28: ffff0000c9bc6000 x27: ffff0000ddfff3d8 x26: ffff0000ddfff378 x25: dfff800000000000 x24: 0000000000000001 x23: ffff8000a4ce7660 x22: ffff70001499cecc x21: ffff0000e1d8c160 x20: ffff0000e1cb7800 x19: ffff0000e1d8c0b0 x18: 00000000ffffffff x17: ffff800092f39000 x16: ffff80008ad27e48 x15: ffff700011e740c0 x14: 1ffff00011e740c0 x13: 0000000000000004 x12: ffffffffffffffff x11: ffff700011e740c0 x10: 0000000000ff0100 x9 : 94ef24f55d2dbc00 x8 : 94ef24f55d2dbc00 x7 : 0000000000000001 x6 : 0000000000000001 x5 : ffff8000a4ce6f98 x4 : ffff80008f415ba0 x3 : ffff800080548ef0 x2 : 0000000000000000 x1 : 0000000100000000 x0 : 000000000000003e Call trace: populate_free_space_tree+0x514/0x518 fs/btrfs/free-space-tree.c:1102 (P) btrfs_rebuild_free_space_tree+0x14c/0x54c fs/btrfs/free-space-tree.c:1337 btrfs_start_pre_rw_mount+0xa78/0xe10 fs/btrfs/disk-io.c:3074 btrfs_remount_rw fs/btrfs/super.c:1319 [inline] btrfs_reconfigure+0x828/0x2418 fs/btrfs/super.c:1543 reconfigure_super+0x1d4/0x6f0 fs/super.c:1083 do_remount fs/namespace.c:3365 [inline] path_mount+0xb34/0xde0 fs/namespace.c:4200 do_mount fs/namespace.c:4221 [inline] __do_sys_mount fs/namespace.c:4432 [inline] __se_sys_mount fs/namespace.c:4409 [inline] __arm64_sys_mount+0x3e8/0x468 fs/namespace.c:4409 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x58/0x17c arch/arm64/kernel/entry-common.c:767 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:786 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 Code: f0047182 91178042 528089c3 9771d47b (d4210000) ---[ end trace 0000000000000000 ]--- This happens because we are processing an empty block group, which has no extents allocated from it, there are no items for this block group, including the block group item since block group items are stored in a dedicated tree when using the block group tree feature. It also means this is the block group with the highest start offset, so there are no higher keys in the extent root, hence btrfs_search_slot_for_read() returns 1 (no higher key found). Fix this by asserting 'ret' is 0 only if the block group tree feature is not enabled, in which case we should find a block group item for the block group since it's stored in the extent root and block group item keys are greater than extent item keys (the value for BTRFS_BLOCK_GROUP_ITEM_KEY is 192 and for BTRFS_EXTENT_ITEM_KEY and BTRFS_METADATA_ITEM_KEY the values are 168 and 169 respectively). In case 'ret' is 1, we just need to add a record to the free space tree which spans the whole block group, and we can achieve this by making 'ret == 0' as the while loop's condition. CVE-2025-38503 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38503.html CVE-2025-38503 https://bugzilla.suse.com/1248183 SUSE Bug 1248183 In the Linux kernel, the following vulnerability has been resolved: KVM: Allow CPU to reschedule while setting per-page memory attributes When running an SEV-SNP guest with a sufficiently large amount of memory (1TB+), the host can experience CPU soft lockups when running an operation in kvm_vm_set_mem_attributes() to set memory attributes on the whole range of guest memory. watchdog: BUG: soft lockup - CPU#8 stuck for 26s! [qemu-kvm:6372] CPU: 8 UID: 0 PID: 6372 Comm: qemu-kvm Kdump: loaded Not tainted 6.15.0-rc7.20250520.el9uek.rc1.x86_64 #1 PREEMPT(voluntary) Hardware name: Oracle Corporation ORACLE SERVER E4-2c/Asm,MB Tray,2U,E4-2c, BIOS 78016600 11/13/2024 RIP: 0010:xas_create+0x78/0x1f0 Code: 00 00 00 41 80 fc 01 0f 84 82 00 00 00 ba 06 00 00 00 bd 06 00 00 00 49 8b 45 08 4d 8d 65 08 41 39 d6 73 20 83 ed 06 48 85 c0 <74> 67 48 89 c2 83 e2 03 48 83 fa 02 75 0c 48 3d 00 10 00 00 0f 87 RSP: 0018:ffffad890a34b940 EFLAGS: 00000286 RAX: ffff96f30b261daa RBX: ffffad890a34b9c8 RCX: 0000000000000000 RDX: 000000000000001e RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000000000018 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffad890a356868 R13: ffffad890a356860 R14: 0000000000000000 R15: ffffad890a356868 FS: 00007f5578a2a400(0000) GS:ffff97ed317e1000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f015c70fb18 CR3: 00000001109fd006 CR4: 0000000000f70ef0 PKRU: 55555554 Call Trace: <TASK> xas_store+0x58/0x630 __xa_store+0xa5/0x130 xa_store+0x2c/0x50 kvm_vm_set_mem_attributes+0x343/0x710 [kvm] kvm_vm_ioctl+0x796/0xab0 [kvm] __x64_sys_ioctl+0xa3/0xd0 do_syscall_64+0x8c/0x7a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f5578d031bb Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 2d 4c 0f 00 f7 d8 64 89 01 48 RSP: 002b:00007ffe0a742b88 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 000000004020aed2 RCX: 00007f5578d031bb RDX: 00007ffe0a742c80 RSI: 000000004020aed2 RDI: 000000000000000b RBP: 0000010000000000 R08: 0000010000000000 R09: 0000017680000000 R10: 0000000000000080 R11: 0000000000000246 R12: 00005575e5f95120 R13: 00007ffe0a742c80 R14: 0000000000000008 R15: 00005575e5f961e0 While looping through the range of memory setting the attributes, call cond_resched() to give the scheduler a chance to run a higher priority task on the runqueue if necessary and avoid staying in kernel mode long enough to trigger the lockup. CVE-2025-38506 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38506.html CVE-2025-38506 https://bugzilla.suse.com/1248186 SUSE Bug 1248186 In the Linux kernel, the following vulnerability has been resolved: kasan: remove kasan_find_vm_area() to prevent possible deadlock find_vm_area() couldn't be called in atomic_context. If find_vm_area() is called to reports vm area information, kasan can trigger deadlock like: CPU0 CPU1 vmalloc(); alloc_vmap_area(); spin_lock(&vn->busy.lock) spin_lock_bh(&some_lock); <interrupt occurs> <in softirq> spin_lock(&some_lock); <access invalid address> kasan_report(); print_report(); print_address_description(); kasan_find_vm_area(); find_vm_area(); spin_lock(&vn->busy.lock) // deadlock! To prevent possible deadlock while kasan reports, remove kasan_find_vm_area(). CVE-2025-38510 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38510.html CVE-2025-38510 https://bugzilla.suse.com/1248166 SUSE Bug 1248166 In the Linux kernel, the following vulnerability has been resolved: wifi: prevent A-MSDU attacks in mesh networks This patch is a mitigation to prevent the A-MSDU spoofing vulnerability for mesh networks. The initial update to the IEEE 802.11 standard, in response to the FragAttacks, missed this case (CVE-2025-27558). It can be considered a variant of CVE-2020-24588 but for mesh networks. This patch tries to detect if a standard MSDU was turned into an A-MSDU by an adversary. This is done by parsing a received A-MSDU as a standard MSDU, calculating the length of the Mesh Control header, and seeing if the 6 bytes after this header equal the start of an rfc1042 header. If equal, this is a strong indication of an ongoing attack attempt. This defense was tested with mac80211_hwsim against a mesh network that uses an empty Mesh Address Extension field, i.e., when four addresses are used, and when using a 12-byte Mesh Address Extension field, i.e., when six addresses are used. Functionality of normal MSDUs and A-MSDUs was also tested, and confirmed working, when using both an empty and 12-byte Mesh Address Extension field. It was also tested with mac80211_hwsim that A-MSDU attacks in non-mesh networks keep being detected and prevented. Note that the vulnerability being patched, and the defense being implemented, was also discussed in the following paper and in the following IEEE 802.11 presentation: https://papers.mathyvanhoef.com/wisec2025.pdf https://mentor.ieee.org/802.11/dcn/25/11-25-0949-00-000m-a-msdu-mesh-spoof-protection.docx CVE-2025-38512 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38512.html CVE-2025-38512 https://bugzilla.suse.com/1248178 SUSE Bug 1248178 In the Linux kernel, the following vulnerability has been resolved: wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() There is a potential NULL pointer dereference in zd_mac_tx_to_dev(). For example, the following is possible: T0 T1 zd_mac_tx_to_dev() /* len == skb_queue_len(q) */ while (len > ZD_MAC_MAX_ACK_WAITERS) { filter_ack() spin_lock_irqsave(&q->lock, flags); /* position == skb_queue_len(q) */ for (i=1; i<position; i++) skb = __skb_dequeue(q) if (mac->type == NL80211_IFTYPE_AP) skb = __skb_dequeue(q); spin_unlock_irqrestore(&q->lock, flags); skb_dequeue() -> NULL Since there is a small gap between checking skb queue length and skb being unconditionally dequeued in zd_mac_tx_to_dev(), skb_dequeue() can return NULL. Then the pointer is passed to zd_mac_tx_status() where it is dereferenced. In order to avoid potential NULL pointer dereference due to situations like above, check if skb is not NULL before passing it to zd_mac_tx_status(). Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2025-38513 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38513.html CVE-2025-38513 https://bugzilla.suse.com/1248179 SUSE Bug 1248179 In the Linux kernel, the following vulnerability has been resolved: drm/sched: Increment job count before swapping tail spsc queue A small race exists between spsc_queue_push and the run-job worker, in which spsc_queue_push may return not-first while the run-job worker has already idled due to the job count being zero. If this race occurs, job scheduling stops, leading to hangs while waiting on the job's DMA fences. Seal this race by incrementing the job count before appending to the SPSC queue. This race was observed on a drm-tip 6.16-rc1 build with the Xe driver in an SVM test case. CVE-2025-38515 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38515.html CVE-2025-38515 https://bugzilla.suse.com/1248212 SUSE Bug 1248212 In the Linux kernel, the following vulnerability has been resolved: pinctrl: qcom: msm: mark certain pins as invalid for interrupts On some platforms, the UFS-reset pin has no interrupt logic in TLMM but is nevertheless registered as a GPIO in the kernel. This enables the user-space to trigger a BUG() in the pinctrl-msm driver by running, for example: `gpiomon -c 0 113` on RB2. The exact culprit is requesting pins whose intr_detection_width setting is not 1 or 2 for interrupts. This hits a BUG() in msm_gpio_irq_set_type(). Potentially crashing the kernel due to an invalid request from user-space is not optimal, so let's go through the pins and mark those that would fail the check as invalid for the irq chip as we should not even register them as available irqs. This function can be extended if we determine that there are more corner-cases like this. CVE-2025-38516 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38516.html CVE-2025-38516 https://bugzilla.suse.com/1248209 SUSE Bug 1248209 In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Don't call mmput from MMU notifier callback If the process is exiting, the mmput inside mmu notifier callback from compactd or fork or numa balancing could release the last reference of mm struct to call exit_mmap and free_pgtable, this triggers deadlock with below backtrace. The deadlock will leak kfd process as mmu notifier release is not called and cause VRAM leaking. The fix is to take mm reference mmget_non_zero when adding prange to the deferred list to pair with mmput in deferred list work. If prange split and add into pchild list, the pchild work_item.mm is not used, so remove the mm parameter from svm_range_unmap_split and svm_range_add_child. The backtrace of hung task: INFO: task python:348105 blocked for more than 64512 seconds. Call Trace: __schedule+0x1c3/0x550 schedule+0x46/0xb0 rwsem_down_write_slowpath+0x24b/0x4c0 unlink_anon_vmas+0xb1/0x1c0 free_pgtables+0xa9/0x130 exit_mmap+0xbc/0x1a0 mmput+0x5a/0x140 svm_range_cpu_invalidate_pagetables+0x2b/0x40 [amdgpu] mn_itree_invalidate+0x72/0xc0 __mmu_notifier_invalidate_range_start+0x48/0x60 try_to_unmap_one+0x10fa/0x1400 rmap_walk_anon+0x196/0x460 try_to_unmap+0xbb/0x210 migrate_page_unmap+0x54d/0x7e0 migrate_pages_batch+0x1c3/0xae0 migrate_pages_sync+0x98/0x240 migrate_pages+0x25c/0x520 compact_zone+0x29d/0x590 compact_zone_order+0xb6/0xf0 try_to_compact_pages+0xbe/0x220 __alloc_pages_direct_compact+0x96/0x1a0 __alloc_pages_slowpath+0x410/0x930 __alloc_pages_nodemask+0x3a9/0x3e0 do_huge_pmd_anonymous_page+0xd7/0x3e0 __handle_mm_fault+0x5e3/0x5f0 handle_mm_fault+0xf7/0x2e0 hmm_vma_fault.isra.0+0x4d/0xa0 walk_pmd_range.isra.0+0xa8/0x310 walk_pud_range+0x167/0x240 walk_pgd_range+0x55/0x100 __walk_page_range+0x87/0x90 walk_page_range+0xf6/0x160 hmm_range_fault+0x4f/0x90 amdgpu_hmm_range_get_pages+0x123/0x230 [amdgpu] amdgpu_ttm_tt_get_user_pages+0xb1/0x150 [amdgpu] init_user_pages+0xb1/0x2a0 [amdgpu] amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu+0x543/0x7d0 [amdgpu] kfd_ioctl_alloc_memory_of_gpu+0x24c/0x4e0 [amdgpu] kfd_ioctl+0x29d/0x500 [amdgpu] (cherry picked from commit a29e067bd38946f752b0ef855f3dfff87e77bec7) CVE-2025-38520 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38520.html CVE-2025-38520 https://bugzilla.suse.com/1248217 SUSE Bug 1248217 In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix recv-recv race of completed call If a call receives an event (such as incoming data), the call gets placed on the socket's queue and a thread in recvmsg can be awakened to go and process it. Once the thread has picked up the call off of the queue, further events will cause it to be requeued, and once the socket lock is dropped (recvmsg uses call->user_mutex to allow the socket to be used in parallel), a second thread can come in and its recvmsg can pop the call off the socket queue again. In such a case, the first thread will be receiving stuff from the call and the second thread will be blocked on call->user_mutex. The first thread can, at this point, process both the event that it picked call for and the event that the second thread picked the call for and may see the call terminate - in which case the call will be "released", decoupling the call from the user call ID assigned to it (RXRPC_USER_CALL_ID in the control message). The first thread will return okay, but then the second thread will wake up holding the user_mutex and, if it sees that the call has been released by the first thread, it will BUG thusly: kernel BUG at net/rxrpc/recvmsg.c:474! Fix this by just dequeuing the call and ignoring it if it is seen to be already released. We can't tell userspace about it anyway as the user call ID has become stale. CVE-2025-38524 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38524.html CVE-2025-38524 https://bugzilla.suse.com/1248194 SUSE Bug 1248194 In the Linux kernel, the following vulnerability has been resolved: bpf: Reject %p% format string in bprintf-like helpers static const char fmt[] = "%p%"; bpf_trace_printk(fmt, sizeof(fmt)); The above BPF program isn't rejected and causes a kernel warning at runtime: Please remove unsupported %\x00 in format string WARNING: CPU: 1 PID: 7244 at lib/vsprintf.c:2680 format_decode+0x49c/0x5d0 This happens because bpf_bprintf_prepare skips over the second %, detected as punctuation, while processing %p. This patch fixes it by not skipping over punctuation. %\x00 is then processed in the next iteration and rejected. CVE-2025-38528 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38528.html CVE-2025-38528 https://bugzilla.suse.com/1248198 SUSE Bug 1248198 In the Linux kernel, the following vulnerability has been resolved: comedi: aio_iiro_16: Fix bit shift out of bounds When checking for a supported IRQ number, the following test is used: if ((1 << it->options[1]) & 0xdcfc) { However, `it->options[i]` is an unchecked `int` value from userspace, so the shift amount could be negative or out of bounds. Fix the test by requiring `it->options[1]` to be within bounds before proceeding with the original test. Valid `it->options[1]` values that select the IRQ will be in the range [1,15]. The value 0 explicitly disables the use of interrupts. CVE-2025-38529 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38529.html CVE-2025-38529 https://bugzilla.suse.com/1248196 SUSE Bug 1248196 In the Linux kernel, the following vulnerability has been resolved: comedi: pcl812: Fix bit shift out of bounds When checking for a supported IRQ number, the following test is used: if ((1 << it->options[1]) & board->irq_bits) { However, `it->options[i]` is an unchecked `int` value from userspace, so the shift amount could be negative or out of bounds. Fix the test by requiring `it->options[1]` to be within bounds before proceeding with the original test. Valid `it->options[1]` values that select the IRQ will be in the range [1,15]. The value 0 explicitly disables the use of interrupts. CVE-2025-38530 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38530.html CVE-2025-38530 https://bugzilla.suse.com/1248206 SUSE Bug 1248206 In the Linux kernel, the following vulnerability has been resolved: iio: common: st_sensors: Fix use of uninitialize device structs Throughout the various probe functions &indio_dev->dev is used before it is initialized. This caused a kernel panic in st_sensors_power_enable() when the call to devm_regulator_bulk_get_enable() fails and then calls dev_err_probe() with the uninitialized device. This seems to only cause a panic with dev_err_probe(), dev_err(), dev_warn() and dev_info() don't seem to cause a panic, but are fixed as well. The issue is reported and traced here: [1] CVE-2025-38531 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38531.html CVE-2025-38531 https://bugzilla.suse.com/1248205 SUSE Bug 1248205 In the Linux kernel, the following vulnerability has been resolved: phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode When transitioning from USB_ROLE_DEVICE to USB_ROLE_NONE, the code assumed that the regulator should be disabled. However, if the regulator is marked as always-on, regulator_is_enabled() continues to return true, leading to an incorrect attempt to disable a regulator which is not enabled. This can result in warnings such as: [ 250.155624] WARNING: CPU: 1 PID: 7326 at drivers/regulator/core.c:3004 _regulator_disable+0xe4/0x1a0 [ 250.155652] unbalanced disables for VIN_SYS_5V0 To fix this, we move the regulator control logic into tegra186_xusb_padctl_id_override() function since it's directly related to the ID override state. The regulator is now only disabled when the role transitions from USB_ROLE_HOST to USB_ROLE_NONE, by checking the VBUS_ID register. This ensures that regulator enable/disable operations are properly balanced and only occur when actually transitioning to/from host mode. CVE-2025-38535 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38535.html CVE-2025-38535 https://bugzilla.suse.com/1248240 SUSE Bug 1248240 In the Linux kernel, the following vulnerability has been resolved: net: phy: Don't register LEDs for genphy If a PHY has no driver, the genphy driver is probed/removed directly in phy_attach/detach. If the PHY's ofnode has an "leds" subnode, then the LEDs will be (un)registered when probing/removing the genphy driver. This could occur if the leds are for a non-generic driver that isn't loaded for whatever reason. Synchronously removing the PHY device in phy_detach leads to the following deadlock: rtnl_lock() ndo_close() ... phy_detach() phy_remove() phy_leds_unregister() led_classdev_unregister() led_trigger_set() netdev_trigger_deactivate() unregister_netdevice_notifier() rtnl_lock() There is a corresponding deadlock on the open/register side of things (and that one is reported by lockdep), but it requires a race while this one is deterministic. Generic PHYs do not support LEDs anyway, so don't bother registering them. CVE-2025-38537 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38537.html CVE-2025-38537 https://bugzilla.suse.com/1248229 SUSE Bug 1248229 In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure this can't happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the "chan" iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn't in the correct place and it would always return -EINVAL. However, now it will always be in the correct place. I deleted the check since we know the result. CVE-2025-38538 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38538.html CVE-2025-38538 https://bugzilla.suse.com/1248213 SUSE Bug 1248213 In the Linux kernel, the following vulnerability has been resolved: HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras The Chicony Electronics HP 5MP Cameras (USB ID 04F2:B824 & 04F2:B82C) report a HID sensor interface that is not actually implemented. Attempting to access this non-functional sensor via iio_info causes system hangs as runtime PM tries to wake up an unresponsive sensor. Add these 2 devices to the HID ignore list since the sensor interface is non-functional by design and should not be exposed to userspace. CVE-2025-38540 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38540.html CVE-2025-38540 https://bugzilla.suse.com/1248208 SUSE Bug 1248208 In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() devm_kasprintf() returns NULL on error. Currently, mt7925_thermal_init() does not check for this case, which results in a NULL pointer dereference. Add NULL check after devm_kasprintf() to prevent this issue. CVE-2025-38541 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38541.html CVE-2025-38541 https://bugzilla.suse.com/1248216 SUSE Bug 1248216 In the Linux kernel, the following vulnerability has been resolved: drm/tegra: nvdec: Fix dma_alloc_coherent error check Check for NULL return value with dma_alloc_coherent, in line with Robin's fix for vic.c in 'drm/tegra: vic: Fix DMA API misuse'. CVE-2025-38543 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38543.html CVE-2025-38543 https://bugzilla.suse.com/1248214 SUSE Bug 1248214 In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix memory leak of struct clip_vcc. ioctl(ATMARP_MKIP) allocates struct clip_vcc and set it to vcc->user_back. The code assumes that vcc_destroy_socket() passes NULL skb to vcc->push() when the socket is close()d, and then clip_push() frees clip_vcc. However, ioctl(ATMARPD_CTRL) sets NULL to vcc->push() in atm_init_atmarp(), resulting in memory leak. Let's serialise two ioctl() by lock_sock() and check vcc->push() in atm_init_atmarp() to prevent memleak. CVE-2025-38546 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38546.html CVE-2025-38546 https://bugzilla.suse.com/1248223 SUSE Bug 1248223 In the Linux kernel, the following vulnerability has been resolved: hwmon: (corsair-cpro) Validate the size of the received input buffer Add buffer_recv_size to store the size of the received bytes. Validate buffer_recv_size in send_usb_cmd(). CVE-2025-38548 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38548.html CVE-2025-38548 https://bugzilla.suse.com/1248228 SUSE Bug 1248228 In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: Delay put pmc->idev in mld_del_delrec() pmc->idev is still used in ip6_mc_clear_src(), so as mld_clear_delrec() does, the reference should be put after ip6_mc_clear_src() return. CVE-2025-38550 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38550.html CVE-2025-38550 https://bugzilla.suse.com/1248227 SUSE Bug 1248227 In the Linux kernel, the following vulnerability has been resolved: net/sched: Restrict conditions for adding duplicating netems to qdisc tree netem_enqueue's duplication prevention logic breaks when a netem resides in a qdisc tree with other netems - this can lead to a soft lockup and OOM loop in netem_dequeue, as seen in [1]. Ensure that a duplicating netem cannot exist in a tree with other netems. Previous approaches suggested in discussions in chronological order: 1) Track duplication status or ttl in the sk_buff struct. Considered too specific a use case to extend such a struct, though this would be a resilient fix and address other previous and potential future DOS bugs like the one described in loopy fun [2]. 2) Restrict netem_enqueue recursion depth like in act_mirred with a per cpu variable. However, netem_dequeue can call enqueue on its child, and the depth restriction could be bypassed if the child is a netem. 3) Use the same approach as in 2, but add metadata in netem_skb_cb to handle the netem_dequeue case and track a packet's involvement in duplication. This is an overly complex approach, and Jamal notes that the skb cb can be overwritten to circumvent this safeguard. 4) Prevent the addition of a netem to a qdisc tree if its ancestral path contains a netem. However, filters and actions can cause a packet to change paths when re-enqueued to the root from netem duplication, leading us to the current solution: prevent a duplicating netem from inhabiting the same tree as other netems. [1] https://lore.kernel.org/netdev/8DuRWwfqjoRDLDmBMlIfbrsZg9Gx50DHJc1ilxsEBNe2D6NMoigR_eIRIG0LOjMc3r10nUUZtArXx4oZBIdUfZQrwjcQhdinnMis_0G7VEk=@willsroot.io/ [2] https://lwn.net/Articles/719297/ CVE-2025-38553 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38553.html CVE-2025-38553 https://bugzilla.suse.com/1248255 SUSE Bug 1248255 In the Linux kernel, the following vulnerability has been resolved: usb: gadget : fix use-after-free in composite_dev_cleanup() 1. In func configfs_composite_bind() -> composite_os_desc_req_prepare(): if kmalloc fails, the pointer cdev->os_desc_req will be freed but not set to NULL. Then it will return a failure to the upper-level function. 2. in func configfs_composite_bind() -> composite_dev_cleanup(): it will checks whether cdev->os_desc_req is NULL. If it is not NULL, it will attempt to use it.This will lead to a use-after-free issue. BUG: KASAN: use-after-free in composite_dev_cleanup+0xf4/0x2c0 Read of size 8 at addr 0000004827837a00 by task init/1 CPU: 10 PID: 1 Comm: init Tainted: G O 5.10.97-oh #1 kasan_report+0x188/0x1cc __asan_load8+0xb4/0xbc composite_dev_cleanup+0xf4/0x2c0 configfs_composite_bind+0x210/0x7ac udc_bind_to_driver+0xb4/0x1ec usb_gadget_probe_driver+0xec/0x21c gadget_dev_desc_UDC_store+0x264/0x27c CVE-2025-38555 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38555.html CVE-2025-38555 https://bugzilla.suse.com/1248297 SUSE Bug 1248297 https://bugzilla.suse.com/1248298 SUSE Bug 1248298 In the Linux kernel, the following vulnerability has been resolved: x86/sev: Evict cache lines during SNP memory validation An SNP cache coherency vulnerability requires a cache line eviction mitigation when validating memory after a page state change to private. The specific mitigation is to touch the first and last byte of each 4K page that is being validated. There is no need to perform the mitigation when performing a page state change to shared and rescinding validation. CPUID bit Fn8000001F_EBX[31] defines the COHERENCY_SFW_NO CPUID bit that, when set, indicates that the software mitigation for this vulnerability is not needed. Implement the mitigation and invoke it when validating memory (making it private) and the COHERENCY_SFW_NO bit is not set, indicating the SNP guest is vulnerable. CVE-2025-38560 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38560.html CVE-2025-38560 https://bugzilla.suse.com/1248312 SUSE Bug 1248312 https://bugzilla.suse.com/1248313 SUSE Bug 1248313 In the Linux kernel, the following vulnerability has been resolved: perf/core: Prevent VMA split of buffer mappings The perf mmap code is careful about mmap()'ing the user page with the ringbuffer and additionally the auxiliary buffer, when the event supports it. Once the first mapping is established, subsequent mapping have to use the same offset and the same size in both cases. The reference counting for the ringbuffer and the auxiliary buffer depends on this being correct. Though perf does not prevent that a related mapping is split via mmap(2), munmap(2) or mremap(2). A split of a VMA results in perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() calls are not longer fulfilling the offset and size checks. This leads to reference count leaks. As perf already has the requirement for subsequent mappings to match the initial mapping, the obvious consequence is that VMA splits, caused by resizing of a mapping or partial unmapping, have to be prevented. Implement the vm_operations_struct::may_split() callback and return unconditionally -EINVAL. That ensures that the mapping offsets and sizes cannot be changed after the fact. Remapping to a different fixed address with the same size is still possible as it takes the references for the new mapping and drops those of the old mapping. CVE-2025-38563 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38563.html CVE-2025-38563 https://bugzilla.suse.com/1248306 SUSE Bug 1248306 https://bugzilla.suse.com/1248307 SUSE Bug 1248307 In the Linux kernel, the following vulnerability has been resolved: perf/core: Exit early on perf_mmap() fail When perf_mmap() fails to allocate a buffer, it still invokes the event_mapped() callback of the related event. On X86 this might increase the perf_rdpmc_allowed reference counter. But nothing undoes this as perf_mmap_close() is never called in this case, which causes another reference count leak. Return early on failure to prevent that. CVE-2025-38565 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38565.html CVE-2025-38565 https://bugzilla.suse.com/1248377 SUSE Bug 1248377 In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix handling of server side tls alerts Scott Mayhew discovered a security exploit in NFS over TLS in tls_alert_recv() due to its assumption it can read data from the msg iterator's kvec.. kTLS implementation splits TLS non-data record payload between the control message buffer (which includes the type such as TLS aler or TLS cipher change) and the rest of the payload (say TLS alert's level/description) which goes into the msg payload buffer. This patch proposes to rework how control messages are setup and used by sock_recvmsg(). If no control message structure is setup, kTLS layer will read and process TLS data record types. As soon as it encounters a TLS control message, it would return an error. At that point, NFS can setup a kvec backed msg buffer and read in the control message such as a TLS alert. Msg iterator can advance the kvec pointer as a part of the copy process thus we need to revert the iterator before calling into the tls_alert_recv. CVE-2025-38566 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38566.html CVE-2025-38566 https://bugzilla.suse.com/1248374 SUSE Bug 1248374 https://bugzilla.suse.com/1248376 SUSE Bug 1248376 In the Linux kernel, the following vulnerability has been resolved: net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing TCA_MQPRIO_TC_ENTRY_INDEX is validated using NLA_POLICY_MAX(NLA_U32, TC_QOPT_MAX_QUEUE), which allows the value TC_QOPT_MAX_QUEUE (16). This leads to a 4-byte out-of-bounds stack write in the fp[] array, which only has room for 16 elements (0–15). Fix this by changing the policy to allow only up to TC_QOPT_MAX_QUEUE - 1. CVE-2025-38568 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38568.html CVE-2025-38568 https://bugzilla.suse.com/1248386 SUSE Bug 1248386 In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix client side handling of tls alerts A security exploit was discovered in NFS over TLS in tls_alert_recv due to its assumption that there is valid data in the msghdr's iterator's kvec. Instead, this patch proposes the rework how control messages are setup and used by sock_recvmsg(). If no control message structure is setup, kTLS layer will read and process TLS data record types. As soon as it encounters a TLS control message, it would return an error. At that point, NFS can setup a kvec backed control buffer and read in the control message such as a TLS alert. Scott found that a msg iterator can advance the kvec pointer as a part of the copy process thus we need to revert the iterator before calling into the tls_alert_recv. CVE-2025-38571 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38571.html CVE-2025-38571 https://bugzilla.suse.com/1248401 SUSE Bug 1248401 https://bugzilla.suse.com/1248402 SUSE Bug 1248402 In the Linux kernel, the following vulnerability has been resolved: ipv6: reject malicious packets in ipv6_gso_segment() syzbot was able to craft a packet with very long IPv6 extension headers leading to an overflow of skb->transport_header. This 16bit field has a limited range. Add skb_reset_transport_header_careful() helper and use it from ipv6_gso_segment() WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 skb_reset_transport_header include/linux/skbuff.h:3032 [inline] WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151 Modules linked in: CPU: 0 UID: 0 PID: 5871 Comm: syz-executor211 Not tainted 6.16.0-rc6-syzkaller-g7abc678e3084 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:skb_reset_transport_header include/linux/skbuff.h:3032 [inline] RIP: 0010:ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151 Call Trace: <TASK> skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53 nsh_gso_segment+0x54a/0xe10 net/nsh/nsh.c:110 skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53 __skb_gso_segment+0x342/0x510 net/core/gso.c:124 skb_gso_segment include/net/gso.h:83 [inline] validate_xmit_skb+0x857/0x11b0 net/core/dev.c:3950 validate_xmit_skb_list+0x84/0x120 net/core/dev.c:4000 sch_direct_xmit+0xd3/0x4b0 net/sched/sch_generic.c:329 __dev_xmit_skb net/core/dev.c:4102 [inline] __dev_queue_xmit+0x17b6/0x3a70 net/core/dev.c:4679 CVE-2025-38572 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38572.html CVE-2025-38572 https://bugzilla.suse.com/1248399 SUSE Bug 1248399 https://bugzilla.suse.com/1248400 SUSE Bug 1248400 In the Linux kernel, the following vulnerability has been resolved: powerpc/eeh: Make EEH driver device hotplug safe Multiple race conditions existed between the PCIe hotplug driver and the EEH driver, leading to a variety of kernel oopses of the same general nature: <pcie device unplug> <eeh driver trigger> <hotplug removal trigger> <pcie tree reconfiguration> <eeh recovery next step> <oops in EEH driver bus iteration loop> A second class of oops is also seen when the underlying bus disappears during device recovery. Refactor the EEH module to be PCI rescan and remove safe. Also clean up a few minor formatting / readability issues. CVE-2025-38576 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38576.html CVE-2025-38576 https://bugzilla.suse.com/1248354 SUSE Bug 1248354 In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix crash when rebind ccp device for ccp.ko When CONFIG_CRYPTO_DEV_CCP_DEBUGFS is enabled, rebinding the ccp device causes the following crash: $ echo '0000:0a:00.2' > /sys/bus/pci/drivers/ccp/unbind $ echo '0000:0a:00.2' > /sys/bus/pci/drivers/ccp/bind [ 204.976930] BUG: kernel NULL pointer dereference, address: 0000000000000098 [ 204.978026] #PF: supervisor write access in kernel mode [ 204.979126] #PF: error_code(0x0002) - not-present page [ 204.980226] PGD 0 P4D 0 [ 204.981317] Oops: Oops: 0002 [#1] SMP NOPTI ... [ 204.997852] Call Trace: [ 204.999074] <TASK> [ 205.000297] start_creating+0x9f/0x1c0 [ 205.001533] debugfs_create_dir+0x1f/0x170 [ 205.002769] ? srso_return_thunk+0x5/0x5f [ 205.004000] ccp5_debugfs_setup+0x87/0x170 [ccp] [ 205.005241] ccp5_init+0x8b2/0x960 [ccp] [ 205.006469] ccp_dev_init+0xd4/0x150 [ccp] [ 205.007709] sp_init+0x5f/0x80 [ccp] [ 205.008942] sp_pci_probe+0x283/0x2e0 [ccp] [ 205.010165] ? srso_return_thunk+0x5/0x5f [ 205.011376] local_pci_probe+0x4f/0xb0 [ 205.012584] pci_device_probe+0xdb/0x230 [ 205.013810] really_probe+0xed/0x380 [ 205.015024] __driver_probe_device+0x7e/0x160 [ 205.016240] device_driver_attach+0x2f/0x60 [ 205.017457] bind_store+0x7c/0xb0 [ 205.018663] drv_attr_store+0x28/0x40 [ 205.019868] sysfs_kf_write+0x5f/0x70 [ 205.021065] kernfs_fop_write_iter+0x145/0x1d0 [ 205.022267] vfs_write+0x308/0x440 [ 205.023453] ksys_write+0x6d/0xe0 [ 205.024616] __x64_sys_write+0x1e/0x30 [ 205.025778] x64_sys_call+0x16ba/0x2150 [ 205.026942] do_syscall_64+0x56/0x1e0 [ 205.028108] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 205.029276] RIP: 0033:0x7fbc36f10104 [ 205.030420] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 e1 08 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5 This patch sets ccp_debugfs_dir to NULL after destroying it in ccp5_debugfs_destroy, allowing the directory dentry to be recreated when rebinding the ccp device. Tested on AMD Ryzen 7 1700X. CVE-2025-38581 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38581.html CVE-2025-38581 https://bugzilla.suse.com/1248345 SUSE Bug 1248345 In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix double destruction of rsv_qp rsv_qp may be double destroyed in error flow, first in free_mr_init(), and then in hns_roce_exit(). Fix it by moving the free_mr_init() call into hns_roce_v2_init(). list_del corruption, ffff589732eb9b50->next is LIST_POISON1 (dead000000000100) WARNING: CPU: 8 PID: 1047115 at lib/list_debug.c:53 __list_del_entry_valid+0x148/0x240 ... Call trace: __list_del_entry_valid+0x148/0x240 hns_roce_qp_remove+0x4c/0x3f0 [hns_roce_hw_v2] hns_roce_v2_destroy_qp_common+0x1dc/0x5f4 [hns_roce_hw_v2] hns_roce_v2_destroy_qp+0x22c/0x46c [hns_roce_hw_v2] free_mr_exit+0x6c/0x120 [hns_roce_hw_v2] hns_roce_v2_exit+0x170/0x200 [hns_roce_hw_v2] hns_roce_exit+0x118/0x350 [hns_roce_hw_v2] __hns_roce_hw_v2_init_instance+0x1c8/0x304 [hns_roce_hw_v2] hns_roce_hw_v2_reset_notify_init+0x170/0x21c [hns_roce_hw_v2] hns_roce_hw_v2_reset_notify+0x6c/0x190 [hns_roce_hw_v2] hclge_notify_roce_client+0x6c/0x160 [hclge] hclge_reset_rebuild+0x150/0x5c0 [hclge] hclge_reset+0x10c/0x140 [hclge] hclge_reset_subtask+0x80/0x104 [hclge] hclge_reset_service_task+0x168/0x3ac [hclge] hclge_service_task+0x50/0x100 [hclge] process_one_work+0x250/0x9a0 worker_thread+0x324/0x990 kthread+0x190/0x210 ret_from_fork+0x10/0x18 CVE-2025-38582 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38582.html CVE-2025-38582 https://bugzilla.suse.com/1248349 SUSE Bug 1248349 In the Linux kernel, the following vulnerability has been resolved: clk: xilinx: vcu: unregister pll_post only if registered correctly If registration of pll_post is failed, it will be set to NULL or ERR, unregistering same will fail with following call trace: Unable to handle kernel NULL pointer dereference at virtual address 008 pc : clk_hw_unregister+0xc/0x20 lr : clk_hw_unregister_fixed_factor+0x18/0x30 sp : ffff800011923850 ... Call trace: clk_hw_unregister+0xc/0x20 clk_hw_unregister_fixed_factor+0x18/0x30 xvcu_unregister_clock_provider+0xcc/0xf4 [xlnx_vcu] xvcu_probe+0x2bc/0x53c [xlnx_vcu] CVE-2025-38583 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38583.html CVE-2025-38583 https://bugzilla.suse.com/1248350 SUSE Bug 1248350 In the Linux kernel, the following vulnerability has been resolved: staging: media: atomisp: Fix stack buffer overflow in gmin_get_var_int() When gmin_get_config_var() calls efi.get_variable() and the EFI variable is larger than the expected buffer size, two behaviors combine to create a stack buffer overflow: 1. gmin_get_config_var() does not return the proper error code when efi.get_variable() fails. It returns the stale 'ret' value from earlier operations instead of indicating the EFI failure. 2. When efi.get_variable() returns EFI_BUFFER_TOO_SMALL, it updates *out_len to the required buffer size but writes no data to the output buffer. However, due to bug #1, gmin_get_var_int() believes the call succeeded. The caller gmin_get_var_int() then performs: - Allocates val[CFG_VAR_NAME_MAX + 1] (65 bytes) on stack - Calls gmin_get_config_var(dev, is_gmin, var, val, &len) with len=64 - If EFI variable is >64 bytes, efi.get_variable() sets len=required_size - Due to bug #1, thinks call succeeded with len=required_size - Executes val[len] = 0, writing past end of 65-byte stack buffer This creates a stack buffer overflow when EFI variables are larger than 64 bytes. Since EFI variables can be controlled by firmware or system configuration, this could potentially be exploited for code execution. Fix the bug by returning proper error codes from gmin_get_config_var() based on EFI status instead of stale 'ret' value. The gmin_get_var_int() function is called during device initialization for camera sensor configuration on Intel Bay Trail and Cherry Trail platforms using the atomisp camera stack. CVE-2025-38585 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38585.html CVE-2025-38585 https://bugzilla.suse.com/1248355 SUSE Bug 1248355 https://bugzilla.suse.com/1248671 SUSE Bug 1248671 In the Linux kernel, the following vulnerability has been resolved: ipv6: fix possible infinite loop in fib6_info_uses_dev() fib6_info_uses_dev() seems to rely on RCU without an explicit protection. Like the prior fix in rt6_nlmsg_size(), we need to make sure fib6_del_route() or fib6_add_rt2node() have not removed the anchor from the list, or we risk an infinite loop. CVE-2025-38587 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38587.html CVE-2025-38587 https://bugzilla.suse.com/1248361 SUSE Bug 1248361 In the Linux kernel, the following vulnerability has been resolved: ipv6: prevent infinite loop in rt6_nlmsg_size() While testing prior patch, I was able to trigger an infinite loop in rt6_nlmsg_size() in the following place: list_for_each_entry_rcu(sibling, &f6i->fib6_siblings, fib6_siblings) { rt6_nh_nlmsg_size(sibling->fib6_nh, &nexthop_len); } This is because fib6_del_route() and fib6_add_rt2node() uses list_del_rcu(), which can confuse rcu readers, because they might no longer see the head of the list. Restart the loop if f6i->fib6_nsiblings is zero. CVE-2025-38588 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38588.html CVE-2025-38588 https://bugzilla.suse.com/1248368 SUSE Bug 1248368 https://bugzilla.suse.com/1249241 SUSE Bug 1249241 In the Linux kernel, the following vulnerability has been resolved: bpf: Reject narrower access to pointer ctx fields The following BPF program, simplified from a syzkaller repro, causes a kernel warning: r0 = *(u8 *)(r1 + 169); exit; With pointer field sk being at offset 168 in __sk_buff. This access is detected as a narrower read in bpf_skb_is_valid_access because it doesn't match offsetof(struct __sk_buff, sk). It is therefore allowed and later proceeds to bpf_convert_ctx_access. Note that for the "is_narrower_load" case in the convert_ctx_accesses(), the insn->off is aligned, so the cnt may not be 0 because it matches the offsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However, the target_size stays 0 and the verifier errors with a kernel warning: verifier bug: error during ctx access conversion(1) This patch fixes that to return a proper "invalid bpf_context access off=X size=Y" error on the load instruction. The same issue affects multiple other fields in context structures that allow narrow access. Some other non-affected fields (for sk_msg, sk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for consistency. Note this syzkaller crash was reported in the "Closes" link below, which used to be about a different bug, fixed in commit fce7bd8e385a ("bpf/verifier: Handle BPF_LOAD_ACQ instructions in insn_def_regno()"). Because syzbot somehow confused the two bugs, the new crash and repro didn't get reported to the mailing list. CVE-2025-38591 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38591.html CVE-2025-38591 https://bugzilla.suse.com/1248363 SUSE Bug 1248363 In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: clear initialized flag for deinit-ed srng lists In a number of cases we see kernel panics on resume due to ath11k kernel page fault, which happens under the following circumstances: 1) First ath11k_hal_dump_srng_stats() call Last interrupt received for each group: ath11k_pci 0000:01:00.0: group_id 0 22511ms before ath11k_pci 0000:01:00.0: group_id 1 14440788ms before [..] ath11k_pci 0000:01:00.0: failed to receive control response completion, polling.. ath11k_pci 0000:01:00.0: Service connect timeout ath11k_pci 0000:01:00.0: failed to connect to HTT: -110 ath11k_pci 0000:01:00.0: failed to start core: -110 ath11k_pci 0000:01:00.0: firmware crashed: MHI_CB_EE_RDDM ath11k_pci 0000:01:00.0: already resetting count 2 ath11k_pci 0000:01:00.0: failed to wait wlan mode request (mode 4): -110 ath11k_pci 0000:01:00.0: qmi failed to send wlan mode off: -110 ath11k_pci 0000:01:00.0: failed to reconfigure driver on crash recovery [..] 2) At this point reconfiguration fails (we have 2 resets) and ath11k_core_reconfigure_on_crash() calls ath11k_hal_srng_deinit() which destroys srng lists. However, it does not reset per-list ->initialized flag. 3) Second ath11k_hal_dump_srng_stats() call sees stale ->initialized flag and attempts to dump srng stats: Last interrupt received for each group: ath11k_pci 0000:01:00.0: group_id 0 66785ms before ath11k_pci 0000:01:00.0: group_id 1 14485062ms before ath11k_pci 0000:01:00.0: group_id 2 14485062ms before ath11k_pci 0000:01:00.0: group_id 3 14485062ms before ath11k_pci 0000:01:00.0: group_id 4 14780845ms before ath11k_pci 0000:01:00.0: group_id 5 14780845ms before ath11k_pci 0000:01:00.0: group_id 6 14485062ms before ath11k_pci 0000:01:00.0: group_id 7 66814ms before ath11k_pci 0000:01:00.0: group_id 8 68997ms before ath11k_pci 0000:01:00.0: group_id 9 67588ms before ath11k_pci 0000:01:00.0: group_id 10 69511ms before BUG: unable to handle page fault for address: ffffa007404eb010 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 100000067 P4D 100000067 PUD 10022d067 PMD 100b01067 PTE 0 Oops: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:ath11k_hal_dump_srng_stats+0x2b4/0x3b0 [ath11k] Call Trace: <TASK> ? __die_body+0xae/0xb0 ? page_fault_oops+0x381/0x3e0 ? exc_page_fault+0x69/0xa0 ? asm_exc_page_fault+0x22/0x30 ? ath11k_hal_dump_srng_stats+0x2b4/0x3b0 [ath11k (HASH:6cea 4)] ath11k_qmi_driver_event_work+0xbd/0x1050 [ath11k (HASH:6cea 4)] worker_thread+0x389/0x930 kthread+0x149/0x170 Clear per-list ->initialized flag in ath11k_hal_srng_deinit(). CVE-2025-38601 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38601.html CVE-2025-38601 https://bugzilla.suse.com/1248340 SUSE Bug 1248340 In the Linux kernel, the following vulnerability has been resolved: iwlwifi: Add missing check for alloc_ordered_workqueue Add check for the return value of alloc_ordered_workqueue since it may return NULL pointer. CVE-2025-38602 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38602.html CVE-2025-38602 https://bugzilla.suse.com/1248341 SUSE Bug 1248341 In the Linux kernel, the following vulnerability has been resolved: wifi: rtl818x: Kill URBs before clearing tx status queue In rtl8187_stop() move the call of usb_kill_anchored_urbs() before clearing b_tx_status.queue. This change prevents callbacks from using already freed skb due to anchor was not killed before freeing such skb. BUG: kernel NULL pointer dereference, address: 0000000000000080 #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: 7 UID: 0 PID: 0 Comm: swapper/7 Not tainted 6.15.0 #8 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 RIP: 0010:ieee80211_tx_status_irqsafe+0x21/0xc0 [mac80211] Call Trace: <IRQ> rtl8187_tx_cb+0x116/0x150 [rtl8187] __usb_hcd_giveback_urb+0x9d/0x120 usb_giveback_urb_bh+0xbb/0x140 process_one_work+0x19b/0x3c0 bh_worker+0x1a7/0x210 tasklet_action+0x10/0x30 handle_softirqs+0xf0/0x340 __irq_exit_rcu+0xcd/0xf0 common_interrupt+0x85/0xa0 </IRQ> Tested on RTL8187BvE device. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2025-38604 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38604.html CVE-2025-38604 https://bugzilla.suse.com/1248333 SUSE Bug 1248333 In the Linux kernel, the following vulnerability has been resolved: bpf, ktls: Fix data corruption when using bpf_msg_pop_data() in ktls When sending plaintext data, we initially calculated the corresponding ciphertext length. However, if we later reduced the plaintext data length via socket policy, we failed to recalculate the ciphertext length. This results in transmitting buffers containing uninitialized data during ciphertext transmission. This causes uninitialized bytes to be appended after a complete "Application Data" packet, leading to errors on the receiving end when parsing TLS record. CVE-2025-38608 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38608.html CVE-2025-38608 https://bugzilla.suse.com/1248338 SUSE Bug 1248338 https://bugzilla.suse.com/1248670 SUSE Bug 1248670 In the Linux kernel, the following vulnerability has been resolved: PM / devfreq: Check governor before using governor->name Commit 96ffcdf239de ("PM / devfreq: Remove redundant governor_name from struct devfreq") removes governor_name and uses governor->name to replace it. But devfreq->governor may be NULL and directly using devfreq->governor->name may cause null pointer exception. Move the check of governor to before using governor->name. CVE-2025-38609 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38609.html CVE-2025-38609 https://bugzilla.suse.com/1248337 SUSE Bug 1248337 In the Linux kernel, the following vulnerability has been resolved: powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() The get_pd_power_uw() function can crash with a NULL pointer dereference when em_cpu_get() returns NULL. This occurs when a CPU becomes impossible during runtime, causing get_cpu_device() to return NULL, which propagates through em_cpu_get() and leads to a crash when em_span_cpus() dereferences the NULL pointer. Add a NULL check after em_cpu_get() and return 0 if unavailable, matching the existing fallback behavior in __dtpm_cpu_setup(). [ rjw: Drop an excess empty code line ] CVE-2025-38610 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38610.html CVE-2025-38610 https://bugzilla.suse.com/1248395 SUSE Bug 1248395 In the Linux kernel, the following vulnerability has been resolved: staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() In the error paths after fb_info structure is successfully allocated, the memory allocated in fb_deferred_io_init() for info->pagerefs is not freed. Fix that by adding the cleanup function on the error path. CVE-2025-38612 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38612.html CVE-2025-38612 https://bugzilla.suse.com/1248390 SUSE Bug 1248390 In the Linux kernel, the following vulnerability has been resolved: net/packet: fix a race in packet_set_ring() and packet_notifier() When packet_set_ring() releases po->bind_lock, another thread can run packet_notifier() and process an NETDEV_UP event. This race and the fix are both similar to that of commit 15fe076edea7 ("net/packet: fix a race in packet_bind() and packet_notifier()"). There too the packet_notifier NETDEV_UP event managed to run while a po->bind_lock critical section had to be temporarily released. And the fix was similarly to temporarily set po->num to zero to keep the socket unhooked until the lock is retaken. The po->bind_lock in packet_set_ring and packet_notifier precede the introduction of git history. CVE-2025-38617 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38617.html CVE-2025-38617 https://bugzilla.suse.com/1248621 SUSE Bug 1248621 https://bugzilla.suse.com/1249208 SUSE Bug 1249208 In the Linux kernel, the following vulnerability has been resolved: vsock: Do not allow binding to VMADDR_PORT_ANY It is possible for a vsock to autobind to VMADDR_PORT_ANY. This can cause a use-after-free when a connection is made to the bound socket. The socket returned by accept() also has port VMADDR_PORT_ANY but is not on the list of unbound sockets. Binding it will result in an extra refcount decrement similar to the one fixed in fcdd2242c023 (vsock: Keep the binding until socket destruction). Modify the check in __vsock_bind_connectible() to also prevent binding to VMADDR_PORT_ANY. CVE-2025-38618 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38618.html CVE-2025-38618 https://bugzilla.suse.com/1248511 SUSE Bug 1248511 https://bugzilla.suse.com/1249207 SUSE Bug 1249207 In the Linux kernel, the following vulnerability has been resolved: md: make rdev_addable usable for rcu mode Our testcase trigger panic: BUG: kernel NULL pointer dereference, address: 00000000000000e0 ... Oops: Oops: 0000 [#1] SMP NOPTI CPU: 2 UID: 0 PID: 85 Comm: kworker/2:1 Not tainted 6.16.0+ #94 PREEMPT(none) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 Workqueue: md_misc md_start_sync RIP: 0010:rdev_addable+0x4d/0xf0 ... Call Trace: <TASK> md_start_sync+0x329/0x480 process_one_work+0x226/0x6d0 worker_thread+0x19e/0x340 kthread+0x10f/0x250 ret_from_fork+0x14d/0x180 ret_from_fork_asm+0x1a/0x30 </TASK> Modules linked in: raid10 CR2: 00000000000000e0 ---[ end trace 0000000000000000 ]--- RIP: 0010:rdev_addable+0x4d/0xf0 md_spares_need_change in md_start_sync will call rdev_addable which protected by rcu_read_lock/rcu_read_unlock. This rcu context will help protect rdev won't be released, but rdev->mddev will be set to NULL before we call synchronize_rcu in md_kick_rdev_from_array. Fix this by using READ_ONCE and check does rdev->mddev still alive. CVE-2025-38621 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38621.html CVE-2025-38621 https://bugzilla.suse.com/1248609 SUSE Bug 1248609 In the Linux kernel, the following vulnerability has been resolved: PCI: pnv_php: Clean up allocated IRQs on unplug When the root of a nested PCIe bridge configuration is unplugged, the pnv_php driver leaked the allocated IRQ resources for the child bridges' hotplug event notifications, resulting in a panic. Fix this by walking all child buses and deallocating all its IRQ resources before calling pci_hp_remove_devices(). Also modify the lifetime of the workqueue at struct pnv_php_slot::wq so that it is only destroyed in pnv_php_free_slot(), instead of pnv_php_disable_irq(). This is required since pnv_php_disable_irq() will now be called by workers triggered by hot unplug interrupts, so the workqueue needs to stay allocated. The abridged kernel panic that occurs without this patch is as follows: WARNING: CPU: 0 PID: 687 at kernel/irq/msi.c:292 msi_device_data_release+0x6c/0x9c CPU: 0 UID: 0 PID: 687 Comm: bash Not tainted 6.14.0-rc5+ #2 Call Trace: msi_device_data_release+0x34/0x9c (unreliable) release_nodes+0x64/0x13c devres_release_all+0xc0/0x140 device_del+0x2d4/0x46c pci_destroy_dev+0x5c/0x194 pci_hp_remove_devices+0x90/0x128 pci_hp_remove_devices+0x44/0x128 pnv_php_disable_slot+0x54/0xd4 power_write_file+0xf8/0x18c pci_slot_attr_store+0x40/0x5c sysfs_kf_write+0x64/0x78 kernfs_fop_write_iter+0x1b0/0x290 vfs_write+0x3bc/0x50c ksys_write+0x84/0x140 system_call_exception+0x124/0x230 system_call_vectored_common+0x15c/0x2ec [bhelgaas: tidy comments] CVE-2025-38624 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38624.html CVE-2025-38624 https://bugzilla.suse.com/1248617 SUSE Bug 1248617 In the Linux kernel, the following vulnerability has been resolved: fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref fb_add_videomode() can fail with -ENOMEM when its internal kmalloc() cannot allocate a struct fb_modelist. If that happens, the modelist stays empty but the driver continues to register. Add a check for its return value to prevent poteintial null-ptr-deref, which is similar to the commit 17186f1f90d3 ("fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var"). CVE-2025-38630 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38630.html CVE-2025-38630 https://bugzilla.suse.com/1248575 SUSE Bug 1248575 In the Linux kernel, the following vulnerability has been resolved: pinmux: fix race causing mux_owner NULL with active mux_usecount commit 5a3e85c3c397 ("pinmux: Use sequential access to access desc->pinmux data") tried to address the issue when two client of the same gpio calls pinctrl_select_state() for the same functionality, was resulting in NULL pointer issue while accessing desc->mux_owner. However, issue was not completely fixed due to the way it was handled and it can still result in the same NULL pointer. The issue occurs due to the following interleaving: cpu0 (process A) cpu1 (process B) pin_request() { pin_free() { mutex_lock() desc->mux_usecount--; //becomes 0 .. mutex_unlock() mutex_lock(desc->mux) desc->mux_usecount++; // becomes 1 desc->mux_owner = owner; mutex_unlock(desc->mux) mutex_lock(desc->mux) desc->mux_owner = NULL; mutex_unlock(desc->mux) This sequence leads to a state where the pin appears to be in use (`mux_usecount == 1`) but has no owner (`mux_owner == NULL`), which can cause NULL pointer on next pin_request on the same pin. Ensure that updates to mux_usecount and mux_owner are performed atomically under the same lock. Only clear mux_owner when mux_usecount reaches zero and no new owner has been assigned. CVE-2025-38632 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38632.html CVE-2025-38632 https://bugzilla.suse.com/1248669 SUSE Bug 1248669 In the Linux kernel, the following vulnerability has been resolved: power: supply: cpcap-charger: Fix null check for power_supply_get_by_name In the cpcap_usb_detect() function, the power_supply_get_by_name() function may return `NULL` instead of an error pointer. To prevent potential null pointer dereferences, Added a null check. CVE-2025-38634 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38634.html CVE-2025-38634 https://bugzilla.suse.com/1248666 SUSE Bug 1248666 In the Linux kernel, the following vulnerability has been resolved: clk: davinci: Add NULL check in davinci_lpsc_clk_register() devm_kasprintf() returns NULL when memory allocation fails. Currently, davinci_lpsc_clk_register() does not check for this case, which results in a NULL pointer dereference. Add NULL check after devm_kasprintf() to prevent this issue and ensuring no resources are left allocated. CVE-2025-38635 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38635.html CVE-2025-38635 https://bugzilla.suse.com/1248573 SUSE Bug 1248573 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: reject TDLS operations when station is not associated syzbot triggered a WARN in ieee80211_tdls_oper() by sending NL80211_TDLS_ENABLE_LINK immediately after NL80211_CMD_CONNECT, before association completed and without prior TDLS setup. This left internal state like sdata->u.mgd.tdls_peer uninitialized, leading to a WARN_ON() in code paths that assumed it was valid. Reject the operation early if not in station mode or not associated. CVE-2025-38644 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38644.html CVE-2025-38644 https://bugzilla.suse.com/1248748 SUSE Bug 1248748 https://bugzilla.suse.com/1248749 SUSE Bug 1248749 In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band With a quite rare chance, RX report might be problematic to make SW think a packet is received on 6 GHz band even if the chip does not support 6 GHz band actually. Since SW won't initialize stuffs for unsupported bands, NULL dereference will happen then in the sequence, rtw89_vif_rx_stats_iter() -> rtw89_core_cancel_6ghz_probe_tx(). So, add a check to avoid it. The following is a crash log for this case. BUG: kernel NULL pointer dereference, address: 0000000000000032 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 1 PID: 1907 Comm: irq/131-rtw89_p Tainted: G U 6.6.56-05896-g89f5fb0eb30b #1 (HASH:1400 4) Hardware name: Google Telith/Telith, BIOS Google_Telith.15217.747.0 11/12/2024 RIP: 0010:rtw89_vif_rx_stats_iter+0xd2/0x310 [rtw89_core] Code: 4c 89 7d c8 48 89 55 c0 49 8d 44 24 02 48 89 45 b8 45 31 ff eb 11 41 c6 45 3a 01 41 b7 01 4d 8b 6d 00 4d 39 f5 74 42 8b 43 10 <41> 33 45 32 0f b7 4b 14 66 41 33 4d 36 0f b7 c9 09 c1 74 d8 4d 85 RSP: 0018:ffff9f3080138ca0 EFLAGS: 00010246 RAX: 00000000b8bf5770 RBX: ffff91b5e8c639c0 RCX: 0000000000000011 RDX: ffff91b582de1be8 RSI: 0000000000000000 RDI: ffff91b5e8c639e6 RBP: ffff9f3080138d00 R08: 0000000000000000 R09: 0000000000000000 R10: ffff91b59de70000 R11: ffffffffc069be50 R12: ffff91b5e8c639e4 R13: 0000000000000000 R14: ffff91b5828020b8 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff91b8efa40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000032 CR3: 00000002bf838000 CR4: 0000000000750ee0 PKRU: 55555554 Call Trace: <IRQ> ? __die_body+0x68/0xb0 ? page_fault_oops+0x379/0x3e0 ? exc_page_fault+0x4f/0xa0 ? asm_exc_page_fault+0x22/0x30 ? __pfx_rtw89_vif_rx_stats_iter+0x10/0x10 [rtw89_core (HASH:1400 5)] ? rtw89_vif_rx_stats_iter+0xd2/0x310 [rtw89_core (HASH:1400 5)] __iterate_interfaces+0x59/0x110 [mac80211 (HASH:1400 6)] ? __pfx_rtw89_vif_rx_stats_iter+0x10/0x10 [rtw89_core (HASH:1400 5)] ? __pfx_rtw89_vif_rx_stats_iter+0x10/0x10 [rtw89_core (HASH:1400 5)] ieee80211_iterate_active_interfaces_atomic+0x36/0x50 [mac80211 (HASH:1400 6)] rtw89_core_rx_to_mac80211+0xfd/0x1b0 [rtw89_core (HASH:1400 5)] rtw89_core_rx+0x43a/0x980 [rtw89_core (HASH:1400 5)] CVE-2025-38646 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38646.html CVE-2025-38646 https://bugzilla.suse.com/1248577 SUSE Bug 1248577 In the Linux kernel, the following vulnerability has been resolved: hfsplus: remove mutex_lock check in hfsplus_free_extents Syzbot reported an issue in hfsplus filesystem: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 4400 at fs/hfsplus/extents.c:346 hfsplus_free_extents+0x700/0xad0 Call Trace: <TASK> hfsplus_file_truncate+0x768/0xbb0 fs/hfsplus/extents.c:606 hfsplus_write_begin+0xc2/0xd0 fs/hfsplus/inode.c:56 cont_expand_zero fs/buffer.c:2383 [inline] cont_write_begin+0x2cf/0x860 fs/buffer.c:2446 hfsplus_write_begin+0x86/0xd0 fs/hfsplus/inode.c:52 generic_cont_expand_simple+0x151/0x250 fs/buffer.c:2347 hfsplus_setattr+0x168/0x280 fs/hfsplus/inode.c:263 notify_change+0xe38/0x10f0 fs/attr.c:420 do_truncate+0x1fb/0x2e0 fs/open.c:65 do_sys_ftruncate+0x2eb/0x380 fs/open.c:193 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd To avoid deadlock, Commit 31651c607151 ("hfsplus: avoid deadlock on file truncation") unlock extree before hfsplus_free_extents(), and add check wheather extree is locked in hfsplus_free_extents(). However, when operations such as hfsplus_file_release, hfsplus_setattr, hfsplus_unlink, and hfsplus_get_block are executed concurrently in different files, it is very likely to trigger the WARN_ON, which will lead syzbot and xfstest to consider it as an abnormality. The comment above this warning also describes one of the easy triggering situations, which can easily trigger and cause xfstest&syzbot to report errors. [task A] [task B] ->hfsplus_file_release ->hfsplus_file_truncate ->hfs_find_init ->mutex_lock ->mutex_unlock ->hfsplus_write_begin ->hfsplus_get_block ->hfsplus_file_extend ->hfsplus_ext_read_extent ->hfs_find_init ->mutex_lock ->hfsplus_free_extents WARN_ON(mutex_is_locked) !!! Several threads could try to lock the shared extents tree. And warning can be triggered in one thread when another thread has locked the tree. This is the wrong behavior of the code and we need to remove the warning. CVE-2025-38650 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38650.html CVE-2025-38650 https://bugzilla.suse.com/1248746 SUSE Bug 1248746 In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() Preserve the error code if iwl_setup_deferred_work() fails. The current code returns ERR_PTR(0) (which is NULL) on this path. I believe the missing error code potentially leads to a use after free involving debugfs. CVE-2025-38656 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38656.html CVE-2025-38656 https://bugzilla.suse.com/1248643 SUSE Bug 1248643 In the Linux kernel, the following vulnerability has been resolved: nilfs2: reject invalid file types when reading inodes To prevent inodes with invalid file types from tripping through the vfs and causing malfunctions or assertion failures, add a missing sanity check when reading an inode from a block device. If the file type is not valid, treat it as a filesystem error. CVE-2025-38663 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38663.html CVE-2025-38663 https://bugzilla.suse.com/1248636 SUSE Bug 1248636 In the Linux kernel, the following vulnerability has been resolved: can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode Andrei Lalaev reported a NULL pointer deref when a CAN device is restarted from Bus Off and the driver does not implement the struct can_priv::do_set_mode callback. There are 2 code path that call struct can_priv::do_set_mode: - directly by a manual restart from the user space, via can_changelink() - delayed automatic restart after bus off (deactivated by default) To prevent the NULL pointer deference, refuse a manual restart or configure the automatic restart delay in can_changelink() and report the error via extack to user space. As an additional safety measure let can_restart() return an error if can_priv::do_set_mode is not set instead of dereferencing it unchecked. CVE-2025-38665 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38665.html CVE-2025-38665 https://bugzilla.suse.com/1248648 SUSE Bug 1248648 In the Linux kernel, the following vulnerability has been resolved: arm64/entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack() `cpu_switch_to()` and `call_on_irq_stack()` manipulate SP to change to different stacks along with the Shadow Call Stack if it is enabled. Those two stack changes cannot be done atomically and both functions can be interrupted by SErrors or Debug Exceptions which, though unlikely, is very much broken : if interrupted, we can end up with mismatched stacks and Shadow Call Stack leading to clobbered stacks. In `cpu_switch_to()`, it can happen when SP_EL0 points to the new task, but x18 stills points to the old task's SCS. When the interrupt handler tries to save the task's SCS pointer, it will save the old task SCS pointer (x18) into the new task struct (pointed to by SP_EL0), clobbering it. In `call_on_irq_stack()`, it can happen when switching from the task stack to the IRQ stack and when switching back. In both cases, we can be interrupted when the SCS pointer points to the IRQ SCS, but SP points to the task stack. The nested interrupt handler pushes its return addresses on the IRQ SCS. It then detects that SP points to the task stack, calls `call_on_irq_stack()` and clobbers the task SCS pointer with the IRQ SCS pointer, which it will also use ! This leads to tasks returning to addresses on the wrong SCS, or even on the IRQ SCS, triggering kernel panics via CONFIG_VMAP_STACK or FPAC if enabled. This is possible on a default config, but unlikely. However, when enabling CONFIG_ARM64_PSEUDO_NMI, DAIF is unmasked and instead the GIC is responsible for filtering what interrupts the CPU should receive based on priority. Given the goal of emulating NMIs, pseudo-NMIs can be received by the CPU even in `cpu_switch_to()` and `call_on_irq_stack()`, possibly *very* frequently depending on the system configuration and workload, leading to unpredictable kernel panics. Completely mask DAIF in `cpu_switch_to()` and restore it when returning. Do the same in `call_on_irq_stack()`, but restore and mask around the branch. Mask DAIF even if CONFIG_SHADOW_CALL_STACK is not enabled for consistency of behaviour between all configurations. Introduce and use an assembly macro for saving and masking DAIF, as the existing one saves but only masks IF. CVE-2025-38670 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38670.html CVE-2025-38670 https://bugzilla.suse.com/1248655 SUSE Bug 1248655 In the Linux kernel, the following vulnerability has been resolved: i2c: qup: jump out of the loop in case of timeout Original logic only sets the return value but doesn't jump out of the loop if the bus is kept active by a client. This is not expected. A malicious or buggy i2c client can hang the kernel in this case and should be avoided. This is observed during a long time test with a PCA953x GPIO extender. Fix it by changing the logic to not only sets the return value, but also jumps out of the loop and return to the caller with -ETIMEDOUT. CVE-2025-38671 SUSE Linux Micro 6.0:kernel-default-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-default-base-6.4.0-34.1.21.11 SUSE Linux Micro 6.0:kernel-default-livepatch-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-devel-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-kvmsmall-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-macros-6.4.0-34.1 SUSE Linux Micro 6.0:kernel-source-6.4.0-34.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520653-1/ https://www.suse.com/security/cve/CVE-2025-38671.html CVE-2025-38671 https://bugzilla.suse.com/1248652 SUSE Bug 1248652