rpm package
suse/kernel-source-azure&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP6
pkg:rpm/suse/kernel-source-azure&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Public%20Cloud%2015%20SP6
Vulnerabilities (3,769)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-52751 | Hig | 7.8 | < 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free in smb2_query_info_compound() The following UAF was triggered when running fstests generic/072 with KASAN enabled against Windows Server 2022 and mount options 'multichannel,max_ | |
| CVE-2023-52750 | Med | 5.5 | < 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: arm64: Restrict CPU_BIG_ENDIAN to GNU as or LLVM IAS 15.x or newer Prior to LLVM 15.0.0, LLVM's integrated assembler would incorrectly byte-swap NOP when compiling for big-endian, and the resulting series of by | |
| CVE-2023-52749 | Med | 4.7 | < 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: spi: Fix null dereference on suspend A race condition exists where a synchronous (noqueue) transfer can be active during a system suspend. This can cause a null pointer dereference exception to occur when the s | |
| CVE-2023-52735 | Cri | 9.1 | < 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself sock_map proto callbacks should never call themselves by design. Protect against bugs like [1] and break out of the recursive loop to avoid a | |
| CVE-2021-47432 | Med | 5.5 | < 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: lib/generic-radix-tree.c: Don't overflow in peek() When we started spreading new inode numbers throughout most of the 64 bit inode space, that triggered some corner case bugs, in particular some integer overflo | |
| CVE-2024-36009 | Hig | 7.8 | < 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: ax25: Fix netdev refcount issue The dev_tracker is added to ax25_cb in ax25_bind(). When the ax25 device is detaching, the dev_tracker of ax25_cb should be deallocated in ax25_kill_by_device() instead of the de | |
| CVE-2024-36008 | Med | 5.5 | < 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: ipv4: check for NULL idev in ip_route_use_hint() syzbot was able to trigger a NULL deref in fib_validate_source() in an old tree [1]. It appears the bug exists in latest trees. All calls to __in_dev_get_rcu() | |
| CVE-2024-36007 | Hig | 7.8 | < 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix warning during rehash As previously explained, the rehash delayed work migrates filters from one region to another. This is done by iterating over all chunks (all the filters with | |
| CVE-2024-36006 | Med | 5.5 | < 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix incorrect list API usage Both the function that migrates all the chunks within a region and the function that migrates all the entries within a chunk call list_first_entry() on the | |
| CVE-2024-36005 | Med | 5.5 | < 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: honor table dormant flag from netdev release event path Check for table dormant flag otherwise netdev release event path tries to unregister an already unregistered hook. [524854.857999] | |
| CVE-2024-36004 | Med | 5.5 | < 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: i40e: Do not use WQ_MEM_RECLAIM flag for workqueue Issue reported by customer during SRIOV testing, call trace: When both i40e and the i40iw driver are loaded, a warning in check_flush_dependency is being trigg | |
| CVE-2024-36003 | Med | 5.5 | < 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: ice: fix LAG and VF lock dependency in ice_reset_vf() 9f74a3dfcf83 ("ice: Fix VF Reset paths when interface in a failed over aggregate"), the ice driver has acquired the LAG mutex in ice_reset_vf(). The commit | |
| CVE-2024-36002 | Med | 5.5 | < 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: dpll: fix dpll_pin_on_pin_register() for multiple parent pins In scenario where pin is registered with multiple parent pins via dpll_pin_on_pin_register(..), all belonging to the same dpll device. A second call | |
| CVE-2024-36000 | Med | 5.5 | < 6.4.0-150600.8.20.1 | 6.4.0-150600.8.20.1 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix missing hugetlb_lock for resv uncharge There is a recent report on UFFDIO_COPY over hugetlb: https://lore.kernel.org/all/[email protected]/ 350: lockdep_assert_held(&huge | |
| CVE-2024-35999 | Hig | 7.5 | < 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: smb3: missing lock when picking channel Coverity spotted a place where we should have been holding the channel lock when accessing the ses channel index. Addresses-Coverity: 1582039 ("Data race condition (MISS | |
| CVE-2024-35998 | Hig | 7.5 | < 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: smb3: fix lock ordering potential deadlock in cifs_sync_mid_result Coverity spotted that the cifs_sync_mid_result function could deadlock "Thread deadlock (ORDER_REVERSAL) lock_order: Calling spin_lock acquire | |
| CVE-2024-35997 | Med | 5.5 | < 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up The flag I2C_HID_READ_PENDING is used to serialize I2C operations. However, this is not necessary, because I2C core already has its own locking | |
| CVE-2024-35995 | Med | 5.5 | < 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Use access_width over bit_width for system memory accesses To align with ACPI 6.3+, since bit_width can be any 8-bit value, it cannot be depended on to be always on a clean 8b boundary. This was unc | |
| CVE-2024-35992 | Med | 5.5 | < 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: phy: marvell: a3700-comphy: Fix out of bounds read There is an out of bounds read access of 'gbe_phy_init_fix[fix_idx].addr' every iteration after 'fix_idx' reaches 'ARRAY_SIZE(gbe_phy_init_fix)'. Make sure 'g | |
| CVE-2024-35991 | Med | 5.5 | < 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 | May 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Convert spinlock to mutex to lock evl workqueue drain_workqueue() cannot be called safely in a spinlocked context due to possible task rescheduling. In the multi-task scenario, calling queue_wo |
- affected < 6.4.0-150600.8.8.2fixed 6.4.0-150600.8.8.2
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free in smb2_query_info_compound() The following UAF was triggered when running fstests generic/072 with KASAN enabled against Windows Server 2022 and mount options 'multichannel,max_
- affected < 6.4.0-150600.8.8.2fixed 6.4.0-150600.8.8.2
In the Linux kernel, the following vulnerability has been resolved: arm64: Restrict CPU_BIG_ENDIAN to GNU as or LLVM IAS 15.x or newer Prior to LLVM 15.0.0, LLVM's integrated assembler would incorrectly byte-swap NOP when compiling for big-endian, and the resulting series of by
- affected < 6.4.0-150600.8.8.2fixed 6.4.0-150600.8.8.2
In the Linux kernel, the following vulnerability has been resolved: spi: Fix null dereference on suspend A race condition exists where a synchronous (noqueue) transfer can be active during a system suspend. This can cause a null pointer dereference exception to occur when the s
- affected < 6.4.0-150600.8.8.2fixed 6.4.0-150600.8.8.2
In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself sock_map proto callbacks should never call themselves by design. Protect against bugs like [1] and break out of the recursive loop to avoid a
- affected < 6.4.0-150600.8.8.2fixed 6.4.0-150600.8.8.2
In the Linux kernel, the following vulnerability has been resolved: lib/generic-radix-tree.c: Don't overflow in peek() When we started spreading new inode numbers throughout most of the 64 bit inode space, that triggered some corner case bugs, in particular some integer overflo
- affected < 6.4.0-150600.8.5.4fixed 6.4.0-150600.8.5.4
In the Linux kernel, the following vulnerability has been resolved: ax25: Fix netdev refcount issue The dev_tracker is added to ax25_cb in ax25_bind(). When the ax25 device is detaching, the dev_tracker of ax25_cb should be deallocated in ax25_kill_by_device() instead of the de
- affected < 6.4.0-150600.8.8.2fixed 6.4.0-150600.8.8.2
In the Linux kernel, the following vulnerability has been resolved: ipv4: check for NULL idev in ip_route_use_hint() syzbot was able to trigger a NULL deref in fib_validate_source() in an old tree [1]. It appears the bug exists in latest trees. All calls to __in_dev_get_rcu()
- affected < 6.4.0-150600.8.5.4fixed 6.4.0-150600.8.5.4
In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix warning during rehash As previously explained, the rehash delayed work migrates filters from one region to another. This is done by iterating over all chunks (all the filters with
- affected < 6.4.0-150600.8.5.4fixed 6.4.0-150600.8.5.4
In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix incorrect list API usage Both the function that migrates all the chunks within a region and the function that migrates all the entries within a chunk call list_first_entry() on the
- affected < 6.4.0-150600.8.8.2fixed 6.4.0-150600.8.8.2
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: honor table dormant flag from netdev release event path Check for table dormant flag otherwise netdev release event path tries to unregister an already unregistered hook. [524854.857999]
- affected < 6.4.0-150600.8.8.2fixed 6.4.0-150600.8.8.2
In the Linux kernel, the following vulnerability has been resolved: i40e: Do not use WQ_MEM_RECLAIM flag for workqueue Issue reported by customer during SRIOV testing, call trace: When both i40e and the i40iw driver are loaded, a warning in check_flush_dependency is being trigg
- affected < 6.4.0-150600.8.8.2fixed 6.4.0-150600.8.8.2
In the Linux kernel, the following vulnerability has been resolved: ice: fix LAG and VF lock dependency in ice_reset_vf() 9f74a3dfcf83 ("ice: Fix VF Reset paths when interface in a failed over aggregate"), the ice driver has acquired the LAG mutex in ice_reset_vf(). The commit
- affected < 6.4.0-150600.8.5.4fixed 6.4.0-150600.8.5.4
In the Linux kernel, the following vulnerability has been resolved: dpll: fix dpll_pin_on_pin_register() for multiple parent pins In scenario where pin is registered with multiple parent pins via dpll_pin_on_pin_register(..), all belonging to the same dpll device. A second call
- affected < 6.4.0-150600.8.20.1fixed 6.4.0-150600.8.20.1
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix missing hugetlb_lock for resv uncharge There is a recent report on UFFDIO_COPY over hugetlb: https://lore.kernel.org/all/[email protected]/ 350: lockdep_assert_held(&huge
- affected < 6.4.0-150600.8.5.4fixed 6.4.0-150600.8.5.4
In the Linux kernel, the following vulnerability has been resolved: smb3: missing lock when picking channel Coverity spotted a place where we should have been holding the channel lock when accessing the ses channel index. Addresses-Coverity: 1582039 ("Data race condition (MISS
- affected < 6.4.0-150600.8.8.2fixed 6.4.0-150600.8.8.2
In the Linux kernel, the following vulnerability has been resolved: smb3: fix lock ordering potential deadlock in cifs_sync_mid_result Coverity spotted that the cifs_sync_mid_result function could deadlock "Thread deadlock (ORDER_REVERSAL) lock_order: Calling spin_lock acquire
- affected < 6.4.0-150600.8.5.4fixed 6.4.0-150600.8.5.4
In the Linux kernel, the following vulnerability has been resolved: HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up The flag I2C_HID_READ_PENDING is used to serialize I2C operations. However, this is not necessary, because I2C core already has its own locking
- affected < 6.4.0-150600.8.5.4fixed 6.4.0-150600.8.5.4
In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Use access_width over bit_width for system memory accesses To align with ACPI 6.3+, since bit_width can be any 8-bit value, it cannot be depended on to be always on a clean 8b boundary. This was unc
- affected < 6.4.0-150600.8.5.4fixed 6.4.0-150600.8.5.4
In the Linux kernel, the following vulnerability has been resolved: phy: marvell: a3700-comphy: Fix out of bounds read There is an out of bounds read access of 'gbe_phy_init_fix[fix_idx].addr' every iteration after 'fix_idx' reaches 'ARRAY_SIZE(gbe_phy_init_fix)'. Make sure 'g
- affected < 6.4.0-150600.8.5.4fixed 6.4.0-150600.8.5.4
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Convert spinlock to mutex to lock evl workqueue drain_workqueue() cannot be called safely in a spinlocked context due to possible task rescheduling. In the multi-task scenario, calling queue_wo
Page 163 of 189