VYPR

rpm package

suse/kernel-default-base&distro=SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS

pkg:rpm/suse/kernel-default-base&distro=SUSE%20Linux%20Enterprise%20High%20Performance%20Computing%2015%20SP5-LTSS

Vulnerabilities (2,310)

  • CVE-2023-54159Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: usb: mtu3: fix kernel panic at qmu transfer done irq handler When handle qmu transfer irq, it will unlock @mtu->lock before give back request, if another thread handle disconnect event at the same time, and try

  • CVE-2023-54156Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: sfc: fix crash when reading stats while NIC is resetting efx_net_stats() (.ndo_get_stats64) can be called during an ethtool selftest, during which time nic_data->mc_stats is NULL as the NIC has been fini'd.

  • CVE-2023-54153Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: turn quotas off if mount failed after enabling quotas Yi found during a review of the patch "ext4: don't BUG on inconsistent journal feature" that when ext4_mark_recovery_complete() returns an error value

  • CVE-2023-54150Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amd: Fix an out of bounds error in BIOS parser The array is hardcoded to 8 in atomfirmware.h, but firmware provides a bigger one sometimes. Deferencing the larger array causes an out of bounds error. commi

  • CVE-2023-54148Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Move representor neigh cleanup to profile cleanup_tx For IP tunnel encapsulation in ECMP (Equal-Cost Multipath) mode, as the flow is duplicated to the peer eswitch, the related neighbour information

  • CVE-2023-54146Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: x86/kexec: Fix double-free of elf header buffer After b3e34a47f989 ("x86/kexec: fix memory leak of elf header buffer"), freeing image->elf_headers in the error path of crash_load_segments() is not needed be

  • CVE-2023-54144Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix kernel warning during topology setup This patch fixes the following kernel warning seen during driver load by correctly initializing the p2plink attr before creating the sysfs file: [ +0.00286

  • CVE-2023-54142Dec 24, 2025
    affected < 5.14.21-150500.55.136.1.150500.6.67.1fixed 5.14.21-150500.55.136.1.150500.6.67.1

    In the Linux kernel, the following vulnerability has been resolved: gtp: Fix use-after-free in __gtp_encap_destroy(). syzkaller reported use-after-free in __gtp_encap_destroy(). [0] It shows the same process freed sk and touched it illegally. Commit e198987e7dd7 ("gtp: fix su

  • CVE-2023-54140Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse A syzbot stress test using a corrupted disk image reported that mark_buffer_dirty() called from __nilfs_mark_inode_dirty() or nilfs_palloc_

  • CVE-2023-54138Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: drm/msm: fix NULL-deref on irq uninstall In case of early initialisation errors and on platforms that do not use the DPU controller, the deinitilisation code can be called with the kms pointer set to NULL. Pat

  • CVE-2023-54136Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: serial: sprd: Fix DMA buffer leak issue Release DMA buffer when _probe() returns failure to avoid memory leak.

  • CVE-2023-54134Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: autofs: fix memory leak of waitqueues in autofs_catatonic_mode Syzkaller reports a memory leak: BUG: memory leak unreferenced object 0xffff88810b279e00 (size 96): comm "syz-executor399", pid 3631, jiffies 42

  • CVE-2023-54132Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: erofs: stop parsing non-compact HEAD index if clusterofs is invalid Syzbot generated a crafted image [1] with a non-compact HEAD index of clusterofs 33024 while valid numbers should be 0 ~ lclustersize-1, which

  • CVE-2023-54131Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: rt2x00: Fix memory leak when handling surveys When removing a rt2x00 device, its associated channel surveys are not freed, causing a memory leak observable with kmemleak: unreferenced object 0xffff9620f0

  • CVE-2023-54130Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling Commit 55d1cbbbb29e ("hfs/hfsplus: use WARN_ON for sanity check") fixed a build warning by turning a comment into a WARN_ON(), but it tur

  • CVE-2023-54128Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: fs: drop peer group ids under namespace lock When cleaning up peer group ids in the failure path we need to make sure to hold on to the namespace lock. Otherwise another thread might just turn the mount from a

  • CVE-2023-54127Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: fs/jfs: prevent double-free in dbUnmount() after failed jfs_remount() Syzkaller reported the following issue: ================================================================== BUG: KASAN: double-free in slab_f

  • CVE-2023-54126Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: crypto: safexcel - Cleanup ring IRQ workqueues on load failure A failure loading the safexcel driver results in the following warning on boot, because the IRQ affinity has not been correctly cleaned up. Ensure

  • CVE-2023-54123Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix memleak for 'conf->bio_split' In the error path of raid10_run(), 'conf' need be freed, however, 'conf->bio_split' is missed and memory will be leaked. Since there are 3 places to free 'conf', fa

  • CVE-2023-54122Dec 24, 2025
    affected < 5.14.21-150500.55.133.1.150500.6.65.1fixed 5.14.21-150500.55.133.1.150500.6.65.1

    In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: Add check for cstate As kzalloc may fail and return NULL pointer, it should be better to check cstate in order to avoid the NULL pointer dereference in __drm_atomic_helper_crtc_reset. Patchwork: h

Page 9 of 116