CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53390 – drivers: base: dd: fix memory leak with using debugfs_lookup()
https://notcve.org/view.php?id=CVE-2023-53390
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: drivers: base: dd: 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. In the Linux kernel, the following vulnerability has been resolved: drivers: base: dd: fix memory leak with using debugfs_lookup() When calling debugfs_looku... • https://git.kernel.org/stable/c/7f1e53f88e8babf293ec052b70aa9d2a3554360c • CWE-772: Missing Release of Resource after Effective Lifetime •
CVSS: 7.8EPSS: 0%CPEs: 7EXPL: 0CVE-2023-53388 – drm/mediatek: Clean dangling pointer on bind error path
https://notcve.org/view.php?id=CVE-2023-53388
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Clean dangling pointer on bind error path mtk_drm_bind() can fail, in which case drm_dev_put() is called, destroying the drm_device object. However a pointer to it was still being held in the private object, and that pointer would be passed along to DRM in mtk_drm_sys_prepare() if a suspend were triggered at that point, resulting in a panic. Clean the pointer when destroying the object in the error path to prevent this from ha... • https://git.kernel.org/stable/c/119f5173628aa7a0c3cf9db83460d40709e8241d •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53387 – scsi: ufs: core: Fix device management cmd timeout flow
https://notcve.org/view.php?id=CVE-2023-53387
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix device management cmd timeout flow In the UFS error handling flow, the host will send a device management cmd (NOP OUT) to the device for link recovery. If this cmd times out and clearing the doorbell fails, ufshcd_wait_for_dev_cmd() will do nothing and return. hba->dev_cmd.complete struct is not set to NULL. When this happens, if cmd has been completed by device, then we will call complete() in __ufshcd_transfer_req_co... • https://git.kernel.org/stable/c/cf45493432704786a0f8294c7723ad4eeb5fff24 •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2023-53384 – wifi: mwifiex: avoid possible NULL skb pointer dereference
https://notcve.org/view.php?id=CVE-2023-53384
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: avoid possible NULL skb pointer dereference In 'mwifiex_handle_uap_rx_forward()', always check the value returned by 'skb_copy()' to avoid potential NULL pointer dereference in 'mwifiex_uap_queue_bridged_pkt()', and drop original skb in case of copying failure. Found by Linux Verification Center (linuxtesting.org) with SVACE. In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: avoid possible NUL... • https://git.kernel.org/stable/c/838e4f44929782a2163c7bc95a7cd2da5d8b47f9 • CWE-476: NULL Pointer Dereference •
CVSS: 8.8EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53383 – irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4
https://notcve.org/view.php?id=CVE-2023-53383
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4 The T241 platform suffers from the T241-FABRIC-4 erratum which causes unexpected behavior in the GIC when multiple transactions are received simultaneously from different sources. This hardware issue impacts NVIDIA server platforms that use more than two T241 chips interconnected. Each chip has support for 320 {E}SPIs. This issue occurs when multiple packets from different GICs are ... • https://git.kernel.org/stable/c/86ba4f7b9f949e4c4bcb425f2a1ce490fea30df0 •
CVSS: 5.5EPSS: 0%CPEs: 12EXPL: 0CVE-2023-53379 – usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe()
https://notcve.org/view.php?id=CVE-2023-53379
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe() Smatch reports: drivers/usb/phy/phy-tahvo.c: tahvo_usb_probe() warn: missing unwind goto? After geting irq, if ret < 0, it will return without error handling to free memory. Just add error handling to fix this problem. In the Linux kernel, the following vulnerability has been resolved: usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe() Smatch reports: drivers/usb/phy/phy-tahvo... • https://git.kernel.org/stable/c/3f06415418f37ac602e71a61ee83ea43553e6bbd •
CVSS: 8.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53373 – crypto: seqiv - Handle EBUSY correctly
https://notcve.org/view.php?id=CVE-2023-53373
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv only handles the special return value of EINPROGERSS, which means that in all other cases it will free data related to the request. However, as the caller of seqiv may specify MAY_BACKLOG, we also need to expect EBUSY and treat it in the same way. Otherwise backlogged requests will trigger a use-after-free. In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv... • https://git.kernel.org/stable/c/0a270321dbf948963aeb0e8382fe17d2c2eb3771 • CWE-416: Use After Free •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53370 – drm/amdgpu: fix memory leak in mes self test
https://notcve.org/view.php?id=CVE-2023-53370
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix memory leak in mes self test The fences associated with mes queue have to be freed up during amdgpu_ring_fini. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix memory leak in mes self test The fences associated with mes queue have to be freed up during amdgpu_ring_fini. This update provides the initial livepatch for this kernel update. This update does not contain any fixes and will be upda... • https://git.kernel.org/stable/c/d38ceaf99ed015f2a0b9af3499791bd3a3daae21 • CWE-772: Missing Release of Resource after Effective Lifetime •
CVSS: 7.8EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53369 – net: dcb: choose correct policy to parse DCB_ATTR_BCN
https://notcve.org/view.php?id=CVE-2023-53369
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: net: dcb: choose correct policy to parse DCB_ATTR_BCN The dcbnl_bcn_setcfg uses erroneous policy to parse tb[DCB_ATTR_BCN], which is introduced in commit 859ee3c43812 ("DCB: Add support for DCB BCN"). Please see the comment in below code static int dcbnl_bcn_setcfg(...) { ... ret = nla_parse_nested_deprecated(..., dcbnl_pfc_up_nest, .. ) // !!! dcbnl_pfc_up_nest for attributes // DCB_PFC_UP_ATTR_0 to DCB_PFC_UP_ATTR_ALL in enum dcbnl_pfc_up... • https://git.kernel.org/stable/c/859ee3c43812051e21816c6d6d4cc04fb7ce9b2e •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50399 – media: atomisp: prevent integer overflow in sh_css_set_black_frame()
https://notcve.org/view.php?id=CVE-2022-50399
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: media: atomisp: prevent integer overflow in sh_css_set_black_frame() The "height" and "width" values come from the user so the "height * width" multiplication can overflow. In the Linux kernel, the following vulnerability has been resolved: media: atomisp: prevent integer overflow in sh_css_set_black_frame() The "height" and "width" values come from the user so the "height * width" multiplication can overflow. This update provides the initi... • https://git.kernel.org/stable/c/a49d25364dfb9f8a64037488a39ab1f56c5fa419 •