CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53594 – driver core: fix resource leak in device_add()
https://notcve.org/view.php?id=CVE-2023-53594
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: driver core: fix resource leak in device_add() When calling kobject_add() failed in device_add(), it will call cleanup_glue_dir() to free resource. But in kobject_add(), dev->kobj.parent has been set to NULL. This will cause resource leak. The process is as follows: device_add() get_device_parent() class_dir_create_and_add() kobject_add() //kobject_get() ... dev->kobj.parent = kobj; ... kobject_add() //failed, but set dev->kobj.parent = NUL... • https://git.kernel.org/stable/c/cebf8fd16900fdfd58c0028617944f808f97fe50 • CWE-771: Missing Reference to Active Allocated Resource •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53593 – cifs: Release folio lock on fscache read hit.
https://notcve.org/view.php?id=CVE-2023-53593
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: cifs: Release folio lock on fscache read hit. Under the current code, when cifs_readpage_worker is called, the call contract is that the callee should unlock the page. This is documented in the read_folio section of Documentation/filesystems/vfs.rst as: > The filesystem should unlock the folio once the read has completed, > whether it was successful or not. Without this change, when fscache is in use and cache hit occurs during a read, the ... • https://git.kernel.org/stable/c/c3ac8323f2f5b50e32681c254b8318f7fa2dc3f4 •
CVSS: 7.2EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53588 – wifi: mac80211: check for station first in client probe
https://notcve.org/view.php?id=CVE-2023-53588
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: check for station first in client probe When probing a client, first check if we have it, and then check for the channel context, otherwise you can trigger the warning there easily by probing when the AP isn't even started yet. Since a client existing means the AP is also operating, we can then keep the warning. Also simplify the moved code a bit. In the Linux kernel, the following vulnerability has been resolved: wifi: mac8... • https://git.kernel.org/stable/c/7e1cda5cf07f848e6b50b4e5e7761ffbce905a3d •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2023-53587 – ring-buffer: Sync IRQ works before buffer destruction
https://notcve.org/view.php?id=CVE-2023-53587
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Sync IRQ works before buffer destruction If something was written to the buffer just before destruction, it may be possible (maybe not in a real system, but it did happen in ARCH=um with time-travel) to destroy the ringbuffer before the IRQ work ran, leading this KASAN report (or a crash without KASAN): BUG: KASAN: slab-use-after-free in irq_work_run_list+0x11a/0x13a Read of size 8 at addr 000000006d640a48 by task swapper/0 CPU... • https://git.kernel.org/stable/c/15693458c4bc0693fd63a50d60f35b628fcf4e29 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53584 – ubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process
https://notcve.org/view.php?id=CVE-2023-53584
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process There are two states for ubifs writing pages: 1. Dirty, Private 2. Not Dirty, Not Private The normal process cannot go to ubifs_releasepage() which means there exists pages being private but not dirty. Reproducer[1] shows that it could occur (which maybe related to [2]) with following process: PA PB PC lock(page)[PA] ubifs_write_end attach_page_private // set Private __s... • https://git.kernel.org/stable/c/1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d •
CVSS: 9.6EPSS: 0%CPEs: 7EXPL: 0CVE-2023-53582 – wifi: brcmfmac: ensure CLM version is null-terminated to prevent stack-out-of-bounds
https://notcve.org/view.php?id=CVE-2023-53582
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: ensure CLM version is null-terminated to prevent stack-out-of-bounds Fix a stack-out-of-bounds read in brcmfmac that occurs when 'buf' that is not null-terminated is passed as an argument of strreplace() in brcmf_c_preinit_dcmds(). This buffer is filled with a CLM version string by memcpy() in brcmf_fil_iovar_data_get(). Ensure buf is null-terminated. Found by a modified version of syzkaller. [ 33.004414][ T1896] brcmfmac: b... • https://git.kernel.org/stable/c/3b173b4ad9c001a555f44adc7836d6fe3afbe9ec • CWE-125: Out-of-bounds Read •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50504 – powerpc/rtas: avoid scheduling in rtas_os_term()
https://notcve.org/view.php?id=CVE-2022-50504
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: powerpc/rtas: avoid scheduling in rtas_os_term() It's unsafe to use rtas_busy_delay() to handle a busy status from the ibm,os-term RTAS function in rtas_os_term(): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b BUG: sleeping function called from invalid context at arch/powerpc/kernel/rtas.c:618 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 1, name: swapper/0 preempt_count: 2, expected: 0 CPU: 7 PID: 1 Comm:... • https://git.kernel.org/stable/c/f413135b337c4e90c1e593c6613f8717e17bc724 •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50503 – mtd: lpddr2_nvm: Fix possible null-ptr-deref
https://notcve.org/view.php?id=CVE-2022-50503
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: mtd: lpddr2_nvm: Fix possible null-ptr-deref It will cause null-ptr-deref when resource_size(add_range) invoked, if platform_get_resource() returns NULL. In the Linux kernel, the following vulnerability has been resolved: mtd: lpddr2_nvm: Fix possible null-ptr-deref It will cause null-ptr-deref when resource_size(add_range) invoked, if platform_get_resource() returns NULL. • https://git.kernel.org/stable/c/96ba9dd65788a0bd2a7d1e57ec78b7642f0ccc25 •
CVSS: 6.4EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50501 – media: coda: Add check for dcoda_iram_alloc
https://notcve.org/view.php?id=CVE-2022-50501
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: media: coda: Add check for dcoda_iram_alloc As the coda_iram_alloc may return NULL pointer, it should be better to check the return value in order to avoid NULL poineter dereference, same as the others. In the Linux kernel, the following vulnerability has been resolved: media: coda: Add check for dcoda_iram_alloc As the coda_iram_alloc may return NULL pointer, it should be better to check the return value in order to avoid NULL poineter der... • https://git.kernel.org/stable/c/b313bcc9a46795c0233a765411cef9a15caaa7fb •
CVSS: 7.8EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50497 – binfmt_misc: fix shift-out-of-bounds in check_special_flags
https://notcve.org/view.php?id=CVE-2022-50497
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: fix shift-out-of-bounds in check_special_flags UBSAN reported a shift-out-of-bounds warning: left shift of 1 by 31 places cannot be represented in type 'int' Call Trace: