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-2022-49442 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: drivers/base/node.c: fix compaction sysfs file leak Compaction sysfs file is created via compaction_register_node in register_node. But we forgot to remove it in unregister_node. Thus compaction sysfs file is | |
| CVE-2022-49441 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print failure message. This can cause a deadlock in the scenario reported b | |
| CVE-2022-49440 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: powerpc/rtas: Keep MSR[RI] set when calling RTAS RTAS runs in real mode (MSR[DR] and MSR[IR] unset) and in 32-bit big endian mode (MSR[SF,LE] unset). The change in MSR is done in enter_rtas() in a relatively c | |
| CVE-2022-49438 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: Input: sparcspkr - fix refcount leak in bbc_beep_probe of_find_node_by_path() calls of_find_node_opts_by_path(), which returns a node pointer with refcount incremented, we should use of_node_put() on it when do | |
| CVE-2022-49437 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: powerpc/xive: Fix refcount leak in xive_spapr_init of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid ref | |
| CVE-2022-49435 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: mfd: davinci_voicecodec: Fix possible null-ptr-deref davinci_vc_probe() It will cause null-ptr-deref when using 'res', if platform_get_resource() returns NULL, so move using 'res' after devm_ioremap_resource() | |
| CVE-2022-49434 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store() The sysfs sriov_numvfs_store() path acquires the device lock before the config space access lock: sriov_numvfs_store device_lock | |
| CVE-2022-49433 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent use of lock before it is initialized If there is a failure during probe of hfi1 before the sdma_map_lock is initialized, the call to hfi1_free_devdata() will attempt to use a lock that has no | |
| CVE-2022-49432 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: powerpc/xics: fix refcount leak in icp_opal_init() The of_find_compatible_node() function returns a node pointer with refcount incremented, use of_node_put() on it when done. | |
| CVE-2022-49431 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: powerpc/iommu: Add missing of_node_put in iommu_init_early_dart The device_node pointer is returned by of_find_compatible_node with refcount incremented. We should use of_node_put() to avoid the refcount leak. | |
| CVE-2022-49430 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: Input: gpio-keys - cancel delayed work only in case of GPIO gpio_keys module can either accept gpios or interrupts. The module initializes delayed work in case of gpios only and is only used if debounce timer i | |
| CVE-2022-49429 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent panic when SDMA is disabled If the hfi1 module is loaded with HFI1_CAP_SDMA off, a call to hfi1_write_iter() will dereference a NULL pointer and panic. A typical stack frame is: sdma_selec | |
| CVE-2022-49427 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Remove clk_disable in mtk_iommu_remove After the commit b34ea31fe013 ("iommu/mediatek: Always enable the clk on resume"), the iommu clock is controlled by the runtime callback. thus remove the c | |
| CVE-2022-49426 | Hig | 7.8 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3-sva: Fix mm use-after-free We currently call arm64_mm_context_put() without holding a reference to the mm, which can result in use-after-free. Call mmgrab()/mmdrop() to ensure the mm only gets | |
| CVE-2022-49424 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Fix NULL pointer dereference when printing dev_name When larbdev is NULL (in the case I hit, the node is incorrectly set iommus = <&iommu NUM>), it will cause device_link_add() fail and kernel c | |
| CVE-2022-49422 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix the error handling path in idxd_cdev_register() If a call to alloc_chrdev_region() fails, the already allocated resources are leaking. Add the needed error handling path to fix the leak. | |
| CVE-2022-49421 | Med | 5.5 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: video: fbdev: clcdfb: Fix refcount leak in clcdfb_of_vram_setup of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node | |
| CVE-2022-49418 | Cri | 9.8 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: NFSv4: Fix free of uninitialized nfs4_label on referral lookup. Send along the already-allocated fattr along with nfs4_fs_locations, and drop the memcpy of fattr. We end up growing two more allocations, but th | |
| CVE-2022-49416 | Hig | 8.8 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix use-after-free in chanctx code In ieee80211_vif_use_reserved_context(), when we have an old context and the new context's replace_state is set to IEEE80211_CHANCTX_REPLACE_NONE, we free the | |
| CVE-2022-49414 | Med | 4.7 | < 5.14.21-150400.24.158.1.150400.24.78.1 | 5.14.21-150400.24.158.1.150400.24.78.1 | Feb 26, 2025 | In the Linux kernel, the following vulnerability has been resolved: ext4: fix race condition between ext4_write and ext4_convert_inline_data Hulk Robot reported a BUG_ON: ================================================================== EXT4-fs error (device loop3): ext4_mb_ |
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: drivers/base/node.c: fix compaction sysfs file leak Compaction sysfs file is created via compaction_register_node in register_node. But we forgot to remove it in unregister_node. Thus compaction sysfs file is
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print failure message. This can cause a deadlock in the scenario reported b
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: powerpc/rtas: Keep MSR[RI] set when calling RTAS RTAS runs in real mode (MSR[DR] and MSR[IR] unset) and in 32-bit big endian mode (MSR[SF,LE] unset). The change in MSR is done in enter_rtas() in a relatively c
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: Input: sparcspkr - fix refcount leak in bbc_beep_probe of_find_node_by_path() calls of_find_node_opts_by_path(), which returns a node pointer with refcount incremented, we should use of_node_put() on it when do
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: powerpc/xive: Fix refcount leak in xive_spapr_init of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid ref
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: mfd: davinci_voicecodec: Fix possible null-ptr-deref davinci_vc_probe() It will cause null-ptr-deref when using 'res', if platform_get_resource() returns NULL, so move using 'res' after devm_ioremap_resource()
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store() The sysfs sriov_numvfs_store() path acquires the device lock before the config space access lock: sriov_numvfs_store device_lock
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent use of lock before it is initialized If there is a failure during probe of hfi1 before the sdma_map_lock is initialized, the call to hfi1_free_devdata() will attempt to use a lock that has no
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: powerpc/xics: fix refcount leak in icp_opal_init() The of_find_compatible_node() function returns a node pointer with refcount incremented, use of_node_put() on it when done.
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: powerpc/iommu: Add missing of_node_put in iommu_init_early_dart The device_node pointer is returned by of_find_compatible_node with refcount incremented. We should use of_node_put() to avoid the refcount leak.
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: Input: gpio-keys - cancel delayed work only in case of GPIO gpio_keys module can either accept gpios or interrupts. The module initializes delayed work in case of gpios only and is only used if debounce timer i
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent panic when SDMA is disabled If the hfi1 module is loaded with HFI1_CAP_SDMA off, a call to hfi1_write_iter() will dereference a NULL pointer and panic. A typical stack frame is: sdma_selec
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Remove clk_disable in mtk_iommu_remove After the commit b34ea31fe013 ("iommu/mediatek: Always enable the clk on resume"), the iommu clock is controlled by the runtime callback. thus remove the c
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3-sva: Fix mm use-after-free We currently call arm64_mm_context_put() without holding a reference to the mm, which can result in use-after-free. Call mmgrab()/mmdrop() to ensure the mm only gets
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Fix NULL pointer dereference when printing dev_name When larbdev is NULL (in the case I hit, the node is incorrectly set iommus = <&iommu NUM>), it will cause device_link_add() fail and kernel c
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix the error handling path in idxd_cdev_register() If a call to alloc_chrdev_region() fails, the already allocated resources are leaking. Add the needed error handling path to fix the leak.
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: clcdfb: Fix refcount leak in clcdfb_of_vram_setup of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: NFSv4: Fix free of uninitialized nfs4_label on referral lookup. Send along the already-allocated fattr along with nfs4_fs_locations, and drop the memcpy of fattr. We end up growing two more allocations, but th
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix use-after-free in chanctx code In ieee80211_vif_use_reserved_context(), when we have an old context and the new context's replace_state is set to IEEE80211_CHANCTX_REPLACE_NONE, we free the
- affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1
In the Linux kernel, the following vulnerability has been resolved: ext4: fix race condition between ext4_write and ext4_convert_inline_data Hulk Robot reported a BUG_ON: ================================================================== EXT4-fs error (device loop3): ext4_mb_
Page 75 of 143