CVE-2026-53177 is a vulnerability in the Linux kernel's bnxt_en driver where a NULL pointer dereference can occur during PCIe error recovery on a closed NIC. This happens because the driver attempts to disable and synchronize IRQs using a pointer that may be NULL if the NIC is closed. The issue is fixed by adding a check for the NULL pointer before performing these operations.
CVE-2026-11475 is a medium severity SQL injection vulnerability in the Kushan2k student-management-system. It affects the getStatus function in controllers/GradeController.php within the Certificate Verification Endpoint. The vulnerability allows remote attackers to manipulate the 'nic' argument to perform SQL injection. The product uses a rolling release model, so no specific affected or fixed versions are identified. The issue was reported early, but no vendor response or patch is currently available.
CZ.NIC BIRD Internet Routing Daemon through 2.19.0 contains a stack-based buffer overflow in the BGP AS_PATH mask matching implementation in nest/a-path.c. The as_path_match() function uses a fixed-size stack array of 2048 + 1 pm_pos entries, while parse_path() expands AS_PATH segments from a received BGP UPDATE without enforcing a corresponding capacity limit. When RFC 8654 BGP Extended Messages are enabled and a BIRD filter evaluates an AS path mask expression such as "bgp_path ~ [= ... =]", an established BGP peer can send a long AS_PATH containing more than 2048 expanded ASNs. This causes parse_path()/as_path_match() to write beyond the fixed stack buffer, resulting in a crash of the daemon. NOTE: reportedly, the Supplier's position is that a fix is not being prioritized because all network operators should already be rejecting routes with unusually long attributes.
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present The DATA-packet handler in rxrpc_input_call_event() and the RESPONSE handler in rxrpc_verify_response() copy the skb to a linear one before calling into the security ops only when skb_cloned() is true. An skb that is not cloned but still carries externally-owned paged fragments (e.g. SKBFL_SHARED_FRAG set by splice() into a UDP socket via __ip_append_data, or a chained skb_has_frag_list()) falls through to the in-place decryption path, which binds the frag pages directly into the AEAD/skcipher SGL via skb_to_sgvec(). Extend the gate to also unshare when skb_has_frag_list() or skb_has_shared_frag() is true. This catches the splice-loopback vector and other externally-shared frag sources while preserving the zero-copy fast path for skbs whose frags are kernel-private (e.g. NIC page_pool RX, GRO). The OOM/trace handling already in place is reused.
CVE-2026-43385 is a Linux kernel vulnerability related to a stall in the rcu_tasks grace period when using threaded busypoll in network drivers. The issue causes the kernel's RCU (Read-Copy-Update) subsystem to detect stalls due to improper handling of the last quiescent state timestamp in the polling loop. This can lead to hangs in tools like bpftrace that rely on network interface card (NIC) drivers with threaded busypoll enabled.
In the Linux kernel, the following vulnerability has been resolved: net: airoha: Fix memory leak in airoha_qdma_rx_process() If an error occurs on the subsequents buffers belonging to the non-linear part of the skb (e.g. due to an error in the payload length reported by the NIC or if we consumed all the available fragments for the skb), the page_pool fragment will not be linked to the skb so it will not return to the pool in the airoha_qdma_rx_process() error path. Fix the memory leak partially reverting commit 'd6d2b0e1538d ("net: airoha: Fix page recycling in airoha_qdma_rx_process()")' and always running page_pool_put_full_page routine in the airoha_qdma_rx_process() error path.
CVE-2026-39402 is an authorization logic flaw in the lxc container runtime's setuid helper lxc-user-nic. The vulnerability allows an unprivileged user to delete OpenVSwitch-attached network interfaces owned by other users in multi-tenant environments. This occurs because the interface name comparison in the delete path can incorrectly authorize deletion based on name match alone, bypassing ownership checks. The flaw enables denial of service by disconnecting networking from containers of other tenants sharing the same infrastructure. The issue is fixed in lxc version 7.0.0.
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler The ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER handler in bnxt_async_event_process() uses a firmware-supplied 'type' field directly as an index into bp->bs_trace[] without bounds validation. The 'type' field is a 16-bit value extracted from DMA-mapped completion ring memory that the NIC writes directly to host RAM. A malicious or compromised NIC can supply any value from 0 to 65535, causing an out-of-bounds access into kernel heap memory. The bnxt_bs_trace_check_wrap() call then dereferences bs_trace->magic_byte and writes to bs_trace->last_offset and bs_trace->wrapped, leading to kernel memory corruption or a crash. Fix by adding a bounds check and defining BNXT_TRACE_MAX as DBG_LOG_BUFFER_FLUSH_REQ_TYPE_ERR_QPC_TRACE + 1 to cover all currently defined firmware trace types (0x0 through 0xc).
A vulnerability in the Linux kernel's gve driver causes stats report corruption when the queue count changes. The NIC and driver share a stats memory region, and resizing this region incorrectly allows the NIC to write beyond allocated memory or causes gaps in stats reporting. This issue has been fixed by allocating the stats region at maximum size and adjusting the NIC offset calculation accordingly.
In the Linux kernel, the following vulnerability has been resolved: igc: fix PTM cycle trigger logic Writing to clear the PTM status 'valid' bit while the PTM cycle is triggered results in unreliable PTM operation. To fix this, clear the PTM 'trigger' and status after each PTM transaction. The issue can be reproduced with the following: $ sudo phc2sys -R 1000 -O 0 -i tsn0 -m Note: 1000 Hz (-R 1000) is unrealistically large, but provides a way to quickly reproduce the issue. PHC2SYS exits with: "ioctl PTP_OFFSET_PRECISE: Connection timed out" when the PTM transaction fails This patch also fixes a hang in igc_probe() when loading the igc driver in the kdump kernel on systems supporting PTM. The igc driver running in the base kernel enables PTM trigger in igc_probe(). Therefore the driver is always in PTM trigger mode, except in brief periods when manually triggering a PTM cycle. When a crash occurs, the NIC is reset while PTM trigger is enabled. Due to a hardware problem, the NIC is subsequently in a bad busmaster state and doesn't handle register reads/writes. When running igc_probe() in the kdump kernel, the first register access to a NIC register hangs driver probing and ultimately breaks kdump. With this patch, igc has PTM trigger disabled most of the time, and the trigger is only enabled for very brief (10 - 100 us) periods when manually triggering a PTM cycle. Chances that a crash occurs during a PTM trigger are not 0, but extremely reduced.
CVE-2024-42148 is a high-severity vulnerability in the Linux kernel's bnx2x network driver. It involves multiple array-index-out-of-bounds errors detected by UBSAN, caused by an undersized array for handling Ethernet queues on certain Broadcom NICs. The issue arises when the number of Ethernet queues exceeds the array size defined for older hardware models, leading to out-of-bounds memory access. This flaw affects systems with 32 or more physical CPU cores or configurations with a high number of Ethernet queues. The vulnerability has been fixed by increasing the array size to accommodate newer NIC models with more queues.
CVE-2024-39507 is a vulnerability in the Linux kernel's hns3 network driver that could cause a kernel crash during concurrent operations. The issue arises when the link status changes and the NIC driver notifies the RoCE driver, which may have already been uninitialized, leading to a crash. The fix involves checking the RoCE driver's registration status before notification and ensuring link updates complete before uninitialization.
CVE-2024-35901 is a vulnerability in the Linux kernel's Microsoft Azure Network Adapter (MANA) driver related to incorrect handling of Rx DMA datasize alignment. The flaw caused oversized packets slightly larger than the MTU to trigger a kernel panic (skb_over_panic), resulting in a denial of service. The issue was fixed by removing unnecessary alignment code so that oversized packets are properly marked as truncated and dropped by the NIC.
CVE-2024-26640 is a vulnerability in the Linux kernel's TCP zero-copy receive path. It arises because the kernel incorrectly allows mapping of pages owned by a filesystem, rather than only pages allocated from NIC drivers, leading to a kernel panic. The issue was fixed by adding sanity checks to ensure pages are not compound and have no mapping, preventing improper page mappings that cause crashes.