VYPR

rpm package

suse/kernel-source-azure&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP7

pkg:rpm/suse/kernel-source-azure&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Public%20Cloud%2015%20SP7

Vulnerabilities (2,127)

  • CVE-2025-22109HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: ax25: Remove broken autobind Binding AX25 socket by using the autobind feature leads to memory leaks in ax25_connect() and also refcount leaks in ax25_release(). Memory leak was detected with kmemleak: =======

  • CVE-2025-22108HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Mask the bd_cnt field in the TX BD properly The bd_cnt field in the TX BD specifies the total number of BDs for the TX packet. The bd_cnt field has 5 bits and the maximum number supported is 32 with t

  • CVE-2025-22107HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: net: dsa: sja1105: fix kasan out-of-bounds warning in sja1105_table_delete_entry() There are actually 2 problems: - deleting the last element doesn't require the memmove of elements [i + 1, end) over it. Actu

  • CVE-2025-22106MedApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: vmxnet3: unregister xdp rxq info in the reset path vmxnet3 does not unregister xdp rxq info in the vmxnet3_reset_work() code path as vmxnet3_rq_destroy() is not invoked in this code path. So, we get below messa

  • CVE-2025-22105MedApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: bonding: check xdp prog when set bond mode Following operations can trigger a warning[1]: ip netns add ns1 ip netns exec ns1 ip link add bond0 type bond mode balance-rr ip netns exec ns1 ip link se

  • CVE-2025-22104HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Use kernel helpers for hex dumps Previously, when the driver was printing hex dumps, the buffer was cast to an 8 byte long and printed using string formatters. If the buffer size was not a multiple of

  • CVE-2025-22103MedApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: net: fix NULL pointer dereference in l3mdev_l3_rcv When delete l3s ipvlan: ip link del link eth0 ipvlan1 type ipvlan mode l3s This may cause a null pointer dereference: Call trace: ip_rcv_finish

  • CVE-2025-22102HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Fix kernel panic during FW release This fixes a kernel panic seen during release FW in a stress test scenario where WLAN and BT FW download occurs simultaneously, and due to a HW bug, chip

  • CVE-2025-22097HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: drm/vkms: Fix use after free and double free on init error If the driver initialization fails, the vkms_exit() function might access an uninitialized or freed default_config pointer and it might double free it.

  • CVE-2025-22095MedApr 16, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: PCI: brcmstb: Fix error path after a call to regulator_bulk_get() If the regulator_bulk_get() returns an error and no regulators are created, we need to set their number to zero. If we don't do this and the PC

  • CVE-2025-22094HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: powerpc/perf: Fix ref-counting on the PMU 'vpa_pmu' Commit 176cda0619b6 ("powerpc/perf: Add perf interface to expose vpa counters") introduced 'vpa_pmu' to expose Book3s-HV nested APIv2 provided L1<->L2 context

  • CVE-2025-22093MedApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: avoid NPD when ASIC does not support DMUB ctx->dmub_srv will de NULL if the ASIC does not support DMUB, which is tested in dm_dmub_sw_init. However, it will be dereferenced in dmub_hw_lock_mgr

  • CVE-2025-22091MedApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix page_size variable overflow Change all variables storing mlx5_umem_mkc_find_best_pgsz() result to unsigned long to support values larger than 31 and avoid overflow. For example: If we try to reg

  • CVE-2025-22090HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() If track_pfn_copy() fails, we already added the dst VMA to the maple tree. As fork() fails, we'll cleanup the maple tree, and stumble over

  • CVE-2025-22089HigApr 16, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Don't expose hw_counters outside of init net namespace Commit 467f432a521a ("RDMA/core: Split port and device counter sysfs attributes") accidentally almost exposed hw counters to non-init net namesp

  • CVE-2025-22088CriApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: RDMA/erdma: Prevent use-after-free in erdma_accept_newconn() After the erdma_cep_put(new_cep) being called, new_cep will be freed, and the following dereference will cause a UAF problem. Fix this issue.

  • CVE-2025-22086HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bu

  • CVE-2025-22085HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix use-after-free when rename device name Syzbot reported a slab-use-after-free with the following call trace: ================================================================== BUG: KASAN: slab-us

  • CVE-2025-22083HigApr 16, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint If vhost_scsi_set_endpoint is called multiple times without a vhost_scsi_clear_endpoint between them, we can hit multiple bugs found by Haor

  • CVE-2025-22080HigApr 16, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Prevent integer overflow in hdr_first_de() The "de_off" and "used" variables come from the disk so they both need to check. The problem is that on 32bit systems if they're both greater than UINT_MAX

Page 90 of 107