VYPR

rpm package

suse/kernel-zfcpdump&distro=SUSE Manager Server LTS 4.3

pkg:rpm/suse/kernel-zfcpdump&distro=SUSE%20Manager%20Server%20LTS%204.3

Vulnerabilities (542)

  • CVE-2023-53449Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: s390/dasd: Fix potential memleak in dasd_eckd_init() `dasd_reserve_req` is allocated before `dasd_vol_info_req`, and it also needs to be freed before the error returns, just like the other cases in this functio

  • CVE-2022-50444Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: clk: tegra20: Fix refcount leak in tegra20_clock_init of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put()

  • CVE-2022-50443Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: drm/rockchip: lvds: fix PM usage counter unbalance in poweron pm_runtime_get_sync will increment pm usage counter even it failed. Forgetting to putting operation will result in reference leak here. We fix it by

  • CVE-2022-50440Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Validate the box size for the snooped cursor Invalid userspace dma surface copies could potentially overflow the memcpy from the surface to the snooped image leading to crashes. To fix it the dimens

  • CVE-2022-50439Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8173: Enable IRQ when pdata is ready If the device does not come straight from reset, we might receive an IRQ before we are ready to handle it. [ 2.334737] Unable to handle kernel read fr

  • CVE-2022-50437Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: drm/msm/hdmi: fix memory corruption with too many bridges Add the missing sanity check on the bridge counter to avoid corrupting data beyond the fixed-sized bridge array in case there are ever more than eight b

  • CVE-2022-50436Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: don't set up encryption key during jbd2 transaction Commit a80f7fcf1867 ("ext4: fixup ext4_fc_track_* functions' signature") extended the scope of the transaction in ext4_unlink() too far, making it inclu

  • CVE-2022-50435Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: avoid crash when inline data creation follows DIO write When inode is created and written to using direct IO, there is nothing to clear the EXT4_STATE_MAY_INLINE_DATA flag. Thus when inode gets truncated

  • CVE-2022-50434Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix possible memleak when register 'hctx' failed There's issue as follows when do fault injection test: unreferenced object 0xffff888132a9f400 (size 512): comm "insmod", pid 308021, jiffies 4324277909

  • CVE-2022-50432Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: kernfs: fix use-after-free in __kernfs_remove Syzkaller managed to trigger concurrent calls to kernfs_remove_by_name_ns() for the same file resulting in a KASAN detected use-after-free. The race occurs when the

  • CVE-2022-50431Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: ALSA: aoa: i2sbus: fix possible memory leak in i2sbus_add_dev() dev_set_name() in soundbus_add_one() allocates memory for name, it need be freed when of_device_register() fails, call soundbus_dev_put() to give

  • CVE-2022-50430Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING vub300_enable_sdio_irq() works with mutex and need TASK_RUNNING here. Ensure that we mark current as TASK_RUNNING for sleepable context. [

  • CVE-2022-50429Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: memory: of: Fix refcount leak bug in of_lpddr3_get_ddr_timings() We should add the of_node_put() when breaking out of for_each_child_of_node() as it will automatically increase and decrease the refcount.

  • CVE-2022-50428Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix off-by-one errors in fast-commit block filling Due to several different off-by-one errors, or perhaps due to a late change in design that wasn't fully reflected in the code that was actually merged, t

  • CVE-2022-50427Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: ALSA: ac97: fix possible memory leak in snd_ac97_dev_register() If device_register() fails in snd_ac97_dev_register(), it should call put_device() to give up reference, or the name allocated in dev_set_name() i

  • CVE-2022-50425Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Fix copy_xstate_to_uabi() to copy init states correctly When an extended state component is not present in fpstate, but in init state, the function copies from init_fpstate via copy_feature(). But, dy

  • CVE-2022-50423Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage() There is an use-after-free reported by KASAN: BUG: KASAN: use-after-free in acpi_ut_remove_reference+0x3b/0x82 Read of size 1 at addr ffff8

  • CVE-2022-50422Oct 1, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() When executing SMP task failed, the smp_execute_task_sg() calls del_timer() to delete "slow_task->timer". However, if the timer handler sas_task_int

  • CVE-2025-39869Sep 23, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map Fix a critical memory allocation bug in edma_setup_from_hw() where queue_priority_map was allocated with insufficient memory. The code decl

  • CVE-2025-39860HigSep 19, 2025
    affected < 5.14.21-150400.24.179.1fixed 5.14.21-150400.24.179.1

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() syzbot reported the splat below without a repro. In the splat, a single thread calling bt_accept_dequeue() freed sk and touched it after that. The

Page 12 of 28