Debian Linux vulnerabilities

CVE-2022-49819 [MEDIUM] CVE-2022-49819: linux - In the Linux kernel, the following vulnerability has been resolved: octeon_ep: ... In the Linux kernel, the following vulnerability has been resolved: octeon_ep: fix potential memory leak in octep_device_setup() When occur unsupported_dev and mbox init errors, it did not free oct->conf and iounmap() oct->mmio[i].hw_addr. That would trigger memory leak problem. Add kfree() for oct->conf and iounmap() for oct->mmio[i].hw_addr under unsupported_dev a

CVE-2020-36790 [MEDIUM] CVE-2020-36790: linux - In the Linux kernel, the following vulnerability has been resolved: nvmet: fix ... In the Linux kernel, the following vulnerability has been resolved: nvmet: fix a memory leak We forgot to free new_model_number Scope: local bookworm: resolved (fixed in 5.8.7-1) bullseye: resolved (fixed in 5.8.7-1) forky: resolved (fixed in 5.8.7-1) sid: resolved (fixed in 5.8.7-1) trixie: resolved (fixed in 5.8.7-1)

CVE-2025-38410 [MEDIUM] CVE-2025-38410: linux - In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fi... In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix a fence leak in submit error path In error paths, we could unref the submit without calling drm_sched_entity_push_job(), so msm_job_free() will never get called. Since drm_sched_job_cleanup() will NULL out the s_fence, we can use that to detect this case. Patchwork: https://patchwork.fr

CVE-2023-53367 [MEDIUM] CVE-2023-53367: linux - In the Linux kernel, the following vulnerability has been resolved: accel/haban... In the Linux kernel, the following vulnerability has been resolved: accel/habanalabs: fix mem leak in capture user mappings This commit fixes a memory leak caused when clearing the user_mappings info when a new context is opened immediately after user_mapping is captured and a hard reset is performed. Scope: local bookworm: open bullseye: open forky: resolved (fixed

CVE-2022-49745 [MEDIUM] CVE-2022-49745: linux - In the Linux kernel, the following vulnerability has been resolved: fpga: m10bm... In the Linux kernel, the following vulnerability has been resolved: fpga: m10bmc-sec: Fix probe rollback Handle probe error rollbacks properly to avoid leaks. Scope: local bookworm: resolved (fixed in 6.1.11-1) bullseye: resolved forky: resolved (fixed in 6.1.11-1) sid: resolved (fixed in 6.1.11-1) trixie: resolved (fixed in 6.1.11-1)

CVE-2023-53017 [MEDIUM] CVE-2023-53017: linux - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ... In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: fix memory leak in hci_update_adv_data() When hci_cmd_sync_queue() failed in hci_update_adv_data(), inst_ptr is not freed, which will cause memory leak, convert to use ERR_PTR/PTR_ERR to pass the instance to callback so no memory needs to be allocated. Scope: local bookworm: res

CVE-2023-53018 [MEDIUM] CVE-2023-53018: linux - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ... In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: Fix memory leaks When hci_cmd_sync_queue() failed in hci_le_terminate_big() or hci_le_big_terminate(), the memory pointed by variable d is not freed, which will cause memory leak. Add release process to error path. Scope: local bookworm: resolved (fixed in 6.1.11-1) bullseye: re

CVE-2022-50449 [MEDIUM] CVE-2022-50449: linux - In the Linux kernel, the following vulnerability has been resolved: clk: samsun... In the Linux kernel, the following vulnerability has been resolved: clk: samsung: Fix memory leak in _samsung_clk_register_pll() If clk_register() fails, @pll->rate_table may have allocated memory by kmemdup(), so it needs to be freed, otherwise will cause memory leak issue, this patch fixes it. Scope: local bookworm: resolved (fixed in 6.1.4-1) bullseye: resolved (

CVE-2023-53202 [MEDIUM] CVE-2023-53202: linux - In the Linux kernel, the following vulnerability has been resolved: PM: domains... In the Linux kernel, the following vulnerability has been resolved: PM: domains: 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_lookup_and_remove() instead which handles all of the logic at once. Scope: local bookwo

CVE-2023-53197 [MEDIUM] CVE-2023-53197: linux - In the Linux kernel, the following vulnerability has been resolved: USB: uhci: ... In the Linux kernel, the following vulnerability has been resolved: USB: uhci: 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_lookup_and_remove() instead which handles all of the logic at once. Scope: local bookworm

CVE-2022-50523 [MEDIUM] CVE-2022-50523: linux - In the Linux kernel, the following vulnerability has been resolved: clk: rockch... In the Linux kernel, the following vulnerability has been resolved: clk: rockchip: Fix memory leak in rockchip_clk_register_pll() If clk_register() fails, @pll->rate_table may have allocated memory by kmemdup(), so it needs to be freed, otherwise will cause memory leak issue, this patch fixes it. Scope: local bookworm: resolved (fixed in 6.1.4-1) bullseye: resolved

CVE-2022-50525 [MEDIUM] CVE-2022-50525: linux - In the Linux kernel, the following vulnerability has been resolved: iommu/fsl_p... In the Linux kernel, the following vulnerability has been resolved: iommu/fsl_pamu: Fix resource leak in fsl_pamu_probe() The fsl_pamu_probe() returns directly when create_csd() failed, leaving irq and memories unreleased. Fix by jumping to error if create_csd() returns error. Scope: local bookworm: resolved (fixed in 6.1.4-1) bullseye: resolved (fixed in 5.10.178-1

CVE-2022-50544 [MEDIUM] CVE-2022-50544: linux - In the Linux kernel, the following vulnerability has been resolved: usb: host: ... In the Linux kernel, the following vulnerability has been resolved: usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info() xhci_alloc_stream_info() allocates stream context array for stream_info ->stream_ctx_array with xhci_alloc_stream_ctx(). When some error occurs, stream_info->stream_ctx_array is not released, which will lead to a memory leak. We

CVE-2022-50242 [MEDIUM] CVE-2022-50242: linux - In the Linux kernel, the following vulnerability has been resolved: drivers: ne... In the Linux kernel, the following vulnerability has been resolved: drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init() If vp alloc failed in qlcnic_sriov_init(), all previously allocated vp needs to be freed. Scope: local bookworm: resolved (fixed in 6.1.4-1) bullseye: resolved (fixed in 5.10.178-1) forky: resolved (fixed in 6.1.4-1) sid: resolve

CVE-2022-50349 [MEDIUM] CVE-2022-50349: linux - In the Linux kernel, the following vulnerability has been resolved: misc: tifm:... In the Linux kernel, the following vulnerability has been resolved: misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() If device_register() returns error in tifm_7xx1_switch_media(), name of kobject which is allocated in dev_set_name() called in device_add() is leaked. Never directly free @dev after calling device_register(), even if it returned an err

CVE-2023-53422 [MEDIUM] CVE-2023-53422: linux - In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwi... 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. Scope: local bookworm: resolved (fixed in 6.1.37-1) bullseye: resolved (fixed in 5.10.191-1)

CVE-2022-50246 [MEDIUM] CVE-2022-50246: linux - In the Linux kernel, the following vulnerability has been resolved: usb: typec:... In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpci: fix of node refcount leak in tcpci_register_port() I got the following report while doing device(mt6370-tcpc) load test with CONFIG_OF_UNITTEST and CONFIG_OF_DYNAMIC enabled: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy

CVE-2022-50514 [MEDIUM] CVE-2022-50514: linux - In the Linux kernel, the following vulnerability has been resolved: usb: gadget... In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_hid: fix refcount leak on error path When failing to allocate report_desc, opts->refcnt has already been incremented so it needs to be decremented to avoid leaving the options structure permanently locked. Scope: local bookworm: resolved (fixed in 6.1.4-1) bullseye: resolved (fixed in

CVE-2023-53482 [MEDIUM] CVE-2023-53482: linux - In the Linux kernel, the following vulnerability has been resolved: iommu: Fix ... In the Linux kernel, the following vulnerability has been resolved: iommu: Fix error unwind in iommu_group_alloc() If either iommu_group_grate_file() fails then the iommu_group is leaked. Destroy it on these error paths. Found by kselftest/iommu/iommufd_fail_nth Scope: local bookworm: resolved (fixed in 6.1.20-1) bullseye: open forky: resolved (fixed in 6.1.20-1) si

CVE-2023-53174 [MEDIUM] CVE-2023-53174: linux - In the Linux kernel, the following vulnerability has been resolved: scsi: core:... In the Linux kernel, the following vulnerability has been resolved: scsi: core: 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 decrease the reference count in the error path. So fix this by calling put_device(), then