CVE Vulnerability Catalog

In the Linux kernel, netfilter nf_tables has a use-after-free vulnerability due to a global rhltable for nft objects. This allows access to objects being dismantled from other network namespaces, potentially leading to use-after-free.

In the Linux kernel, netfilter xt_hashlimit has a vulnerability due to uninitialized access to the burst field in the union of the dsthash_ent structure when XT_HASHLIMIT_RATE_MATCH mode is used by fewer than two rules referring to the same hashtable. Additionally, this mode is rejected for revisions less than 3.

In the Linux kernel, RDS/TCP has a use-after-free vulnerability in rds_tcp_laddr_check(). The function obtains a pointer to an IPv6 interface, drops the RCU lock, and then uses that pointer in ipv6_chk_addr(), which can lead to reading freed memory if the interface is deleted.

In the Linux kernel's nexthop module, there is a race condition during nexthop replacement. The functions fib6_check_nh_list() and __nexthop_replace_notify() walk the f6i_list without holding the nh->lock, while IPv6 RTM_NEWROUTE/RTM_DELROUTE operations mutate that list under the same lock. This leads to a use-after-free condition that could be exploited for code execution or system crash.

In the Linux kernel's nexthop module, there is a race condition in the nh_rt_cache_flush() function, which walks the f6i_list without holding the nh->lock. IPv6 route add/delete operations mutate that list under the lock and can free fib6_info entries, leading to a use-after-free. An attacker could exploit this to escalate privileges or cause a system crash.

In the Linux kernel's libiscsi (SCSI) library, there is a vulnerability involving stale-data leak into the sense buffer. The iscsi_scsi_cmd_rsp() function copies sense data from a SCSI response, but the bounds check does not account for the 2-byte sense length prefix. A target can return a response with datalen equal to senselen, causing a read up to two bytes past the data and copying them into the sense buffer, which is returned to userspace.

In the Linux kernel, the ath12k driver had an out-of-bounds error in ath12k_mac_dp_peer_cleanup(), where indexing the free_ml_peer_id_map bitmap used peer_id with the ATH12K_PEER_ML_ID_VALID bit (BIT(13)) set, leading to writes beyond the bitmap memory (256 bits). This caused memory corruption and exhaustion of ML peer IDs.

In the Linux kernel, the hwmon nzxt-smart2 driver had an output buffer not aligned to DMA boundaries, which on architectures with non-coherent caches (e.g., ARM, MIPS) led to memory corruption during DMA mapping. The fix aligns the buffer to ARCH_DMA_MINALIGN.

In the Linux kernel network stack, when peer entry allocation (inet_getpeer_v4/v6) fails, functions sending ICMP/NDISC Redirects sent packets without rate limiting, potentially leading to a packet storm. The fix prevents sending redirects when peer is NULL.

In the Linux kernel, the hwmon nct6775-core driver for the NCT6116 chip has weight register arrays with only 3 elements, but the driver iterates up to 5 PWM channels, leading to out-of-bounds reads (KASAN) and invalid hardware register access. The fix extends the arrays with zeroed fields to mark unsupported registers.

In the Linux kernel, the forcedeth driver has a use-after-free vulnerability in nv_remove(), where per-CPU txrx_stats are freed before unregistering the network device, potentially leading to access to freed memory. The fix moves the free after unregister_netdev().

In the Linux kernel, the cls_u32 classifier lacks validation of the offshift value, allowing shift-out-of-bounds during packet classification. An unprivileged user can trigger undefined behavior via user/network namespaces.

In the Linux kernel, Bluetooth ISO has a use-after-free vulnerability when detaching a connection from hcon. Failure to clear iso_data leads to later use after memory free.

In the Linux kernel, Bluetooth L2CAP has a use-after-free vulnerability in l2cap_le_connect_rsp. The channel is obtained without holding a reference, allowing a concurrent disconnect to free it, leading to use-after-free.

In the Linux kernel, Bluetooth ISO function iso_sock_getname does not hold the socket lock when accessing the conn field, leading to a race condition and potential use-after-free.

In the Linux kernel, Bluetooth ISO function iso_connect_ind does not hold the socket lock when accessing the conn field, leading to a race condition and potential use-after-free. Additionally, conn may be NULL if the socket has changed state.

In the Linux kernel, Bluetooth ISO function iso_conn_ready does not properly hold a reference to the socket when accessing conn->sk, leading to a use-after-free if the socket is concurrently closed.

In the Linux kernel, in the Bluetooth ISO subsystem, a potential deadlock was found in iso_sock_timeout(), which takes lock_sock and then synchronously disables the timer, potentially causing a deadlock. Additionally, iso_sock_timeout() may run concurrently with iso_conn_del(), leading to use-after-free (UAF) — one thread frees the hcon structure while another tries to access it.

In the Linux kernel, in the Bluetooth ISO subsystem, a reference counting bug was found in the iso_conn structure. A race between iso_conn_del() and iso_chan_del() can lead to a double-put of iso_conn, resulting in use-after-free (UAF). The issue stems from an extra put in iso_conn_del() for the case when iso_chan_add() fails.

In the Linux kernel, in the Bluetooth ISO subsystem, a race condition was found between kfree and kref_get_unless_zero on the hci_conn::iso_data field, which is accessed and modified without synchronization (lock or RCU). This can lead to use-after-free (UAF) and races between iso_conn_add() and iso_conn_free().