CVE Vulnerability Catalog

In the Linux kernel, a vulnerability was found in the BPF verifier regarding ld_{abs,ind} instructions in subprograms. The verifier did not simulate the failure path of packet data load, which could lead to incorrect analysis. Added simulation of both success and failure paths, similar to tail calls.

In the Linux kernel, in the BPF subsystem, a use-after-free (UAF) occurs when filling info for offloaded maps or programs. bpf_map_offload_info_fill_ns() and bpf_prog_offload_info_fill_ns() use get_net() on a netdev's netns that may already be destroyed.

In the Linux kernel, the bcmgenet driver has a bug leaking free buffer descriptors (free_bds) when reclaiming the TX queue. Dropped frames are not returned to the pool, potentially leading to resource exhaustion.

In the Linux kernel, the open-coded task_vma BPF iterator has a use-after-free (UAF) vulnerability. The iterator reads task->mm locklessly and does not call mmget(), allowing the mm_struct to be freed during concurrent process exit.

In the Linux kernel's BPF subsystem, a vulnerability was found due to inconsistent ID mapping for scalar registers with the BPF_ADD_CONST flag. The regsafe() function fails to verify that underlying base IDs are consistent with existing mappings, potentially leading to incorrect verifier state pruning.

In the Linux kernel, in BPF sock_ops programs, when the destination register is the same as the source, the SOCK_OPS_GET_SK() and SOCK_OPS_GET_FIELD() macros fail to zero the destination register in the !fullsock / !locked_tcp_sock path. This leads to stack out-of-bounds read and kernel pointer leak.

In the Linux kernel, the use of RDS/IB is now restricted to the initial network namespace. The RDS/IB code does not work correctly in other namespaces, which could lead to errors or unexpected behavior.

In the Linux kernel, an out-of-bounds read occurs in pcpu_init_value when copying data from a CGROUP_STORAGE map to a pcpu map with the same value size not rounded up to 8 bytes. The issue arises when the source has less than 8 bytes and the copy is rounded up.

In the Linux kernel, the ppp driver lacks a requirement for CAP_NET_ADMIN in the target network namespace for unattached ioctls. A local unprivileged user can create a new user namespace, gain CAP_NET_ADMIN only in that namespace, and then issue PPPIOCNEWUNIT, PPPIOCATTACH, or PPPIOCATTCHAN against an inherited network namespace.

In the Linux kernel, a vulnerability was found in the Bluetooth stack where hci_conn_request_evt() calls hci_connect_cfm() without holding the hdev->lock when the protocol sets HCI_PROTO_DEFER. This can lead to a use-after-free (UAF) if the connection is deleted concurrently.

In the Linux kernel, missing channel lock in l2cap_ecred_reconf_rsp allows a remote BLE device to send a crafted L2CAP ECRED reconfiguration response, potentially corrupting the channel list while another thread iterates it.

A vulnerability in the Linux kernel's SCTP over UDP implementation fails to disable BH before calling tunnel xmit functions, causing unbalanced recursion counters and potential packet drops.

A null-pointer dereference vulnerability was found in the Linux kernel's xdp_master_redirect() function when redirecting XDP traffic to a master interface that has not been brought up. The issue occurs when a bond interface in round-robin mode is never opened (bond_open()), leaving the per-CPU rr_tx_counter uninitialized, leading to a kernel panic.

In the Linux kernel, the DRM komeda driver had an integer overflow vulnerability in AFBC framebuffer size validation. The minimum required buffer size calculation added AFBC payload size to the framebuffer offset without overflow checking, potentially allowing an undersized GEM object and out-of-bounds memory access.

In the Linux kernel PCI endpoint subsystem, a vulnerability was found in pci_epf_alloc_doorbell(). After a failed MSI vector allocation, the doorbell message array is freed but EPF structure pointers still point to freed memory, potentially causing a double-free. Additionally, missing checks for already allocated doorbells allow memory leaks or overwriting existing allocations.

In the Linux kernel, the SMQ cache policy for dm-cache devices lacks locks when invalidating cache blocks in passthrough mode. Concurrent invalidation operations from multiple workers can cause data races on the allocated blocks counter and use-after-free issues in internal data structures.

In the Linux kernel, a vulnerability in the dm log module causes an out-of-bounds write due to a 32-bit integer overflow in region_count. The variable cannot hold the 64-bit result of sector division, leading to undersized buffer allocation and subsequent heap memory corruption.

A missing TLB and context cache invalidation after updating DDT/PDT entries was found in the Linux kernel's RISC-V IOMMU driver. The RISC-V IOMMU specification (Sections 6.3.1 and 6.3.2) mandates these invalidations to ensure address translation consistency.

In the Linux kernel, a locking bug was found in the drm/msm driver's VM_BIND UNMAP operation. An incorrect argument caused objects involved in UNMAP operations not to be always locked. The issue affected non-_NO_SHARE buffer objects.

In the Linux kernel, a vulnerability was found in the AMD IOMMU subsystem's clone_alias() function. It incorrectly assumed the first argument (pdev) always points to the original device, while it could be an alias. This caused the wrong devid to be used when copying DTE entries, leading to incorrect or stale entries being propagated to the alias device.