CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50523 – clk: rockchip: Fix memory leak in rockchip_clk_register_pll()
https://notcve.org/view.php?id=CVE-2022-50523
07 Oct 2025 — 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. 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... • https://git.kernel.org/stable/c/90c590254051f511299538c158e12fdad41ce163 •
CVSS: 7.1EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50522 – mcb: mcb-parse: fix error handing in chameleon_parse_gdd()
https://notcve.org/view.php?id=CVE-2022-50522
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: mcb: mcb-parse: fix error handing in chameleon_parse_gdd() If mcb_device_register() returns error in chameleon_parse_gdd(), the refcount of bus and device name are leaked. Fix this by calling put_device() to give up the reference, so they can be released in mcb_release_dev() and kobject_cleanup(). In the Linux kernel, the following vulnerability has been resolved: mcb: mcb-parse: fix error handing in chameleon_parse_gdd() If mcb_device_regi... • https://git.kernel.org/stable/c/3764e82e5150d87b205c10cd78a9c9ab86fbfa51 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50521 – platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]()
https://notcve.org/view.php?id=CVE-2022-50521
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]() The ACPI buffer memory (out.pointer) returned by wmi_evaluate_method() is not freed after the call, so it leads to memory leak. The method results in ACPI buffer is not used, so just pass NULL to wmi_evaluate_method() which fixes the memory leak. In the Linux kernel, the following vulnerability has been resolved: platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]() The... • https://git.kernel.org/stable/c/99b38b4acc0d7dbbab443273577cff60080fcfad •
CVSS: 7.1EPSS: 0%CPEs: 13EXPL: 0CVE-2022-50520 – drm/radeon: Fix PCI device refcount leak in radeon_atrm_get_bios()
https://notcve.org/view.php?id=CVE-2022-50520
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Fix PCI device refcount leak in radeon_atrm_get_bios() As comment of pci_get_class() says, it returns a pci_device with its refcount increased and decreased the refcount for the input parameter @from if it is not NULL. If we break the loop in radeon_atrm_get_bios() with 'pdev' not NULL, we need to call pci_dev_put() to decrease the refcount. Add the missing pci_dev_put() to avoid refcount leak. In the Linux kernel, the following... • https://git.kernel.org/stable/c/c61e2775873f603148e8e998a938721b7d222d24 • CWE-911: Improper Update of Reference Count •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50519 – nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
https://notcve.org/view.php?id=CVE-2022-50519
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure If creation or finalization of a checkpoint fails due to anomalies in the checkpoint metadata on disk, a kernel warning is generated. This patch replaces the WARN_ONs by nilfs_error, so that a kernel, booted with panic_on_warn, does not panic. A nilfs_error is appropriate here to handle the abnormal filesystem condition. This also replaces the detected error codes wi... • https://git.kernel.org/stable/c/b63026b5e13040cd5afa11769dd0d9e1504b031a •
CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50518 – parisc: Fix locking in pdc_iodc_print() firmware call
https://notcve.org/view.php?id=CVE-2022-50518
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: parisc: Fix locking in pdc_iodc_print() firmware call Utilize pdc_lock spinlock to protect parallel modifications of the iodc_dbuf[] buffer, check length to prevent buffer overflow of iodc_dbuf[], drop the iodc_retbuf[] buffer and fix some wrong indentings. In the Linux kernel, the following vulnerability has been resolved: parisc: Fix locking in pdc_iodc_print() firmware call Utilize pdc_lock spinlock to protect parallel modifications of t... • https://git.kernel.org/stable/c/04a603058e70b8b881bb7860b8bd649f931f2591 •
CVSS: 5.2EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50516 – fs: dlm: fix invalid derefence of sb_lvbptr
https://notcve.org/view.php?id=CVE-2022-50516
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: fs: dlm: fix invalid derefence of sb_lvbptr I experience issues when putting a lkbsb on the stack and have sb_lvbptr field to a dangled pointer while not using DLM_LKF_VALBLK. It will crash with the following kernel message, the dangled pointer is here 0xdeadbeef as example: [ 102.749317] BUG: unable to handle page fault for address: 00000000deadbeef [ 102.749320] #PF: supervisor read access in kernel mode [ 102.749323] #PF: error_code(0x00... • https://git.kernel.org/stable/c/ea7be82fd7e1f5de72208bce93fbbe6de6c13dec • CWE-476: NULL Pointer Dereference •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50515 – drm/amdgpu: Fix memory leak in hpd_rx_irq_create_workqueue()
https://notcve.org/view.php?id=CVE-2022-50515
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix memory leak in hpd_rx_irq_create_workqueue() If construction of the array of work queues to handle hpd_rx_irq offload work fails, we need to unwind. Destroy all the created workqueues and the allocated memory for the hpd_rx_irq_offload_work_queue struct array. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix memory leak in hpd_rx_irq_create_workqueue() If construction of the array of work q... • https://git.kernel.org/stable/c/e980e1d978e0eb4c0399cff37f175779237db53b • CWE-772: Missing Release of Resource after Effective Lifetime •
CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2022-50514 – usb: gadget: f_hid: fix refcount leak on error path
https://notcve.org/view.php?id=CVE-2022-50514
07 Oct 2025 — 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. 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 decre... • https://git.kernel.org/stable/c/21a9476a7ba847e413bf1c144d7c614532aed6dd •
CVSS: 5.6EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50513 – staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv()
https://notcve.org/view.php?id=CVE-2022-50513
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv() In rtw_init_cmd_priv(), if `pcmdpriv->rsp_allocated_buf` is allocated in failure, then `pcmdpriv->cmd_allocated_buf` will be not properly released. Besides, considering there are only two error paths and the first one can directly return, so we do not need implicitly jump to the `exit` tag to execute the error handler. So this patch added `kfree(pcmdpriv->cmd_allocated_b... • https://git.kernel.org/stable/c/e5d8f05edb36fc4ab15beec62cb6ab62f5a60fe2 •