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,337)

  • CVE-2023-53082HigMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: vp_vdpa: fix the crash in hot unplug with vp_vdpa While unplugging the vp_vdpa device, it triggers a kernel panic The root cause is: vdpa_mgmtdev_unregister() will accesses modern devices which will cause a use

  • CVE-2023-53081HigMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    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-53079MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    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-53078MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    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-53077HigMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    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-53076May 2, 2025
    affected < 5.14.21-150500.55.113.1.150500.6.53.1fixed 5.14.21-150500.55.113.1.150500.6.53.1

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

  • CVE-2023-53075HigMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    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-53074MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix ttm_bo calltrace warning in psp_hw_fini The call trace occurs when the amdgpu is removed after the mode1 reset. During mode1 reset, from suspend to resume, there is no need to reinitialize the t

  • CVE-2023-53073MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd/core: Always clear status for idx The variable 'status' (which contains the unhandled overflow bits) is not being properly masked in some cases, displaying the following warning: WARNING: CPU: 1

  • CVE-2023-53071MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: do not run mt76_unregister_device() on unregistered hw Trying to probe a mt7921e pci card without firmware results in a successful probe where ieee80211_register_hw hasn't been called. When removing

  • CVE-2023-53070MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: ACPI: PPTT: Fix to avoid sleep in the atomic context when PPTT is absent Commit 0c80f9e165f8 ("ACPI: PPTT: Leave the table mapped for the runtime usage") enabled to map PPTT once on the first invocation of acpi

  • CVE-2023-53068MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    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

  • CVE-2023-53066MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info We have to make sure that the info returned by the helper is valid before using it. Found by Linux Verification Center (linuxtesting.org) with

  • CVE-2023-53065HigMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix perf_output_begin parameter is incorrectly invoked in perf_event_bpf_output syzkaller reportes a KASAN issue with stack-out-of-bounds. The call trace is as follows: dump_stack+0x9c/0xd3 print

  • CVE-2023-53064MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: iavf: fix hang on reboot with ice When a system with E810 with existing VFs gets rebooted the following hang may be observed. Pid 1 is hung in iavf_remove(), part of a network driver: PID: 1 TASK: fff

  • CVE-2023-53062MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: net: usb: smsc95xx: 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

  • CVE-2023-53060MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: igb: revert rtnl_lock() that causes deadlock The commit 6faee3d4ee8b ("igb: Add lock to avoid data race") adds rtnl_lock to eliminate a false data race shown below (FREE from device detaching) | (USE f

  • CVE-2023-53059HigMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_chardev: fix kernel data leak from ioctl It is possible to peep kernel page's data by providing larger `insize` in struct cros_ec_command[1] when invoking EC host commands. Fix it by u

  • CVE-2023-53058MedMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: net/mlx5: E-Switch, Fix an Oops in error handling code The error handling dereferences "vport". There is nothing we can do if it is an error pointer except returning the error code.

  • CVE-2023-53057HigMay 2, 2025
    affected < 5.14.21-150500.55.110.1.150500.6.51.3fixed 5.14.21-150500.55.110.1.150500.6.51.3

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: HCI: Fix global-out-of-bounds To loop a variable-length array, hci_init_stage_sync(stage) considers that stage[i] is valid as long as stage[i-1].func is valid. Thus, the last element of stage[].func

Page 66 of 117