suse/kernel-livepatch-SLE15-SP5-RT_Update_16&distro=SUSE Linux Enterprise Live Patching 15 SP5

Vulnerabilities (561)

• CVE-2024-26846Apr 17, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl a

• CVE-2024-26840Apr 17, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: cachefiles: fix memory leak in cachefiles_add_cache() The following memory leak was reported after unbinding /dev/cachefiles: ================================================================== unreferenced obj

• CVE-2024-26839Apr 17, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix a memleak in init_credit_return When dma_alloc_coherent fails to allocate dd->cr_base[i].va, init_credit_return should deallocate dd->cr_base and dd->cr_base[i] that allocated before. Or those reso

• CVE-2024-26838Apr 17, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Fix KASAN issue with tasklet KASAN testing revealed the following issue assocated with freeing an IRQ. [50006.466686] Call Trace: [50006.466691] [50006.489538] dump_stack+0x5c/0x80 [50006.4

• CVE-2024-26829Apr 17, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: media: ir_toy: fix a memleak in irtoy_tx When irtoy_command fails, buf should be freed since it is allocated by irtoy_tx, or there is a memleak.

• CVE-2024-26828Apr 17, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: cifs: fix underflow in parse_server_interfaces() In this loop, we step through the buffer and after each item we check if the size_left is greater than the minimum size we need. However, the problem is that "b

• CVE-2024-26822Apr 17, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: smb: client: set correct id, uid and cruid for multiuser automounts When uid, gid and cruid are not specified, we need to dynamically set them into the filesystem context used for automounting otherwise they'll

• CVE-2023-52643Apr 17, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: iio: core: fix memleak in iio_device_register_sysfs When iio_device_register_sysfs_group() fails, we should free iio_dev_opaque->chan_attr_group.attrs to prevent potential memleak.

• CVE-2023-52642Apr 17, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: media: rc: bpf attach/detach requires write permission Note that bpf attach/detach also requires CAP_NET_ADMIN.

• CVE-2021-47200Apr 10, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: drm/prime: Fix use after free in mmap with drm_gem_ttm_mmap drm_gem_ttm_mmap() drops a reference to the gem object on success. If the gem object's refcount == 1 on entry to drm_gem_prime_mmap(), that drop will

• CVE-2024-26801Apr 4, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Avoid potential use-after-free in hci_error_reset While handling the HCI_EV_HARDWARE_ERROR event, if the underlying BT controller is not responding, the GPIO reset mechanism would free the hci_dev an

• CVE-2024-26791Apr 4, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: btrfs: dev-replace: properly validate device names There's a syzbot report that device name buffers passed to device replace are not properly checked for string termination which could lead to a read out of bou

• CVE-2024-26788Apr 4, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: dmaengine: fsl-qdma: init irq after reg initialization Initialize the qDMA irqs after the registers are configured so that interrupts that may have been pending from a primary kernel don't get processed by the

• CVE-2024-26778Apr 3, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: fbdev: savage: Error out if pixclock equals zero The userspace program could pass any values to the driver through ioctl() interface. If the driver doesn't check the value of pixclock, it may cause divide-by-ze

• CVE-2024-26777Apr 3, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: fbdev: sis: Error out if pixclock equals zero The userspace program could pass any values to the driver through ioctl() interface. If the driver doesn't check the value of pixclock, it may cause divide-by-zero

• CVE-2024-26775Apr 3, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: aoe: avoid potential deadlock at set_capacity Move set_capacity() outside of the section procected by (&d->lock). To avoid possible interrupt unsafe locking scenario: CPU0 CPU1

• CVE-2024-26764Apr 3, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio If kiocb_set_cancel_fn() is called for I/O submitted via io_uring, the following kernel warning appears: WARNING: CPU: 3 PID: 368 at fs/aio.c:

• CVE-2024-26758Apr 3, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: md: Don't ignore suspended array in md_check_recovery() mddev_suspend() never stop sync_thread, hence it doesn't make sense to ignore suspended array in md_check_recovery(), which might cause sync_thread can't

• CVE-2024-26748Apr 3, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: usb: cdns3: fix memory double free when handle zero packet 829 if (request->complete) { 830 spin_unlock(&priv_dev->lock); 831 usb_gadget_giveback_request(&priv_ep->endpoint, 832

• CVE-2024-26742Apr 3, 2024
  affected < 1-150500.11.3.1fixed 1-150500.11.3.1

  In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Fix disable_managed_interrupts Correct blk-mq registration issue with module parameter disable_managed_interrupts enabled. When we turn off the default PCI_IRQ_AFFINITY flag, the driver needs t