CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2025-71185 – dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation
https://notcve.org/view.php?id=CVE-2025-71185
31 Jan 2026 — In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation Make sure to drop the reference taken when looking up the crossbar platform device during am335x route allocation. In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation Make sure to drop the reference taken when looking up the crossbar platform device during am335x route allocation. • https://git.kernel.org/stable/c/42dbdcc6bf965997c088caff2a8be7f9bf44f701 •
CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2026-23021 – net: usb: pegasus: fix memory leak in update_eth_regs_async()
https://notcve.org/view.php?id=CVE-2026-23021
31 Jan 2026 — In the Linux kernel, the following vulnerability has been resolved: net: usb: pegasus: fix memory leak in update_eth_regs_async() When asynchronously writing to the device registers and if usb_submit_urb() fail, the code fail to release allocated to this point resources. In the Linux kernel, the following vulnerability has been resolved: net: usb: pegasus: fix memory leak in update_eth_regs_async() When asynchronously writing to the device registers and if usb_submit_urb() fail, the code fail to release all... • https://git.kernel.org/stable/c/323b34963d113efb566635f43858f40cce01d5f9 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2026-23020 – net: 3com: 3c59x: fix possible null dereference in vortex_probe1()
https://notcve.org/view.php?id=CVE-2026-23020
31 Jan 2026 — In the Linux kernel, the following vulnerability has been resolved: net: 3com: 3c59x: fix possible null dereference in vortex_probe1() pdev can be null and free_ring: can be called in 1297 with a null pdev. In the Linux kernel, the following vulnerability has been resolved: net: 3com: 3c59x: fix possible null dereference in vortex_probe1() pdev can be null and free_ring: can be called in 1297 with a null pdev. • https://git.kernel.org/stable/c/55c82617c3e82210b7471e9334e8fc5df6a9961f •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2026-23019 – net: marvell: prestera: fix NULL dereference on devlink_alloc() failure
https://notcve.org/view.php?id=CVE-2026-23019
31 Jan 2026 — In the Linux kernel, the following vulnerability has been resolved: net: marvell: prestera: fix NULL dereference on devlink_alloc() failure devlink_alloc() may return NULL on allocation failure, but prestera_devlink_alloc() unconditionally calls devlink_priv() on the returned pointer. This leads to a NULL pointer dereference if devlink allocation fails. Add a check for a NULL devlink pointer and return NULL early to avoid the crash. In the Linux kernel, the following vulnerability has been resolved: net: ma... • https://git.kernel.org/stable/c/34dd1710f5a3c9a7dc78e1ff6de69a19d407db25 •
CVSS: 7.2EPSS: 0%CPEs: 3EXPL: 0CVE-2025-71184 – btrfs: fix NULL dereference on root when tracing inode eviction
https://notcve.org/view.php?id=CVE-2025-71184
31 Jan 2026 — In the Linux kernel, the following vulnerability has been resolved: btrfs: fix NULL dereference on root when tracing inode eviction When evicting an inode the first thing we do is to setup tracing for it, which implies fetching the root's id. But in btrfs_evict_inode() the root might be NULL, as implied in the next check that we do in btrfs_evict_inode(). Hence, we either should set the ->root_objectid to 0 in case the root is NULL, or we move tracing setup after checking that the root is not NULL. Setting ... • https://git.kernel.org/stable/c/1abe9b8a138c9988ba8f7bfded6453649a31541f •
CVSS: 6.3EPSS: 0%CPEs: 9EXPL: 0CVE-2025-71183 – btrfs: always detect conflicting inodes when logging inode refs
https://notcve.org/view.php?id=CVE-2025-71183
31 Jan 2026 — In the Linux kernel, the following vulnerability has been resolved: btrfs: always detect conflicting inodes when logging inode refs After rename exchanging (either with the rename exchange operation or regular renames in multiple non-atomic steps) two inodes and at least one of them is a directory, we can end up with a log tree that contains only of the inodes and after a power failure that can result in an attempt to delete the other inode when it should not because it was not deleted before the power fail... • https://git.kernel.org/stable/c/56f23fdbb600e6087db7b009775b95ce07cc3195 •
CVSS: 7.1EPSS: 0%CPEs: 7EXPL: 0CVE-2025-71182 – can: j1939: make j1939_session_activate() fail if device is no longer registered
https://notcve.org/view.php?id=CVE-2025-71182
31 Jan 2026 — In the Linux kernel, the following vulnerability has been resolved: can: j1939: make j1939_session_activate() fail if device is no longer registered syzbot is still reporting unregister_netdevice: waiting for vcan0 to become free. Usage count = 2 even after commit 93a27b5891b8 ("can: j1939: add missing calls in NETDEV_UNREGISTER notification handler") was added. A debug printk() patch found that j1939_session_activate() can succeed even after j1939_cancel_active_session() from j1939_netdev_notify(NETDEV_UNR... • https://git.kernel.org/stable/c/9d71dd0c70099914fcd063135da3c580865e924c •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2025-71180 – counter: interrupt-cnt: Drop IRQF_NO_THREAD flag
https://notcve.org/view.php?id=CVE-2025-71180
31 Jan 2026 — In the Linux kernel, the following vulnerability has been resolved: counter: interrupt-cnt: Drop IRQF_NO_THREAD flag An IRQ handler can either be IRQF_NO_THREAD or acquire spinlock_t, as CONFIG_PROVE_RAW_LOCK_NESTING warns: ============================= [ BUG: Invalid wait context ] 6.18.0-rc1+git... #1 ----------------------------- some-user-space-process/1251 is trying to lock: (&counter->events_list_lock){....}-{3:3}, at: counter_push_event [counter] other info that might help us debug this: context-{2:2... • https://git.kernel.org/stable/c/a55ebd47f21f6f0472766fb52c973849e31d1466 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2026-23011 – ipv4: ip_gre: make ipgre_header() robust
https://notcve.org/view.php?id=CVE-2026-23011
25 Jan 2026 — In the Linux kernel, the following vulnerability has been resolved: ipv4: ip_gre: make ipgre_header() robust Analog to commit db5b4e39c4e6 ("ip6_gre: make ip6gre_header() robust") Over the years, syzbot found many ways to crash the kernel in ipgre_header() [1]. This involves team or bonding drivers ability to dynamically change their dev->needed_headroom and/or dev->hard_header_len In this particular crash mld_newpack() allocated an skb with a too small reserve/headroom, and by the time mld_sendpack() was c... • https://git.kernel.org/stable/c/c54419321455631079c7d6e60bc732dd0c5914c5 •
CVSS: 7.1EPSS: 0%CPEs: 2EXPL: 0CVE-2026-23004 – dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list()
https://notcve.org/view.php?id=CVE-2026-23004
25 Jan 2026 — In the Linux kernel, the following vulnerability has been resolved: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() syzbot was able to crash the kernel in rt6_uncached_list_flush_dev() in an interesting way [1] Crash happens in list_del_init()/INIT_LIST_HEAD() while writing list->prev, while the prior write on list->next went well. static inline void INIT_LIST_HEAD(struct list_head *list) { WRITE_ONCE(list->next, list); // This went well WRITE_ONCE(list->prev, list); // Crash, @list has... • https://git.kernel.org/stable/c/78df76a065ae3b5dbcb9a29912adc02f697de498 •