CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2023-53489 – tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp.
https://notcve.org/view.php?id=CVE-2023-53489
01 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp. syzkaller reported [0] memory leaks of an UDP socket and ZEROCOPY skbs. We can reproduce the problem with these sequences: sk = socket(AF_INET, SOCK_DGRAM, 0) sk.setsockopt(SOL_SOCKET, SO_TIMESTAMPING, SOF_TIMESTAMPING_TX_SOFTWARE) sk.setsockopt(SOL_SOCKET, SO_ZEROCOPY, 1) sk.sendto(b'', MSG_ZEROCOPY, ('127.0.0.1', 53)) sk.close() sendmsg() calls msg_zerocopy_alloc(), which al... • https://git.kernel.org/stable/c/f214f915e7db99091f1312c48b30928c1e0c90b7 •
CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53488 – IB/hfi1: Fix possible panic during hotplug remove
https://notcve.org/view.php?id=CVE-2023-53488
01 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix possible panic during hotplug remove During hotplug remove it is possible that the update counters work might be pending, and may run after memory has been freed. Cancel the update counters work before freeing memory. In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix possible panic during hotplug remove During hotplug remove it is possible that the update counters work might be pending, and may ru... • https://git.kernel.org/stable/c/7724105686e718ac476a6ad3304fea2fbcfcffde •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50469 – staging: rtl8723bs: fix potential memory leak in rtw_init_drv_sw()
https://notcve.org/view.php?id=CVE-2022-50469
01 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix potential memory leak in rtw_init_drv_sw() In rtw_init_drv_sw(), there are various init functions are called to populate the padapter structure and some checks for their return value. However, except for the first one error path, the other five error paths do not properly release the previous allocated resources, which leads to various memory leaks. This patch fixes them and keeps the success and error separate. Note... • https://git.kernel.org/stable/c/554c0a3abf216c991c5ebddcdb2c08689ecd290b •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50463 – powerpc/52xx: Fix a resource leak in an error handling path
https://notcve.org/view.php?id=CVE-2022-50463
01 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: powerpc/52xx: Fix a resource leak in an error handling path The error handling path of mpc52xx_lpbfifo_probe() has a request_irq() that is not balanced by a corresponding free_irq(). Add the missing call, as already done in the remove function. In the Linux kernel, the following vulnerability has been resolved: powerpc/52xx: Fix a resource leak in an error handling path The error handling path of mpc52xx_lpbfifo_probe() has a request_irq() ... • https://git.kernel.org/stable/c/3c9059d79f5eea6b8b75ddac97693127c3c41db4 •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50462 – MIPS: vpe-mt: fix possible memory leak while module exiting
https://notcve.org/view.php?id=CVE-2022-50462
01 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: MIPS: vpe-mt: fix possible memory leak while module exiting Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's bus_id string array"), the name of device is allocated dynamically, it need be freed when module exiting, call put_device() to give up reference, so that it can be freed in kobject_cleanup() when the refcount hit to 0. The vpe_device is static, so remove kfree() from vpe_device_release(). In the Linux kernel, the fo... • https://git.kernel.org/stable/c/1fa5ae857bb14f6046205171d98506d8112dd74e •
CVSS: 7.1EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50458 – clk: tegra: Fix refcount leak in tegra210_clock_init
https://notcve.org/view.php?id=CVE-2022-50458
01 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: tegra: Fix refcount leak in tegra210_clock_init of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. In the Linux kernel, the following vulnerability has been resolved: clk: tegra: Fix refcount leak in tegra210_clock_init of_find_matching_node() returns a node pointer with refcount incremented, we should use o... • https://git.kernel.org/stable/c/6b301a059eb2ebed1b12a900e3b21a38e48dd410 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50456 – btrfs: fix resolving backrefs for inline extent followed by prealloc
https://notcve.org/view.php?id=CVE-2022-50456
01 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: btrfs: fix resolving backrefs for inline extent followed by prealloc If a file consists of an inline extent followed by a regular or prealloc extent, then a legitimate attempt to resolve a logical address in the non-inline region will result in add_all_parents reading the invalid offset field of the inline extent. If the inline extent item is placed in the leaf eb s.t. it is the first item, attempting to access the offset field will not onl... • https://git.kernel.org/stable/c/8da6d5815c592b713ecaf4f4f8b631f8359c96c4 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2022-50453 – gpiolib: cdev: fix NULL-pointer dereferences
https://notcve.org/view.php?id=CVE-2022-50453
01 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: fix NULL-pointer dereferences There are several places where we can crash the kernel by requesting lines, unbinding the GPIO device, then calling any of the system calls relevant to the GPIO character device's annonymous file descriptors: ioctl(), read(), poll(). While I observed it with the GPIO simulator, it will also happen for any of the GPIO devices that can be hot-unplugged - for instance any HID GPIO expander (e.g. CP2... • https://git.kernel.org/stable/c/d7c51b47ac11e66f547b55640405c1c474642d72 • CWE-476: NULL Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50452 – net: sched: cake: fix null pointer access issue when cake_init() fails
https://notcve.org/view.php?id=CVE-2022-50452
01 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: net: sched: cake: fix null pointer access issue when cake_init() fails When the default qdisc is cake, if the qdisc of dev_queue fails to be inited during mqprio_init(), cake_reset() is invoked to clear resources. In this case, the tins is NULL, and it will cause gpf issue. The process is as follows: qdisc_create_dflt() cake_init() q->tins = kvcalloc(...) --->failed, q->tins is NULL ... qdisc_put() ... cake_reset() ... cake_dequeue_one() b ... • https://git.kernel.org/stable/c/046f6fd5daefac7f5abdafb436b30f63bc7c602b • CWE-476: NULL Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-50449 – clk: samsung: Fix memory leak in _samsung_clk_register_pll()
https://notcve.org/view.php?id=CVE-2022-50449
01 Oct 2025 — 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. 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 i... • https://git.kernel.org/stable/c/3ff6e0d8d64d594a551b5c4904e4b617bf7eee22 •