A flaw was found in the Linux kernel's ALSA sound driver for the cs35l41 component. This vulnerability occurs because the driver fails to properly remove controls and cancel firmware load work during component unbinding or device removal, especially when firmware autostart is disabled. This can lead to a worker attempting to access driver data that is no longer valid after teardown, resulting in memory corruption. An attacker with local access could potentially exploit this to cause a denial of service or escalate privileges.

A flaw was found in the Linux kernel's Advanced Linux Sound Architecture (ALSA) ice1712 driver. This vulnerability occurs because the `snd_ctl_new1()` function, which allocates memory, can return a null value upon failure, but the driver does not properly check for this. An attacker could potentially trigger a memory allocation failure, leading to a null pointer dereference and causing the system to crash, resulting in a Denial of Service (DoS).

A flaw was found in the Linux kernel's Advanced Linux Sound Architecture (ALSA) sequencer. This vulnerability allows an unprivileged local user to trigger a heap information leak in the `snd_seq_event_dup()` function. By reading from `/dev/snd/seq`, an attacker can obtain 4 bytes of uninitialized kernel heap memory. This could lead to the disclosure of sensitive kernel data.

A flaw was found in the Linux kernel's ALSA USB audio driver, specifically affecting DualSense controllers. A local attacker with physical access to a DualSense controller could exploit this by rapidly disconnecting and reconnecting the device due to a weak physical connection. This action can cause the kernel to attempt to access an invalid memory location, leading to a system crash and a denial of service.

A flaw was found in the Linux kernel. When a CPU is taken offline on systems with Sub-NUMA Clustering (SNC) enabled, a programming error in the resource control (resctrl) file system can lead to an out-of-bounds memory access. This issue may cause system instability or crashes. The vulnerability arises from an incorrect attempt to query a non-existent CPU during the offlining process.

A flaw was found in the Linux kernel's vfio/pci driver. The `disable_idle_d3` flag, which controls device power states, was handled as a global module parameter instead of being latched per device. This improper handling could lead to unbalanced Power Management (PM) operations for devices already bound to vfio-pci drivers. Such an imbalance in PM operations can result in unexpected device behavior or instability.

A flaw was found in the Linux kernel's vfio/pci subsystem. A missing cleanup operation during device registration could lead to a stale registration and a callback using freed memory. This vulnerability could result in system instability or potentially lead to a denial of service.

A flaw was found in the Linux kernel's Virtual Function I/O (VFIO) device migration feature. The `vfio_mig_get_next_state()` function, responsible for managing device migration states, contains an infinite loop. This occurs when processing certain blocked transitions, causing the system to hold a driver state mutex indefinitely. This can lead to a soft lockup of the system and potentially a kernel panic, resulting in a Denial of Service (DoS).

A flaw was found in the VFIO (Virtual Function I/O) subsystem of the Linux kernel. During device unregistration, debugfs (a diagnostic filesystem) entries might remain visible with outdated or "stale" data after the associated resources have been released. This occurs because the debugfs entries are not removed before the device resources are deallocated. While primarily affecting diagnostic views, this could lead to an attacker observing incorrect system state.

A flaw was found in the Linux kernel's vfio/mlx5 subsystem. This vulnerability arises from non-atomic bitfield operations, where multiple updates to shared data structures can occur concurrently. This race condition may lead to unexpected behavior or data corruption due to inconsistent state, potentially impacting system stability or integrity.

A flaw was found in the Linux kernel's Bluetooth subsystem (btusb). When a Bluetooth controller fails to register, the system may not properly release associated interfaces. This can lead to a use-after-free or double-free memory error when these interfaces are later disconnected, potentially causing system instability or a denial of service (DoS).

A flaw was found in the Linux kernel's Bluetooth USB (btusb) driver. This vulnerability occurs during the Marvell Out-Of-Band (OOB) wakeup configuration when a probe failure happens. An attacker could potentially exploit a use-after-free condition in the completion callback, which may lead to system instability, denial of service, or potentially arbitrary code execution.

A flaw was found in the Linux kernel's binder component. This vulnerability allows a local attacker to trigger a use-after-free error due to a race condition during specific thread and process operations. Successful exploitation could lead to arbitrary code execution, granting the attacker unauthorized control over the system, or cause a system crash, resulting in a denial of service.

A flaw was found in the Linux kernel's binder component. A use-after-free (UAF) vulnerability exists in the `binder_free_transaction()` function, where a process's reference is accessed after the lock protecting it is released, allowing the process to terminate prematurely. A local attacker with low privileges could exploit this to cause a system crash (denial of service) or potentially gain elevated privileges.

A flaw was found in the Linux kernel's rust_binder component. This vulnerability arises from an error in how memory offsets are handled during cleanup operations on 32-bit systems. An attacker could exploit this to corrupt the system's reference accounting, causing resources to be released prematurely. This can lead to unexpected system behavior or instability, potentially resulting in a denial of service.

A flaw was found in the Linux kernel's Rust Binder component. This vulnerability occurs when a freeze listener is not properly cleared upon node removal, leading to a reference count cycle. This can result in a memory leak, potentially impacting system stability and performance over time.

A flaw was found in the Linux kernel's USB xHCI (eXtensible Host Controller Interface) driver. When a USB device with active stream endpoints is disconnected, the system attempts to free stream resources while holding a lock with interrupts disabled. This can lead to a situation where a function that is designed to sleep is called in an atomic context, triggering a kernel bug and causing a system crash. This vulnerability could allow a local attacker to cause a Denial of Service (DoS).

A flaw was found in the Linux kernel's xHCI (eXtensible Host Controller Interface) sideband functionality. A memory leak occurs in the `xhci_ring_to_sgtable()` function because a temporary memory array is not properly released after use. This continuous leakage of memory can lead to system instability and a Denial of Service (DoS) over time, impacting the availability of the system.

A flaw was found in the Linux kernel's USB Type-C subsystem, specifically within the `tcpci_rt1711h` driver. When a USB Type-C port is initialized, the system may fail to properly unregister the port if certain setup steps do not complete successfully. This oversight in resource management could lead to system instability or a denial of service (DoS), where legitimate users are unable to access system resources.

A flaw was found in the Linux kernel's MediaTek PCIe driver. When a Peripheral Component Interconnect Express (PCIe) port fails to enable, the associated Interrupt Request (IRQ) domains are not properly released. This resource leak can accumulate over time, potentially leading to a denial of service (DoS) due to resource exhaustion.