VYPR

rpm package

suse/kernel-default&distro=SUSE Linux Enterprise Live Patching 15 SP5

pkg:rpm/suse/kernel-default&distro=SUSE%20Linux%20Enterprise%20Live%20Patching%2015%20SP5

Vulnerabilities (4,709)

  • CVE-2023-53659HigOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: iavf: Fix out-of-bounds when setting channels on remove If we set channels greater during iavf_remove(), and waiting reset done would be timeout, then returned with error but changed num_active_queues directly,

  • CVE-2023-53658MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: spi: bcm-qspi: return error if neither hif_mspi nor mspi is available If neither a "hif_mspi" nor "mspi" resource is present, the driver will just early exit in probe but still return success. Apart from not do

  • CVE-2023-53651MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: Input: exc3000 - properly stop timer on shutdown We need to stop the timer on driver unbind or probe failures, otherwise we get UAF/Oops.

  • CVE-2023-53650MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: fbdev: omapfb: lcd_mipid: Fix an error handling path in mipid_spi_probe() If 'mipid_detect()' fails, we must free 'md' to avoid a memory leak.

  • CVE-2023-53648MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: ALSA: ac97: Fix possible NULL dereference in snd_ac97_mixer smatch error: sound/pci/ac97/ac97_codec.c:2354 snd_ac97_mixer() error: we previously assumed 'rac97' could be null (see line 2072) remove redundant a

  • CVE-2023-53644MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: media: radio-shark: Add endpoint checks The syzbot fuzzer was able to provoke a WARNING from the radio-shark2 driver: ------------[ cut here ]------------ usb 1-1: BOGUS urb xfer, pipe 1 != type 3 WARNING: CPU

  • CVE-2023-53641MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: hif_usb: fix memory leak of remain_skbs hif_dev->remain_skb is allocated and used exclusively in ath9k_hif_usb_rx_stream(). It is implied that an allocated remain_skb is processed and subsequently

  • CVE-2023-53640HigOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: ASoC: lpass: Fix for KASAN use_after_free out of bounds When we run syzkaller we get below Out of Bounds error. "KASAN: slab-out-of-bounds Read in regcache_flat_read" Below is the backtrace of the issue: BUG

  • CVE-2023-53639MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: ath6kl: reduce WARN to dev_dbg() in callback The warn is triggered on a known race condition, documented in the code above the test, that is correctly handled. Using WARN() hinders automated testing. Red

  • CVE-2023-53637MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: media: i2c: ov772x: Fix memleak in ov772x_probe() A memory leak was reported when testing ov772x with bpf mock device: AssertionError: unreferenced object 0xffff888109afa7a8 (size 8): comm "python3", pid 279

  • CVE-2023-53631MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: platform/x86: dell-sysman: Fix reference leak If a duplicate attribute is found using kset_find_obj(), a reference to that attribute is returned. This means that we need to dispose it accordingly. Use kobject_p

  • CVE-2023-53626HigOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix possible double unlock when moving a directory

  • CVE-2023-53625MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: drm/i915/gvt: fix vgpu debugfs clean in remove Check carefully on root debugfs available when destroying vgpu, e.g in remove case drm minor's debugfs root might already be destroyed, which led to kernel oops li

  • CVE-2023-53622HigOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix possible data races in gfs2_show_options() Some fields such as gt_logd_secs of the struct gfs2_tune are accessed without holding the lock gt_spin in gfs2_show_options(): val = sdp->sd_tune.gt_logd_

  • CVE-2023-53619HigOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free If nf_conntrack_init_start() fails (for example due to a register_nf_conntrack_bpf() failure), the nf_conntrack_helper_fini() clean-up path frees th

  • CVE-2023-53617MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: soc: aspeed: socinfo: Add kfree for kstrdup Add kfree() in the later error handling in order to avoid memory leak.

  • CVE-2022-50553MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: tracing/hist: Fix out-of-bound write on 'action_data.var_ref_idx' When generate a synthetic event with many params and then create a trace action for it [1], kernel panic happened [2]. It is because that in tr

  • CVE-2022-50551HigOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() This patch fixes a shift-out-of-bounds in brcmfmac that occurs in BIT(chiprev) when a 'chiprev' provided by the device is too large.

  • CVE-2022-50549MedOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: dm thin: Fix ABBA deadlock between shrink_slab and dm_pool_abort_metadata Following concurrent processes: P1(drop cache) P2(kworker) drop_caches_sysctl_handler drop_slab shrink_slab

  • CVE-2022-50546HigOct 7, 2025
    affected < 5.14.21-150500.55.127.1fixed 5.14.21-150500.55.127.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix uninititialized value in 'ext4_evict_inode' Syzbot found the following issue: ===================================================== BUG: KMSAN: uninit-value in ext4_evict_inode+0xdd/0x26b0 fs/ext4/ino

Page 26 of 236