VYPR

rpm package

suse/kernel-default-base&distro=SUSE Manager Proxy 4.3

pkg:rpm/suse/kernel-default-base&distro=SUSE%20Manager%20Proxy%204.3

Vulnerabilities (1,907)

  • CVE-2023-53106May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: nfc: st-nci: Fix use after free bug in ndlc_remove due to race condition This bug influences both st_nci_i2c_remove and st_nci_spi_remove. Take st_nci_i2c_remove as an example. In st_nci_i2c_probe, it called n

  • CVE-2023-53101May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: zero i_disksize when initializing the bootloader inode If the boot loader inode has never been used before, the EXT4_IOC_SWAP_BOOT inode will initialize it, including setting the i_size to 0. However, if

  • CVE-2023-53100May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix WARNING in ext4_update_inline_data Syzbot found the following issue: EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 without journal. Quota mode: none. fscrypt: AES-256-CTS-CB

  • CVE-2023-53099May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: firmware: xilinx: don't make a sleepable memory allocation from an atomic context The following issue was discovered using lockdep: [ 6.691371] BUG: sleeping function called from invalid context at include/l

  • CVE-2023-53098May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: media: rc: gpio-ir-recv: add remove function In case runtime PM is enabled, do runtime PM clean up to remove cpu latency qos request, otherwise driver removal may have below kernel dump: [ 19.463299] Unable

  • CVE-2023-53097May 2, 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/iommu: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call de

  • CVE-2023-53096May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: interconnect: fix mem leak when freeing nodes The node link array is allocated when adding links to a node but is not deallocated when nodes are destroyed.

  • CVE-2023-53093May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: tracing: Do not let histogram values have some modifiers Histogram values can not be strings, stacktraces, graphs, symbols, syscalls, or grouped in buckets or log. Give an error if a value is set to do so. Not

  • CVE-2023-53092May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: interconnect: exynos: fix node leak in probe PM QoS error path Make sure to add the newly allocated interconnect node to the provider before adding the PM QoS request so that the node is freed on errors.

  • CVE-2023-53091May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: update s_journal_inum if it changes after journal replay When mounting a crafted ext4 image, s_journal_inum may change after journal replay, which is obviously unreasonable because we have successfully lo

  • CVE-2023-53090May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix an illegal memory access In the kfd_wait_on_events() function, the kfd_event_waiter structure is allocated by alloc_event_waiters(), but the event field of the waiter structure is not initialize

  • CVE-2023-53089May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix task hung in ext4_xattr_delete_inode Syzbot reported a hung task problem: ================================================================== INFO: task syz-executor232:5073 blocked for more than 143 s

  • CVE-2023-53087May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: drm/i915/active: Fix misuse of non-idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a number of concurrently running graphics applications. Root cause analysi

  • CVE-2023-53084May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: drm/shmem-helper: Remove another errant put in error path drm_gem_shmem_mmap() doesn't own reference in error code path, resulting in the dma-buf shmem GEM object getting prematurely freed leading to a later us

  • CVE-2023-53081May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix data corruption after failed write When buffered write fails to copy data into underlying page cache page, ocfs2_write_end_nolock() just zeroes out and dirties the page. This can leave dirty page be

  • CVE-2023-53079May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix steering rules cleanup vport's mc, uc and multicast rules are not deleted in teardown path when EEH happens. Since the vport's promisc settings(uc, mc and all) in firmware are reset after EEH, mlx

  • CVE-2023-53078May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate() If alua_rtpg_queue() failed from alua_activate(), then 'qdata' is not freed, which will cause following memleak: unreferenced object 0xffff88810b2

  • CVE-2023-53077May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix shift-out-of-bounds in CalculateVMAndRowBytes [WHY] When PTEBufferSizeInRequests is zero, UBSAN reports the following warning because dml_log2 returns an unexpected negative value: shift

  • CVE-2023-53075May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix invalid address access in lookup_rec() when index is 0 KASAN reported follow problem: BUG: KASAN: use-after-free in lookup_rec Read of size 8 at addr ffff000199270ff0 by task modprobe CPU: 2 Com

  • CVE-2023-53068May 2, 2025
    affected < 5.14.21-150400.24.167.1.150400.24.84.1fixed 5.14.21-150400.24.167.1.150400.24.84.1

    In the Linux kernel, the following vulnerability has been resolved: net: usb: lan78xx: Limit packet length to skb->len Packet length retrieved from descriptor may be larger than the actual socket buffer length. In such case the cloned skb passed up the network stack will leak k

Page 11 of 96