CVE Vulnerability Catalog

A use-after-free vulnerability was found in the Linux kernel's CAN ISO-TP module (can/isotp). The issue occurs during concurrent network device unregistration (NETDEV_UNREGISTER) and socket release (isotp_release), potentially leading to use of freed memory.

In the Linux kernel, a vulnerability in the CAN ISO-TP subsystem was fixed regarding unsynchronized TX state machine transitions. Different contexts (sendmsg, RX path, timers) could act on stale state, corrupting unrelated transfers. The fix serializes the full TX claim lifecycle under so->rx_lock.

A use-after-free (UAF) vulnerability was found in the Linux kernel's CAN BCM (Broadcast Manager) module, specifically in the hrtimer. The issue stems from a missing RX_NO_AUTOTIMER flag check in the packet RX fast-path, allowing the timer to be re-armed after call_rcu() has scheduled memory deallocation. The fix defers timer cancellation and memory freeing to a dedicated workqueue and holds a socket reference until the deferred work completes.

In the Linux kernel, the CAN BCM module has a race condition between lockless reads of bo->ifindex and bo->bound and their locked modifications. This can cause a socket bound to a specific CAN interface to also match 'any' interface. Additionally, bcm_rx_setup() may silently return success when the device disappears concurrently instead of reporting -ENODEV.

A vulnerability in the Linux kernel's CAN BCM (Broadcast Manager) module was found, caused by missing synchronization when updating timer and filter values. Concurrent access from CAN traffic handling threads can lead to a race condition, resulting in incorrect behavior or potential privilege escalation.

In the Linux kernel, the CAN BCM module lacks proper RCU list operations. bcm_rx_setup() and bcm_tx_setup() do not use list_add_rcu(), which can lead to improper initialization of the bcm_op structure during traversal by bcm_proc_show(). Also, bcm_release() removes operations without list_del_rcu(), potentially causing synchronization issues.

In the Linux kernel, the CAN BCM module extends the use of bcm_tx_lock for data and timer updates. New frame data is first validated in a separate buffer and then copied under the lock, preventing observation of partially updated frames. Error handling for memcpy_from_msg() was added, and timer updates were moved under the lock, eliminating torn 64-bit reads on 32-bit platforms.

In the Linux kernel, the CAN BCM module has an issue with stale RX/TX ops after device removal. For RX, an RX_SETUP update could skip re-registering the filter when the device was removed, leaving the filter inactive. For TX, bcm_notify() did not handle tx_ops, leading to an endless timer re-arming and potential injection into a later reused ifindex.

In the Linux kernel, the CAN BCM module adds tracking of a single source interface for ANYDEV ops with timeout or throttle. Previously, when frames matched from different interfaces, races and data corruption could occur. Now the first interface that delivers a matching frame is remembered, and frames from other interfaces are rejected.

In the Linux kernel, the CAN BCM module lacks frame length validation in bcm_rx_setup() for RTR replies. bcm_tx_setup() validates frame length, but bcm_rx_setup() does not, which can lead to incorrect data.

In the Linux kernel, the CAN BCM module lacks proper device refcounting during CAN filter removal. Functions bcm_release(), bcm_delete_rx_op(), and bcm_notifier() relied on re-looking up the device by ifindex, which could fail during concurrent unregistration, leaving a stale filter. The patch adds holding a reference on op->rx_reg_dev from filter registration to unregistration.

A vulnerability in the Linux kernel's io_uring/bpf-ops mechanism allows re-registration of an already-bound BPF ops set. An attacker with CAP_BPF and CAP_PERFMON can trigger a use-after-free in io_uring context, potentially leading to privilege escalation or system crash.

In the Linux kernel, the BPF verifier fails to reset register bounds before narrowing the return value range of an LSM hook, leading to a verifier/runtime mismatch. An attacker could exploit this to bypass BPF memory safety checks.

In the Linux kernel, during fork(), the bpf_storage field in the task structure may not be initialized before certain error paths, leading to use of an uninitialized pointer. This can cause system hangs or use-after-free (UAF).

In the Linux kernel's sparx5 network driver, if workqueue allocation fails, the blocking notifier registration is not undone, leading to resource leak. This can cause system instability or crash.

In the Linux kernel, the dm thin metadata module has a vulnerability causing metadata inconsistency when a metadata snapshot reservation or release operation fails during commit. Direct modifications to the held_root field in the superblock are flushed to disk on transaction abort, corrupting metadata.

In the Linux kernel's dm-era module, there is an out-of-bounds memory access when the start sector is non-zero. The writeset block calculation does not apply the target offset, potentially leading to out-of-bounds read (detected by KASAN).

In the Linux kernel's dm-log module, there is a bitset_size overflow on 32-bit machines. Rounding region_count to a multiple of BITS_PER_LONG can cause wrap to zero, leading to incorrect memory allocation.

In the Linux kernel's dm module, there is a leak of the caller's thread keyring via the table device file. This causes the LUKS volume key to remain in memory after luksSuspend, potentially allowing its recovery.

In the Linux kernel, the dm_early_create function has a bug where it attempts to free an already used table when dm_resume fails. The table was already instantiated with dm_swap_table, and the code tries to destroy it again, which may lead to incorrect behavior. The fix skips the dm_table_destroy call in this case.