suse/kernel-syms&distro=SUSE Manager Server LTS 4.3

Vulnerabilities (542)

• CVE-2023-53375Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: tracing: Free error logs of tracing instances When a tracing instance is removed, the error messages that hold errors that occurred in the instance needs to be freed. The following reports a memory leak: # cd

• CVE-2023-53373Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv 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-2022-50399Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: media: atomisp: prevent integer overflow in sh_css_set_black_frame() The "height" and "width" values come from the user so the "height * width" multiplication can overflow.

• CVE-2022-50395Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: integrity: Fix memory leakage in keyring allocation error path Key restriction is allocated in integrity_init_keyring(). However, if keyring allocation failed, it is not freed, causing memory leaks.

• CVE-2022-50394Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: i2c: ismt: Fix an out-of-bounds bug in ismt_access() When the driver does not check the data from the user, the variable 'data->block[0]' may be very large to cause an out-of-bounds bug. The following log can

• CVE-2022-50392Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8183: fix refcount leak in mt8183_mt6358_ts3a227_max98357_dev_probe() The node returned by of_parse_phandle() with refcount incremented, of_node_put() needs be called when finish using it. So

• CVE-2022-50391Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix memory leak in set_mempolicy_home_node system call When encountering any vma in the range with policy other than MPOL_BIND or MPOL_PREFERRED_MANY, an error is returned without issuing a mpol_p

• CVE-2022-50389Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak In crb_acpi_add(), we get the TPM2 table to retrieve information like start method, and then assign them to the priv data, so the TPM2 table is n

• CVE-2022-50388Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: nvme: fix multipath crash caused by flush request when blktrace is enabled The flush request initialized by blk_kick_flush has NULL bio, and it may be dealt with nvme_end_req during io completion. When blktrace

• CVE-2022-50386Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix user-after-free This uses l2cap_chan_hold_unless_zero() after calling __l2cap_get_chan_blah() to prevent the following trace: Bluetooth: l2cap_core.c:static void l2cap_chan_destroy(struct

• CVE-2022-50385Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: NFS: Fix an Oops in nfs_d_automount() When mounting from a NFSv4 referral, path->dentry can end up being a negative dentry, so derive the struct nfs_server from the dentry itself instead.

• CVE-2022-50381Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: md: fix a crash in mempool_free There's a crash in mempool_free when running the lvm test shell/lvchange-rebuild-raid.sh. The reason for the crash is this: * super_written calls atomic_dec_and_test(&mddev->pen

• CVE-2022-50379Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race between quota enable and quota rescan ioctl When enabling quotas, at btrfs_quota_enable(), after committing the transaction, we change fs_info->quota_root to point to the quota root we created a

• CVE-2022-50376Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: orangefs: Fix kmemleak in orangefs_{kernel,client}_debug_init() When insert and remove the orangefs module, there are memory leaked as below: unreferenced object 0xffff88816b0cc000 (size 2048): comm "insmod"

• CVE-2022-50375Sep 18, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: tty: serial: fsl_lpuart: disable dma rx/tx use flags in lpuart_dma_shutdown lpuart_dma_shutdown tears down lpuart dma, but lpuart_flush_buffer can still occur which in turn tries to access dma apis if lpuart_dm

• CVE-2023-53368Sep 17, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: tracing: Fix race issue between cpu buffer write and swap Warning happened in rb_end_commit() at code: if (RB_WARN_ON(cpu_buffer, !local_read(&cpu_buffer->committing))) WARNING: CPU: 0 PID: 139 at kernel/tr

• CVE-2023-53365Sep 17, 2025
  affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

  In the Linux kernel, the following vulnerability has been resolved: ip6mr: Fix skb_under_panic in ip6mr_cache_report() skbuff: skb_under_panic: text:ffffffff88771f69 len:56 put:-4 head:ffff88805f86a800 data:ffff887f5f86a850 tail:0x88 end:0x2c0 dev:pim6reg ------------[ cut he

• CVE-2023-53359Sep 17, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: USB: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_look

• CVE-2023-53356Sep 17, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: usb: gadget: u_serial: Add null pointer check in gserial_suspend Consider a case where gserial_disconnect has already cleared gser->ioport. And if gserial_suspend gets called afterwards, it will lead to accessi

• CVE-2023-53352Sep 17, 2025
  affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

  In the Linux kernel, the following vulnerability has been resolved: drm/ttm: check null pointer before accessing when swapping Add a check to avoid null pointer dereference as below: [ 90.002283] general protection fault, probably for non-canonical address 0xdffffc0000000000