CVSS: 5.5EPSS: 0%CPEs: 11EXPL: 0CVE-2023-53433 – net: add vlan_get_protocol_and_depth() helper
https://notcve.org/view.php?id=CVE-2023-53433
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: net: add vlan_get_protocol_and_depth() helper Before blamed commit, pskb_may_pull() was used instead of skb_header_pointer() in __vlan_get_protocol() and friends. Few callers depended on skb->head being populated with MAC header, syzbot caught one of them (skb_mac_gso_segment()) Add vlan_get_protocol_and_depth() to make the intent clearer and use it where sensible. This is a more generic fix than commit e9d3f80935b6 ("net/af_packet: make su... • https://git.kernel.org/stable/c/30d015f5ecd9ce5706ad18a4a0649f364e3e6f7b • CWE-125: Out-of-bounds Read •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53432 – firewire: net: fix use after free in fwnet_finish_incoming_packet()
https://notcve.org/view.php?id=CVE-2023-53432
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: firewire: net: fix use after free in fwnet_finish_incoming_packet() The netif_rx() function frees the skb so we can't dereference it to save the skb->len. In the Linux kernel, the following vulnerability has been resolved: firewire: net: fix use after free in fwnet_finish_incoming_packet() The netif_rx() function frees the skb so we can't dereference it to save the skb->len. This update provides the initial livepatch for this kernel update.... • https://git.kernel.org/stable/c/c76acec6d55107b652a37c90b36c00bc8b04dabb • CWE-416: Use After Free •
CVSS: 7.5EPSS: 0%CPEs: 7EXPL: 0CVE-2023-53431 – scsi: ses: Handle enclosure with just a primary component gracefully
https://notcve.org/view.php?id=CVE-2023-53431
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: ses: Handle enclosure with just a primary component gracefully This reverts commit 3fe97ff3d949 ("scsi: ses: Don't attach if enclosure has no components") and introduces proper handling of case where there are no detected secondary components, but primary component (enumerated in num_enclosures) does exist. That fix was originally proposed by Ding Hui
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2023-53429 – btrfs: don't check PageError in __extent_writepage
https://notcve.org/view.php?id=CVE-2023-53429
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handle... • https://git.kernel.org/stable/c/61391d562229ed94899ed4b4973dc2f0c015292a •
CVSS: 7.8EPSS: 0%CPEs: 7EXPL: 0CVE-2023-53427 – cifs: Fix warning and UAF when destroy the MR list
https://notcve.org/view.php?id=CVE-2023-53427
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: cifs: Fix warning and UAF when destroy the MR list If the MR allocate failed, the MR recovery work not initialized and list not cleared. Then will be warning and UAF when release the MR: WARNING: CPU: 4 PID: 824 at kernel/workqueue.c:3066 __flush_work.isra.0+0xf7/0x110 CPU: 4 PID: 824 Comm: mount.cifs Not tainted 6.1.0-rc5+ #82 RIP: 0010:__flush_work.isra.0+0xf7/0x110 Call Trace:
CVSS: 7.8EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53426 – xsk: Fix xsk_diag use-after-free error during socket cleanup
https://notcve.org/view.php?id=CVE-2023-53426
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: xsk: Fix xsk_diag use-after-free error during socket cleanup Fix a use-after-free error that is possible if the xsk_diag interface is used after the socket has been unbound from the device. This can happen either due to the socket being closed or the device disappearing. In the early days of AF_XDP, the way we tested that a socket was not bound to a device was to simply check if the netdevice pointer in the xsk socket structure was NULL. La... • https://git.kernel.org/stable/c/ad7219cd8751bd258b9d1e69ae0654ec00f71875 • CWE-416: Use After Free •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53425 – media: platform: mediatek: vpu: fix NULL ptr dereference
https://notcve.org/view.php?id=CVE-2023-53425
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: media: platform: mediatek: vpu: fix NULL ptr dereference If pdev is NULL, then it is still dereferenced. This fixes this smatch warning: drivers/media/platform/mediatek/vpu/mtk_vpu.c:570 vpu_load_firmware() warn: address of NULL pointer 'pdev' This update provides the initial livepatch for this kernel update. This update does not contain any fixes and will be updated with livepatches later. • https://git.kernel.org/stable/c/3003a180ef6b9462f3cccc2a89884ef2332d2a1c • CWE-476: NULL Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53424 – clk: mediatek: fix of_iomap memory leak
https://notcve.org/view.php?id=CVE-2023-53424
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: fix of_iomap memory leak Smatch reports: drivers/clk/mediatek/clk-mtk.c:583 mtk_clk_simple_probe() warn: 'base' from of_iomap() not released on lines: 496. This problem was also found in linux-next. In mtk_clk_simple_probe(), base is not released when handling errors if clk_data is not existed, which may cause a leak. So free_base should be added here to release base. In the Linux kernel, the following vulnerability has been ... • https://git.kernel.org/stable/c/c58cd0e40ffac67961b945793876b973728f9b80 • CWE-401: Missing Release of Memory after Effective Lifetime •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2023-53423 – objtool: Fix memory leak in create_static_call_sections()
https://notcve.org/view.php?id=CVE-2023-53423
18 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: objtool: Fix memory leak in create_static_call_sections() strdup() allocates memory for key_name. We need to release the memory in the following error paths. Add free() to avoid memory leak. In the Linux kernel, the following vulnerability has been resolved: objtool: Fix memory leak in create_static_call_sections() strdup() allocates memory for key_name. We need to release the memory in the following error paths. • https://git.kernel.org/stable/c/1e7e47883830aae5e8246a22ca2fc6883c61acdf • CWE-401: Missing Release of Memory after Effective Lifetime •
CVSS: 7.8EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53422 – wifi: iwlwifi: fw: fix memory leak in debugfs
https://notcve.org/view.php?id=CVE-2023-53422
18 Sep 2025 — 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. 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... • https://git.kernel.org/stable/c/36dfe9ac6e8b8fc2e25733d003a867a40db791da • CWE-401: Missing Release of Memory after Effective Lifetime CWE-772: Missing Release of Resource after Effective Lifetime •