CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50874 – RDMA/erdma: Fix refcount leak in erdma_mmap
https://notcve.org/view.php?id=CVE-2022-50874
30 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: RDMA/erdma: Fix refcount leak in erdma_mmap rdma_user_mmap_entry_get() take reference, we should release it when not need anymore, add the missing rdma_user_mmap_entry_put() in the error path to fix it. • https://git.kernel.org/stable/c/155055771704f8cbb5c176a4309b7dc30a50450c •
CVSS: -EPSS: 0%CPEs: 9EXPL: 0CVE-2023-54279 – MIPS: fw: Allow firmware to pass a empty env
https://notcve.org/view.php?id=CVE-2023-54279
30 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: MIPS: fw: Allow firmware to pass a empty env fw_getenv will use env entry to determine style of env, however it is legal for firmware to just pass a empty list. Check if first entry exist before running strchr to avoid null pointer dereference. • https://git.kernel.org/stable/c/f334b31625683418aaa2a335470eec950a95a254 •
CVSS: -EPSS: 0%CPEs: 7EXPL: 0CVE-2023-54277 – fbdev: udlfb: Fix endpoint check
https://notcve.org/view.php?id=CVE-2023-54277
30 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: fbdev: udlfb: Fix endpoint check The syzbot fuzzer detected a problem in the udlfb driver, caused by an endpoint not having the expected type: usb 1-1: Read EDID byte 0 failed: -71 usb 1-1: Unable to get valid EDID from device/display ------------[ cut here ]------------ usb 1-1: BOGUS urb xfer, pipe 3 != type 1 WARNING: CPU: 0 PID: 9 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 Modules linked in: CPU... • https://git.kernel.org/stable/c/f6db63819db632158647d5bbf4d7d2d90dc1a268 •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2023-54275 – wifi: ath11k: Fix memory leak in ath11k_peer_rx_frag_setup
https://notcve.org/view.php?id=CVE-2023-54275
30 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: Fix memory leak in ath11k_peer_rx_frag_setup crypto_alloc_shash() allocates resources, which should be released by crypto_free_shash(). When ath11k_peer_find() fails, there has memory leak. Add missing crypto_free_shash() to fix this. • https://git.kernel.org/stable/c/243874c64c8137bc90455200a7735da72836ecab •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2023-54274 – RDMA/srpt: Add a check for valid 'mad_agent' pointer
https://notcve.org/view.php?id=CVE-2023-54274
30 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: RDMA/srpt: Add a check for valid 'mad_agent' pointer When unregistering MAD agent, srpt module has a non-null check for 'mad_agent' pointer before invoking ib_unregister_mad_agent(). This check can pass if 'mad_agent' variable holds an error value. The 'mad_agent' can have an error value for a short window when srpt_add_one() and srpt_remove_one() is executed simultaneously. In srpt module, added a valid pointer check for 'sport->mad_agent'... • https://git.kernel.org/stable/c/a42d985bd5b234da8b61347a78dc3057bf7bb94d •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2023-54272 – fs/ntfs3: Fix a possible null-pointer dereference in ni_clear()
https://notcve.org/view.php?id=CVE-2023-54272
30 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix a possible null-pointer dereference in ni_clear() In a previous commit c1006bd13146, ni->mi.mrec in ni_write_inode() could be NULL, and thus a NULL check is added for this variable. However, in the same call stack, ni->mi.mrec can be also dereferenced in ni_clear(): ntfs_evict_inode(inode) ni_write_inode(inode, ...) ni = ntfs_i(inode); is_rec_inuse(ni->mi.mrec) -> Add a NULL check by previous commit ni_clear(ntfs_i(inode)) is_... • https://git.kernel.org/stable/c/20f9bfc664d6a478f9a5bbc0c380f80f7a1a06c6 •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2023-54271 – blk-cgroup: Fix NULL deref caused by blkg_policy_data being installed before init
https://notcve.org/view.php?id=CVE-2023-54271
30 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: Fix NULL deref caused by blkg_policy_data being installed before init blk-iocost sometimes causes the following crash: BUG: kernel NULL pointer dereference, address: 00000000000000e0 ... RIP: 0010:_raw_spin_lock+0x17/0x30 Code: be 01 02 00 00 e8 79 38 39 ff 31 d2 89 d0 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 65 ff 05 48 d0 34 7e b9 01 00 00 00 31 c0
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2023-54270 – media: usb: siano: Fix use after free bugs caused by do_submit_urb
https://notcve.org/view.php?id=CVE-2023-54270
30 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: media: usb: siano: Fix use after free bugs caused by do_submit_urb There are UAF bugs caused by do_submit_urb(). One of the KASan reports is shown below: [ 36.403605] BUG: KASAN: use-after-free in worker_thread+0x4a2/0x890 [ 36.406105] Read of size 8 at addr ffff8880059600e8 by task kworker/0:2/49 [ 36.408316] [ 36.408867] CPU: 0 PID: 49 Comm: kworker/0:2 Not tainted 6.2.0-rc3-15798-g5a41237ad1d4-dir8 [ 36.411696] Hardware name: QEMU Standa... • https://git.kernel.org/stable/c/dd47fbd40e6ea6884e295e13a2e50b0894258fdf •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2023-54269 – SUNRPC: double free xprt_ctxt while still in use
https://notcve.org/view.php?id=CVE-2023-54269
30 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: SUNRPC: double free xprt_ctxt while still in use When an RPC request is deferred, the rq_xprt_ctxt pointer is moved out of the svc_rqst into the svc_deferred_req. When the deferred request is revisited, the pointer is copied into the new svc_rqst - and also remains in the svc_deferred_req. In the (rare?) case that the request is deferred a second time, the old svc_deferred_req is reused - it still has all the correct content. However in tha... • https://git.kernel.org/stable/c/f5e13d700a4d40ccde3d36e383f9247dcb3c1d2d •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2023-54268 – debugobjects: Don't wake up kswapd from fill_pool()
https://notcve.org/view.php?id=CVE-2023-54268
30 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: debugobjects: Don't wake up kswapd from fill_pool() syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd, which acquires kswapd_wait::lock. Since fill_pool() might be called with arbitrary locks held, fill_pool() should not assume that acquiring kswapd_wait::lock is safe. Use __GFP_HIGH instead and... • https://git.kernel.org/stable/c/3ac7fe5a4aab409bd5674d0b070bce97f9d20872 •