CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2026-23395 – Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ
https://notcve.org/view.php?id=CVE-2026-23395
25 Mar 2026 — In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ Currently the code attempts to accept requests regardless of the command identifier which may cause multiple requests to be marked as pending (FLAG_DEFER_SETUP) which can cause more than L2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer causing an overflow. The spec is quite clear that the same identifier shall not be used on subsequent requests: 'Within each signal... • https://git.kernel.org/stable/c/15f02b91056253e8cdc592888f431da0731337b8 •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2026-23394 – af_unix: Give up GC if MSG_PEEK intervened.
https://notcve.org/view.php?id=CVE-2026-23394
25 Mar 2026 — In the Linux kernel, the following vulnerability has been resolved: af_unix: Give up GC if MSG_PEEK intervened. Igor Ushakov reported that GC purged the receive queue of an alive socket due to a race with MSG_PEEK with a nice repro. This is the exact same issue previously fixed by commit cbcf01128d0a ("af_unix: fix garbage collect vs MSG_PEEK"). After GC was replaced with the current algorithm, the cited commit removed the locking dance in unix_peek_fds() and reintroduced the same issue. The problem is that... • https://git.kernel.org/stable/c/118f457da9ed58a79e24b73c2ef0aa1987241f0e •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2026-23393 – bridge: cfm: Fix race condition in peer_mep deletion
https://notcve.org/view.php?id=CVE-2026-23393
25 Mar 2026 — In the Linux kernel, the following vulnerability has been resolved: bridge: cfm: Fix race condition in peer_mep deletion When a peer MEP is being deleted, cancel_delayed_work_sync() is called on ccm_rx_dwork before freeing. However, br_cfm_frame_rx() runs in softirq context under rcu_read_lock (without RTNL) and can re-schedule ccm_rx_dwork via ccm_rx_timer_start() between cancel_delayed_work_sync() returning and kfree_rcu() being called. The following is a simple race scenario: cpu0 cpu1 mep_delete_impleme... • https://git.kernel.org/stable/c/dc32cbb3dbd7da38c700d6e0fc6354df24920525 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2026-23392 – netfilter: nf_tables: release flowtable after rcu grace period on error
https://notcve.org/view.php?id=CVE-2026-23392
25 Mar 2026 — In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: release flowtable after rcu grace period on error Call synchronize_rcu() after unregistering the hooks from error path, since a hook that already refers to this flowtable can be already registered, exposing this flowtable to packet path and nfnetlink_hook control plane. This error path is rare, it should only happen by reaching the maximum number hooks or by failing to set up to hardware offload, just call synchronize_... • https://git.kernel.org/stable/c/3b49e2e94e6ebb8b23d0955d9e898254455734f8 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2026-23391 – netfilter: xt_CT: drop pending enqueued packets on template removal
https://notcve.org/view.php?id=CVE-2026-23391
25 Mar 2026 — In the Linux kernel, the following vulnerability has been resolved: netfilter: xt_CT: drop pending enqueued packets on template removal Templates refer to objects that can go away while packets are sitting in nfqueue refer to: - helper, this can be an issue on module removal. - timeout policy, nfnetlink_cttimeout might remove it. The use of templates with zone and event cache filter are safe, since this just copies values. Flush these enqueued packets in case the template rule gets removed. • https://git.kernel.org/stable/c/24de58f465165298aaa8f286b2592f0163706cfe •
CVSS: -EPSS: 0%CPEs: 2EXPL: 0CVE-2026-23389 – ice: Fix memory leak in ice_set_ringparam()
https://notcve.org/view.php?id=CVE-2026-23389
25 Mar 2026 — In the Linux kernel, the following vulnerability has been resolved: ice: Fix memory leak in ice_set_ringparam() In ice_set_ringparam, tx_rings and xdp_rings are allocated before rx_rings. If the allocation of rx_rings fails, the code jumps to the done label leaking both tx_rings and xdp_rings. Furthermore, if the setup of an individual Rx ring fails during the loop, the code jumps to the free_tx label which releases tx_rings but leaks xdp_rings. Fix this by introducing a free_xdp label and updating the erro... • https://git.kernel.org/stable/c/fcea6f3da546b93050f3534aadea7bd96c1d7349 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2026-23388 – Squashfs: check metadata block offset is within range
https://notcve.org/view.php?id=CVE-2026-23388
25 Mar 2026 — In the Linux kernel, the following vulnerability has been resolved: Squashfs: check metadata block offset is within range Syzkaller reports a "general protection fault in squashfs_copy_data" This is ultimately caused by a corrupted index look-up table, which produces a negative metadata block offset. This is subsequently passed to squashfs_copy_data (via squashfs_read_metadata) where the negative offset causes an out of bounds access. The fix is to check that the offset is within range in squashfs_read_meta... • https://git.kernel.org/stable/c/f400e12656ab518be107febfe2315fb1eab5a342 •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2026-23383 – bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing
https://notcve.org/view.php?id=CVE-2026-23383
25 Mar 2026 — In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing struct bpf_plt contains a u64 target field. Currently, the BPF JIT allocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT buffer. Because the base address of the JIT buffer can be 4-byte aligned (e.g., ending in 0x4 or 0xc), the relative padding logic in build_plt() fails to ensure that target lands on an 8-byte boundary. This leads to two issues: 1. • https://git.kernel.org/stable/c/b2ad54e1533e91449cb2a371e034942bd7882b58 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2026-23382 – HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them
https://notcve.org/view.php?id=CVE-2026-23382
25 Mar 2026 — In the Linux kernel, the following vulnerability has been resolved: HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them In commit 2ff5baa9b527 ("HID: appleir: Fix potential NULL dereference at raw event handle"), we handle the fact that raw event callbacks can happen even for a HID device that has not been "claimed" causing a crash if a broken device were attempted to be connected to the system. Fix up the remaining in-tree HID drivers that forgot to add this same check to resolve the same... • https://git.kernel.org/stable/c/d0742abaa1c396a26bb3d3ce2732988cd3faa020 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2026-23381 – net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled
https://notcve.org/view.php?id=CVE-2026-23381
25 Mar 2026 — In the Linux kernel, the following vulnerability has been resolved: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled When booting with the 'ipv6.disable=1' parameter, the nd_tbl is never initialized because inet6_init() exits before ndisc_init() is called which initializes it. Then, if neigh_suppress is enabled and an ICMPv6 Neighbor Discovery packet reaches the bridge, br_do_suppress_nd() will dereference ipv6_stub->nd_tbl which is NULL, passing it to neigh_lookup(). This causes a kernel NULL... • https://git.kernel.org/stable/c/ed842faeb2bd49256f00485402f3113205f91d30 •