A vulnerability in the Linux kernel's namespace handling has been resolved. The issue involves the may_copy_tree() function accepting mounts whose roots are nsfs or pidfs files before verifying if the mount is actually mounted. This allowed recursive copying of unmounted mount trees, which is unintended behavior. The fix prevents walking an unmounted tree during recursive copy operations, causing such attempts to fail with EINVAL. Bind mounting a namespace that is gone remains possible if pinned by a file descriptor.
A use-after-free vulnerability in the Linux kernel Bluetooth subsystem was resolved. The flaw involved improper handling of socket buffer (skb) lifetimes during passive scan setup, leading to potential use of freed memory. The issue was caused by lack of proper locking around command skb references, allowing concurrent workqueues to free and replace command data while still in use.
A vulnerability in the Linux kernel's drm/i915/gem component could cause improper memory cleanup by overstepping the exec array boundary during relocation parsing. This occurs when the function eb_relocate_parse_slow() calls kvfree() on entries beyond the original exec array due to an incremented buffer count that includes appended VMAs. The issue has been resolved by ensuring relocation cleanup uses the original exec object count, excluding appended VMAs.
A race condition vulnerability in the Linux kernel's i915 DRM driver was resolved by ensuring interrupts are only unmasked when the RPS (Render Power State) is active. The flaw involved a timing window where interrupts could be unmasked after the GPU was parked and the runtime power management wakelock was dropped, causing kernel taint due to hardware access without the wakelock held.
A vulnerability in the Linux kernel's openvswitch component caused a soft lockup during netlink flow dumps on production compute nodes with many datapath flows. The issue arises because the softirq backlog refills as fast as it drains, causing the dumping thread to monopolize CPU time without rescheduling, leading to a system hang. The fix involves holding bottom halves off across the entire callback to prevent nested softirq draining, ensuring the CPU can reschedule properly.
A vulnerability in the Linux kernel's skb_copy_and_csum_bits() function could cause stale memory bytes to be sent in network packets. When the function encounters unreadable fragments, it copies only the linear part of the buffer and leaves the rest unchanged, potentially leaking residual memory data in ICMP error messages or driver transmit buffers. The issue has been resolved by zeroing the unfilled parts of the buffer to prevent unintended data leakage.
A vulnerability in the Linux kernel's SCSI changer driver (ch) caused references to data transfer element devices to be retained improperly. This led to scsi_device objects never being released after device removal, preventing the unloading of the low-level driver module and requiring a system reboot to recover. The issue was fixed by dropping the reference immediately after use and removing the unused array that caused the leak.
A vulnerability in the Linux kernel's packet_rcv_spkt() function could cause a kernel panic when processing packets on devices without a visible link layer header, such as CAN interfaces. The issue arises because packet_rcv_spkt() does not guard the link layer header push operation, leading to an invalid length calculation and a panic in skb_push(). This flaw was introduced when other receive paths were updated but packet_rcv_spkt() was not. The vulnerability has been resolved by adding the appropriate guard to prevent the panic.
A locking order vulnerability in the Linux kernel's Bluetooth RFCOMM implementation (CVE-2026-99009) has been resolved. The issue involves a circular locking dependency between rfcomm_mutex and hdev->lock during RFCOMM socket connection and HCI event handling, which can cause lockdep warnings and potential deadlocks. The fix changes the order of locking by connecting the session socket before acquiring rfcomm_mutex, eliminating the circular dependency. Additional safeguards were added to handle race conditions where sockets or DLCs might be closed during connection setup.
A NULL pointer dereference vulnerability in the Linux kernel Bluetooth RFCOMM subsystem was fixed. The issue occurs in the rfcomm_dev_shutdown() function when closing an RFCOMM tty device. If the tty device registration fails, a NULL pointer dereference can happen because the code does not check if the tty device pointer is NULL before using it. This can lead to a kernel crash (general protection fault). The fix adds a NULL check to prevent this dereference.
A vulnerability in the Linux kernel's Xilinx axienet network driver was resolved. The issue involved the improper freeing of DMA buffers on dmaengine stop, causing a memory leak of SKBs and DMA mappings during interface shutdown. This could exhaust limited IOMMU aperture resources. The fix ensures all DMA-mapped buffers are properly unmapped and freed on stop, and adds synchronization to prevent race conditions between buffer callbacks and driver stop operations.
A vulnerability in the Linux kernel regulator driver for the LTC3676 chip involved reading write-only registers HRST and CLIRQ. These registers trigger hardware reset and interrupt clear commands when written, but reading them causes unintended board resets. The issue was resolved by making these registers writable only and preventing reads that cause resets.
A vulnerability in the Linux kernel's TPS6594 regulator driver was resolved involving an out-of-bounds array access due to an incorrect count of linear voltage ranges. The issue affects the TPS65224 BUCK2, BUCK3, and BUCK4 descriptors, as well as TPS652G1, where the code reads beyond the defined array when checking voltage selectors. This could cause improper handling of voltage constraints during regulator registration.
A use-after-free vulnerability in the Linux kernel's net/smc subsystem was resolved. The flaw occurs in the smc_getname() function, which dereferences a pointer to a CLC socket without proper locking, allowing a race condition where the socket may be released asynchronously. This can lead to either a use-after-free or a NULL pointer dereference during getsockname() calls. The fix involves holding the clcsock_release_lock to serialize access and returning an error if the socket has already been released.
A vulnerability in the Linux kernel's RISC-V architecture under CONFIG_SHADOW_CALL_STACK allowed an unprivileged user to bypass kernel shadow call stack pointer reload checks by manipulating the user-writable tp register. This could lead to arbitrary kernel memory write and control-flow hijacking. The issue was fixed by changing the check to rely on the hardware sstatus.SPP bit, which cannot be forged by user mode, ensuring correct reload of the shadow call stack pointer on user traps.
A vulnerability in the Linux kernel's network team driver was resolved involving improper handling of broadcast packets when no transmitable port is available. The function bc_transmit() sends the original socket buffer (skb) through the last transmitable port, but if no port is transmitable, it returns false without consuming the skb. However, team_xmit() incorrectly returns NETDEV_TX_OK, causing AF_PACKET sockets to retain the skb and its associated socket write-memory charge, potentially leading to resource leaks. The fix ensures the original skb is freed on the no-port path while maintaining existing drop accounting.
A vulnerability in the Linux kernel's network bridge component involving recursive multicast port cleanup has been resolved. The issue occurs in the function br_multicast_sg_del_exclude_ports(), which removes automatically added STAR_EXCL port groups by calling br_multicast_del_pg(). For certain S,G entries, this deletion triggers recursive calls that consume one kernel stack frame per port, potentially hitting the stack guard page and causing a stack overflow. The fix suppresses recursive exclude-port cleanup during the same entry walk while retaining the overall port-group deletion behavior.
A race condition vulnerability in the Linux kernel Bluetooth subsystem (hci_sock) has been resolved. The issue involves rebinding an HCI socket after its controller is unregistered, which can lead to a kernel crash due to a NULL pointer dereference or use-after-free. The root cause is missing serialization when detaching dead devices, allowing concurrent access to freed or nullified device pointers.
A vulnerability in the Linux kernel's mmc sdhci-sprd driver was resolved. The issue involved improper runtime power management (PM) cleanup during device removal, where runtime PM was enabled on probe but not properly disabled on remove. This could lead to clocks being disabled twice or in an inconsistent state if the device was runtime suspended during removal. The fix ensures the device is resumed before removal and runtime PM is properly disabled before clocks are turned off.
A use-after-free vulnerability in the Linux kernel Bluetooth ISO subsystem was resolved. The flaw occurs due to improper handling of concurrent BIS listener setups on the same broadcast socket, leading to a stale socket access and potential memory corruption. The issue was fixed by adding rechecks and rejecting competing setups to prevent connection reference leaks and stale accesses.