suse/kernel-default&distro=SUSE Linux Enterprise High Availability Extension 15 SP6

Vulnerabilities (4,170)

• CVE-2024-39471Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: add error handle to avoid out-of-bounds if the sdma_v4_0_irq_id_to_seq return -EINVAL, the process should be stop to avoid out-of-bounds read, so directly return -EINVAL.

• CVE-2024-39469Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errors The error handling in nilfs_empty_dir() when a directory folio/page read fails is incorrect, as in the old ext2 implementation, and if the f

• CVE-2024-39466Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: thermal/drivers/qcom/lmh: Check for SCM availability at probe Up until now, the necessary scm availability check has not been performed, leading to possible null pointer dereferences (which did happen for me on

• CVE-2024-39463Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: 9p: add missing locking around taking dentry fid list Fix a use-after-free on dentry's d_fsdata fid list when a thread looks up a fid through dentry while another thread unlinks it: UAF thread: refcount_t: add

• CVE-2024-39371Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: io_uring: check for non-NULL file pointer in io_file_can_poll() In earlier kernels, it was possible to trigger a NULL pointer dereference off the forced async preparation path, if no file had been assigned. The

• CVE-2024-39301Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: net/9p: fix uninit-value in p9_client_rpc() Syzbot with the help of KMSAN reported the following error: BUG: KMSAN: uninit-value in trace_9p_client_res include/trace/events/9p.h:146 [inline] BUG: KMSAN: uninit

• CVE-2024-39296Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: bonding: fix oops during rmmod "rmmod bonding" causes an oops ever since commit cc317ea3d927 ("bonding: remove redundant NULL check in debugfs function"). Here are the relevant functions being called: bonding

• CVE-2024-39276Jun 25, 2024
  affected < 6.4.0-150600.23.17.1fixed 6.4.0-150600.23.17.1

  In the Linux kernel, the following vulnerability has been resolved: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() Syzbot reports a warning as follows: ============================================ WARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cach

• CVE-2024-38661Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: s390/ap: Fix crash in AP internal function modify_bitmap() A system crash like this Failing address: 200000cb7df6f000 TEID: 200000cb7df6f403 Fault in home space mode while using kernel ASCE. AS:00000002d

• CVE-2024-38385Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: genirq/irqdesc: Prevent use-after-free in irq_find_at_or_after() irq_find_at_or_after() dereferences the interrupt descriptor which is returned by mt_find() while neither holding sparse_irq_lock nor RCU read lo

• CVE-2024-37354Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: btrfs: fix crash on racing fsync and size-extending write into prealloc We have been seeing crashes on duplicate keys in btrfs_set_item_key_safe(): BTRFS critical (device vdb): slot 4 key (450 108 8192) new

• CVE-2024-37078Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential kernel bug due to lack of writeback flag waiting Destructive writes to a block device on which nilfs2 is mounted can cause a kernel bug in the folio/page writeback start routine or writeba

• CVE-2022-48772Jun 25, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: media: lgdt3306a: Add a check against null-pointer-def The driver should check whether the client provides the platform_data. The following log reveals it: [ 29.610324] BUG: KASAN: null-ptr-deref in kmemdup

• CVE-2024-37021Jun 24, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take

• CVE-2024-36479Jun 24, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: fpga: bridge: add owner module and take its refcount The current implementation of the fpga bridge assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take t

• CVE-2024-35247Jun 24, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: fpga: region: add owner module and take its refcount The current implementation of the fpga region assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take t

• CVE-2024-39291Jun 24, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix buffer size in gfx_v9_4_3_init_ cp_compute_microcode() and rlc_microcode() The function gfx_v9_4_3_init_microcode in gfx_v9_4_3.c was generating about potential truncation of output when using t

• CVE-2024-38664Jun 24, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: drm: zynqmp_dpsub: Always register bridge We must always register the DRM bridge, since zynqmp_dp_hpd_work_func calls drm_bridge_hpd_notify, which in turn expects hpd_mutex to be initialized. We do this before

• CVE-2024-38663Jun 24, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix list corruption from resetting io stat Since commit 3b8cc6298724 ("blk-cgroup: Optimize blkcg_rstat_flush()"), each iostat instance is added to blkcg percpu list, so blkcg_reset_stats() can't re

• CVE-2024-38384Jun 24, 2024
  affected < 6.4.0-150600.23.14.2fixed 6.4.0-150600.23.14.2

  In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix list corruption from reorder of WRITE ->lqueued __blkcg_rstat_flush() can be run anytime, especially when blk_cgroup_bio_start is being executed. If WRITE of `->lqueued` is re-ordered with READ