rpm package
suse/kernel-rt&distro=SUSE Linux Enterprise Micro 5.2
pkg:rpm/suse/kernel-rt&distro=SUSE%20Linux%20Enterprise%20Micro%205.2
Vulnerabilities (1,678)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2022-50344 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 16, 2025 | In the Linux kernel, the following vulnerability has been resolved: ext4: fix null-ptr-deref in ext4_write_info I caught a null-ptr-deref bug as follows: ================================================================== KASAN: null-ptr-deref in range [0x0000000000000068-0x0000 | ||
| CVE-2025-39823 | Hig | 7.8 | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 16, 2025 | In the Linux kernel, the following vulnerability has been resolved: KVM: x86: use array_index_nospec with indices that come from guest min and dest_id are guest-controlled indices. Using array_index_nospec() after the bounds checks clamps these values to mitigate speculative ex | |
| CVE-2023-53282 | — | < 5.3.18-150300.226.1 | 5.3.18-150300.226.1 | Sep 16, 2025 | In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write During the sysfs firmware write process, a use-after-free read warning is logged from the lpfc_wr_object() routine: BUG: KFENCE: us | ||
| CVE-2023-53273 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 16, 2025 | In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channel() assumes vmbus channel array to be allocated when called. However, in cases such as kdump/kexec, not all relids will be reset | ||
| CVE-2023-53265 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 16, 2025 | In the Linux kernel, the following vulnerability has been resolved: ubi: ensure that VID header offset + VID header size <= alloc, size Ensure that the VID header offset + VID header size does not exceed the allocated area to avoid slab OOB. BUG: KASAN: slab-out-of-bounds in c | ||
| CVE-2022-50334 | — | < 5.3.18-150300.226.1 | 5.3.18-150300.226.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() Syzkaller reports a null-ptr-deref bug as follows: ====================================================== KASAN: null-ptr-deref in range [0x0000000000000 | ||
| CVE-2022-50330 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: crypto: cavium - prevent integer overflow loading firmware The "code_length" value comes from the firmware file. If your firmware is untrusted realistically there is probably very little you can do to protect | ||
| CVE-2022-50329 | — | < 5.3.18-150300.235.1 | 5.3.18-150300.235.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq Commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq->bic'") will access 'bic->bfqq' in bic_set_bfqq(), however, bfq_exit_icq_bfqq() can free bfqq first | ||
| CVE-2022-50327 | — | < 5.3.18-150300.226.1 | 5.3.18-150300.226.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value The return value of acpi_fetch_acpi_dev() could be NULL, which would cause a NULL pointer dereference to occur in acpi_device_hid(). [ rjw: Subje | ||
| CVE-2022-50317 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/bridge: megachips: Fix a null pointer dereference bug When removing the module we will get the following warning: [ 31.911505] i2c-core: driver [stdp2690-ge-b850v3-fw] unregistered [ 31.912484] general | ||
| CVE-2023-53254 | — | < 5.3.18-150300.232.1 | 5.3.18-150300.232.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: cacheinfo: Fix shared_cpu_map to handle shared caches at different levels The cacheinfo sets up the shared_cpu_map by checking whether the caches with the same index are shared between CPUs. However, this will | ||
| CVE-2022-50312 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: drivers: serial: jsm: fix some leaks in probe This error path needs to unwind instead of just returning directly. | ||
| CVE-2022-50309 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: media: xilinx: vipp: Fix refcount leak in xvip_graph_dma_init of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_nod | ||
| CVE-2022-50299 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: md: Replace snprintf with scnprintf Current code produces a warning as shown below when total characters in the constituent block device names plus the slashes exceeds 200. snprintf() returns the number of char | ||
| CVE-2023-53215 | — | < 5.3.18-150300.232.1 | 5.3.18-150300.232.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: sched/fair: Don't balance task to its current running CPU We've run into the case that the balancer tries to balance a migration disabled task and trigger the warning in set_task_cpu() like below: ----------- | ||
| CVE-2023-53213 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() Fix a slab-out-of-bounds read that occurs in kmemdup() called from brcmf_get_assoc_ies(). The bug could occur when assoc_info->req_len, data from | ||
| CVE-2022-50282 | — | < 5.3.18-150300.232.1 | 5.3.18-150300.232.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: chardev: fix error handling in cdev_device_add() While doing fault injection test, I got the following report: ------------[ cut here ]------------ kobject: '(null)' (0000000039956980): is not initialized, yet | ||
| CVE-2022-50280 | — | < 5.3.18-150300.229.2 | 5.3.18-150300.229.2 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: pnode: terminate at peers of source The propagate_mnt() function handles mount propagation when creating mounts and propagates the source mount tree @source_mnt to all applicable nodes of the destination propag | ||
| CVE-2022-50272 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer() Wei Chen reports a kernel bug as blew: general protection fault, probably for non-canonical address KASAN: null-ptr-deref in range [0x00000000000 | ||
| CVE-2022-50271 | — | < 5.3.18-150300.223.1 | 5.3.18-150300.223.1 | Sep 15, 2025 | In the Linux kernel, the following vulnerability has been resolved: vhost/vsock: Use kvmalloc/kvfree for larger packets. When copying a large file over sftp over vsock, data size is usually 32kB, and kmalloc seems to fail to try to allocate 32 32kB regions. vhost-5837: page a |
- CVE-2022-50344Sep 16, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: ext4: fix null-ptr-deref in ext4_write_info I caught a null-ptr-deref bug as follows: ================================================================== KASAN: null-ptr-deref in range [0x0000000000000068-0x0000
- affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: use array_index_nospec with indices that come from guest min and dest_id are guest-controlled indices. Using array_index_nospec() after the bounds checks clamps these values to mitigate speculative ex
- CVE-2023-53282Sep 16, 2025affected < 5.3.18-150300.226.1fixed 5.3.18-150300.226.1
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write During the sysfs firmware write process, a use-after-free read warning is logged from the lpfc_wr_object() routine: BUG: KFENCE: us
- CVE-2023-53273Sep 16, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channel() assumes vmbus channel array to be allocated when called. However, in cases such as kdump/kexec, not all relids will be reset
- CVE-2023-53265Sep 16, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: ubi: ensure that VID header offset + VID header size <= alloc, size Ensure that the VID header offset + VID header size does not exceed the allocated area to avoid slab OOB. BUG: KASAN: slab-out-of-bounds in c
- CVE-2022-50334Sep 15, 2025affected < 5.3.18-150300.226.1fixed 5.3.18-150300.226.1
In the Linux kernel, the following vulnerability has been resolved: hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() Syzkaller reports a null-ptr-deref bug as follows: ====================================================== KASAN: null-ptr-deref in range [0x0000000000000
- CVE-2022-50330Sep 15, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: crypto: cavium - prevent integer overflow loading firmware The "code_length" value comes from the firmware file. If your firmware is untrusted realistically there is probably very little you can do to protect
- CVE-2022-50329Sep 15, 2025affected < 5.3.18-150300.235.1fixed 5.3.18-150300.235.1
In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq Commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq->bic'") will access 'bic->bfqq' in bic_set_bfqq(), however, bfq_exit_icq_bfqq() can free bfqq first
- CVE-2022-50327Sep 15, 2025affected < 5.3.18-150300.226.1fixed 5.3.18-150300.226.1
In the Linux kernel, the following vulnerability has been resolved: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value The return value of acpi_fetch_acpi_dev() could be NULL, which would cause a NULL pointer dereference to occur in acpi_device_hid(). [ rjw: Subje
- CVE-2022-50317Sep 15, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: drm/bridge: megachips: Fix a null pointer dereference bug When removing the module we will get the following warning: [ 31.911505] i2c-core: driver [stdp2690-ge-b850v3-fw] unregistered [ 31.912484] general
- CVE-2023-53254Sep 15, 2025affected < 5.3.18-150300.232.1fixed 5.3.18-150300.232.1
In the Linux kernel, the following vulnerability has been resolved: cacheinfo: Fix shared_cpu_map to handle shared caches at different levels The cacheinfo sets up the shared_cpu_map by checking whether the caches with the same index are shared between CPUs. However, this will
- CVE-2022-50312Sep 15, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: drivers: serial: jsm: fix some leaks in probe This error path needs to unwind instead of just returning directly.
- CVE-2022-50309Sep 15, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: media: xilinx: vipp: Fix refcount leak in xvip_graph_dma_init of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_nod
- CVE-2022-50299Sep 15, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: md: Replace snprintf with scnprintf Current code produces a warning as shown below when total characters in the constituent block device names plus the slashes exceeds 200. snprintf() returns the number of char
- CVE-2023-53215Sep 15, 2025affected < 5.3.18-150300.232.1fixed 5.3.18-150300.232.1
In the Linux kernel, the following vulnerability has been resolved: sched/fair: Don't balance task to its current running CPU We've run into the case that the balancer tries to balance a migration disabled task and trigger the warning in set_task_cpu() like below: -----------
- CVE-2023-53213Sep 15, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() Fix a slab-out-of-bounds read that occurs in kmemdup() called from brcmf_get_assoc_ies(). The bug could occur when assoc_info->req_len, data from
- CVE-2022-50282Sep 15, 2025affected < 5.3.18-150300.232.1fixed 5.3.18-150300.232.1
In the Linux kernel, the following vulnerability has been resolved: chardev: fix error handling in cdev_device_add() While doing fault injection test, I got the following report: ------------[ cut here ]------------ kobject: '(null)' (0000000039956980): is not initialized, yet
- CVE-2022-50280Sep 15, 2025affected < 5.3.18-150300.229.2fixed 5.3.18-150300.229.2
In the Linux kernel, the following vulnerability has been resolved: pnode: terminate at peers of source The propagate_mnt() function handles mount propagation when creating mounts and propagates the source mount tree @source_mnt to all applicable nodes of the destination propag
- CVE-2022-50272Sep 15, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer() Wei Chen reports a kernel bug as blew: general protection fault, probably for non-canonical address KASAN: null-ptr-deref in range [0x00000000000
- CVE-2022-50271Sep 15, 2025affected < 5.3.18-150300.223.1fixed 5.3.18-150300.223.1
In the Linux kernel, the following vulnerability has been resolved: vhost/vsock: Use kvmalloc/kvfree for larger packets. When copying a large file over sftp over vsock, data size is usually 32kB, and kmalloc seems to fail to try to allocate 32 32kB regions. vhost-5837: page a
Page 9 of 84