rpm package
suse/kernel-default-base&distro=SUSE Linux Enterprise Server for SAP Applications 15 SP3
pkg:rpm/suse/kernel-default-base&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2015%20SP3
Vulnerabilities (1,485)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-53063 | Hig | 7.8 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 19, 2024 | In the Linux kernel, the following vulnerability has been resolved: media: dvbdev: prevent the risk of out of memory access The dvbdev contains a static variable used to store dvb minors. The behavior of it depends if CONFIG_DVB_DYNAMIC_MINORS is set or not. When not set, dvb_ | |
| CVE-2024-53061 | Hig | 7.3 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 19, 2024 | In the Linux kernel, the following vulnerability has been resolved: media: s5p-jpeg: prevent buffer overflows The current logic allows word to be less than 2. If this happens, there will be buffer overflows, as reported by smatch. Add extra checks to prevent it. While here, re | |
| CVE-2024-50302 | Med | 5.5 | KEV | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 19, 2024 | In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak k |
| CVE-2024-50301 | Hig | 7.8 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 19, 2024 | In the Linux kernel, the following vulnerability has been resolved: security/keys: fix slab-out-of-bounds in key_task_permission KASAN reports an out of bounds read: BUG: KASAN: slab-out-of-bounds in __kuid_val include/linux/uidgid.h:36 BUG: KASAN: slab-out-of-bounds in uid_eq | |
| CVE-2024-50290 | Med | 5.5 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 19, 2024 | In the Linux kernel, the following vulnerability has been resolved: media: cx24116: prevent overflows on SNR calculus as reported by Coverity, if reading SNR registers fail, a negative number will be returned, causing an underflow when reading SNR registers. Prevent that. | |
| CVE-2024-50279 | Hig | 7.1 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 19, 2024 | In the Linux kernel, the following vulnerability has been resolved: dm cache: fix out-of-bounds access to the dirty bitset when resizing dm-cache checks the dirty bits of the cache blocks to be dropped when shrinking the fast device, but an index bug in bitset iteration causes | |
| CVE-2024-50267 | Hig | 7.8 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 19, 2024 | In the Linux kernel, the following vulnerability has been resolved: USB: serial: io_edgeport: fix use after free in debug printk The "dev_dbg(&urb->dev->dev, ..." which happens after usb_free_urb(urb) is a use after free of the "urb" pointer. Store the "dev" pointer at the sta | |
| CVE-2024-50264 | Hig | 7.8 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 19, 2024 | In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After-Free condition. T | |
| CVE-2023-4134 | Med | 5.5 | < 5.3.18-150300.59.133.1.150300.18.78.1 | 5.3.18-150300.59.133.1.150300.18.78.1 | Nov 14, 2024 | A use-after-free vulnerability was found in the cyttsp4_core driver in the Linux kernel. This issue occurs in the device cleanup routine due to a possible rearming of the watchdog_timer from the workqueue. This could allow a local user to crash the system, causing a denial of ser | |
| CVE-2024-50208 | Hig | 7.8 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 8, 2024 | In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages Avoid memory corruption while setting up Level-2 PBL pages for the non MR resources when num_pages > 256K. There will be a single PDE page address (co | |
| CVE-2024-50205 | Med | 5.5 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 8, 2024 | In the Linux kernel, the following vulnerability has been resolved: ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() The step variable is initialized to zero. It is changed in the loop, but if it's not changed it will remain zero. Add a variable check be | |
| CVE-2024-50199 | Med | 5.5 | < 5.3.18-150300.59.195.1.150300.18.116.1 | 5.3.18-150300.59.195.1.150300.18.116.1 | Nov 8, 2024 | In the Linux kernel, the following vulnerability has been resolved: mm/swapfile: skip HugeTLB pages for unuse_vma I got a bad pud error and lost a 1GB HugeTLB when calling swapoff. The problem can be reproduced by the following steps: 1. Allocate an anonymous 1GB HugeTLB and | |
| CVE-2024-50154 | Cri | 9.8 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 7, 2024 | In the Linux kernel, the following vulnerability has been resolved: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). Martin KaFai Lau reported use-after-free [0] in reqsk_timer_handler(). """ We are seeing a use-after-free from a bpf prog attached to trace_tc | |
| CVE-2024-50127 | Hig | 7.8 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 5, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: sched: fix use-after-free in taprio_change() In 'taprio_change()', 'admin' pointer may become dangling due to sched switch / removal caused by 'advance_sched()', and critical section protected by 'q->curre | |
| CVE-2024-50125 | Hig | 8.0 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 5, 2024 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix UAF on sco_sock_timeout conn->sk maybe have been unlinked/freed while waiting for sco_conn_lock so this checks if the conn->sk is still valid by checking if it part of sco_sk_list. | |
| CVE-2024-50115 | Hig | 8.4 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 5, 2024 | In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory Ignore nCR3[4:0] when loading PDPTEs from memory for nested SVM, as bits 4:0 of CR3 are ignored when PAE paging is used, and thus VMRUN doesn't enforc | |
| CVE-2024-50089 | — | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Nov 5, 2024 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | ||
| CVE-2023-52919 | Med | 5.5 | < 5.3.18-150300.59.182.1.150300.18.107.1 | 5.3.18-150300.59.182.1.150300.18.107.1 | Oct 22, 2024 | In the Linux kernel, the following vulnerability has been resolved: nfc: nci: fix possible NULL pointer dereference in send_acknowledge() Handle memory allocation failure from nci_skb_alloc() (calling alloc_skb()) to avoid possible NULL pointer dereference. | |
| CVE-2024-50047 | Cri | 9.8 | < 5.3.18-150300.59.182.1.150300.18.107.1 | 5.3.18-150300.59.182.1.150300.18.107.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in async decryption Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API. Reproducer: # mount.cifs -o ...,seal,esize=1 //srv/share /mnt | |
| CVE-2022-49032 | Hig | 7.1 | < 5.3.18-150300.59.185.1.150300.18.109.1 | 5.3.18-150300.59.185.1.150300.18.109.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4404_read_raw+0x2ce/0x380 Read of size 4 at addr ffffffffc00e46 |
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: media: dvbdev: prevent the risk of out of memory access The dvbdev contains a static variable used to store dvb minors. The behavior of it depends if CONFIG_DVB_DYNAMIC_MINORS is set or not. When not set, dvb_
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: media: s5p-jpeg: prevent buffer overflows The current logic allows word to be less than 2. If this happens, there will be buffer overflows, as reported by smatch. Add extra checks to prevent it. While here, re
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak k
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: security/keys: fix slab-out-of-bounds in key_task_permission KASAN reports an out of bounds read: BUG: KASAN: slab-out-of-bounds in __kuid_val include/linux/uidgid.h:36 BUG: KASAN: slab-out-of-bounds in uid_eq
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: media: cx24116: prevent overflows on SNR calculus as reported by Coverity, if reading SNR registers fail, a negative number will be returned, causing an underflow when reading SNR registers. Prevent that.
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: dm cache: fix out-of-bounds access to the dirty bitset when resizing dm-cache checks the dirty bits of the cache blocks to be dropped when shrinking the fast device, but an index bug in bitset iteration causes
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: USB: serial: io_edgeport: fix use after free in debug printk The "dev_dbg(&urb->dev->dev, ..." which happens after usb_free_urb(urb) is a use after free of the "urb" pointer. Store the "dev" pointer at the sta
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After-Free condition. T
- affected < 5.3.18-150300.59.133.1.150300.18.78.1fixed 5.3.18-150300.59.133.1.150300.18.78.1
A use-after-free vulnerability was found in the cyttsp4_core driver in the Linux kernel. This issue occurs in the device cleanup routine due to a possible rearming of the watchdog_timer from the workqueue. This could allow a local user to crash the system, causing a denial of ser
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages Avoid memory corruption while setting up Level-2 PBL pages for the non MR resources when num_pages > 256K. There will be a single PDE page address (co
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() The step variable is initialized to zero. It is changed in the loop, but if it's not changed it will remain zero. Add a variable check be
- affected < 5.3.18-150300.59.195.1.150300.18.116.1fixed 5.3.18-150300.59.195.1.150300.18.116.1
In the Linux kernel, the following vulnerability has been resolved: mm/swapfile: skip HugeTLB pages for unuse_vma I got a bad pud error and lost a 1GB HugeTLB when calling swapoff. The problem can be reproduced by the following steps: 1. Allocate an anonymous 1GB HugeTLB and
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). Martin KaFai Lau reported use-after-free [0] in reqsk_timer_handler(). """ We are seeing a use-after-free from a bpf prog attached to trace_tc
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: net: sched: fix use-after-free in taprio_change() In 'taprio_change()', 'admin' pointer may become dangling due to sched switch / removal caused by 'advance_sched()', and critical section protected by 'q->curre
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix UAF on sco_sock_timeout conn->sk maybe have been unlinked/freed while waiting for sco_conn_lock so this checks if the conn->sk is still valid by checking if it part of sco_sk_list.
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory Ignore nCR3[4:0] when loading PDPTEs from memory for nested SVM, as bits 4:0 of CR3 are ignored when PAE paging is used, and thus VMRUN doesn't enforc
- CVE-2024-50089Nov 5, 2024affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
- affected < 5.3.18-150300.59.182.1.150300.18.107.1fixed 5.3.18-150300.59.182.1.150300.18.107.1
In the Linux kernel, the following vulnerability has been resolved: nfc: nci: fix possible NULL pointer dereference in send_acknowledge() Handle memory allocation failure from nci_skb_alloc() (calling alloc_skb()) to avoid possible NULL pointer dereference.
- affected < 5.3.18-150300.59.182.1.150300.18.107.1fixed 5.3.18-150300.59.182.1.150300.18.107.1
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in async decryption Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API. Reproducer: # mount.cifs -o ...,seal,esize=1 //srv/share /mnt
- affected < 5.3.18-150300.59.185.1.150300.18.109.1fixed 5.3.18-150300.59.185.1.150300.18.109.1
In the Linux kernel, the following vulnerability has been resolved: iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4404_read_raw+0x2ce/0x380 Read of size 4 at addr ffffffffc00e46
Page 31 of 75