VYPR

rpm package

suse/kernel-default-base&distro=SUSE Linux Enterprise Server 15 SP4-LTSS

pkg:rpm/suse/kernel-default-base&distro=SUSE%20Linux%20Enterprise%20Server%2015%20SP4-LTSS

Vulnerabilities (2,843)

  • CVE-2022-50026Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: habanalabs/gaudi: fix shift out of bounds When validating NIC queues, queue offset calculation must be performed only for NIC queues.

  • CVE-2022-50024Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-axi-dmac: do not print NULL LLI during error During debugging we have seen an issue where axi_chan_dump_lli() is passed a NULL LLI pointer which ends up causing an OOPS due to trying to get fields

  • CVE-2022-50023Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-axi-dmac: ignore interrupt if no descriptor If the channel has no descriptor and the interrupt is raised then the kernel will OOPS. Check the result of vchan_next_desc() in the handler axi_chan_bl

  • CVE-2022-50022Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: drivers:md:fix a potential use-after-free bug In line 2884, "raid5_release_stripe(sh);" drops the reference to sh and may cause sh to be released. However, sh is subsequently used in lines 2886 "if (sh->batch_h

  • CVE-2022-50021Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: ext4: block range must be validated before use in ext4_mb_clear_bb() Block range to free is validated in ext4_free_blocks() using ext4_inode_block_valid() and then it's passed to ext4_mb_clear_bb(). However in

  • CVE-2022-50020Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: ext4: avoid resizing to a partial cluster size This patch avoids an attempt to resize the filesystem to an unaligned cluster boundary. An online resize to a size that is not integral to cluster size results in

  • CVE-2022-50019Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: tty: serial: Fix refcount leak bug in ucc_uart.c In soc_info(), of_find_node_by_type() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.

  • CVE-2022-50012Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: powerpc/64: Init jump labels before parse_early_param() On 64-bit, calling jump_label_init() in setup_feature_keys() is too late because static keys may be used in subroutines of parse_early_param() which is ag

  • CVE-2022-50011Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: venus: pm_helpers: Fix warning in OPP during probe Fix the following WARN triggered during Venus driver probe on 5.19.0-rc8-next-20220728: WARNING: CPU: 7 PID: 339 at drivers/opp/core.c:2471 dev_pm_opp_set_co

  • CVE-2022-50010Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: video: fbdev: i740fb: Check the argument of i740_calc_vclk() Since the user can control the arguments of the ioctl() from the user space, under special arguments that may result in a divide-by-zero bug. If the

  • CVE-2022-50008Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: kprobes: don't call disarm_kprobe() for disabled kprobes The assumption in __disable_kprobe() is wrong, and it could try to disarm an already disarmed kprobe and fire the WARN_ONCE() below. [0] We can easily r

  • CVE-2022-50006Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: NFSv4.2 fix problems with __nfs42_ssc_open A destination server while doing a COPY shouldn't accept using the passed in filehandle if its not a regular filehandle. If alloc_file_pseudo() has failed, we need to

  • CVE-2022-50005Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout When the pn532 uart device is detaching, the pn532_uart_remove() is called. But there are no functions in pn532_uart_remove() that could delete th

  • CVE-2022-49999Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: btrfs: fix space cache corruption and potential double allocations When testing space_cache v2 on a large set of machines, we encountered a few symptoms: 1. "unable to add free space :-17" (EEXIST) errors. 2.

  • CVE-2022-49995Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdi_unregister gets called to stop further writeback and wait for associated delayed work to complete. However, wb_inode_writeback_

  • CVE-2022-49993Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: loop: Check for overflow while configuring loop The userspace can configure a loop using an ioctl call, wherein a configuration of type loop_config is passed (see lo_ioctl()'s case on line 1550 of drivers/block

  • CVE-2022-49990Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: s390: fix double free of GS and RI CBs on fork() failure The pointers for guarded storage and runtime instrumentation control blocks are stored in the thread_struct of the associated task. These pointers are in

  • CVE-2022-49989Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: fix error exit of privcmd_ioctl_dm_op() The error exit of privcmd_ioctl_dm_op() is calling unlock_pages() potentially with pages being NULL, leading to a NULL dereference. Additionally lock_pages(

  • CVE-2022-49987Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: md: call __md_stop_writes in md_stop From the link [1], we can see raid1d was running even after the path raid_dtr -> md_stop -> __md_stop. Let's stop write first in destructor to align with normal md-raid to

  • CVE-2022-49986Jun 18, 2025
    affected < 5.14.21-150400.24.170.2.150400.24.86.2fixed 5.14.21-150400.24.170.2.150400.24.86.2

    In the Linux kernel, the following vulnerability has been resolved: scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq storvsc_error_wq workqueue should not be marked as WQ_MEM_RECLAIM as it doesn't need to make forward progress under memory pressure. Marking this work

Page 52 of 143