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/b4acb6c3ede88d6b7d33742a09e63cfce5e7fb69 •
CVSS: 9.3EPSS: 0%CPEs: 4EXPL: 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/314135b7bae9618a317874ae195272682cf2d5d4 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50527 – drm/amdgpu: Fix size validation for non-exclusive domains (v4)
https://notcve.org/view.php?id=CVE-2022-50527
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix size validation for non-exclusive domains (v4) Fix amdgpu_bo_validate_size() to check whether the TTM domain manager for the requested memory exists, else we get a kernel oops when dereferencing "man". v2: Make the patch standalone, i.e. not dependent on local patches. v3: Preserve old behaviour and just check that the manager pointer is not NULL. v4: Complain if GTT domain requested and it is uninitialized--most likely a bu... • https://git.kernel.org/stable/c/80546eef216854a7bd47e39e828f04b406c00599 • CWE-476: NULL Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50519 – nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
https://notcve.org/view.php?id=CVE-2022-50519
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure If creation or finalization of a checkpoint fails due to anomalies in the checkpoint metadata on disk, a kernel warning is generated. This patch replaces the WARN_ONs by nilfs_error, so that a kernel, booted with panic_on_warn, does not panic. A nilfs_error is appropriate here to handle the abnormal filesystem condition. This also replaces the detected error codes wi... • https://git.kernel.org/stable/c/b63026b5e13040cd5afa11769dd0d9e1504b031a •
CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50518 – parisc: Fix locking in pdc_iodc_print() firmware call
https://notcve.org/view.php?id=CVE-2022-50518
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: parisc: Fix locking in pdc_iodc_print() firmware call Utilize pdc_lock spinlock to protect parallel modifications of the iodc_dbuf[] buffer, check length to prevent buffer overflow of iodc_dbuf[], drop the iodc_retbuf[] buffer and fix some wrong indentings. In the Linux kernel, the following vulnerability has been resolved: parisc: Fix locking in pdc_iodc_print() firmware call Utilize pdc_lock spinlock to protect parallel modifications of t... • https://git.kernel.org/stable/c/04a603058e70b8b881bb7860b8bd649f931f2591 •
CVSS: 5.2EPSS: 0%CPEs: 4EXPL: 0CVE-2022-50516 – fs: dlm: fix invalid derefence of sb_lvbptr
https://notcve.org/view.php?id=CVE-2022-50516
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: fs: dlm: fix invalid derefence of sb_lvbptr I experience issues when putting a lkbsb on the stack and have sb_lvbptr field to a dangled pointer while not using DLM_LKF_VALBLK. It will crash with the following kernel message, the dangled pointer is here 0xdeadbeef as example: [ 102.749317] BUG: unable to handle page fault for address: 00000000deadbeef [ 102.749320] #PF: supervisor read access in kernel mode [ 102.749323] #PF: error_code(0x00... • https://git.kernel.org/stable/c/ea7be82fd7e1f5de72208bce93fbbe6de6c13dec • CWE-476: NULL Pointer Dereference •
CVSS: 5.6EPSS: 0%CPEs: 6EXPL: 0CVE-2022-50513 – staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv()
https://notcve.org/view.php?id=CVE-2022-50513
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv() In rtw_init_cmd_priv(), if `pcmdpriv->rsp_allocated_buf` is allocated in failure, then `pcmdpriv->cmd_allocated_buf` will be not properly released. Besides, considering there are only two error paths and the first one can directly return, so we do not need implicitly jump to the `exit` tag to execute the error handler. So this patch added `kfree(pcmdpriv->cmd_allocated_b... • https://git.kernel.org/stable/c/e5d8f05edb36fc4ab15beec62cb6ab62f5a60fe2 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2022-50512 – ext4: fix potential memory leak in ext4_fc_record_regions()
https://notcve.org/view.php?id=CVE-2022-50512
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: fix potential memory leak in ext4_fc_record_regions() As krealloc may return NULL, in this case 'state->fc_regions' may not be freed by krealloc, but 'state->fc_regions' already set NULL. Then will lead to 'state->fc_regions' memory leak. In the Linux kernel, the following vulnerability has been resolved: ext4: fix potential memory leak in ext4_fc_record_regions() As krealloc may return NULL, in this case 'state->fc_regions' may not b... • https://git.kernel.org/stable/c/2cfb769d60a2a57eb3566765428b6131cd16dcfe • CWE-772: Missing Release of Resource after Effective Lifetime •
CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53616 – jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount
https://notcve.org/view.php?id=CVE-2023-53616
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount syzbot found an invalid-free in diUnmount: BUG: KASAN: double-free in slab_free mm/slub.c:3661 [inline] BUG: KASAN: double-free in __kmem_cache_free+0x71/0x110 mm/slub.c:3674 Free of addr ffff88806f410000 by task syz-executor131/3632 CPU: 0 PID: 3632 Comm: syz-executor131 Not tainted 6.1.0-rc7-syzkaller-00012-gca57f02295f1 #0 Hardware name: Google Google Compute Engine/Google Comp... • https://git.kernel.org/stable/c/c3c0f0ddd851b3fa3e9d3450bbcd561f4f850469 •
CVSS: 7.1EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53612 – hwmon: (coretemp) Simplify platform device handling
https://notcve.org/view.php?id=CVE-2023-53612
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) Simplify platform device handling Coretemp's platform driver is unconventional. All the real work is done globally by the initcall and CPU hotplug notifiers, while the "driver" effectively just wraps an allocation and the registration of the hwmon interface in a long-winded round-trip through the driver core. The whole logic of dynamically creating and destroying platform devices to bring the interfaces up and down is erro... • https://git.kernel.org/stable/c/4000384684f612b3645a944f6acde0e65ac370b8 • CWE-476: NULL Pointer Dereference •