VYPR

rpm package

suse/kernel-default-base&distro=SUSE Linux Enterprise Module for Basesystem 15 SP6

pkg:rpm/suse/kernel-default-base&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP6

Vulnerabilities (3,752)

  • CVE-2024-38384HigJun 24, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    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

  • CVE-2024-37021MedJun 24, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    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-36479MedJun 24, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    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-35247MedJun 24, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    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-39277HigJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: dma-mapping: benchmark: handle NUMA_NO_NODE correctly cpumask_of_node() can be called for NUMA_NO_NODE inside do_map_benchmark() resulting in the following sanitizer report: UBSAN: array-index-out-of-bounds in

  • CVE-2024-38780MedJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: dma-buf/sw-sync: don't enable IRQ from sync_print_obj() Since commit a6aa8fca4d79 ("dma-buf/sw-sync: Reduce irqsave/irqrestore from known context") by error replaced spin_unlock_irqrestore() with spin_unlock_ir

  • CVE-2024-38662MedJun 21, 2024
    affected < 6.4.0-150600.23.22.1.150600.12.8.3fixed 6.4.0-150600.23.22.1.150600.12.8.3

    In the Linux kernel, the following vulnerability has been resolved: bpf: Allow delete from sockmap/sockhash only if update is allowed We have seen an influx of syzkaller reports where a BPF program attached to a tracepoint triggers a locking rule violation by performing a map_d

  • CVE-2024-36477HigJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the maximum transfer length and the size of the transfer buffer. As su

  • CVE-2024-36288CriJun 21, 2024
    affected < 6.4.0-150600.23.22.1.150600.12.8.3fixed 6.4.0-150600.23.22.1.150600.12.8.3

    In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix loop termination condition in gss_free_in_token_pages() The in_token->pages[] array is not NULL terminated. This results in the following KASAN splat: KASAN: maybe wild-memory-access in range [0x

  • CVE-2024-34777HigJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: dma-mapping: benchmark: fix node id validation While validating node ids in map_benchmark_ioctl(), node_possible() may be provided with invalid argument outside of [0,MAX_NUMNODES-1] range leading to: BUG: KAS

  • CVE-2024-38659HigJun 21, 2024
    affected < 6.4.0-150600.23.17.1.150600.12.6.2fixed 6.4.0-150600.23.17.1.150600.12.6.2

    In the Linux kernel, the following vulnerability has been resolved: enic: Validate length of nl attributes in enic_set_vf_port enic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE is of length PORT_PROFILE_MAX and that the nl attributes IFLA_PORT_INSTANCE_UUID, IFLA

  • CVE-2024-38636MedJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: f2fs: multidev: fix to recognize valid zero block address As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below: ./check zbd/010 zbd/010 (test gap zone support wi

  • CVE-2024-38635HigJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: soundwire: cadence: fix invalid PDI offset For some reason, we add an offset to the PDI, presumably to skip the PDI0 and PDI1 which are reserved for BPT. This code is however completely wrong and leads to an o

  • CVE-2024-38634MedJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Lock port->lock when calling uart_handle_cts_change() uart_handle_cts_change() has to be called with port lock taken, Since we run it in a separate work, the lock may not be taken at the time o

  • CVE-2024-38633MedJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Update uart_driver_registered on driver removal The removal of the last MAX3100 device triggers the removal of the driver. However, code doesn't update the respective global variable and after

  • CVE-2024-38632MedJun 21, 2024
    affected < 6.4.0-150600.23.25.1.150600.12.10.2fixed 6.4.0-150600.23.25.1.150600.12.10.2

    In the Linux kernel, the following vulnerability has been resolved: vfio/pci: fix potential memory leak in vfio_intx_enable() If vfio_irq_ctx_alloc() failed will lead to 'name' memory leak.

  • CVE-2024-38630HigJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger When the cpu5wdt module is removing, the origin code uses del_timer() to de-activate the timer. If the timer handler is running, del_timer()

  • CVE-2024-38629HigJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Avoid unnecessary destruction of file_ida file_ida is allocated during cdev open and is freed accordingly during cdev release. This sequence is guaranteed by driver file operations. Therefore,

  • CVE-2024-38628HigJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: usb: gadget: u_audio: Fix race condition use of controls after free during gadget unbind. Hang on to the control IDs instead of pointers since those are correctly handled with locks.

  • CVE-2024-38627HigJun 21, 2024
    affected < 6.4.0-150600.23.14.2.150600.12.4.3fixed 6.4.0-150600.23.14.2.150600.12.4.3

    In the Linux kernel, the following vulnerability has been resolved: stm class: Fix a double free in stm_register_device() The put_device(&stm->dev) call will trigger stm_device_release() which frees "stm" so the vfree(stm) on the next line is a double free.

Page 147 of 188