rpm package
suse/kernel-rt&distro=SUSE Linux Enterprise Micro 5.4
pkg:rpm/suse/kernel-rt&distro=SUSE%20Linux%20Enterprise%20Micro%205.4
Vulnerabilities (2,965)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-53396 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix memory leak in do_rename If renaming a file in an encrypted directory, function fscrypt_setup_filename allocates memory for a file name. This name is never used, and before returning to the caller th | ||
| CVE-2023-53395 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer ACPICA commit 90310989a0790032f5a0140741ff09b545af4bc5 According to the ACPI specification 19.6.134, no argument is required to be passed for ASL Timer instruct | ||
| CVE-2023-53393 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_ib_get_hw_stats when used for device Currently, when mlx5_ib_get_hw_stats() is used for device (port_num = 0), there is a special handling in order to use the correct counters, but, port_num | ||
| CVE-2023-53390 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: drivers: base: dd: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just cal | ||
| CVE-2023-53388 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Clean dangling pointer on bind error path mtk_drm_bind() can fail, in which case drm_dev_put() is called, destroying the drm_device object. However a pointer to it was still being held in the priv | ||
| CVE-2023-53386 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix potential use-after-free when clear keys Similar to commit c5d2b6fa26b5 ("Bluetooth: Fix use-after-free in hci_remove_ltk/hci_remove_irk"). We can not access k after kfree_rcu() call. | ||
| CVE-2023-53384 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: avoid possible NULL skb pointer dereference In 'mwifiex_handle_uap_rx_forward()', always check the value returned by 'skb_copy()' to avoid potential NULL pointer dereference in 'mwifiex_uap_queue | ||
| CVE-2023-53381 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: NFSD: fix leaked reference count of nfsd4_ssc_umount_item The reference count of nfsd4_ssc_umount_item is not decremented on error conditions. This prevents the laundromat from unmounting the vfsmount of the so | ||
| CVE-2023-53380 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request There are two check of 'mreplace' in raid10_sync_request(). In the first check, 'need_replace' will be set and 'mreplace' will be used later if n | ||
| CVE-2023-53379 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe() Smatch reports: drivers/usb/phy/phy-tahvo.c: tahvo_usb_probe() warn: missing unwind goto? After geting irq, if ret < 0, it will return without error ha | ||
| CVE-2023-53377 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: cifs: prevent use-after-free by freeing the cfile later In smb2_compound_op we have a possible use-after-free which can cause hard to debug problems later on. This was revealed during stress testing with KASAN | ||
| CVE-2023-53375 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: tracing: Free error logs of tracing instances When a tracing instance is removed, the error messages that hold errors that occurred in the instance needs to be freed. The following reports a memory leak: # cd | ||
| CVE-2023-53373 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv only handles the special return value of EINPROGERSS, which means that in all other cases it will free data related to the request. However, as the caller | ||
| CVE-2022-50399 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: media: atomisp: prevent integer overflow in sh_css_set_black_frame() The "height" and "width" values come from the user so the "height * width" multiplication can overflow. | ||
| CVE-2022-50395 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: integrity: Fix memory leakage in keyring allocation error path Key restriction is allocated in integrity_init_keyring(). However, if keyring allocation failed, it is not freed, causing memory leaks. | ||
| CVE-2022-50394 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: i2c: ismt: Fix an out-of-bounds bug in ismt_access() When the driver does not check the data from the user, the variable 'data->block[0]' may be very large to cause an out-of-bounds bug. The following log can | ||
| CVE-2022-50392 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8183: fix refcount leak in mt8183_mt6358_ts3a227_max98357_dev_probe() The node returned by of_parse_phandle() with refcount incremented, of_node_put() needs be called when finish using it. So | ||
| CVE-2022-50391 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix memory leak in set_mempolicy_home_node system call When encountering any vma in the range with policy other than MPOL_BIND or MPOL_PREFERRED_MANY, an error is returned without issuing a mpol_p | ||
| CVE-2022-50389 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak In crb_acpi_add(), we get the TPM2 table to retrieve information like start method, and then assign them to the priv data, so the TPM2 table is n | ||
| CVE-2022-50388 | — | < 5.14.21-150400.15.133.1 | 5.14.21-150400.15.133.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: nvme: fix multipath crash caused by flush request when blktrace is enabled The flush request initialized by blk_kick_flush has NULL bio, and it may be dealt with nvme_end_req during io completion. When blktrace |
- CVE-2023-53396Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix memory leak in do_rename If renaming a file in an encrypted directory, function fscrypt_setup_filename allocates memory for a file name. This name is never used, and before returning to the caller th
- CVE-2023-53395Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer ACPICA commit 90310989a0790032f5a0140741ff09b545af4bc5 According to the ACPI specification 19.6.134, no argument is required to be passed for ASL Timer instruct
- CVE-2023-53393Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_ib_get_hw_stats when used for device Currently, when mlx5_ib_get_hw_stats() is used for device (port_num = 0), there is a special handling in order to use the correct counters, but, port_num
- CVE-2023-53390Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: drivers: base: dd: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just cal
- CVE-2023-53388Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Clean dangling pointer on bind error path mtk_drm_bind() can fail, in which case drm_dev_put() is called, destroying the drm_device object. However a pointer to it was still being held in the priv
- CVE-2023-53386Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix potential use-after-free when clear keys Similar to commit c5d2b6fa26b5 ("Bluetooth: Fix use-after-free in hci_remove_ltk/hci_remove_irk"). We can not access k after kfree_rcu() call.
- CVE-2023-53384Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: avoid possible NULL skb pointer dereference In 'mwifiex_handle_uap_rx_forward()', always check the value returned by 'skb_copy()' to avoid potential NULL pointer dereference in 'mwifiex_uap_queue
- CVE-2023-53381Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: NFSD: fix leaked reference count of nfsd4_ssc_umount_item The reference count of nfsd4_ssc_umount_item is not decremented on error conditions. This prevents the laundromat from unmounting the vfsmount of the so
- CVE-2023-53380Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request There are two check of 'mreplace' in raid10_sync_request(). In the first check, 'need_replace' will be set and 'mreplace' will be used later if n
- CVE-2023-53379Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe() Smatch reports: drivers/usb/phy/phy-tahvo.c: tahvo_usb_probe() warn: missing unwind goto? After geting irq, if ret < 0, it will return without error ha
- CVE-2023-53377Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: cifs: prevent use-after-free by freeing the cfile later In smb2_compound_op we have a possible use-after-free which can cause hard to debug problems later on. This was revealed during stress testing with KASAN
- CVE-2023-53375Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: tracing: Free error logs of tracing instances When a tracing instance is removed, the error messages that hold errors that occurred in the instance needs to be freed. The following reports a memory leak: # cd
- CVE-2023-53373Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv only handles the special return value of EINPROGERSS, which means that in all other cases it will free data related to the request. However, as the caller
- CVE-2022-50399Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: media: atomisp: prevent integer overflow in sh_css_set_black_frame() The "height" and "width" values come from the user so the "height * width" multiplication can overflow.
- CVE-2022-50395Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: integrity: Fix memory leakage in keyring allocation error path Key restriction is allocated in integrity_init_keyring(). However, if keyring allocation failed, it is not freed, causing memory leaks.
- CVE-2022-50394Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: i2c: ismt: Fix an out-of-bounds bug in ismt_access() When the driver does not check the data from the user, the variable 'data->block[0]' may be very large to cause an out-of-bounds bug. The following log can
- CVE-2022-50392Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8183: fix refcount leak in mt8183_mt6358_ts3a227_max98357_dev_probe() The node returned by of_parse_phandle() with refcount incremented, of_node_put() needs be called when finish using it. So
- CVE-2022-50391Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix memory leak in set_mempolicy_home_node system call When encountering any vma in the range with policy other than MPOL_BIND or MPOL_PREFERRED_MANY, an error is returned without issuing a mpol_p
- CVE-2022-50389Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak In crb_acpi_add(), we get the TPM2 table to retrieve information like start method, and then assign them to the priv data, so the TPM2 table is n
- CVE-2022-50388Sep 18, 2025affected < 5.14.21-150400.15.133.1fixed 5.14.21-150400.15.133.1
In the Linux kernel, the following vulnerability has been resolved: nvme: fix multipath crash caused by flush request when blktrace is enabled The flush request initialized by blk_kick_flush has NULL bio, and it may be dealt with nvme_end_req during io completion. When blktrace
Page 33 of 149