rpm package
suse/kernel-default&distro=SUSE Linux Enterprise Live Patching 15 SP3
pkg:rpm/suse/kernel-default&distro=SUSE%20Linux%20Enterprise%20Live%20Patching%2015%20SP3
Vulnerabilities (1,768)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2022-50012 | Med | 5.5 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: powerpc/64: Init jump labels before parse_early_param() On 64-bit, calling jump_label_init() in setup_feature_keys() is too late because static keys may be used in subroutines of parse_early_param() which is ag | |
| CVE-2022-50010 | Med | 5.5 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: video: fbdev: i740fb: Check the argument of i740_calc_vclk() Since the user can control the arguments of the ioctl() from the user space, under special arguments that may result in a divide-by-zero bug. If the | |
| CVE-2022-49993 | Med | 5.5 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: loop: Check for overflow while configuring loop The userspace can configure a loop using an ioctl call, wherein a configuration of type loop_config is passed (see lo_ioctl()'s case on line 1550 of drivers/block | |
| CVE-2022-49990 | Hig | 7.8 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: s390: fix double free of GS and RI CBs on fork() failure The pointers for guarded storage and runtime instrumentation control blocks are stored in the thread_struct of the associated task. These pointers are in | |
| CVE-2022-49989 | Med | 5.5 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: fix error exit of privcmd_ioctl_dm_op() The error exit of privcmd_ioctl_dm_op() is calling unlock_pages() potentially with pages being NULL, leading to a NULL dereference. Additionally lock_pages( | |
| CVE-2022-49987 | Med | 5.5 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: md: call __md_stop_writes in md_stop From the link [1], we can see raid1d was running even after the path raid_dtr -> md_stop -> __md_stop. Let's stop write first in destructor to align with normal md-raid to | |
| CVE-2022-49986 | Med | 5.5 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq storvsc_error_wq workqueue should not be marked as WQ_MEM_RECLAIM as it doesn't need to make forward progress under memory pressure. Marking this work | |
| CVE-2022-49985 | Hig | 7.8 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: bpf: Don't use tnum_range on array range checking for poke descriptors Hsin-Wei reported a KASAN splat triggered by their BPF runtime fuzzer which is based on a customized syzkaller: BUG: KASAN: slab-out-of- | |
| CVE-2022-49984 | Med | 5.5 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report It is possible for a malicious device to forgo submitting a Feature Report. The HID Steam driver presently makes no prevision for this a | |
| CVE-2022-49981 | Med | 5.5 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: HID: hidraw: fix memory leak in hidraw_release() Free the buffered reports before deleting the list entry. BUG: memory leak unreferenced object 0xffff88810e72f180 (size 32): comm "softirq", pid 0, jiffies 42 | |
| CVE-2022-49980 | Hig | 7.8 | < 5.3.18-150300.59.221.1 | 5.3.18-150300.59.221.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: USB: gadget: Fix use-after-free Read in usb_udc_uevent() The syzbot fuzzer found a race between uevent callbacks and gadget driver unregistration that can cause a use-after-free bug: -------------------------- | |
| CVE-2022-49978 | Med | 5.5 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: fbdev: fb_pm2fb: Avoid potential divide by zero error In `do_fb_ioctl()` of fbmem.c, if cmd is FBIOPUT_VSCREENINFO, var will be copied from user, then go through `fb_set_var()` and `info->fbops->fb_check_var()` | |
| CVE-2022-49977 | Hig | 7.8 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead ftrace_startup does not remove ops from ftrace_ops_list when ftrace_startup_enable fails: register_ftrace_function ftrace_star | |
| CVE-2022-49968 | Hig | 8.0 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: ieee802154/adf7242: defer destroy_workqueue call There is a possible race condition (use-after-free) like below (FREE) | (USE) adf7242_remove | adf7242_channel cancel_d | |
| CVE-2022-49956 | Hig | 7.0 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: staging: rtl8712: fix use after free bugs _Read/Write_MACREG callbacks are NULL so the read/write_macreg_hdl() functions don't do anything except free the "pcmd" pointer. It results in a use after free. Delet | |
| CVE-2022-49954 | Med | 5.5 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev->mutex held is | |
| CVE-2022-49952 | Hig | 7.8 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: fix memory corruption on probe Add the missing sanity check on the probed-session count to avoid corrupting memory beyond the fixed-size slab-allocated session array when there are more than FAST | |
| CVE-2022-49950 | Hig | 7.8 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: fix memory corruption on open The probe session-duplication overflow check incremented the session count also when there were no more available sessions so that memory beyond the fixed-size slab- | |
| CVE-2022-49948 | Hig | 7.8 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: vt: Clear selection before changing the font When changing the console font with ioctl(KDFONTOP) the new font size can be bigger than the previous font. A previous selection may thus now be outside of the new s | |
| CVE-2022-49945 | Hig | 7.1 | < 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: hwmon: (gpio-fan) Fix array out of bounds access The driver does not check if the cooling state passed to gpio_fan_set_cur_state() exceeds the maximum cooling state as stored in fan_data->num_speeds. Since the |
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: powerpc/64: Init jump labels before parse_early_param() On 64-bit, calling jump_label_init() in setup_feature_keys() is too late because static keys may be used in subroutines of parse_early_param() which is ag
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: i740fb: Check the argument of i740_calc_vclk() Since the user can control the arguments of the ioctl() from the user space, under special arguments that may result in a divide-by-zero bug. If the
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: loop: Check for overflow while configuring loop The userspace can configure a loop using an ioctl call, wherein a configuration of type loop_config is passed (see lo_ioctl()'s case on line 1550 of drivers/block
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: s390: fix double free of GS and RI CBs on fork() failure The pointers for guarded storage and runtime instrumentation control blocks are stored in the thread_struct of the associated task. These pointers are in
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: fix error exit of privcmd_ioctl_dm_op() The error exit of privcmd_ioctl_dm_op() is calling unlock_pages() potentially with pages being NULL, leading to a NULL dereference. Additionally lock_pages(
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: md: call __md_stop_writes in md_stop From the link [1], we can see raid1d was running even after the path raid_dtr -> md_stop -> __md_stop. Let's stop write first in destructor to align with normal md-raid to
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq storvsc_error_wq workqueue should not be marked as WQ_MEM_RECLAIM as it doesn't need to make forward progress under memory pressure. Marking this work
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: bpf: Don't use tnum_range on array range checking for poke descriptors Hsin-Wei reported a KASAN splat triggered by their BPF runtime fuzzer which is based on a customized syzkaller: BUG: KASAN: slab-out-of-
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report It is possible for a malicious device to forgo submitting a Feature Report. The HID Steam driver presently makes no prevision for this a
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: HID: hidraw: fix memory leak in hidraw_release() Free the buffered reports before deleting the list entry. BUG: memory leak unreferenced object 0xffff88810e72f180 (size 32): comm "softirq", pid 0, jiffies 42
- affected < 5.3.18-150300.59.221.1fixed 5.3.18-150300.59.221.1
In the Linux kernel, the following vulnerability has been resolved: USB: gadget: Fix use-after-free Read in usb_udc_uevent() The syzbot fuzzer found a race between uevent callbacks and gadget driver unregistration that can cause a use-after-free bug: --------------------------
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: fbdev: fb_pm2fb: Avoid potential divide by zero error In `do_fb_ioctl()` of fbmem.c, if cmd is FBIOPUT_VSCREENINFO, var will be copied from user, then go through `fb_set_var()` and `info->fbops->fb_check_var()`
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead ftrace_startup does not remove ops from ftrace_ops_list when ftrace_startup_enable fails: register_ftrace_function ftrace_star
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: ieee802154/adf7242: defer destroy_workqueue call There is a possible race condition (use-after-free) like below (FREE) | (USE) adf7242_remove | adf7242_channel cancel_d
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: staging: rtl8712: fix use after free bugs _Read/Write_MACREG callbacks are NULL so the read/write_macreg_hdl() functions don't do anything except free the "pcmd" pointer. It results in a use after free. Delet
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev->mutex held is
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: fix memory corruption on probe Add the missing sanity check on the probed-session count to avoid corrupting memory beyond the fixed-size slab-allocated session array when there are more than FAST
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: fix memory corruption on open The probe session-duplication overflow check incremented the session count also when there were no more available sessions so that memory beyond the fixed-size slab-
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: vt: Clear selection before changing the font When changing the console font with ioctl(KDFONTOP) the new font size can be bigger than the previous font. A previous selection may thus now be outside of the new s
- affected < 5.3.18-150300.59.211.1fixed 5.3.18-150300.59.211.1
In the Linux kernel, the following vulnerability has been resolved: hwmon: (gpio-fan) Fix array out of bounds access The driver does not check if the cooling state passed to gpio_fan_set_cur_state() exceeds the maximum cooling state as stored in fan_data->num_speeds. Since the
Page 12 of 89