A flaw was found in the Linux kernel's BPF (Berkeley Packet Filter) devmap feature. When handling devmap broadcast redirects, fragmented network frames are not properly managed during the cloning process. This can lead to an out-of-bounds access, where the system attempts to read or write data beyond the allocated memory, potentially causing system instability or denial of service.

A flaw was found in the Linux kernel's BPF (Berkeley Packet Filter) component. This vulnerability, located in the `btf_repeat_fields()` function, is caused by an integer overflow when processing user-supplied BPF Type Format (BTF) data. A local attacker could exploit this flaw by providing a specially crafted BTF, leading to a heap out-of-bounds write. This could result in privilege escalation, allowing the attacker to gain elevated access to the system.

A flaw was found in the Linux kernel's BPF (Berkeley Packet Filter) subsystem. When certain security modules interact with network routing tables, it can trigger diagnostic warnings. This issue primarily affects debug kernels by generating console messages and does not lead to direct security exploits like data corruption or unauthorized access.

A flaw was found in the Linux kernel's USB Kalmia driver. An attacker with a specially crafted USB device could exploit an out-of-bounds read vulnerability in the `kalmia_rx_fixup()` function. This occurs due to an incorrect calculation of the USB packet length when processing short bulk-IN frames, leading to a memory underflow. This flaw could allow an attacker to read sensitive information from outside the intended memory buffer or potentially cause a denial of service.

A flaw was found in the Linux kernel's USB cdnsp driver. The `cdnsp_alloc_stream_info()` function allocates a stream context array but fails to free it if subsequent allocations or updates fail. This memory leak could lead to a denial of service due to resource exhaustion.

A flaw was found in the Linux kernel's USB dwc3 driver. Incorrect type handling in the `dwc3_readl()` and `dwc3_writel()` functions within `dwc3_ulpi_setup()` can lead to memory corruption. This vulnerability may allow an attacker to cause system instability or potentially execute arbitrary code, depending on the specific memory corruption scenario.

A flaw was found in the Linux kernel's Universal Serial Bus (USB) subsystem. When an isochronous USB request block (URB) submission fails, the associated schedule is not properly freed. This memory leak can accumulate over time, potentially leading to memory exhaustion and a denial of service (DoS) for the system.

A flaw was found in the USB gadget composite driver in the Linux kernel. An issue with an empty check in the USB_DT_OTG handler can lead to reading from an invalid memory location. This can result in a kernel AddressSanitizer (KASAN) fault, potentially causing information disclosure or a denial of service.

A flaw was found in the Linux kernel's USB gadget driver. A race condition exists where the `udc` (USB Device Controller) memory, which manages USB gadgets, can be freed while still being accessed. This use-after-free vulnerability can be triggered by a local attacker, potentially through operations like mode-switching or configuration file system (configfs) interactions. Successful exploitation leads to a NULL pointer dereference, causing a system crash and resulting in a Denial of Service (DoS).

A flaw was found in the Linux kernel's USB printer gadget driver. The `printer_open()` function incorrectly increments a reference counter even when the device is already in use and the open operation fails. This prevents the reference from being properly released, leading to a permanent leak of system resources. Over time, repeated failed attempts to open the printer device can exhaust available resources, potentially causing a denial of service (DoS) for affected systems.

A flaw was found in the Linux kernel's USB idmouse driver. A local attacker could exploit a use-after-free vulnerability due to a race condition that occurs when a USB idmouse device is disconnected. This race condition allows `mutex_unlock()` to access freed memory, which can lead to a system crash and result in a denial of service.

A flaw was found in the Linux kernel. A race condition exists in the `ldusb` USB driver where a `mutex_unlock()` operation can attempt to access a mutex structure after it has been freed. This occurs when the `release()` and `disconnect()` functions race, leading to a use-after-free vulnerability. A local attacker could potentially exploit this to cause a system crash, leading to a denial of service.

A flaw was found in the Linux kernel's USB iowarrior driver. This vulnerability, a use-after-free, occurs because write operations are not properly halted when a device disconnects. An attacker could potentially exploit this to cause system instability or execute arbitrary code.

A flaw was found in the Linux kernel's USB iowarrior driver. This vulnerability involves a use-after-free error, which occurs when the system attempts to use memory that has already been deallocated. This specific issue arises from a race condition during device disconnection, where the mutex_unlock() function may access a freed mutex structure. A local attacker could potentially exploit this to cause a system crash (denial of service) or execute arbitrary code.

A flaw was found in the Linux kernel's `legousbtower` USB driver. This vulnerability is a use-after-free, which means the system attempts to use memory after it has been released. It occurs due to a timing issue (race condition) when a USB device is disconnected, potentially leading to system instability or crashes.

A flaw was found in the Linux kernel's `uss720` driver. When the `uss720_probe()` function attempts to initialize a USB parallel port (parport) device, it registers the parport but may fail to unregister it if a subsequent hardware register read operation fails. This improper resource management leaves a registered parport device with a pointer to memory that has already been released, potentially leading to system instability or a denial of service (DoS) condition.

A flaw was found in the Linux kernel's USB `mtu3` gadget driver. When the `mtu3_gadget_queue()` function encounters a failure during the preparation of a USB transfer, the associated Direct Memory Access (DMA) mapping is not properly released. This leaves the DMA mapping active, which can lead to a resource leak. Repeated exploitation of this flaw could allow a local attacker to cause a denial of service by exhausting system resources.

A flaw was found in the Linux kernel's keyspan_pda USB serial driver. An issue with the write() callback function allows it to report more data written than was actually provided. This can lead to the system writing data beyond its allocated buffer, resulting in an information leak. A local attacker could exploit this to potentially gain access to sensitive information.

A flaw was found in the Linux kernel's USB serial digi_acceleport driver. This vulnerability occurs when a port is closed while it is in a throttled state, preventing the read Urban Request Block (URB) from being resubmitted. As a result, the affected port will cease to receive any further data, leading to a denial of service (DoS) for data reception until the device is reconnected or the driver is rebound.

A flaw was found in the Linux kernel's `digi_acceleport` USB serial driver. This vulnerability occurs when a USB device using the driver is disconnected, and operations such as opening or closing the device are happening concurrently. Persistent errors in sending out-of-band (OOB) write Universal Serial Bus Request Blocks (URBs) can cause the driver to enter an indefinite loop with interrupts disabled. This leads to a system hard lockup, resulting in a Denial of Service (DoS).