suse/kernel-source&distro=SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS

Vulnerabilities (2,830)

• CVE-2023-54046Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: crypto: essiv - Handle EBUSY correctly As it is essiv only handles the special return value of EINPROGERSS, which means that in all other cases it will free data related to the request. However, as the caller

• CVE-2023-54045Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: audit: fix possible soft lockup in __audit_inode_child() Tracefs or debugfs maybe cause hundreds to thousands of PATH records, too many PATH records maybe cause soft lockup. For example: 1. CONFIG_KASAN=y &&

• CVE-2022-50782Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug_on in __es_tree_search caused by bad quota inode We got a issue as fllows: ================================================================== kernel BUG at fs/ext4/extents_status.c:202! invalid

• CVE-2022-50781Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: amdgpu/pm: prevent array underflow in vega20_odn_edit_dpm_table() In the PP_OD_EDIT_VDDC_CURVE case the "input_index" variable is capped at 2 but not checked for negative values so it results in an out of bound

• CVE-2022-50779Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: orangefs: Fix kmemleak in orangefs_prepare_debugfs_help_string() When insert and remove the orangefs module, then debug_help_string will be leaked: unreferenced object 0xffff8881652ba000 (size 4096): com

• CVE-2022-50777Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: net: phy: xgmiitorgmii: Fix refcount leak in xgmiitorgmii_probe of_phy_find_device() return device node with refcount incremented. Call put_device() to relese it when not needed anymore.

• CVE-2022-50776Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: clk: st: Fix memory leak in st_of_quadfs_setup() If st_clk_register_quadfs_pll() fails, @lock should be freed before goto @err_exit, otherwise will cause meory leak issue, fix it.

• CVE-2022-50774Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix DMA transfer direction When CONFIG_DMA_API_DEBUG is selected, while running the crypto self test on the QAT crypto algorithms, the function add_dma_entry() reports a warning similar to the one

• CVE-2022-50773Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt I got a null-ptr-defer error report when I do the following tests on the qemu platform: make defconfig and CONFIG_PARPORT=m, CONFIG_PARPORT_PC=m,

• CVE-2022-50770Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix memory leak in ocfs2_mount_volume() There is a memory leak reported by kmemleak: unreferenced object 0xffff88810cc65e60 (size 32): comm "mount.ocfs2", pid 23753, jiffies 4302528942 (age 34735.

• CVE-2022-50769Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: mmc: mxcmmc: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, the memory that allocated in mmc_alloc_host() will be leaked and it will lead a kernel crash

• CVE-2022-50767Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: fbdev: smscufx: Fix several use-after-free bugs Several types of UAFs can occur when physically removing a USB device. Adds ufx_ops_destroy() function to .fb_destroy of fb_ops, and in this function, there is k

• CVE-2022-50763Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: crypto: marvell/octeontx - prevent integer overflows The "code_length" value comes from the firmware file. If your firmware is untrusted realistically there is probably very little you can do to protect yourse

• CVE-2022-50761Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: x86/xen: Fix memory leak in xen_init_lock_cpu() In xen_init_lock_cpu(), the @name has allocated new string by kasprintf(), if bind_ipi_to_irqhandler() fails, it should be freed, otherwise may lead to a memory l

• CVE-2022-50760Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix PCI device refcount leak in amdgpu_atrm_get_bios() As comment of pci_get_class() says, it returns a pci_device with its refcount increased and decreased the refcount for the input parameter @fro

• CVE-2022-50758Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: staging: vt6655: fix potential memory leak In function device_init_td0_ring, memory is allocated for member td_info of priv->apTD0Rings[i], with i increasing from 0. In case of allocation failure, the memory is

• CVE-2022-50757Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: media: camss: Clean up received buffers on failed start of streaming It is required to return the received buffers, if streaming can not be started. For instance media_pipeline_start() may fail with EPIPE, if a

• CVE-2022-50756Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix mempool alloc size Convert the max size to bytes to match the units of the divisor that calculates the worst-case number of PRP entries. The result is used to determine how many PRP Lists are req

• CVE-2022-50755Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: udf: Avoid double brelse() in udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace: <T

• CVE-2022-50754Dec 24, 2025
  affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

  In the Linux kernel, the following vulnerability has been resolved: apparmor: fix a memleak in multi_transaction_new() In multi_transaction_new(), the variable t is not freed or passed out on the failure of copy_from_user(t->data, buf, size), which could lead to a memleak. Fix