rpm package
suse/kernel-default-base&distro=SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
pkg:rpm/suse/kernel-default-base&distro=SUSE%20Linux%20Enterprise%20High%20Performance%20Computing%2015%20SP5-LTSS
Vulnerabilities (2,310)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-53436 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: scsi: snic: Fix possible memory leak if device_add() fails If device_add() returns error, the name allocated by dev_set_name() needs be freed. As the comment of device_add() says, put_device() should be used to | ||
| CVE-2023-53435 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: cassini: Fix a memory leak in the error handling path of cas_init_one() cas_saturn_firmware_init() allocates some memory using vmalloc(). This memory is freed in the .remove() function but not it the error hand | ||
| CVE-2023-53431 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: scsi: ses: Handle enclosure with just a primary component gracefully This reverts commit 3fe97ff3d949 ("scsi: ses: Don't attach if enclosure has no components") and introduces proper handling of case where ther | ||
| CVE-2023-53427 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: cifs: Fix warning and UAF when destroy the MR list If the MR allocate failed, the MR recovery work not initialized and list not cleared. Then will be warning and UAF when release the MR: WARNING: CPU: 4 PID: | ||
| CVE-2023-53422 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: fw: fix memory leak in debugfs Fix a memory leak that occurs when reading the fw_info file all the way, since we return NULL indicating no more data, but don't free the status tracking object. | ||
| CVE-2022-50419 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times device_add shall not be called multiple times as stated in its documentation: 'Do not call this routine or device_register() more than on | ||
| CVE-2022-50418 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: mhi: fix potential memory leak in ath11k_mhi_register() mhi_alloc_controller() allocates a memory space for mhi_ctrl. When gets some error, mhi_ctrl should be freed with mhi_free_controller(). But | ||
| CVE-2022-50417 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/panfrost: Fix GEM handle creation ref-counting panfrost_gem_create_with_handle() previously returned a BO but with the only reference being from the handle, which user space could in theory guess and releas | ||
| CVE-2022-50414 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: scsi: fcoe: Fix transport not deattached when fcoe_if_init() fails fcoe_init() calls fcoe_transport_attach(&fcoe_sw_transport), but when fcoe_if_init() fails, &fcoe_sw_transport is not detached and leaves freed | ||
| CVE-2022-50412 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm: bridge: adv7511: unregister cec i2c device after cec adapter cec_unregister_adapter() assumes that the underlying adapter ops are callable. For example, if the CEC adapter currently has a valid physical ad | ||
| CVE-2022-50411 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: ACPICA: Fix error code path in acpi_ds_call_control_method() A use-after-free in acpi_ps_parse_aml() after a failing invocaion of acpi_ds_call_control_method() is reported by KASAN [1] and code inspection revea | ||
| CVE-2022-50410 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: NFSD: Protect against send buffer overflow in NFSv2 READ Since before the git era, NFSD has conserved the number of pages held by each nfsd thread by combining the RPC receive and send buffers into a single arr | ||
| CVE-2022-50409 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: net: If sock is dead don't access sock's sk_wq in sk_stream_wait_memory Fixes the below NULL pointer dereference: [...] [ 14.471200] Call Trace: [ 14.471562] [ 14.471882] lock_acquire+0x | ||
| CVE-2022-50408 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit() > ret = brcmf_proto_tx_queue_data(drvr, ifp->ifidx, skb); may be schedule, and then complete before the line > ndev->stats.tx_bytes += skb-> | ||
| CVE-2022-50406 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: iomap: iomap: fix memory corruption when recording errors during writeback Every now and then I see this crash on arm64: Unable to handle kernel NULL pointer dereference at virtual address 00000000000000f8 Buf | ||
| CVE-2022-50404 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: fbdev: fbcon: release buffer when fbcon_do_set_font() failed syzbot is reporting memory leak at fbcon_do_set_font() [1], for commit a5a923038d70 ("fbdev: fbcon: Properly revert changes when vc_resize() failed") | ||
| CVE-2022-50402 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: drivers/md/md-bitmap: check the return value of md_bitmap_get_counter() Check the return value of md_bitmap_get_counter() in case it returns NULL pointer, which will result in a null pointer dereference. v2: u | ||
| CVE-2022-50401 | — | < 5.14.21-150500.55.124.1.150500.6.59.1 | 5.14.21-150500.55.124.1.150500.6.59.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure On error situation `clp->cl_cb_conn.cb_xprt` should not be given a reference to the xprt otherwise both client cleanup and the error handling p | ||
| CVE-2023-53418 | — | < 5.14.21-150500.55.136.1.150500.6.67.1 | 5.14.21-150500.55.136.1.150500.6.67.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: USB: gadget: lpc32xx_udc: 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, j | ||
| CVE-2023-53417 | — | < 5.14.21-150500.55.136.1.150500.6.67.1 | 5.14.21-150500.55.136.1.150500.6.67.1 | Sep 18, 2025 | In the Linux kernel, the following vulnerability has been resolved: USB: sl811: 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 debug |
- CVE-2023-53436Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: scsi: snic: Fix possible memory leak if device_add() fails If device_add() returns error, the name allocated by dev_set_name() needs be freed. As the comment of device_add() says, put_device() should be used to
- CVE-2023-53435Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: cassini: Fix a memory leak in the error handling path of cas_init_one() cas_saturn_firmware_init() allocates some memory using vmalloc(). This memory is freed in the .remove() function but not it the error hand
- CVE-2023-53431Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: scsi: ses: Handle enclosure with just a primary component gracefully This reverts commit 3fe97ff3d949 ("scsi: ses: Don't attach if enclosure has no components") and introduces proper handling of case where ther
- CVE-2023-53427Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix warning and UAF when destroy the MR list If the MR allocate failed, the MR recovery work not initialized and list not cleared. Then will be warning and UAF when release the MR: WARNING: CPU: 4 PID:
- CVE-2023-53422Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: fw: fix memory leak in debugfs Fix a memory leak that occurs when reading the fw_info file all the way, since we return NULL indicating no more data, but don't free the status tracking object.
- CVE-2022-50419Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times device_add shall not be called multiple times as stated in its documentation: 'Do not call this routine or device_register() more than on
- CVE-2022-50418Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: mhi: fix potential memory leak in ath11k_mhi_register() mhi_alloc_controller() allocates a memory space for mhi_ctrl. When gets some error, mhi_ctrl should be freed with mhi_free_controller(). But
- CVE-2022-50417Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: drm/panfrost: Fix GEM handle creation ref-counting panfrost_gem_create_with_handle() previously returned a BO but with the only reference being from the handle, which user space could in theory guess and releas
- CVE-2022-50414Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: scsi: fcoe: Fix transport not deattached when fcoe_if_init() fails fcoe_init() calls fcoe_transport_attach(&fcoe_sw_transport), but when fcoe_if_init() fails, &fcoe_sw_transport is not detached and leaves freed
- CVE-2022-50412Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: drm: bridge: adv7511: unregister cec i2c device after cec adapter cec_unregister_adapter() assumes that the underlying adapter ops are callable. For example, if the CEC adapter currently has a valid physical ad
- CVE-2022-50411Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: ACPICA: Fix error code path in acpi_ds_call_control_method() A use-after-free in acpi_ps_parse_aml() after a failing invocaion of acpi_ds_call_control_method() is reported by KASAN [1] and code inspection revea
- CVE-2022-50410Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: NFSD: Protect against send buffer overflow in NFSv2 READ Since before the git era, NFSD has conserved the number of pages held by each nfsd thread by combining the RPC receive and send buffers into a single arr
- CVE-2022-50409Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: net: If sock is dead don't access sock's sk_wq in sk_stream_wait_memory Fixes the below NULL pointer dereference: [...] [ 14.471200] Call Trace: [ 14.471562] [ 14.471882] lock_acquire+0x
- CVE-2022-50408Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit() > ret = brcmf_proto_tx_queue_data(drvr, ifp->ifidx, skb); may be schedule, and then complete before the line > ndev->stats.tx_bytes += skb->
- CVE-2022-50406Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: iomap: iomap: fix memory corruption when recording errors during writeback Every now and then I see this crash on arm64: Unable to handle kernel NULL pointer dereference at virtual address 00000000000000f8 Buf
- CVE-2022-50404Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: fbdev: fbcon: release buffer when fbcon_do_set_font() failed syzbot is reporting memory leak at fbcon_do_set_font() [1], for commit a5a923038d70 ("fbdev: fbcon: Properly revert changes when vc_resize() failed")
- CVE-2022-50402Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: drivers/md/md-bitmap: check the return value of md_bitmap_get_counter() Check the return value of md_bitmap_get_counter() in case it returns NULL pointer, which will result in a null pointer dereference. v2: u
- CVE-2022-50401Sep 18, 2025affected < 5.14.21-150500.55.124.1.150500.6.59.1fixed 5.14.21-150500.55.124.1.150500.6.59.1
In the Linux kernel, the following vulnerability has been resolved: nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure On error situation `clp->cl_cb_conn.cb_xprt` should not be given a reference to the xprt otherwise both client cleanup and the error handling p
- CVE-2023-53418Sep 18, 2025affected < 5.14.21-150500.55.136.1.150500.6.67.1fixed 5.14.21-150500.55.136.1.150500.6.67.1
In the Linux kernel, the following vulnerability has been resolved: USB: gadget: lpc32xx_udc: 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, j
- CVE-2023-53417Sep 18, 2025affected < 5.14.21-150500.55.136.1.150500.6.67.1fixed 5.14.21-150500.55.136.1.150500.6.67.1
In the Linux kernel, the following vulnerability has been resolved: USB: sl811: 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 debug
Page 36 of 116