CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53164 – irqchip/ti-sci: Fix refcount leak in ti_sci_intr_irq_domain_probe
https://notcve.org/view.php?id=CVE-2023-53164
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: irqchip/ti-sci: Fix refcount leak in ti_sci_intr_irq_domain_probe of_irq_find_parent() returns a node pointer with refcount incremented, We should use of_node_put() on it when not needed anymore. Add missing of_node_put() to avoid refcount leak. In the Linux kernel, the following vulnerability has been resolved: irqchip/ti-sci: Fix refcount leak in ti_sci_intr_irq_domain_probe of_irq_find_parent() returns a node pointer with refcount increm... • https://git.kernel.org/stable/c/cd844b0715ceda3287d1fa8e5d8e1b25a85c9b0f •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53163 – fs/ntfs3: don't hold ni_lock when calling truncate_setsize()
https://notcve.org/view.php?id=CVE-2023-53163
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: don't hold ni_lock when calling truncate_setsize() syzbot is reporting hung task at do_user_addr_fault() [1], for there is a silent deadlock between PG_locked bit and ni_lock lock. Since filemap_update_page() calls filemap_read_folio() after calling folio_trylock() which will set PG_locked bit, ntfs_truncate() must not call truncate_setsize() which will wait for PG_locked bit to be cleared when holding ni_lock lock. In the Linux k... • https://git.kernel.org/stable/c/4342306f0f0d5ff4315a204d315c1b51b914fca5 •
CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53153 – wifi: cfg80211: Fix use after free for wext
https://notcve.org/view.php?id=CVE-2023-53153
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: Fix use after free for wext Key information in wext.connect is not reset on (re)connect and can hold data from a previous connection. Reset key data to avoid that drivers or mac80211 incorrectly detect a WEP connection request and access the freed or already reused memory. Additionally optimize cfg80211_sme_connect() and avoid an useless schedule of conn_work. In the Linux kernel, the following vulnerability has been resolve... • https://git.kernel.org/stable/c/fffd0934b9390f34bec45762192b7edd3b12b4b5 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53152 – drm/amdgpu: fix calltrace warning in amddrm_buddy_fini
https://notcve.org/view.php?id=CVE-2023-53152
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix calltrace warning in amddrm_buddy_fini The following call trace is observed when removing the amdgpu driver, which is caused by that BOs allocated for psp are not freed until removing. [61811.450562] RIP: 0010:amddrm_buddy_fini.cold+0x29/0x47 [amddrm_buddy] [61811.450577] Call Trace: [61811.450577]
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53151 – md/raid10: prevent soft lockup while flush writes
https://notcve.org/view.php?id=CVE-2023-53151
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: md/raid10: prevent soft lockup while flush writes Currently, there is no limit for raid1/raid10 plugged bio. While flushing writes, raid1 has cond_resched() while raid10 doesn't, and too many writes can cause soft lockup. Follow up soft lockup can be triggered easily with writeback test for raid10 with ramdisks: watchdog: BUG: soft lockup - CPU#10 stuck for 27s! [md0_raid10:1293] Call Trace:
CVSS: 7.1EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53150 – scsi: qla2xxx: Pointer may be dereferenced
https://notcve.org/view.php?id=CVE-2023-53150
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Pointer may be dereferenced Klocwork tool reported pointer 'rport' returned from call to function fc_bsg_to_rport() may be NULL and will be dereferenced. Add a fix to validate rport before dereferencing. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Pointer may be dereferenced Klocwork tool reported pointer 'rport' returned from call to function fc_bsg_to_rport() may be NULL and will be de... • https://git.kernel.org/stable/c/7c3df1320e5e875478775e78d01a09aee96b8abe •
CVSS: 5.8EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53149 – ext4: avoid deadlock in fs reclaim with page writeback
https://notcve.org/view.php?id=CVE-2023-53149
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: avoid deadlock in fs reclaim with page writeback Ext4 has a filesystem wide lock protecting ext4_writepages() calls to avoid races with switching of journalled data flag or inode format. This lock can however cause a deadlock like: CPU0 CPU1 ext4_writepages() percpu_down_read(sbi->s_writepages_rwsem); ext4_change_inode_journal_flag() percpu_down_write(sbi->s_writepages_rwsem); - blocks, all readers block from now on ext4_do_writepages... • https://git.kernel.org/stable/c/c8585c6fcaf2011de54c3592e80a634a2b9e1a7f • CWE-833: Deadlock •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53148 – igb: Fix igb_down hung on surprise removal
https://notcve.org/view.php?id=CVE-2023-53148
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: igb: Fix igb_down hung on surprise removal In a setup where a Thunderbolt hub connects to Ethernet and a display through USB Type-C, users may experience a hung task timeout when they remove the cable between the PC and the Thunderbolt hub. This is because the igb_down function is called multiple times when the Thunderbolt hub is unplugged. For example, the igb_io_error_detected triggers the first call, and the igb_remove triggers the secon... • https://git.kernel.org/stable/c/9d5c824399dea881779d78a6c147288bf2dccb6b • CWE-1341: Multiple Releases of Same Resource or Handle •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53147 – xfrm: add NULL check in xfrm_update_ae_params
https://notcve.org/view.php?id=CVE-2023-53147
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: xfrm: add NULL check in xfrm_update_ae_params Normally, x->replay_esn and x->preplay_esn should be allocated at xfrm_alloc_replay_state_esn(...) in xfrm_state_construct(...), hence the xfrm_update_ae_params(...) is okay to update them. However, the current implementation of xfrm_new_ae(...) allows a malicious user to directly dereference a NULL pointer and crash the kernel like below. BUG: kernel NULL pointer dereference, address: 000000000... • https://git.kernel.org/stable/c/d8647b79c3b7e223ac051439d165bc8e7bbb832f • CWE-476: NULL Pointer Dereference •
CVSS: 8.8EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50261 – drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid()
https://notcve.org/view.php?id=CVE-2022-50261
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid() With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed. A proposed warning in clang... • https://git.kernel.org/stable/c/5402626c83a2f19da14859e2bab231a53e16ee74 •