CVSS: 5.5EPSS: 0%CPEs: 12EXPL: 0CVE-2023-53731 – netlink: fix potential deadlock in netlink_set_err()
https://notcve.org/view.php?id=CVE-2023-53731
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: netlink: fix potential deadlock in netlink_set_err() syzbot reported a possible deadlock in netlink_set_err() [1] A similar issue was fixed in commit 1d482e666b8e ("netlink: disable IRQs for netlink_lock_table()") in netlink_lock_table() This patch adds IRQ safety to netlink_set_err() and __netlink_diag_dump() which were not covered by cited commit. [1] WARNING: possible irq lock inversion dependency detected 6.4.0-rc6-syzkaller-00240-g4e9f... • https://git.kernel.org/stable/c/82b2ea5f904b3826934df4a00f3b8806272185f6 •
CVSS: 7.1EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53730 – blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
https://notcve.org/view.php?id=CVE-2023-53730
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled when unlock. DEADLOCK might happen if we have held other locks and disabled IRQ before invoking it. Fix it by using spin_lock_irqsave() instead, which can keep IRQ state consistent with before when unlock. ================================ WARNING: inconsistent lock state 5.10.0-02758-g8e5f91fd772f #26 Not ... • https://git.kernel.org/stable/c/b0853ab4a238c54b8f97ca7dde1ae156e2bbd5e4 •
CVSS: 9.4EPSS: 0%CPEs: 7EXPL: 0CVE-2023-53729 – soc: qcom: qmi_encdec: Restrict string length in decode
https://notcve.org/view.php?id=CVE-2023-53729
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: soc: qcom: qmi_encdec: Restrict string length in decode The QMI TLV value for strings in a lot of qmi element info structures account for null terminated strings with MAX_LEN + 1. If a string is actually MAX_LEN + 1 length, this will cause an out of bounds access when the NULL character is appended in decoding. In the Linux kernel, the following vulnerability has been resolved: soc: qcom: qmi_encdec: Restrict string length in decode The QMI... • https://git.kernel.org/stable/c/9b8a11e82615274d4133aab3cf5aa1c59191f0a2 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53728 – posix-timers: Ensure timer ID search-loop limit is valid
https://notcve.org/view.php?id=CVE-2023-53728
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: posix-timers: Ensure timer ID search-loop limit is valid posix_timer_add() tries to allocate a posix timer ID by starting from the cached ID which was stored by the last successful allocation. This is done in a loop searching the ID space for a free slot one by one. The loop has to terminate when the search wrapped around to the starting point. But that's racy vs. establishing the starting point. That is read out lockless, which leads to th... • https://git.kernel.org/stable/c/8dc52c200b889bc1cb34288fbf623d4ff381d2ae •
CVSS: 7.2EPSS: 0%CPEs: 5EXPL: 0CVE-2023-53727 – net/sched: fq_pie: avoid stalls in fq_pie_timer()
https://notcve.org/view.php?id=CVE-2023-53727
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: net/sched: fq_pie: avoid stalls in fq_pie_timer() When setting a high number of flows (limit being 65536), fq_pie_timer() is currently using too much time as syzbot reported. Add logic to yield the cpu every 2048 flows (less than 150 usec on debug kernels). It should also help by not blocking qdisc fast paths for too long. Worst case (65536 flows) would need 31 jiffies for a complete scan. Relevant extract from syzbot report: rcu: INFO: rcu... • https://git.kernel.org/stable/c/ec97ecf1ebe485a17cd8395a5f35e6b80b57665a •
CVSS: 6.1EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53726 – arm64: csum: Fix OoB access in IP checksum code for negative lengths
https://notcve.org/view.php?id=CVE-2023-53726
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: arm64: csum: Fix OoB access in IP checksum code for negative lengths Although commit c2c24edb1d9c ("arm64: csum: Fix pathological zero-length calls") added an early return for zero-length input, syzkaller has popped up with an example of a _negative_ length which causes an undefined shift and an out-of-bounds read: | BUG: KASAN: slab-out-of-bounds in do_csum+0x44/0x254 arch/arm64/lib/csum.c:39 | Read of size 4294966928 at addr ffff0000d7ac0... • https://git.kernel.org/stable/c/5777eaed566a1d63e344d3dd8f2b5e33be20643e •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53725 – clocksource/drivers/cadence-ttc: Fix memory leak in ttc_timer_probe
https://notcve.org/view.php?id=CVE-2023-53725
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: clocksource/drivers/cadence-ttc: Fix memory leak in ttc_timer_probe Smatch reports: drivers/clocksource/timer-cadence-ttc.c:529 ttc_timer_probe() warn: 'timer_baseaddr' from of_iomap() not released on lines: 498,508,516. timer_baseaddr may have the problem of not being released after use, I replaced it with the devm_of_iomap() function and added the clk_put() function to cleanup the "clk_ce" and "clk_cs". In the Linux kernel, the following ... • https://git.kernel.org/stable/c/e932900a3279b5dbb6d8f43c7b369003620e137c •
CVSS: 8.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53722 – md: raid1: fix potential OOB in raid1_remove_disk()
https://notcve.org/view.php?id=CVE-2023-53722
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: md: raid1: fix potential OOB in raid1_remove_disk() If rddev->raid_disk is greater than mddev->raid_disks, there will be an out-of-bounds in raid1_remove_disk(). We have already found similar reports as follows: 1) commit d17f744e883b ("md-raid10: fix KASAN warning") 2) commit 1ebc2cec0b7d ("dm raid: fix KASAN warning in raid5_remove_disk") Fix this bug by checking whether the "number" variable is valid. In the Linux kernel, the following v... • https://git.kernel.org/stable/c/beedf40f73939f248c81802eda08a2a8148ea13e •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2023-53721 – wifi: ath12k: Fix a NULL pointer dereference in ath12k_mac_op_hw_scan()
https://notcve.org/view.php?id=CVE-2023-53721
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Fix a NULL pointer dereference in ath12k_mac_op_hw_scan() In ath12k_mac_op_hw_scan(), the return value of kzalloc() is directly used in memcpy(), which may lead to a NULL pointer dereference on failure of kzalloc(). Fix this bug by adding a check of arg.extraie.ptr. Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0-03427-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.15378.4 In the Linux kernel, the following vulnerability has been resolved: wifi: a... • https://git.kernel.org/stable/c/5a263df398b581189fe632b4ab8440f3dd76c251 •
CVSS: 6.3EPSS: 0%CPEs: 5EXPL: 0CVE-2023-53718 – ring-buffer: Do not swap cpu_buffer during resize process
https://notcve.org/view.php?id=CVE-2023-53718
22 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Do not swap cpu_buffer during resize process When ring_buffer_swap_cpu was called during resize process, the cpu buffer was swapped in the middle, resulting in incorrect state. Continuing to run in the wrong state will result in oops. This issue can be easily reproduced using the following two scripts: /tmp # cat test1.sh //#! /bin/sh for i in `seq 0 100000` do echo 2000 > /sys/kernel/debug/tracing/buffer_size_kb sleep 0.5 echo... • https://git.kernel.org/stable/c/66a3b2a121386702663065d5c9e5a33c03d3f4a2 •