CVSS: -EPSS: %CPEs: 7EXPL: 0CVE-2026-23112 – nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec
https://notcve.org/view.php?id=CVE-2026-23112
13 Feb 2026 — In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining entries, and sg->length/offset before building the bvec. • https://git.kernel.org/stable/c/872d26a391da92ed8f0c0f5cb5fef428067b7f30 •
CVSS: -EPSS: %CPEs: 10EXPL: 0CVE-2026-23111 – netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()
https://notcve.org/view.php?id=CVE-2026-23111
13 Feb 2026 — In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() nft_map_catchall_activate() has an inverted element activity check compared to its non-catchall counterpart nft_mapelem_activate() and compared to what is logically required. nft_map_catchall_activate() is called from the abort path to re-activate catchall map elements that were deactivated during a failed transaction. It should skip elements that are already ac... • https://git.kernel.org/stable/c/25aa2ad37c2162be1c0bc4fe6397f7e4c13f00f8 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2026-23110 – scsi: core: Wake up the error handler when final completions race against each other
https://notcve.org/view.php?id=CVE-2026-23110
04 Feb 2026 — In the Linux kernel, the following vulnerability has been resolved: scsi: core: Wake up the error handler when final completions race against each other The fragile ordering between marking commands completed or failed so that the error handler only wakes when the last running command completes or times out has race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. First, there is an memory... • https://git.kernel.org/stable/c/6eb045e092efefafc6687409a6fa6d1dabf0fb69 •
CVSS: -EPSS: 0%CPEs: 2EXPL: 0CVE-2026-23109 – fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes()
https://notcve.org/view.php?id=CVE-2026-23109
04 Feb 2026 — In the Linux kernel, the following vulnerability has been resolved: fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes() Above the while() loop in wait_sb_inodes(), we document that we must wait for all pages under writeback for data integrity. Consequently, if a mapping, like fuse, traditionally does not have data integrity semantics, there is no need to wait at all; we can simply skip these inodes. This restores fuse back to prior behavior where syncs are no-ops. This fixes a user regressi... • https://git.kernel.org/stable/c/0c58a97f919c24fe4245015f4375a39ff05665b6 •
CVSS: -EPSS: 0%CPEs: 7EXPL: 0CVE-2026-23108 – can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak
https://notcve.org/view.php?id=CVE-2026-23108
04 Feb 2026 — In the Linux kernel, the following vulnerability has been resolved: can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak"). In usb_8dev_open() -> usb_8dev_start(), the URBs for USB-in transfers are allocated, added to the priv->rx_submitted anchor and submitted. In the complete callback usb_8dev_read_bulk_callback(), the URBs are processed and resubmitted. In usb_8dev_close() -> ... • https://git.kernel.org/stable/c/0024d8ad1639e32d717445c69ca813fd19c2a91c •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2026-23107 – arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA
https://notcve.org/view.php?id=CVE-2026-23107
04 Feb 2026 — In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA The code to restore a ZA context doesn't attempt to allocate the task's sve_state before setting TIF_SME. Consequently, restoring a ZA context can place a task into an invalid state where TIF_SME is set but the task's sve_state is NULL. In legitimate but uncommon cases where the ZA signal context was NOT created by the kernel in the context of the same task (e.g. if the task is s... • https://git.kernel.org/stable/c/39782210eb7e87634d96cacb6ece370bc59d74ba •
CVSS: -EPSS: 0%CPEs: 2EXPL: 0CVE-2026-23106 – timekeeping: Adjust the leap state for the correct auxiliary timekeeper
https://notcve.org/view.php?id=CVE-2026-23106
04 Feb 2026 — In the Linux kernel, the following vulnerability has been resolved: timekeeping: Adjust the leap state for the correct auxiliary timekeeper When __do_ajdtimex() was introduced to handle adjtimex for any timekeeper, this reference to tk_core was not updated. When called on an auxiliary timekeeper, the core timekeeper would be updated incorrectly. This gets caught by the lock debugging diagnostics because the timekeepers sequence lock gets written to without holding its associated spinlock: WARNING: include/l... • https://git.kernel.org/stable/c/775f71ebedd382da390dc16a4c28cffa5b937f79 •
CVSS: -EPSS: 0%CPEs: 7EXPL: 0CVE-2026-23105 – net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag
https://notcve.org/view.php?id=CVE-2026-23105
04 Feb 2026 — In the Linux kernel, the following vulnerability has been resolved: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag This is more of a preventive patch to make the code more consistent and to prevent possible exploits that employ child qlen manipulations on qfq. use cl_is_active instead of relying on the child qdisc's qlen to determine class activation. Several vulnerabilities have been discovered in the Linux kernel that may lead to a privilege escalation, denial of s... • https://git.kernel.org/stable/c/462dbc9101acd38e92eda93c0726857517a24bbd •
CVSS: -EPSS: 0%CPEs: 2EXPL: 0CVE-2026-23104 – ice: fix devlink reload call trace
https://notcve.org/view.php?id=CVE-2026-23104
04 Feb 2026 — In the Linux kernel, the following vulnerability has been resolved: ice: fix devlink reload call trace Commit 4da71a77fc3b ("ice: read internal temperature sensor") introduced internal temperature sensor reading via HWMON. ice_hwmon_init() was added to ice_init_feature() and ice_hwmon_exit() was added to ice_remove(). As a result if devlink reload is used to reinit the device and then the driver is removed, a call trace can occur. BUG: unable to handle page fault for address: ffffffffc0fd4b5d Call Trace: st... • https://git.kernel.org/stable/c/4da71a77fc3be1fcb680c8d78e1a1fb8017905ad •
CVSS: -EPSS: 0%CPEs: 7EXPL: 0CVE-2026-23103 – ipvlan: Make the addrs_lock be per port
https://notcve.org/view.php?id=CVE-2026-23103
04 Feb 2026 — In the Linux kernel, the following vulnerability has been resolved: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it's highly unlikely that ip... • https://git.kernel.org/stable/c/8230819494b3bf284ca7262ac5f877333147b937 •