rpm package
suse/kernel-default&distro=SUSE Linux Enterprise Server for SAP Applications 15 SP4
pkg:rpm/suse/kernel-default&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2015%20SP4
Vulnerabilities (2,874)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2022-50102 | Med | 5.5 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: video: fbdev: arkfb: Fix a divide-by-zero bug in ark_set_pixclock() 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 i | |
| CVE-2022-50101 | Hig | 7.8 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: video: fbdev: vt8623fb: Check the size of screen before memset_io() In the function vt8623fb_set_par(), the value of 'screen_size' is calculated by the user input. If the user provides the improper value, the v | |
| CVE-2022-50100 | Med | 5.5 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: sched/core: Do not requeue task on CPU excluded from cpus_mask The following warning was triggered on a large machine early in boot on a distribution kernel but the same problem should also affect mainline. | |
| CVE-2022-50099 | Hig | 7.8 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: video: fbdev: arkfb: Check the size of screen before memset_io() In the function arkfb_set_par(), the value of 'screen_size' is calculated by the user input. If the user provides the improper value, the value o | |
| CVE-2022-50098 | Hig | 8.8 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix crash due to stale SRB access around I/O timeouts Ensure SRB is returned during I/O timeout error escalation. If that is not possible fail the escalation path. Following crash stack was seen | |
| CVE-2022-50097 | Hig | 7.1 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: video: fbdev: s3fb: Check the size of screen before memset_io() In the function s3fb_set_par(), the value of 'screen_size' is calculated by the user input. If the user provides the improper value, the value of | |
| CVE-2022-50095 | Hig | 7.8 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Cleanup CPU timers before freeing them during exec Commit 55e8c8eb2c7b ("posix-cpu-timers: Store a reference to a pid not a task") started looking up tasks by PID when deleting a CPU timer. W | |
| CVE-2022-50094 | Hig | 7.1 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: spmi: trace: fix stack-out-of-bound access in SPMI tracing functions trace_spmi_write_begin() and trace_spmi_read_end() both call memcpy() with a length of "len + 1". This leads to one extra byte being read be | |
| CVE-2022-50093 | Hig | 7.1 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: avoid invalid memory access via node_online(NUMA_NO_NODE) KASAN reports: [ 4.668325][ T0] BUG: KASAN: wild-memory-access in dmar_parse_one_rhsa (arch/x86/include/asm/bitops.h:214 arch/x86/include/a | |
| CVE-2022-50092 | Med | 5.5 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: dm thin: fix use-after-free crash in dm_sm_register_threshold_callback Fault inject on pool metadata device reports: BUG: KASAN: use-after-free in dm_pool_register_metadata_threshold+0x40/0x80 Read of size | |
| CVE-2022-50087 | Hig | 7.8 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the scpi_info is not set and will remain NULL until the probe succeeds. If it | |
| CVE-2022-50085 | Hig | 7.8 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: dm raid: fix address sanitizer warning in raid_resume There is a KASAN warning in raid_resume when running the lvm test lvconvert-raid.sh. The reason for the warning is that mddev->raid_disks is greater than rs | |
| CVE-2022-50084 | Hig | 7.1 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: dm raid: fix address sanitizer warning in raid_status There is this warning when using a kernel with the address sanitizer and running this testsuite: https://gitlab.com/cki-project/kernel-tests/-/tree/main/sto | |
| CVE-2022-50083 | — | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | ||
| CVE-2022-50079 | Hig | 7.0 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check correct bounds for stream encoder instances for DCN303 [Why & How] eng_id for DCN303 cannot be more than 1, since we have only two instances of stream encoders. Check the correct boundar | |
| CVE-2022-50077 | Med | 5.5 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: apparmor: fix reference count leak in aa_pivotroot() The aa_pivotroot() function has a reference counting bug in a specific path. When aa_replace_current_label() returns on success, the function forgets to decr | |
| CVE-2022-50076 | Med | 5.5 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: cifs: Fix memory leak on the deferred close xfstests on smb21 report kmemleak as below: unreferenced object 0xffff8881767d6200 (size 64): comm "xfs_io", pid 1284, jiffies 4294777434 (age 20.789s) hex | |
| CVE-2022-50074 | Med | 5.5 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: apparmor: Fix memleak in aa_simple_write_to_buffer() When copy_from_user failed, the memory is freed by kvfree. however the management struct and data blob are allocated independently, so only kvfree(data) caus | |
| CVE-2022-50073 | Med | 5.5 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null Fixes a NULL pointer derefence bug triggered from tap driver. When tap_get_user calls virtio_net_hdr_to_skb the skb->dev is nu | |
| CVE-2022-50072 | Hig | 7.8 | < 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 | Jun 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: NFSv4/pnfs: Fix a use-after-free bug in open If someone cancels the open RPC call, then we must not try to free either the open slot or the layoutget operation arguments, since they are likely still in use by t |
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: arkfb: Fix a divide-by-zero bug in ark_set_pixclock() 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 i
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: vt8623fb: Check the size of screen before memset_io() In the function vt8623fb_set_par(), the value of 'screen_size' is calculated by the user input. If the user provides the improper value, the v
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: sched/core: Do not requeue task on CPU excluded from cpus_mask The following warning was triggered on a large machine early in boot on a distribution kernel but the same problem should also affect mainline.
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: arkfb: Check the size of screen before memset_io() In the function arkfb_set_par(), the value of 'screen_size' is calculated by the user input. If the user provides the improper value, the value o
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix crash due to stale SRB access around I/O timeouts Ensure SRB is returned during I/O timeout error escalation. If that is not possible fail the escalation path. Following crash stack was seen
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: s3fb: Check the size of screen before memset_io() In the function s3fb_set_par(), the value of 'screen_size' is calculated by the user input. If the user provides the improper value, the value of
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Cleanup CPU timers before freeing them during exec Commit 55e8c8eb2c7b ("posix-cpu-timers: Store a reference to a pid not a task") started looking up tasks by PID when deleting a CPU timer. W
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: spmi: trace: fix stack-out-of-bound access in SPMI tracing functions trace_spmi_write_begin() and trace_spmi_read_end() both call memcpy() with a length of "len + 1". This leads to one extra byte being read be
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: avoid invalid memory access via node_online(NUMA_NO_NODE) KASAN reports: [ 4.668325][ T0] BUG: KASAN: wild-memory-access in dmar_parse_one_rhsa (arch/x86/include/asm/bitops.h:214 arch/x86/include/a
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: dm thin: fix use-after-free crash in dm_sm_register_threshold_callback Fault inject on pool metadata device reports: BUG: KASAN: use-after-free in dm_pool_register_metadata_threshold+0x40/0x80 Read of size
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the scpi_info is not set and will remain NULL until the probe succeeds. If it
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: dm raid: fix address sanitizer warning in raid_resume There is a KASAN warning in raid_resume when running the lvm test lvconvert-raid.sh. The reason for the warning is that mddev->raid_disks is greater than rs
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: dm raid: fix address sanitizer warning in raid_status There is this warning when using a kernel with the address sanitizer and running this testsuite: https://gitlab.com/cki-project/kernel-tests/-/tree/main/sto
- CVE-2022-50083Jun 18, 2025affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check correct bounds for stream encoder instances for DCN303 [Why & How] eng_id for DCN303 cannot be more than 1, since we have only two instances of stream encoders. Check the correct boundar
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: apparmor: fix reference count leak in aa_pivotroot() The aa_pivotroot() function has a reference counting bug in a specific path. When aa_replace_current_label() returns on success, the function forgets to decr
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix memory leak on the deferred close xfstests on smb21 report kmemleak as below: unreferenced object 0xffff8881767d6200 (size 64): comm "xfs_io", pid 1284, jiffies 4294777434 (age 20.789s) hex
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: apparmor: Fix memleak in aa_simple_write_to_buffer() When copy_from_user failed, the memory is freed by kvfree. however the management struct and data blob are allocated independently, so only kvfree(data) caus
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null Fixes a NULL pointer derefence bug triggered from tap driver. When tap_get_user calls virtio_net_hdr_to_skb the skb->dev is nu
- affected < 5.14.21-150400.24.170.2fixed 5.14.21-150400.24.170.2
In the Linux kernel, the following vulnerability has been resolved: NFSv4/pnfs: Fix a use-after-free bug in open If someone cancels the open RPC call, then we must not try to free either the open slot or the layoutget operation arguments, since they are likely still in use by t
Page 50 of 144