suse/kernel-rt&distro=SUSE Linux Enterprise Micro 5.1

Vulnerabilities (1,613)

• CVE-2022-50401Sep 18, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure On error situation `clp->cl_cb_conn.cb_xprt` should not be given a reference to the xprt otherwise both client cleanup and the error handling p

• CVE-2022-50386Sep 18, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.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.3.18-150300.223.1fixed 5.3.18-150300.223.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.3.18-150300.223.1fixed 5.3.18-150300.223.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-50375Sep 18, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.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-2022-50368Sep 17, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: fix memory corruption with too many bridges Add the missing sanity check on the bridge counter to avoid corrupting data beyond the fixed-sized bridge array in case there are ever more than eight br

• CVE-2022-50367Sep 17, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: fs: fix UAF/GPF bug in nilfs_mdt_destroy In alloc_inode, inode_init_always() could return -ENOMEM if security_inode_alloc() fails, which causes inode->i_private uninitialized. Then nilfs_is_metadata_file_inode(

• CVE-2022-50359Sep 17, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: media: cx88: Fix a null-ptr-deref bug in buffer_prepare() When the driver calls cx88_risc_buffer() to prepare the buffer, the function call may fail, resulting in a empty buffer and null-ptr-deref later in buff

• CVE-2022-50355Sep 17, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: staging: vt6655: fix some erroneous memory clean-up loops In some initialization functions of this driver, memory is allocated with 'i' acting as an index variable and increasing from 0. The commit in "Fixes" i

• CVE-2023-53333Sep 16, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: dccp: copy entire header to stack buffer, not just basic one Eric Dumazet says: nf_conntrack_dccp_packet() has an unique: dh = skb_header_pointer(skb, dataoff, sizeof(_dh), &_dh);

• CVE-2023-53321Sep 16, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211_hwsim: drop short frames While technically some control frames like ACK are shorter and end after Address 1, such frames shouldn't be forwarded through wmediumd or similar userspace, so require t

• CVE-2023-53304Sep 16, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: fix overlap expiration walk The lazy gc on insert that should remove timed-out entries fails to release the other half of the interval, if any. Can be reproduced with tests/shell/tes

• CVE-2022-50344Sep 16, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: ext4: fix null-ptr-deref in ext4_write_info I caught a null-ptr-deref bug as follows: ================================================================== KASAN: null-ptr-deref in range [0x0000000000000068-0x0000

• CVE-2025-39823HigSep 16, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: KVM: x86: use array_index_nospec with indices that come from guest min and dest_id are guest-controlled indices. Using array_index_nospec() after the bounds checks clamps these values to mitigate speculative ex

• CVE-2023-53273Sep 16, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channel() assumes vmbus channel array to be allocated when called. However, in cases such as kdump/kexec, not all relids will be reset

• CVE-2023-53265Sep 16, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: ubi: ensure that VID header offset + VID header size <= alloc, size Ensure that the VID header offset + VID header size does not exceed the allocated area to avoid slab OOB. BUG: KASAN: slab-out-of-bounds in c

• CVE-2022-50330Sep 15, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: crypto: cavium - prevent integer overflow loading firmware 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

• CVE-2022-50317Sep 15, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: drm/bridge: megachips: Fix a null pointer dereference bug When removing the module we will get the following warning: [ 31.911505] i2c-core: driver [stdp2690-ge-b850v3-fw] unregistered [ 31.912484] general

• CVE-2022-50312Sep 15, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: drivers: serial: jsm: fix some leaks in probe This error path needs to unwind instead of just returning directly.

• CVE-2022-50309Sep 15, 2025
  affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1

  In the Linux kernel, the following vulnerability has been resolved: media: xilinx: vipp: Fix refcount leak in xvip_graph_dma_init of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_nod