rpm package
suse/kernel-default-base&distro=SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
pkg:rpm/suse/kernel-default-base&distro=SUSE%20Linux%20Enterprise%20High%20Performance%20Computing%2015%20SP4-LTSS
Vulnerabilities (2,843)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-49945 | Med | 5.5 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net/ncsi: Disable the ncsi work before freeing the associated structure The work function can run after the ncsi device is freed, resulting in use-after-free bugs or kernel panic. | |
| CVE-2024-49936 | Hig | 8.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net/xen-netback: prevent UAF in xenvif_flush_hash() During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is call | |
| CVE-2024-49930 | Hig | 8.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix array out-of-bound access in SoC stats Currently, the ath11k_soc_dp_stats::hal_reo_error array is defined with a maximum size of DP_REO_DST_RING_MAX. However, the ath11k_dp_process_rx() functi | |
| CVE-2024-49925 | Hig | 7.1 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: fbdev: efifb: Register sysfs groups through driver core The driver core can register and cleanup sysfs groups already. Make use of that functionality to simplify the error handling and cleanup. Also avoid a UA | |
| CVE-2024-49867 | Hig | 7.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the k | |
| CVE-2024-49860 | Hig | 7.3 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: ACPI: sysfs: validate return type of _STR method Only buffer objects are valid return values of _STR. If something else is returned description_show() will access invalid memory. | |
| CVE-2024-47757 | Hig | 7.1 | < 5.14.21-150400.24.144.1.150400.24.70.1 | 5.14.21-150400.24.144.1.150400.24.70.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential oob read in nilfs_btree_check_delete() The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory acc | |
| CVE-2024-47748 | Hig | 7.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don't know if the token pointer is still valid or | |
| CVE-2024-47747 | Hig | 7.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition In the ether3_probe function, a timer is initialized with a callback function ether3_ledoff, bound to &prev(dev)->timer. Once t | |
| CVE-2024-47706 | Hig | 7.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix possible UAF for bfqq->bic with merge chain 1) initial state, three tasks: Process 1 Process 2 Process 3 (BIC1) (BIC2) (BIC3) | Λ | Λ | Λ | | | |
| CVE-2024-47684 | Med | 5.5 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: tcp: check skb is non-NULL in tcp_rto_delta_us() We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_r | |
| CVE-2024-47674 | Hig | 7.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 15, 2024 | In the Linux kernel, the following vulnerability has been resolved: mm: avoid leaving partial pfn mappings around in error case As Jann points out, PFN mappings are special, because unlike normal memory mappings, there is no lifetime information associated with the mapping - it | |
| CVE-2024-47668 | Hig | 7.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Oct 9, 2024 | In the Linux kernel, the following vulnerability has been resolved: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() If we need to increase the tree depth, allocate a new node, and then race with another thread that increased the tree depth before us, we'll sti | |
| CVE-2024-46854 | Hig | 7.1 | < 5.14.21-150400.24.194.1.150400.24.98.3 | 5.14.21-150400.24.194.1.150400.24.98.3 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: dpaa: Pad packets to ETH_ZLEN When sending packets under 60 bytes, up to three bytes of the buffer following the data may be leaked. Avoid this by extending all packets to ETH_ZLEN, ensuring nothing is lea | |
| CVE-2024-46849 | Hig | 7.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: ASoC: meson: axg-card: fix 'use-after-free' Buffer 'card->dai_link' is reallocated in 'meson_card_reallocate_links()', so move 'pad' pointer initialization after this function when memory is already reallocated | |
| CVE-2024-46818 | Hig | 7.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check gpio_id before used as array index [WHY & HOW] GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore should be checked in advance. This fixes 5 OVERRUN issues reported | |
| CVE-2024-46817 | Hig | 7.4 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 [Why] Coverity reports OVERRUN warning. Should abort amdgpu_dm initialize. [How] Return failure to amdgpu_dm_init. | |
| CVE-2024-46816 | Hig | 7.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links [Why] Coverity report OVERRUN warning. There are only max_links elements within dc->links. link count could up to AMDGPU_DM_MAX_D | |
| CVE-2024-46815 | Hig | 7.1 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] [WHY & HOW] num_valid_sets needs to be checked to avoid a negative index when accessing reader_wm_sets[num_valid_sets - 1]. This fixes an | |
| CVE-2024-46814 | Hig | 7.8 | < 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 | Sep 27, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check msg_id before processing transcation [WHY & HOW] HDCP_MESSAGE_ID_INVALID (-1) is not a valid msg_id nor is it a valid array index, and it needs checking before used. This fixes 4 OVERRUN |
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: net/ncsi: Disable the ncsi work before freeing the associated structure The work function can run after the ncsi device is freed, resulting in use-after-free bugs or kernel panic.
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: net/xen-netback: prevent UAF in xenvif_flush_hash() During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is call
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix array out-of-bound access in SoC stats Currently, the ath11k_soc_dp_stats::hal_reo_error array is defined with a maximum size of DP_REO_DST_RING_MAX. However, the ath11k_dp_process_rx() functi
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: fbdev: efifb: Register sysfs groups through driver core The driver core can register and cleanup sysfs groups already. Make use of that functionality to simplify the error handling and cleanup. Also avoid a UA
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the k
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: ACPI: sysfs: validate return type of _STR method Only buffer objects are valid return values of _STR. If something else is returned description_show() will access invalid memory.
- affected < 5.14.21-150400.24.144.1.150400.24.70.1fixed 5.14.21-150400.24.144.1.150400.24.70.1
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential oob read in nilfs_btree_check_delete() The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory acc
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don't know if the token pointer is still valid or
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition In the ether3_probe function, a timer is initialized with a callback function ether3_ledoff, bound to &prev(dev)->timer. Once t
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix possible UAF for bfqq->bic with merge chain 1) initial state, three tasks: Process 1 Process 2 Process 3 (BIC1) (BIC2) (BIC3) | Λ | Λ | Λ | |
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: tcp: check skb is non-NULL in tcp_rto_delta_us() We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_r
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: mm: avoid leaving partial pfn mappings around in error case As Jann points out, PFN mappings are special, because unlike normal memory mappings, there is no lifetime information associated with the mapping - it
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() If we need to increase the tree depth, allocate a new node, and then race with another thread that increased the tree depth before us, we'll sti
- affected < 5.14.21-150400.24.194.1.150400.24.98.3fixed 5.14.21-150400.24.194.1.150400.24.98.3
In the Linux kernel, the following vulnerability has been resolved: net: dpaa: Pad packets to ETH_ZLEN When sending packets under 60 bytes, up to three bytes of the buffer following the data may be leaked. Avoid this by extending all packets to ETH_ZLEN, ensuring nothing is lea
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: ASoC: meson: axg-card: fix 'use-after-free' Buffer 'card->dai_link' is reallocated in 'meson_card_reallocate_links()', so move 'pad' pointer initialization after this function when memory is already reallocated
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check gpio_id before used as array index [WHY & HOW] GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore should be checked in advance. This fixes 5 OVERRUN issues reported
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 [Why] Coverity reports OVERRUN warning. Should abort amdgpu_dm initialize. [How] Return failure to amdgpu_dm_init.
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links [Why] Coverity report OVERRUN warning. There are only max_links elements within dc->links. link count could up to AMDGPU_DM_MAX_D
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] [WHY & HOW] num_valid_sets needs to be checked to avoid a negative index when accessing reader_wm_sets[num_valid_sets - 1]. This fixes an
- affected < 5.14.21-150400.24.141.1.150400.24.68.2fixed 5.14.21-150400.24.141.1.150400.24.68.2
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check msg_id before processing transcation [WHY & HOW] HDCP_MESSAGE_ID_INVALID (-1) is not a valid msg_id nor is it a valid array index, and it needs checking before used. This fixes 4 OVERRUN
Page 97 of 143