rpm package
suse/kernel-default&distro=SUSE Linux Enterprise Workstation Extension 15 SP5
pkg:rpm/suse/kernel-default&distro=SUSE%20Linux%20Enterprise%20Workstation%20Extension%2015%20SP5
Vulnerabilities (2,017)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-26631 | — | < 5.14.21-150500.55.80.2 | 5.14.21-150500.55.80.2 | Mar 18, 2024 | In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work idev->mc_ifc_count can be written over without proper locking. Originally found by syzbot [1], fix this issue by encapsulating calls to mld_ifc_stop_wo | ||
| CVE-2023-52612 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 18, 2024 | In the Linux kernel, the following vulnerability has been resolved: crypto: scomp - fix req->dst buffer overflow The req->dst buffer size should be checked before copying from the scomp_scratch->dst to avoid req->dst buffer overflow problem. | ||
| CVE-2023-52610 | — | < 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 | Mar 18, 2024 | In the Linux kernel, the following vulnerability has been resolved: net/sched: act_ct: fix skb leak and crash on ooo frags act_ct adds skb->users before defragmentation. If frags arrive in order, the last frag's reference is reset in: inet_frag_reasm_prepare skb_morph w | ||
| CVE-2023-28746 | Med | 6.5 | < 5.14.21-150500.55.52.1 | 5.14.21-150500.55.52.1 | Mar 14, 2024 | Information exposure through microarchitectural state after transient execution from some register files for some Intel(R) Atom(R) Processors may allow an authenticated user to potentially enable information disclosure via local access. | |
| CVE-2024-26629 | Med | 5.5 | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 13, 2024 | In the Linux kernel, the following vulnerability has been resolved: nfsd: fix RELEASE_LOCKOWNER The test on so_count in nfsd4_release_lockowner() is nonsense and harmful. Revert to using check_for_locks(), changing that to not sleep. First: harmful. As is documented in the kd | |
| CVE-2023-52608 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 13, 2024 | In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Check mailbox/SMT channel for consistency On reception of a completion interrupt the shared memory area is accessed to retrieve the message header at first and then, if the message sequence | ||
| CVE-2024-26627 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler Inside scsi_eh_wakeup(), scsi_host_busy() is called & checked with host lock every time for deciding if error handler kthread needs to | ||
| CVE-2024-26625 | — | < 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: llc: call sock_orphan() at release time syzbot reported an interesting trace [1] caused by a stale sk->sk_wq pointer in a closed llc socket. In commit ff7b11aa481f ("net: socket: set sock->sk to NULL after cal | ||
| CVE-2023-52607 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: powerpc/mm: Fix null-pointer dereference in pgtable_cache_add kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. Ensure the allocation was successful by checking the p | ||
| CVE-2023-52606 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: powerpc/lib: Validate size for vector operations Some of the fp/vmx code in sstep.c assume a certain maximum size for the instructions being emulated. The size of those operations however is determined separate | ||
| CVE-2023-52604 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree Syzkaller reported the following issue: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:2867:6 index 196694 is out of range for type 's8[1365]' (aka 's | ||
| CVE-2023-52603 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is | ||
| CVE-2023-52602 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: jfs: fix slab-out-of-bounds Read in dtSearch Currently while searching for current page in the sorted entry table of the page there is a out of bound access. Added a bound check to fix the error. Dave: Set ret | ||
| CVE-2023-52601 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: jfs: fix array-index-out-of-bounds in dbAdjTree Currently there is a bound check missing in the dbAdjTree while accessing the dmt_stree. To add the required check added the bool is_ctl which is required to dete | ||
| CVE-2023-52600 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls | ||
| CVE-2023-52599 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: jfs: fix array-index-out-of-bounds in diNewExt [Syz report] UBSAN: array-index-out-of-bounds in fs/jfs/jfs_imap.c:2360:2 index -878706688 is out of range for type 'struct iagctl[128]' CPU: 1 PID: 5065 Comm: syz | ||
| CVE-2023-52598 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: s390/ptrace: handle setting of fpc register correctly If the content of the floating point control (fpc) register of a traced process is modified with the ptrace interface the new value is tested for validity b | ||
| CVE-2023-52597 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: KVM: s390: fix setting of fpc register kvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control (fpc) register of a guest cpu. The new value is tested for validity by temporarily loading it into t | ||
| CVE-2023-52595 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: wifi: rt2x00: restart beacon queue when hardware reset When a hardware reset is triggered, all registers are reset, so all queues are forced to stop in hardware interface. However, mac80211 will not automatical | ||
| CVE-2023-52594 | — | < 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 | Mar 6, 2024 | In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() Fix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug occurs when txs->cnt, data from a URB provided by a USB d |
- CVE-2024-26631Mar 18, 2024affected < 5.14.21-150500.55.80.2fixed 5.14.21-150500.55.80.2
In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work idev->mc_ifc_count can be written over without proper locking. Originally found by syzbot [1], fix this issue by encapsulating calls to mld_ifc_stop_wo
- CVE-2023-52612Mar 18, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: crypto: scomp - fix req->dst buffer overflow The req->dst buffer size should be checked before copying from the scomp_scratch->dst to avoid req->dst buffer overflow problem.
- CVE-2023-52610Mar 18, 2024affected < 5.14.21-150500.55.83.1fixed 5.14.21-150500.55.83.1
In the Linux kernel, the following vulnerability has been resolved: net/sched: act_ct: fix skb leak and crash on ooo frags act_ct adds skb->users before defragmentation. If frags arrive in order, the last frag's reference is reset in: inet_frag_reasm_prepare skb_morph w
- affected < 5.14.21-150500.55.52.1fixed 5.14.21-150500.55.52.1
Information exposure through microarchitectural state after transient execution from some register files for some Intel(R) Atom(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
- affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix RELEASE_LOCKOWNER The test on so_count in nfsd4_release_lockowner() is nonsense and harmful. Revert to using check_for_locks(), changing that to not sleep. First: harmful. As is documented in the kd
- CVE-2023-52608Mar 13, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Check mailbox/SMT channel for consistency On reception of a completion interrupt the shared memory area is accessed to retrieve the message header at first and then, if the message sequence
- CVE-2024-26627Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler Inside scsi_eh_wakeup(), scsi_host_busy() is called & checked with host lock every time for deciding if error handler kthread needs to
- CVE-2024-26625Mar 6, 2024affected < 5.14.21-150500.55.73.1fixed 5.14.21-150500.55.73.1
In the Linux kernel, the following vulnerability has been resolved: llc: call sock_orphan() at release time syzbot reported an interesting trace [1] caused by a stale sk->sk_wq pointer in a closed llc socket. In commit ff7b11aa481f ("net: socket: set sock->sk to NULL after cal
- CVE-2023-52607Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: powerpc/mm: Fix null-pointer dereference in pgtable_cache_add kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. Ensure the allocation was successful by checking the p
- CVE-2023-52606Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: powerpc/lib: Validate size for vector operations Some of the fp/vmx code in sstep.c assume a certain maximum size for the instructions being emulated. The size of those operations however is determined separate
- CVE-2023-52604Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree Syzkaller reported the following issue: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:2867:6 index 196694 is out of range for type 's8[1365]' (aka 's
- CVE-2023-52603Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is
- CVE-2023-52602Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: jfs: fix slab-out-of-bounds Read in dtSearch Currently while searching for current page in the sorted entry table of the page there is a out of bound access. Added a bound check to fix the error. Dave: Set ret
- CVE-2023-52601Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: jfs: fix array-index-out-of-bounds in dbAdjTree Currently there is a bound check missing in the dbAdjTree while accessing the dmt_stree. To add the required check added the bool is_ctl which is required to dete
- CVE-2023-52600Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls
- CVE-2023-52599Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: jfs: fix array-index-out-of-bounds in diNewExt [Syz report] UBSAN: array-index-out-of-bounds in fs/jfs/jfs_imap.c:2360:2 index -878706688 is out of range for type 'struct iagctl[128]' CPU: 1 PID: 5065 Comm: syz
- CVE-2023-52598Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: s390/ptrace: handle setting of fpc register correctly If the content of the floating point control (fpc) register of a traced process is modified with the ptrace interface the new value is tested for validity b
- CVE-2023-52597Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: KVM: s390: fix setting of fpc register kvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control (fpc) register of a guest cpu. The new value is tested for validity by temporarily loading it into t
- CVE-2023-52595Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: wifi: rt2x00: restart beacon queue when hardware reset When a hardware reset is triggered, all registers are reset, so all queues are forced to stop in hardware interface. However, mac80211 will not automatical
- CVE-2023-52594Mar 6, 2024affected < 5.14.21-150500.55.59.1fixed 5.14.21-150500.55.59.1
In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() Fix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug occurs when txs->cnt, data from a URB provided by a USB d
Page 83 of 101