CVE-2026-72123

A flaw was found in the Linux kernel's Controller Area Network CAN Broadcom BCM driver. A race condition during the BCM RX operation teardown can lead to a Use-After-Free UAF vulnerability. This occurs when a timer attempts to access memory that has already been deallocated, potentially causing a...

CVE-2026-72122

A flaw was found in the CAN BCM Controller Area Network Broadcast Manager module of the Linux kernel. A race condition exists where a socket intended for a specific CAN interface can silently be reconfigured to receive messages from any interface. This occurs due to inconsistent reads of socket...

CVE-2026-72120

A flaw was found in the Linux kernel's can: bcm module. Missing Read-Copy-Update RCU list annotations and operations can lead to improperly initialized or removed bcmop structures. This improper handling may cause system instability or a denial of service when these structures are accessed...

CVE-2026-72118

A flaw was found in the Linux kernel's Controller Area Network CAN Broadcast Manager BCM module. A data race condition, occurring when multiple central processing units CPUs simultaneously process CAN frames, can lead to incorrect statistics being reported. This could result in a bogus or negativ...

CVE-2026-72115

A flaw was found in the Linux kernel's Controller Area Network CAN Broadcast Manager BCM module. A race condition can occur when an ANYDEV receive operation, which listens on all interfaces, has an active timeout or throttle timer and receives matching frames from multiple network interfaces...

CVE-2026-72113

A flaw was found in the Linux kernel's Controller Area Network CAN Broadcast Manager BCM module. This vulnerability arises from a missing device reference count during the removal of CAN filters. If a network device is unregistered concurrently while the BCM module attempts to remove a filter, th...

UBUNTU-CVE-2026-72117

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix data race on rxstamp/rxifindex in bcmrxhandler For an rx op subscribed on all interfaces ifindex == 0, the same op is registered once in the shared per-netns wildcard filter list, so bcmrxhandler can run concurrentl...

UBUNTU-CVE-2026-72119

In the Linux kernel, the following vulnerability has been resolved: can: bcm: extend bcmtxlock usage for data and timer updates Stage new CAN frame content for an existing tx op into a kmalloc'd buffer and validate it there, mirroring the approach already used in bcmrxsetup. Only copy the validat...

UBUNTU-CVE-2026-72123

In the Linux kernel, the following vulnerability has been resolved: can: bcm: defer rxop deallocation to workqueue to fix thrtimer UAF Commit f1b4e32aca08 "can: bcm: use callrcu instead of costly synchronizercu" replaced synchronizercu in bcmdeleterxop with callrcu and introduced the RXNOAUTOTIME...

CVE-2026-72120

In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu list annotations and operations sashiko-bot remarked the missing use of listaddrcu in bcmrx|txsetup to have a proper initialized bcmop structure when bcmprocshow traverses the bcmop's under rcureadlock. ...

CVE-2026-72116

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix stale rx/tx ops after device removal RX: an RXSETUP update! for an existing op skipped canrxregister unconditionally, even when a concurrent NETDEVUNREGISTER had already torn down its registration op-rxregdev == NUL...

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...

EUVD-2026-58880

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix lockless bound/ifindex race and silent RXSETUP failure bcmsendmsg reads bo-ifindex and checks bo-bound before taking locksock, while bcmnotify, bcmconnect and bcmrelease all mutate both fields under that same lock...

EUVD-2026-58878

In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu list annotations and operations sashiko-bot remarked the missing use of listaddrcu in bcmrx|txsetup to have a proper initialized bcmop structure when bcmprocshow traverses the bcmop's under rcureadlock. ...

CVE-2026-72120 can: bcm: add missing rcu list annotations and operations

In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu list annotations and operations sashiko-bot remarked the missing use of listaddrcu in bcmrx|txsetup to have a proper initialized bcmop structure when bcmprocshow traverses the bcmop's under rcureadlock. ...

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...

EUVD-2026-59076

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix CAN frame rx/tx statistics KCSAN detected a data race within the bcmrxhandler when two CAN frames have been simultaneously received and processed in a single rx op by two different CPUs. Use atomic operations with...

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...