CVE Vulnerability Catalog

A vulnerability in the Linux kernel has been resolved related to the lack of SRCU protection when reading PDPTR registers in the __get_sregs2() function. Reading these registers may lead to unauthorized access to guest memory.

A vulnerability related to a memory leak in the error path in the radio-keene module has been fixed in the Linux kernel. The issue occurred in the usb_keene_probe() function, where a failure in device registration could lead to a memory leak.

A vulnerability in the Linux kernel has been fixed that could lead to a divide-by-zero error in the tcf_skbedit_hash() function. This issue was addressed by adding support for SKBEDIT_F_TXQ_SKBHASH.

A vulnerability has been identified and resolved in the Linux kernel. It concerns the deletion of empty attribute leaf freemap entries.

A vulnerability has been identified in the Linux kernel related to calculating the maximum value M for scaler configuration. The issue was the lack of a check to ensure that the MIN_X_OUTPUT_SIZE register value is non-zero, which could lead to division by zero.

A vulnerability in the Linux kernel has been fixed related to an error in the kcm_write_msgs() function when processing a message with a zero-fragment skb in the frag_list.

A vulnerability in the Linux kernel related to 'not page aligned sg buffer' errors in the ChipIdea UDC driver has been resolved. This issue occurs when a USB device is reconnected after being disconnected during an active transfer.

A vulnerability related to the TSV110 processor has been resolved in the Linux kernel, which is susceptible to the Spectre-BHB attack. This attack can be exploited to leak information through branch prediction side channels.

A vulnerability has been identified in the Linux kernel in the ceph_zero_partial_object function, which was missing proper snapshot context for OSD write operations. This could lead to data inconsistencies in snapshots.

A vulnerability in the Linux kernel related to the dma_free_coherent() function has been fixed, which was using an incorrect DMA handle in the error path. This could lead to improper unmapping of the buffer.

A vulnerability has been identified in the Linux kernel related to use-after-free in tasklets during device removal. The issue occurs when the PCA-200E or SBA-200E adapter is being detached, potentially leading to unexpected system behavior.

A vulnerability in the Linux kernel related to parameter validation for packet data in communication with nci NFC chips has been resolved. The introduced fix has caused issues with communication with these chips.

A vulnerability has been identified in the Linux kernel related to improper memory deallocation in the uhdlc_memclean() function. The rx_buffer and tx_buffer are allocated as contiguous but freed as two separate buffers, which may lead to memory management issues.

A vulnerability in the Linux kernel related to V3D rendering has been resolved, which occasionally caused segment size mismatch warnings when CONFIG_DMA_API_DEBUG was enabled.

telnetd in GNU inetutils through 2.7 allows an out-of-bounds write in the LINEMODE SLC (Set Local Characters) suboption handler because add_slc does not check whether the buffer is full.

In udev in systemd before version 260, local root execution can occur via malicious hardware devices and unsanitized kernel output.

In OpenPrinting CUPS, versions 2.4.16 and prior, a use-after-free vulnerability exists in the CUPS scheduler (cupsd) when temporary printers are automatically deleted.

A vulnerability in telnet in GNU inetutils through version 2.7 allows servers to read arbitrary environment variables from clients via the NEW_ENVIRON SEND USERVAR command.

In systemd versions 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file in nspawn.

The faraday-http-cache library stores cached responses in JSON format by default and reads them back using JSON.load, which honors the json_class key and calls json_create on the named class. Response headers are stored verbatim in the cache entry, so a malicious origin server can return a response with a json_class key leading to unsafe deserialization.