suse/kernel-syms-azure&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP6

Vulnerabilities (3,769)

• CVE-2024-36922May 30, 2024
  affected < 6.4.0-150600.8.5.1fixed 6.4.0-150600.8.5.1

  In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: read txq->read_ptr under lock If we read txq->read_ptr without lock, we can read the same value twice, then obtain the lock, and reclaim from there to two different places, but crucially reclaim

• CVE-2024-36921May 30, 2024
  affected < 6.4.0-150600.8.5.1fixed 6.4.0-150600.8.5.1

  In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: guard against invalid STA ID on removal Guard against invalid station IDs in iwl_mvm_mld_rm_sta_id as that would result in out-of-bounds array accesses. This prevents issues should the drive

• CVE-2024-36920May 30, 2024
  affected < 6.4.0-150600.8.20.1fixed 6.4.0-150600.8.20.1

  In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Avoid memcpy field-spanning write WARNING When the "storcli2 show" command is executed for eHBA-9600, mpi3mr driver prints this WARNING message: memcpy: detected field-spanning write (size 128)

• CVE-2024-36919May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload The session resources are used by FW and driver when session is offloaded, once session is uploaded these resources are not used. The loc

• CVE-2024-36918May 30, 2024
  affected < 6.4.0-150600.8.5.1fixed 6.4.0-150600.8.5.1

  In the Linux kernel, the following vulnerability has been resolved: bpf: Check bloom filter map value size This patch adds a missing check to bloom filter creating, rejecting values above KMALLOC_MAX_SIZE. This brings the bloom map in line with many other map types. The lack o

• CVE-2024-36917May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: block: fix overflow in blk_ioctl_discard() There is no check for overflow of 'start + len' in blk_ioctl_discard(). Hung task occurs if submit an discard ioctl with the following param: start = 0x80000000000ff

• CVE-2024-36915May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: fix nfc_llcp_setsockopt() unsafe copies syzbot reported unsafe calls to copy_from_sockptr() [1] Use copy_safe_from_sockptr() instead. [1] BUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset

• CVE-2024-36914May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Skip on writeback when it's not applicable [WHY] dynamic memory safety error detector (KASAN) catches and generates error messages "BUG: KASAN: slab-out-of-bounds" as writeback connector does n

• CVE-2024-36913May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned

• CVE-2024-36912May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and t

• CVE-2024-36911May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: hv_netvsc: Don't free decrypted memory In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory

• CVE-2024-36910May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: uio_hv_generic: Don't free decrypted memory In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting m

• CVE-2024-36909May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Don't free ring buffers that couldn't be re-encrypted In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error i

• CVE-2024-36908May 30, 2024
  affected < 6.4.0-150600.8.23.1fixed 6.4.0-150600.8.23.1

  In the Linux kernel, the following vulnerability has been resolved: blk-iocost: do not WARN if iocg was already offlined In iocg_pay_debt(), warn is triggered if 'active_list' is empty, which is intended to confirm iocg is active when it has debt. However, warn can be triggered

• CVE-2024-36906May 30, 2024
  affected < 6.4.0-150600.8.5.1fixed 6.4.0-150600.8.5.1

  In the Linux kernel, the following vulnerability has been resolved: ARM: 9381/1: kasan: clear stale stack poison We found below OOB crash: [ 33.452494] ================================================================== [ 33.453513] BUG: KASAN: stack-out-of-bounds in refres

• CVE-2024-36903May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: ipv6: Fix potential uninit-value access in __ip6_make_skb() As it was done in commit fc1092f51567 ("ipv4: Fix uninit-value access in __ip_make_skb()") for IPv4, check FLOWI_FLAG_KNOWN_NH on fl6->flowi6_flags in

• CVE-2024-36901May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: ipv6: prevent NULL dereference in ip6_output() According to syzbot, there is a chance that ip6_dst_idev() returns NULL in ip6_output(). Most places in IPv6 stack deal with a NULL idev just fine, but not here.

• CVE-2024-36900May 30, 2024
  affected < 6.4.0-150600.8.8.1fixed 6.4.0-150600.8.8.1

  In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix kernel crash when devlink reload during initialization The devlink reload process will access the hardware resources, but the register operation is done before the hardware is initialized. So, pr

• CVE-2024-36897May 30, 2024
  affected < 6.4.0-150600.8.5.1fixed 6.4.0-150600.8.5.1

  In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Atom Integrated System Info v2_2 for DCN35 New request from KMD/VBIOS in order to support new UMA carveout model. This fixes a null dereference from accessing Ctx->dc_bios->integrated_info whil

• CVE-2024-36896May 30, 2024
  affected < 6.4.0-150600.8.5.1fixed 6.4.0-150600.8.5.1

  In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix access violation during port device removal Testing with KASAN and syzkaller revealed a bug in port.c:disable_store(): usb_hub_to_struct_hub() can return NULL if the hub that the port belongs to