rpm package
suse/kernel-livepatch-SLE15-SP5_Update_27&distro=SUSE Linux Enterprise Live Patching 15 SP5
pkg:rpm/suse/kernel-livepatch-SLE15-SP5_Update_27&distro=SUSE%20Linux%20Enterprise%20Live%20Patching%2015%20SP5
Vulnerabilities (218)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-53100 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53099 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53098 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53096 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53095 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix a NULL pointer dereference The LRU mechanism may look up a resource in the process of being removed from an object. The locking rules here are a bit unclear but it looks currently like res->bo assi | ||
| CVE-2023-53093 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53092 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53091 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53090 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53089 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53087 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53084 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53082 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53081 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53079 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53078 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53077 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53075 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53074 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53073 | — | < 1-150500.11.7.1 | 1-150500.11.7.1 | May 2, 2025 | 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-53100May 2, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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-53096May 2, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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-53095May 2, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.1
In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix a NULL pointer dereference The LRU mechanism may look up a resource in the process of being removed from an object. The locking rules here are a bit unclear but it looks currently like res->bo assi
- CVE-2023-53093May 2, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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-53082May 2, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.1
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-53081May 2, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.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-53074May 2, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.1
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-53073May 2, 2025affected < 1-150500.11.7.1fixed 1-150500.11.7.1
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
Page 4 of 11