CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2023-54132 – erofs: stop parsing non-compact HEAD index if clusterofs is invalid
https://notcve.org/view.php?id=CVE-2023-54132
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: erofs: stop parsing non-compact HEAD index if clusterofs is invalid Syzbot generated a crafted image [1] with a non-compact HEAD index of clusterofs 33024 while valid numbers should be 0 ~ lclustersize-1, which causes the following unexpected behavior as below: BUG: unable to handle page fault for address: fffff52101a3fff9 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 23ffed067 P4D 23ffed067 PUD 0... • https://git.kernel.org/stable/c/02827e1796b33f1794966f5c3101f8da2dfa9c1d •
CVSS: 5.6EPSS: 0%CPEs: 5EXPL: 0CVE-2023-54131 – wifi: rt2x00: Fix memory leak when handling surveys
https://notcve.org/view.php?id=CVE-2023-54131
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: rt2x00: Fix memory leak when handling surveys When removing a rt2x00 device, its associated channel surveys are not freed, causing a memory leak observable with kmemleak: unreferenced object 0xffff9620f0881a00 (size 512): comm "systemd-udevd", pid 2290, jiffies 4294906974 (age 33.768s) hex dump (first 32 bytes): 70 44 12 00 00 00 00 00 92 8a 00 00 00 00 00 00 pD.............. 00 00 00 00 00 00 00 00 ab 87 01 00 00 00 00 00 .............. • https://git.kernel.org/stable/c/5447626910f5b8d964761ed4fa4feaf1a3ac47d0 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2023-54130 – hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling
https://notcve.org/view.php?id=CVE-2023-54130
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling Commit 55d1cbbbb29e ("hfs/hfsplus: use WARN_ON for sanity check") fixed a build warning by turning a comment into a WARN_ON(), but it turns out that syzbot then complains because it can trigger said warning with a corrupted hfs image. The warning actually does warn about a bad situation, but we are much better off just handling it as the error it is. So rather than war... • https://git.kernel.org/stable/c/55d1cbbbb29e6656c662ee8f73ba1fc4777532eb •
CVSS: 6.6EPSS: 0%CPEs: 4EXPL: 0CVE-2023-54129 – octeontx2-af: Add validation for lmac type
https://notcve.org/view.php?id=CVE-2023-54129
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: Add validation for lmac type Upon physical link change, firmware reports to the kernel about the change along with the details like speed, lmac_type_id, etc. Kernel derives lmac_type based on lmac_type_id received from firmware. In a few scenarios, firmware returns an invalid lmac_type_id, which is resulting in below kernel panic. This patch adds the missing validation of the lmac_type_id field. Internal error: Oops: 96000005 ... • https://git.kernel.org/stable/c/61071a871ea6eb2125ece91c1a0dbb124a318c8a •
CVSS: 5.6EPSS: 0%CPEs: 4EXPL: 0CVE-2023-54128 – fs: drop peer group ids under namespace lock
https://notcve.org/view.php?id=CVE-2023-54128
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: fs: drop peer group ids under namespace lock When cleaning up peer group ids in the failure path we need to make sure to hold on to the namespace lock. Otherwise another thread might just turn the mount from a shared into a non-shared mount concurrently. In the Linux kernel, the following vulnerability has been resolved: fs: drop peer group ids under namespace lock When cleaning up peer group ids in the failure path we need to make sure to ... • https://git.kernel.org/stable/c/2a1867219c7b27f928e2545782b86daaf9ad50bd •
CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0CVE-2023-54127 – fs/jfs: prevent double-free in dbUnmount() after failed jfs_remount()
https://notcve.org/view.php?id=CVE-2023-54127
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: fs/jfs: prevent double-free in dbUnmount() after failed jfs_remount() Syzkaller reported the following issue: ================================================================== BUG: KASAN: double-free in slab_free mm/slub.c:3787 [inline] BUG: KASAN: double-free in __kmem_cache_free+0x71/0x110 mm/slub.c:3800 Free of addr ffff888086408000 by task syz-executor.4/12750 [...] Call Trace:
CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2023-54126 – crypto: safexcel - Cleanup ring IRQ workqueues on load failure
https://notcve.org/view.php?id=CVE-2023-54126
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: crypto: safexcel - Cleanup ring IRQ workqueues on load failure A failure loading the safexcel driver results in the following warning on boot, because the IRQ affinity has not been correctly cleaned up. Ensure we clean up the affinity and workqueues on a failure to load the driver. crypto-safexcel: probe of f2800000.crypto failed with error -2 ------------[ cut here ]------------ WARNING: CPU: 1 PID: 232 at kernel/irq/manage.c:1913 free_irq... • https://git.kernel.org/stable/c/1b44c5a60c137e5fd0c2c8b86e58fdbc9cd181ce •
CVSS: 7.2EPSS: 0%CPEs: 2EXPL: 0CVE-2023-54125 – fs/ntfs3: Return error for inconsistent extended attributes
https://notcve.org/view.php?id=CVE-2023-54125
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Return error for inconsistent extended attributes ntfs_read_ea is called when we want to read extended attributes. There are some sanity checks for the validity of the EAs. However, it fails to return a proper error code for the inconsistent attributes, which might lead to unpredicted memory accesses after return. [ 138.916927] BUG: KASAN: use-after-free in ntfs_set_ea+0x453/0xbf0 [ 138.923876] Write of size 4 at addr ffff88800205... • https://git.kernel.org/stable/c/1474098b590a426d90f27bb992f17c326e0b60c1 •
CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2023-54124 – f2fs: fix to drop all dirty pages during umount() if cp_error is set
https://notcve.org/view.php?id=CVE-2023-54124
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to drop all dirty pages during umount() if cp_error is set xfstest generic/361 reports a bug as below: f2fs_bug_on(sbi, sbi->fsync_node_num); kernel BUG at fs/f2fs/super.c:1627! RIP: 0010:f2fs_put_super+0x3a8/0x3b0 Call Trace: generic_shutdown_super+0x8c/0x1b0 kill_block_super+0x2b/0x60 kill_f2fs_super+0x87/0x110 deactivate_locked_super+0x39/0x80 deactivate_super+0x46/0x50 cleanup_mnt+0x109/0x170 __cleanup_mnt+0x16/0x20 task_work_... • https://git.kernel.org/stable/c/92575f05a32dafb16348bfa5e62478118a9be069 •
CVSS: 7.1EPSS: 0%CPEs: 8EXPL: 0CVE-2023-54123 – md/raid10: fix memleak for 'conf->bio_split'
https://notcve.org/view.php?id=CVE-2023-54123
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix memleak for 'conf->bio_split' In the error path of raid10_run(), 'conf' need be freed, however, 'conf->bio_split' is missed and memory will be leaked. Since there are 3 places to free 'conf', factor out a helper to fix the problem. In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix memleak for 'conf->bio_split' In the error path of raid10_run(), 'conf' need be freed, however, 'conf->bio_split' ... • https://git.kernel.org/stable/c/fc9977dd069e4f82fcacb262652117c488647319 •