rpm package
suse/kernel-default-base&distro=SUSE Linux Enterprise Server 15 SP4-LTSS
pkg:rpm/suse/kernel-default-base&distro=SUSE%20Linux%20Enterprise%20Server%2015%20SP4-LTSS
Vulnerabilities (2,830)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2022-50395 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.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.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.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.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.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.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.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.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.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.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.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-2022-50386 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix user-after-free This uses l2cap_chan_hold_unless_zero() after calling __l2cap_get_chan_blah() to prevent the following trace: Bluetooth: l2cap_core.c:static void l2cap_chan_destroy(struct | ||
| CVE-2022-50385 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: NFS: Fix an Oops in nfs_d_automount() When mounting from a NFSv4 referral, path->dentry can end up being a negative dentry, so derive the struct nfs_server from the dentry itself instead. | ||
| CVE-2022-50381 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: md: fix a crash in mempool_free There's a crash in mempool_free when running the lvm test shell/lvchange-rebuild-raid.sh. The reason for the crash is this: * super_written calls atomic_dec_and_test(&mddev->pen | ||
| CVE-2022-50379 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race between quota enable and quota rescan ioctl When enabling quotas, at btrfs_quota_enable(), after committing the transaction, we change fs_info->quota_root to point to the quota root we created a | ||
| CVE-2022-50376 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: orangefs: Fix kmemleak in orangefs_{kernel,client}_debug_init() When insert and remove the orangefs module, there are memory leaked as below: unreferenced object 0xffff88816b0cc000 (size 2048): comm "insmod" | ||
| CVE-2022-50375 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: tty: serial: fsl_lpuart: disable dma rx/tx use flags in lpuart_dma_shutdown lpuart_dma_shutdown tears down lpuart dma, but lpuart_flush_buffer can still occur which in turn tries to access dma apis if lpuart_dm | ||
| CVE-2023-53368 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 17, 2025 | In the Linux kernel, the following vulnerability has been resolved: tracing: Fix race issue between cpu buffer write and swap Warning happened in rb_end_commit() at code: if (RB_WARN_ON(cpu_buffer, !local_read(&cpu_buffer->committing))) WARNING: CPU: 0 PID: 139 at kernel/tr | ||
| CVE-2023-53365 | — | < 5.14.21-150400.24.184.1.150400.24.94.2 | 5.14.21-150400.24.184.1.150400.24.94.2 | Sep 17, 2025 | In the Linux kernel, the following vulnerability has been resolved: ip6mr: Fix skb_under_panic in ip6mr_cache_report() skbuff: skb_under_panic: text:ffffffff88771f69 len:56 put:-4 head:ffff88805f86a800 data:ffff887f5f86a850 tail:0x88 end:0x2c0 dev:pim6reg ------------[ cut he | ||
| CVE-2023-53359 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 17, 2025 | In the Linux kernel, the following vulnerability has been resolved: USB: 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 call debugfs_look | ||
| CVE-2023-53356 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 17, 2025 | In the Linux kernel, the following vulnerability has been resolved: usb: gadget: u_serial: Add null pointer check in gserial_suspend Consider a case where gserial_disconnect has already cleared gser->ioport. And if gserial_suspend gets called afterwards, it will lead to accessi | ||
| CVE-2023-53352 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 17, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/ttm: check null pointer before accessing when swapping Add a check to avoid null pointer dereference as below: [ 90.002283] general protection fault, probably for non-canonical address 0xdffffc0000000000 | ||
| CVE-2023-53349 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 17, 2025 | In the Linux kernel, the following vulnerability has been resolved: media: ov2740: Fix memleak in ov2740_init_controls() There is a kmemleak when testing the media/i2c/ov2740.c with bpf mock device: unreferenced object 0xffff8881090e19e0 (size 16): comm "51-i2c-ov2740", pid | ||
| CVE-2023-53344 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 17, 2025 | In the Linux kernel, the following vulnerability has been resolved: can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write Syzkaller reported the following issue: ===================================================== BUG: KMSAN: uninit-value in aio_rw_done fs/aio.c:1520 | ||
| CVE-2023-53337 | — | < 5.14.21-150400.24.179.1.150400.24.92.1 | 5.14.21-150400.24.179.1.150400.24.92.1 | Sep 17, 2025 | In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not write dirty data after degenerating to read-only According to syzbot's report, mark_buffer_dirty() called from nilfs_segctor_do_construct() outputs a warning with some patterns after nilfs2 detec |
- CVE-2022-50395Sep 18, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.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.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.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.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.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.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.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.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.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.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.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
- CVE-2022-50386Sep 18, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix user-after-free This uses l2cap_chan_hold_unless_zero() after calling __l2cap_get_chan_blah() to prevent the following trace: Bluetooth: l2cap_core.c:static void l2cap_chan_destroy(struct
- CVE-2022-50385Sep 18, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: NFS: Fix an Oops in nfs_d_automount() When mounting from a NFSv4 referral, path->dentry can end up being a negative dentry, so derive the struct nfs_server from the dentry itself instead.
- CVE-2022-50381Sep 18, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: md: fix a crash in mempool_free There's a crash in mempool_free when running the lvm test shell/lvchange-rebuild-raid.sh. The reason for the crash is this: * super_written calls atomic_dec_and_test(&mddev->pen
- CVE-2022-50379Sep 18, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race between quota enable and quota rescan ioctl When enabling quotas, at btrfs_quota_enable(), after committing the transaction, we change fs_info->quota_root to point to the quota root we created a
- CVE-2022-50376Sep 18, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: orangefs: Fix kmemleak in orangefs_{kernel,client}_debug_init() When insert and remove the orangefs module, there are memory leaked as below: unreferenced object 0xffff88816b0cc000 (size 2048): comm "insmod"
- CVE-2022-50375Sep 18, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: tty: serial: fsl_lpuart: disable dma rx/tx use flags in lpuart_dma_shutdown lpuart_dma_shutdown tears down lpuart dma, but lpuart_flush_buffer can still occur which in turn tries to access dma apis if lpuart_dm
- CVE-2023-53368Sep 17, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix race issue between cpu buffer write and swap Warning happened in rb_end_commit() at code: if (RB_WARN_ON(cpu_buffer, !local_read(&cpu_buffer->committing))) WARNING: CPU: 0 PID: 139 at kernel/tr
- CVE-2023-53365Sep 17, 2025affected < 5.14.21-150400.24.184.1.150400.24.94.2fixed 5.14.21-150400.24.184.1.150400.24.94.2
In the Linux kernel, the following vulnerability has been resolved: ip6mr: Fix skb_under_panic in ip6mr_cache_report() skbuff: skb_under_panic: text:ffffffff88771f69 len:56 put:-4 head:ffff88805f86a800 data:ffff887f5f86a850 tail:0x88 end:0x2c0 dev:pim6reg ------------[ cut he
- CVE-2023-53359Sep 17, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: USB: 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 call debugfs_look
- CVE-2023-53356Sep 17, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: u_serial: Add null pointer check in gserial_suspend Consider a case where gserial_disconnect has already cleared gser->ioport. And if gserial_suspend gets called afterwards, it will lead to accessi
- CVE-2023-53352Sep 17, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: drm/ttm: check null pointer before accessing when swapping Add a check to avoid null pointer dereference as below: [ 90.002283] general protection fault, probably for non-canonical address 0xdffffc0000000000
- CVE-2023-53349Sep 17, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: media: ov2740: Fix memleak in ov2740_init_controls() There is a kmemleak when testing the media/i2c/ov2740.c with bpf mock device: unreferenced object 0xffff8881090e19e0 (size 16): comm "51-i2c-ov2740", pid
- CVE-2023-53344Sep 17, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write Syzkaller reported the following issue: ===================================================== BUG: KMSAN: uninit-value in aio_rw_done fs/aio.c:1520
- CVE-2023-53337Sep 17, 2025affected < 5.14.21-150400.24.179.1.150400.24.92.1fixed 5.14.21-150400.24.179.1.150400.24.92.1
In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not write dirty data after degenerating to read-only According to syzbot's report, mark_buffer_dirty() called from nilfs_segctor_do_construct() outputs a warning with some patterns after nilfs2 detec
Page 33 of 142