suse/kernel-default-base&distro=SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS

Vulnerabilities (1,350)

• CVE-2024-46813HigSep 27, 2024
  affected < 5.3.18-150300.59.182.1.150300.18.107.1fixed 5.3.18-150300.59.182.1.150300.18.107.1

  In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check link_index before accessing dc->links[] [WHY & HOW] dc->links[] has max size of MAX_LINKS and NULL is return when trying to access with out-of-bound index. This fixes 3 OVERRUN and 1 RES

• CVE-2024-46818Sep 27, 2024
  affected < 5.3.18-150300.59.182.1.150300.18.107.1fixed 5.3.18-150300.59.182.1.150300.18.107.1

  In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check gpio_id before used as array index [WHY & HOW] GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore should be checked in advance. This fixes 5 OVERRUN issues reported

• CVE-2024-46817Sep 27, 2024
  affected < 5.3.18-150300.59.182.1.150300.18.107.1fixed 5.3.18-150300.59.182.1.150300.18.107.1

  In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 [Why] Coverity reports OVERRUN warning. Should abort amdgpu_dm initialize. [How] Return failure to amdgpu_dm_init.

• CVE-2024-46816Sep 27, 2024
  affected < 5.3.18-150300.59.182.1.150300.18.107.1fixed 5.3.18-150300.59.182.1.150300.18.107.1

  In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links [Why] Coverity report OVERRUN warning. There are only max_links elements within dc->links. link count could up to AMDGPU_DM_MAX_D

• CVE-2024-46814Sep 27, 2024
  affected < 5.3.18-150300.59.182.1.150300.18.107.1fixed 5.3.18-150300.59.182.1.150300.18.107.1

  In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check msg_id before processing transcation [WHY & HOW] HDCP_MESSAGE_ID_INVALID (-1) is not a valid msg_id nor is it a valid array index, and it needs checking before used. This fixes 4 OVERRUN

• CVE-2022-48945Sep 23, 2024
  affected < 5.3.18-150300.59.179.1.150300.18.105.2fixed 5.3.18-150300.59.179.1.150300.18.105.2

  In the Linux kernel, the following vulnerability has been resolved: media: vivid: fix compose size exceed boundary syzkaller found a bug: BUG: unable to handle page fault for address: ffffc9000a3b1000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not

• CVE-2024-46774Sep 18, 2024
  affected < 5.3.18-150300.59.179.1.150300.18.105.2fixed 5.3.18-150300.59.179.1.150300.18.105.2

  In the Linux kernel, the following vulnerability has been resolved: powerpc/rtas: Prevent Spectre v1 gadget construction in sys_rtas() Smatch warns: arch/powerpc/kernel/rtas.c:1932 __do_sys_rtas() warn: potential spectre issue 'args.args' [r] (local cap) The 'nargs' and '

• CVE-2024-46695Sep 13, 2024
  affected < 5.3.18-150300.59.179.1.150300.18.105.2fixed 5.3.18-150300.59.179.1.150300.18.105.2

  In the Linux kernel, the following vulnerability has been resolved: selinux,smack: don't bypass permissions check in inode_setsecctx hook Marek Gresko reports that the root user on an NFS client is able to change the security labels on files on an NFS filesystem that is exporte

• CVE-2024-45016MedSep 11, 2024
  affected < 5.3.18-150300.59.182.1.150300.18.107.1fixed 5.3.18-150300.59.182.1.150300.18.107.1

  In the Linux kernel, the following vulnerability has been resolved: netem: fix return value if duplicate enqueue fails There is a bug in netem_enqueue() introduced by commit 5845f706388a ("net: netem: fix skb length BUG_ON in __skb_to_sgvec") that can lead to a use-after-free.

• CVE-2024-45026Sep 11, 2024
  affected < 5.3.18-150300.59.182.1.150300.18.107.1fixed 5.3.18-150300.59.182.1.150300.18.107.1

  In the Linux kernel, the following vulnerability has been resolved: s390/dasd: fix error recovery leading to data corruption on ESE devices Extent Space Efficient (ESE) or thin provisioned volumes need to be formatted on demand during usual IO processing. The dasd_ese_needs_fo

• CVE-2024-45021Sep 11, 2024
  affected < 5.3.18-150300.59.179.1.150300.18.105.2fixed 5.3.18-150300.59.179.1.150300.18.105.2

  In the Linux kernel, the following vulnerability has been resolved: memcg_write_event_control(): fix a user-triggerable oops we are *not* guaranteed that anything past the terminating NUL is mapped (let alone initialized with anything sane).

• CVE-2024-45003Sep 4, 2024
  affected < 5.3.18-150300.59.179.1.150300.18.105.2fixed 5.3.18-150300.59.179.1.150300.18.105.2

  In the Linux kernel, the following vulnerability has been resolved: vfs: Don't evict inode under the inode lru traversing context The inode reclaiming process(See function prune_icache_sb) collects all reclaimable inodes and mark them with I_FREEING flag at first, at that time,

• CVE-2024-44947Sep 2, 2024
  affected < 5.3.18-150300.59.174.1.150300.18.103.1fixed 5.3.18-150300.59.174.1.150300.18.103.1

  In the Linux kernel, the following vulnerability has been resolved: fuse: Initialize beyond-EOF page contents before setting uptodate fuse_notify_store(), unlike fuse_do_readpage(), does not enable page zeroing (because it can be used to change partial page contents). So fuse_

• CVE-2024-44946Aug 31, 2024
  affected < 5.3.18-150300.59.179.1.150300.18.105.2fixed 5.3.18-150300.59.179.1.150300.18.105.2

  In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building s

• CVE-2024-43883Aug 23, 2024
  affected < 5.3.18-150300.59.174.1.150300.18.103.1fixed 5.3.18-150300.59.174.1.150300.18.103.1

  In the Linux kernel, the following vulnerability has been resolved: usb: vhci-hcd: Do not drop references before new references are gained At a few places the driver carries stale pointers to references that can still be used. Make sure that does not happen. This strictly speak

• CVE-2022-48934Aug 22, 2024
  affected < 5.3.18-150300.59.174.1.150300.18.103.1fixed 5.3.18-150300.59.174.1.150300.18.103.1

  In the Linux kernel, the following vulnerability has been resolved: nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac() ida_simple_get() returns an id between min (0) and max (NFP_MAX_MAC_INDEX) inclusive. So NFP_MAX_MAC_INDEX (0xff) is a valid id. In order for th

• CVE-2022-48933Aug 22, 2024
  affected < 5.3.18-150300.59.174.1.150300.18.103.1fixed 5.3.18-150300.59.174.1.150300.18.103.1

  In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix memory leak during stateful obj update stateful objects can be updated from the control plane. The transaction logic allocates a temporary object for this purpose. The ->init function

• CVE-2022-48930Aug 22, 2024
  affected < 5.3.18-150300.59.174.1.150300.18.103.1fixed 5.3.18-150300.59.174.1.150300.18.103.1

  In the Linux kernel, the following vulnerability has been resolved: RDMA/ib_srp: Fix a deadlock Remove the flush_workqueue(system_long_wq) call since flushing system_long_wq is deadlock-prone and since that call is redundant with a preceding cancel_work_sync()

• CVE-2022-48928Aug 22, 2024
  affected < 5.3.18-150300.59.174.1.150300.18.103.1fixed 5.3.18-150300.59.174.1.150300.18.103.1

  In the Linux kernel, the following vulnerability has been resolved: iio: adc: men_z188_adc: Fix a resource leak in an error handling path If iio_device_register() fails, a previous ioremap() is left unbalanced. Update the error handling path and add the missing iounmap() call,

• CVE-2022-48926Aug 22, 2024
  affected < 5.3.18-150300.59.174.1.150300.18.103.1fixed 5.3.18-150300.59.174.1.150300.18.103.1

  In the Linux kernel, the following vulnerability has been resolved: usb: gadget: rndis: add spinlock for rndis response list There's no lock for rndis response list. It could cause list corruption if there're two different list_add at the same time like below. It's better to ad