CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-50119 – rpmsg: Fix possible refcount leak in rpmsg_register_device_override()
https://notcve.org/view.php?id=CVE-2022-50119
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: rpmsg: Fix possible refcount leak in rpmsg_register_device_override() rpmsg_register_device_override need to call put_device to free vch when driver_set_override fails. Fix this by adding a put_device() to the error path. In the Linux kernel, the following vulnerability has been resolved: rpmsg: Fix possible refcount leak in rpmsg_register_device_override() rpmsg_register_device_override need to call put_device to free vch when driver_set_o... • https://git.kernel.org/stable/c/bb17d110cbf270d5247a6e261c5ad50e362d1675 •
CVSS: 7.8EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50118 – powerpc/perf: Optimize clearing the pending PMI and remove WARN_ON for PMI check in power_pmu_disable
https://notcve.org/view.php?id=CVE-2022-50118
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: powerpc/perf: Optimize clearing the pending PMI and remove WARN_ON for PMI check in power_pmu_disable commit 2c9ac51b850d ("powerpc/perf: Fix PMU callbacks to clear pending PMI before resetting an overflown PMC") added a new function "pmi_irq_pending" in hw_irq.h. This function is to check if there is a PMI marked as pending in Paca (PACA_IRQ_PMI).This is used in power_pmu_disable in a WARN_ON. The intention here is to provide a warning if ... • https://git.kernel.org/stable/c/ef798cd035f316a537fee8ed170c127f12407085 •
CVSS: 7.1EPSS: 0%CPEs: 2EXPL: 0CVE-2022-50117 – vfio: Split migration ops from main device ops
https://notcve.org/view.php?id=CVE-2022-50117
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: vfio: Split migration ops from main device ops vfio core checks whether the driver sets some migration op (e.g. set_state/get_state) and accordingly calls its op. However, currently mlx5 driver sets the above ops without regards to its migration caps. This might lead to unexpected usage/Oops if user space may call to the above ops even if the driver doesn't support migration. As for example, the migration state_mutex is not initialized in t... • https://git.kernel.org/stable/c/6fadb021266d03c5fd7bca2cfa1607efd246dad1 •
CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50116 – tty: n_gsm: fix deadlock and link starvation in outgoing data path
https://notcve.org/view.php?id=CVE-2022-50116
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix deadlock and link starvation in outgoing data path The current implementation queues up new control and user packets as needed and processes this queue down to the ldisc in the same code path. That means that the upper and the lower layer are hard coupled in the code. Due to this deadlocks can happen as seen below while transmitting data, especially during ldisc congestion. Furthermore, the data channels starve the control c... • https://git.kernel.org/stable/c/e1eaea46bb4020b38a141b84f88565d4603f8dd0 •
CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50115 – ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes
https://notcve.org/view.php?id=CVE-2022-50115
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes We have sanity checks for byte controls and if any of the fail the locally allocated scontrol->ipc_control_data is freed up, but not set to NULL. On a rollback path of the error the higher level code will also try to free the scontrol->ipc_control_data which will eventually going to lead to memory corruption as double freeing memory is not a good thing. In t... • https://git.kernel.org/stable/c/b5cee8feb1d482a9d07b677f4f2f9565bacda53e •
CVSS: 7.1EPSS: 0%CPEs: 5EXPL: 0CVE-2022-50114 – net: 9p: fix refcount leak in p9_read_work() error handling
https://notcve.org/view.php?id=CVE-2022-50114
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: net: 9p: fix refcount leak in p9_read_work() error handling p9_req_put need to be called when m->rreq->rc.sdata is NULL to avoid temporary refcount leak. [Dominique: commit wording adjustments, p9_req_put argument fixes for rebase] In the Linux kernel, the following vulnerability has been resolved: net: 9p: fix refcount leak in p9_read_work() error handling p9_req_put need to be called when m->rreq->rc.sdata is NULL to avoid temporary refco... • https://git.kernel.org/stable/c/728356dedeff8ef999cb436c71333ef4ac51a81c •
CVSS: 7.1EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50113 – ASoc: audio-graph-card2: Fix refcount leak bug in __graph_get_type()
https://notcve.org/view.php?id=CVE-2022-50113
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoc: audio-graph-card2: Fix refcount leak bug in __graph_get_type() We should call of_node_put() for the reference before its replacement as it returned by of_get_parent() which has increased the refcount. Besides, we should also call of_node_put() before return. In the Linux kernel, the following vulnerability has been resolved: ASoc: audio-graph-card2: Fix refcount leak bug in __graph_get_type() We should call of_node_put() for the refer... • https://git.kernel.org/stable/c/c8c74939f791ccbbfff988aec5f929374dbef2a6 •
CVSS: 7.1EPSS: 0%CPEs: 7EXPL: 0CVE-2022-50112 – rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge
https://notcve.org/view.php?id=CVE-2022-50112
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. In the Linux kernel, the following vulnerability has been resolved: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. • https://git.kernel.org/stable/c/53e2822e56c7bc67e5dc19acb1e5fbb8ebff8614 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50111 – ASoC: mt6359: Fix refcount leak bug
https://notcve.org/view.php?id=CVE-2022-50111
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: mt6359: Fix refcount leak bug In mt6359_parse_dt() and mt6359_accdet_parse_dt(), we should call of_node_put() for the reference returned by of_get_child_by_name() which has increased the refcount. In the Linux kernel, the following vulnerability has been resolved: ASoC: mt6359: Fix refcount leak bug In mt6359_parse_dt() and mt6359_accdet_parse_dt(), we should call of_node_put() for the reference returned by of_get_child_by_name() whic... • https://git.kernel.org/stable/c/6835302853169441069e11bc4642300c22009c2e •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2022-50110 – watchdog: sp5100_tco: Fix a memory leak of EFCH MMIO resource
https://notcve.org/view.php?id=CVE-2022-50110
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: watchdog: sp5100_tco: Fix a memory leak of EFCH MMIO resource Unlike release_mem_region(), a call to release_resource() does not free the resource, so it has to be freed explicitly to avoid a memory leak. In the Linux kernel, the following vulnerability has been resolved: watchdog: sp5100_tco: Fix a memory leak of EFCH MMIO resource Unlike release_mem_region(), a call to release_resource() does not free the resource, so it has to be freed e... • https://git.kernel.org/stable/c/b4c0f1600df43245c8c3425dbd9426fdfba6c4b2 •