CVSS: 7.8EPSS: 0%CPEs: 5EXPL: 0CVE-2023-53626 – ext4: fix possible double unlock when moving a directory
https://notcve.org/view.php?id=CVE-2023-53626
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: fix possible double unlock when moving a directory The SUSE Linux Enterprise 15 SP5 RT kernel was updated to fix various security issues. • https://git.kernel.org/stable/c/8dac5a63cf79707b547ea3d425fead5f4482198f • CWE-459: Incomplete Cleanup •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2023-53625 – drm/i915/gvt: fix vgpu debugfs clean in remove
https://notcve.org/view.php?id=CVE-2023-53625
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/i915/gvt: fix vgpu debugfs clean in remove Check carefully on root debugfs available when destroying vgpu, e.g in remove case drm minor's debugfs root might already be destroyed, which led to kernel oops like below. Console: switching to colour dummy device 80x25 i915 0000:00:02.0: MDEV: Unregistering intel_vgpu_mdev b1338b2d-a709-4c23-b766-cc436c36cdf0: Removing from iommu group 14 BUG: kernel NULL pointer dereference, address: 0000000... • https://git.kernel.org/stable/c/bc7b0be316aebac42eb9e8e54c984609555944da • CWE-476: NULL Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53624 – net/sched: sch_fq: fix integer overflow of "credit"
https://notcve.org/view.php?id=CVE-2023-53624
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_fq: fix integer overflow of "credit" if sch_fq is configured with "initial quantum" having values greater than INT_MAX, the first assignment of "credit" does signed integer overflow to a very negative value. In this situation, the syzkaller script provided by Cristoph triggers the CPU soft-lockup warning even with few sockets. It's not an infinite loop, but "credit" wasn't probably meant to be minus 2Gb for each new flow. Cap... • https://git.kernel.org/stable/c/afe4fd062416b158a8a8538b23adc1930a9b88dc •
CVSS: 5.7EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53623 – mm/swap: fix swap_info_struct race between swapoff and get_swap_pages()
https://notcve.org/view.php?id=CVE-2023-53623
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: mm/swap: fix swap_info_struct race between swapoff and get_swap_pages() The si->lock must be held when deleting the si from the available list. Otherwise, another thread can re-add the si to the available list, which can lead to memory corruption. The only place we have found where this happens is in the swapoff path. This case can be described as below: core 0 core 1 swapoff del_from_avail_list(si) waiting try lock si->lock acquire swap_av... • https://git.kernel.org/stable/c/a2468cc9bfdff6139f59ca896671e5819ff5f94a • CWE-413: Improper Resource Locking •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53622 – gfs2: Fix possible data races in gfs2_show_options()
https://notcve.org/view.php?id=CVE-2023-53622
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix possible data races in gfs2_show_options() Some fields such as gt_logd_secs of the struct gfs2_tune are accessed without holding the lock gt_spin in gfs2_show_options(): val = sdp->sd_tune.gt_logd_secs; if (val != 30) seq_printf(s, ",commit=%d", val); And thus can cause data races when gfs2_show_options() and other functions such as gfs2_reconfigure() are concurrently executed: spin_lock(>->gt_spin); gt->gt_logd_secs = newargs->... • https://git.kernel.org/stable/c/48c2b613616235d7c97fda5982f50100a6c79166 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53620 – md: fix soft lockup in status_resync
https://notcve.org/view.php?id=CVE-2023-53620
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: md: fix soft lockup in status_resync status_resync() will calculate 'curr_resync - recovery_active' to show user a progress bar like following: [============>........] resync = 61.4% 'curr_resync' and 'recovery_active' is updated in md_do_sync(), and status_resync() can read them concurrently, hence it's possible that 'curr_resync - recovery_active' can overflow to a huge number. In this case status_resync() will be stuck in the loop to pri... • https://git.kernel.org/stable/c/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 •
CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53619 – netfilter: conntrack: Avoid nf_ct_helper_hash uses after free
https://notcve.org/view.php?id=CVE-2023-53619
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free If nf_conntrack_init_start() fails (for example due to a register_nf_conntrack_bpf() failure), the nf_conntrack_helper_fini() clean-up path frees the nf_ct_helper_hash map. When built with NF_CONNTRACK=y, further netfilter modules (e.g: netfilter_conntrack_ftp) can still be loaded and call nf_conntrack_helpers_register(), independently of whether nf_conntrack initialized correctl... • https://git.kernel.org/stable/c/12f7a505331e6b2754684b509f2ac8f0011ce644 •
CVSS: 9.3EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53618 – btrfs: reject invalid reloc tree root keys with stack dump
https://notcve.org/view.php?id=CVE-2023-53618
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the abo... • https://git.kernel.org/stable/c/259ee7754b6793af8bdd77f9ca818bc41cfe9541 •
CVSS: 7.2EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50534 – dm thin: Use last transaction's pmd->root when commit failed
https://notcve.org/view.php?id=CVE-2022-50534
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: dm thin: Use last transaction's pmd->root when commit failed Recently we found a softlock up problem in dm thin pool btree lookup code due to corrupted metadata: Kernel panic - not syncing: softlockup: hung tasks CPU: 7 PID: 2669225 Comm: kworker/u16:3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: dm-thin do_worker [dm_thin_pool] Call Trace:
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50532 – scsi: mpt3sas: Fix possible resource leaks in mpt3sas_transport_port_add()
https://notcve.org/view.php?id=CVE-2022-50532
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Fix possible resource leaks in mpt3sas_transport_port_add() In mpt3sas_transport_port_add(), if sas_rphy_add() returns error, sas_rphy_free() needs be called to free the resource allocated in sas_end_device_alloc(). Otherwise a kernel crash will happen: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000108 CPU: 45 PID: 37020 Comm: bash Kdump: loaded Tainted: G W 6.1.0-rc1+ #189 pstate: 60000005 ... • https://git.kernel.org/stable/c/f92363d12359498f9a9960511de1a550f0ec41c2 • CWE-476: NULL Pointer Dereference •