CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2023-54121 – btrfs: fix incorrect splitting in btrfs_drop_extent_map_range
https://notcve.org/view.php?id=CVE-2023-54121
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: btrfs: fix incorrect splitting in btrfs_drop_extent_map_range In production we were seeing a variety of WARN_ON()'s in the extent_map code, specifically in btrfs_drop_extent_map_range() when we have to call add_extent_mapping() for our second split. Consider the following extent map layout PINNED [0 16K) [32K, 48K) and then we call btrfs_drop_extent_map_range for [0, 36K), with skip_pinned == true. The initial loop will have start = 0 end =... • https://git.kernel.org/stable/c/55ef68990029fcd8d04d42fc184aa7fb18cf309e •
CVSS: 7.0EPSS: 0%CPEs: 8EXPL: 0CVE-2023-54120 – Bluetooth: Fix race condition in hidp_session_thread
https://notcve.org/view.php?id=CVE-2023-54120
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix race condition in hidp_session_thread There is a potential race condition in hidp_session_thread that may lead to use-after-free. For instance, the timer is active while hidp_del_timer is called in hidp_session_thread(). After hidp_session_put, then 'session' will be freed, causing kernel panic when hidp_idle_timeout is running. The solution is to use del_timer_sync instead of del_timer. Here is the call trace: ? • https://git.kernel.org/stable/c/152f47bd6b995e0e98c85672f6d19894bc287ef2 •
CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2023-54119 – inotify: Avoid reporting event with invalid wd
https://notcve.org/view.php?id=CVE-2023-54119
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: inotify: Avoid reporting event with invalid wd When inotify_freeing_mark() races with inotify_handle_inode_event() it can happen that inotify_handle_inode_event() sees that i_mark->wd got already reset to -1 and reports this value to userspace which can confuse the inotify listener. Avoid the problem by validating that wd is sensible (and pretend the mark got removed before the event got generated otherwise). In the Linux kernel, the follow... • https://git.kernel.org/stable/c/7e790dd5fc937bc8d2400c30a05e32a9e9eef276 •
CVSS: 7.1EPSS: 0%CPEs: 5EXPL: 0CVE-2023-54118 – serial: sc16is7xx: setup GPIO controller later in probe
https://notcve.org/view.php?id=CVE-2023-54118
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: serial: sc16is7xx: setup GPIO controller later in probe The GPIO controller component of the sc16is7xx driver is setup too early, which can result in a race condition where another device tries to utilise the GPIO lines before the sc16is7xx device has finished initialising. This issue manifests itself as an Oops when the GPIO lines are configured: Unable to handle kernel read from unreadable memory at virtual address ... pc : sc16is7xx_gpio... • https://git.kernel.org/stable/c/17b96b5c19bec791b433890549e44ca523dc82aa •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2023-54117 – s390/dcssblk: fix kernel crash with list_add corruption
https://notcve.org/view.php?id=CVE-2023-54117
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: s390/dcssblk: fix kernel crash with list_add corruption Commit fb08a1908cb1 ("dax: simplify the dax_device <-> gendisk association") introduced new logic for gendisk association, requiring drivers to explicitly call dax_add_host() and dax_remove_host(). For dcssblk driver, some dax_remove_host() calls were missing, e.g. in device remove path. The commit also broke error handling for out_dax case in device add path, resulting in an extra put... • https://git.kernel.org/stable/c/fb08a1908cb119a4585611d91461ab6d27756b14 •
CVSS: 7.1EPSS: 0%CPEs: 3EXPL: 0CVE-2023-54116 – drm/fbdev-generic: prohibit potential out-of-bounds access
https://notcve.org/view.php?id=CVE-2023-54116
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/fbdev-generic: prohibit potential out-of-bounds access The fbdev test of IGT may write after EOF, which lead to out-of-bound access for drm drivers with fbdev-generic. For example, run fbdev test on a x86+ast2400 platform, with 1680x1050 resolution, will cause the linux kernel hang with the following call trace: Oops: 0000 [#1] PREEMPT SMP PTI [IGT] fbdev: starting subtest eof Workqueue: events drm_fb_helper_damage_work [drm_kms_helper]... • https://git.kernel.org/stable/c/aa15c677cc34e626789cb65b8e7375180851c03b •
CVSS: 5.6EPSS: 0%CPEs: 8EXPL: 0CVE-2023-54115 – pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db()
https://notcve.org/view.php?id=CVE-2023-54115
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db() When nonstatic_release_resource_db() frees all resources associated with an PCMCIA socket, it forgets to free socket_data too, causing a memory leak observable with kmemleak: unreferenced object 0xc28d1000 (size 64): comm "systemd-udevd", pid 297, jiffies 4294898478 (age 194.484s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 f0 85 0e c3 00 00 00 00 ............... • https://git.kernel.org/stable/c/bde0b6da7bd893c37afaee3555cc3ac3be582313 •
CVSS: 7.1EPSS: 0%CPEs: 8EXPL: 0CVE-2023-54114 – net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment()
https://notcve.org/view.php?id=CVE-2023-54114
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() As the call trace shows, skb_panic was caused by wrong skb->mac_header in nsh_gso_segment(): invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 3 PID: 2737 Comm: syz Not tainted 6.3.0-next-20230505 #1 RIP: 0010:skb_panic+0xda/0xe0 call Trace: skb_push+0x91/0xa0 nsh_gso_segment+0x4f3/0x570 skb_mac_gso_segment+0x19e/0x270 __skb_gso_segment+0x1e8/0x3c0 validate_xmit_skb+... • https://git.kernel.org/stable/c/c411ed854584a71b0e86ac3019b60e4789d88086 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2023-54113 – rcu: dump vmalloc memory info safely
https://notcve.org/view.php?id=CVE-2023-54113
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: rcu: dump vmalloc memory info safely Currently, for double invoke call_rcu(), will dump rcu_head objects memory info, if the objects is not allocated from the slab allocator, the vmalloc_dump_obj() will be invoke and the vmap_area_lock spinlock need to be held, since the call_rcu() can be invoked in interrupt context, therefore, there is a possibility of spinlock deadlock scenarios. And in Preempt-RT kernel, the rcutorture test also trigger... • https://git.kernel.org/stable/c/98f180837a896ecedf8f7e12af22b57f271d43c9 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-54112 – kcm: Fix memory leak in error path of kcm_sendmsg()
https://notcve.org/view.php?id=CVE-2023-54112
24 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: kcm: Fix memory leak in error path of kcm_sendmsg() syzbot reported a memory leak like below: BUG: memory leak unreferenced object 0xffff88810b088c00 (size 240): comm "syz-executor186", pid 5012, jiffies 4294943306 (age 13.680s) hex dump (first 32 bytes): 00 89 08 0b 81 88 ff ff 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [