CVE-2026-72127

The concrete details show a Linux kernel vulnerability in netdev-genl: netdev_nl_napi_fill_one() reported NAPI kthread PID via task_pid_nr() in the initial pid namespace, and NETDEV_CMD_NAPI_GET allowed in netnsok without GENL_ADMIN_PERM, enabling a caller in a child pid namespace to see the kthr...

CVE-2026-72126

The CVE concerns a Linux kernel race in the isotp path of CAN networking. The fix makes isotp_release() always call synchronize_rcu() before cancelling RX timers, regardless of so->bound, addressing a scenario where NETDEV_UNREGISTER could allow a use-after-free of a timer callback if an in-fl...

CVE-2026-72124

Summary: CVE-2026-72124 affects the Linux kernel CAN isotp TX state machine. The bug arose from mixing a lock-free cmpxchg() claim in sendmsg() with hrtimer_cancel() under so->rx_lock, creating windows where a frame or timer callback could operate on a migrated TX state and corrupt an unrelate...

CVE-2026-72125

In CVE-2026-72125, the Linux kernel’s CAN isotp implementation had a use-after-free race with NETDEV_UNREGISTER. During unregister, the bound net_device could be unlisted from the ifindex hash before the NETDEV_UNREGISTER notifier runs, allowing isotp_release() to free a socket while isotp_notify...

CVE-2026-72123

CVE-2026-72123 concerns Linux kernel CAN BCM RX teardown where a race between a concurrent RCU reader and a deferred thrtimer could dereference a freed op, causing a use-after-free. Root cause: after replacing synchronize_rcu() with call_rcu() and introducing RX_NO_AUTOTIMER, the thrtimer path in...

CVE-2026-72122

CVE-2026-72122 (Linux kernel) fixes a race in the CAN BCM path. The issue arises when bcm_sendmsg() reads bo->ifindex and bo->bound without holding the socket lock, while bcm_notify(), bcm_connect() and bcm_release() update both fields under the same lock. The unsynchronized reads and write...

CVE-2026-72120

CVE-2026-72120 affects the Linux kernel bcm subsystem. The issue stems from missing RCU list annotations/operations for bcm_op handling, leading to improper initialization when traversing bcm_op under rcu_read_lock(). Fixes include moving list_add_rcu() calls to the end of bcm_[rx|tx]_setup and U...

CVE-2026-72121

CVE-2026-72121 describes a Linux kernel CAN subsystem vulnerability in which KCSAN detected a race condition updating timer and filter state during CAN message handling. The fix introduces a per-operation bcm_rx_update_lock to serialize updates to timer values (ival1/ival2/kt_ival1/kt_ival2/kt_la...

CVE-2026-72119

Summary: CVE-2026-72119 concerns a Linux kernel CAN subsystem issue in bcm_tx_lock usage during data and timer updates. The fix stages new CAN frame content for an existing tx operation into a kmalloc() buffer, validates it there, and only copies validated data into op->frames while holding op...

CVE-2026-72118

CVE-2026-72118 concerns a data race in the Linux kernel CAN subsystem (bcm) where two CPUs simultaneously receive CAN frames, triggering KCSAN complaints in bcm_rx_handler(). The fix uses atomic operations on statistics counters (signed long) in hot paths and refactors updates to bcm_update_rx_st...

CVE-2026-72117

CVE-2026-72117 concerns the Linux kernel “can: bcm” code, where a data race on rx_stamp/rx_ifindex in bcm_rx_handler() could occur for an rx op subscribed to all interfaces (ifindex == 0). The same op could be registered in a shared per-netns wildcard filter list, allowing concurrent bcm_rx_handl...

CVE-2026-72116

The CVE-2026-72116 entry describes a Linux kernel issue in the CAN networking path (bcm) where stale RX/TX operation references could occur after device removal. RX: an RX_SETUP update could skip can_rx_register() if NETDEV_UNREGISTER occurred, leaving rx_ops with ifindex=0 and not re-enabling fr...

CVE-2026-72115

The CVE-2026-72115 issue affects the Linux kernel CAN BCM RX path. A race between bcm_rx_handler(), hrtimer_cancel(), bcm_rx_starttimer(), and bcm_rx_timeout_handler() could allow an ANYDEV operation (ifindex == 0) to process frames from multiple interfaces, causing spurious RX_TIMEOUT events and...

CVE-2026-72113

Technical details are not publicly available in the provided documents. Monitor for updates from vendors and security advisories.

CVE-2026-72114

In the Linux kernel CAN BCM subsystem, CVE-2026-72114 is due to bcm_rx_setup() not validating the frame length for RTR-reply frames configured via RX_SETUP with RX_RTR_FRAME, unlike bcm_tx_setup() which validates cf->len against CAN/CAN FD DLC limits. The vulnerability is resolved by adding va...

CVE-2026-72112

CVE-2026-72112 concerns the Linux kernel io_uring/bpf-ops path where a second registration of BPF ops could be bound to the same ring due to not advancing past BPF_STRUCT_OPS_STATE_READY, allowing bpf_io_reg() to re-resolve the target ring and potentially bind the same io_uring_bpf_ops map to dif...

CVE-2026-72111

CVE-2026-72111 affects the Linux kernel BPF verifier. The issue occurs when processing a context load of an LSM hook return value: __mark_reg_s32_range() narrows the destination register by intersecting with stale bounds instead of replacing them, potentially creating a verifier/runtime mismatch ...

CVE-2026-72110

The CVE-2026-72110 entry documents a Linux kernel issue in which a nascent task may bail out of copy_process() to free_task() before p->bpf_storage is initialized, causing the nascent task’s bpf_storage pointer to be a stale copy from the parent. This can lead to kernel hangs or use-after-free...

CVE-2026-72109

The CVE-2026-72109 issue affects the Linux kernel net: sparx5, where sparx5_register_notifier_blocks() registers the switchdev blocking notifier before allocating the ordered workqueue. If the workqueue allocation fails, the error path unregisters the switchdev and netdevice notifiers but leaves ...

CVE-2026-72108

CVE-2026-72108 : The Linux kernel fix addresses a metadata inconsistency in dm thin metadata when a metadata snapshot commit fails. The root cause was that __reserve_metadata_snap() and __release_metadata_snap() modified the superblock’s held_root directly in the block_manager buffer, which could...