Linux kernel vulnerabilities

A vulnerability in the Linux kernel's FUSE filesystem causes a hang during sync initialization when the FUSE server exits (e.g., due to error or crash) while processing the FUSE_INIT request. The issue stems from the lack of abort on a fatal signal, blocking filesystem creation.

In the Linux kernel's fork function, a race condition exists between fork and hugetlbfs file operations. The fix defers linking the file VMA until the VMA is fully initialized.

In the Linux kernel, in the NFS server (nfsd), a race between the laundromat thread and the free_stateid operation was fixed, which could lead to incorrect handling of expired delegations.

In the Linux kernel, in the sc16is7xx serial driver, a TX FIFO corruption was fixed that could occur when a packet was received on channel A at almost the same time as a packet was about to be transmitted on channel B.

In the Linux kernel, in the RDMA/hns driver, a soft lockup issue under heavy CEQE load was fixed by moving CEQE handling to the BH (bottom half) context.

In the Linux kernel, in the DRM/XE driver (guc_submit), a race condition around the suspend_pending field was fixed, which could cause assertions and warnings in certain test scenarios.

In the Linux kernel, a vulnerability in the mshv_vtl component occurs when registering VTL0 memory via MSHV_ADD_VTL0_MEMORY, where the computed vmemmap_shift may exceed MAX_FOLIO_ORDER, leading to incorrect behavior.

A vulnerability has been identified in the Linux kernel in the xfrm6_get_saddr() function, which does not check the return value of ipv6_dev_get_saddr(). If it fails, it may lead to the use of an uninitialized source address.

A vulnerability related to double dma_buf_unpin in failure path has been fixed in the Linux kernel. In the function ib_umem_dmabuf_get_pinned_with_dma_device(), a failure may occur during the call to ib_umem_dmabuf_map_pages(), leading to improper memory management.

A vulnerability has been identified in the Linux kernel related to resource leaks during early registration failures. A recent commit fixed most cases, but for some reason, it left out the first error path, which still leaks resources.

A vulnerability in the Linux kernel has been resolved that allowed a user-triggerable WARN in the nested_svm_load_cr3() function. The WARN has been removed from the svm_set_nested_state() function on failure of loading, as it can be trivially triggered from userspace by modifying CPUID after load.

A vulnerability in the Linux kernel has been fixed that led to a NULL-pointer dereference in the acpi_processor_errata_piix4() function. The issue occurred during the assignment of IDE and ISA devices.

A vulnerability has been identified in the Linux kernel that leads to a memory leak when the cfg80211_inform_bss_frame() function fails. If this function returns NULL, the allocated buffer 'buf' is not freed, resulting in a memory leak.

A vulnerability in the Linux kernel has been fixed that could lead to a null-pointer dereference in the jdi_panel_dsi_remove() function. The issue occurred when the jdi pointer was NULL, potentially causing unexpected system behavior.

A vulnerability in the Linux kernel related to the rio_scan_alloc_net() function has been resolved. In case of idtab allocation failure, memory is released using kfree() instead of rio_free_net().

A vulnerability has been identified in the Linux kernel related to the kexec_load_purgatory() function, which derives the start image from the SHF_EXECINSTR section. The issue occurs when the purgatory object contains multiple executable sections with overlapping addresses.

A vulnerability has been identified in the Linux kernel regarding the allocation of property blobs in DRM_IOCTL_MODE_CREATEPROPBLOB. This allows users to allocate blobs of arbitrary size, potentially leading to uncontrolled memory usage.

A vulnerability has been identified in the Linux kernel that has been resolved. It concerns improper management of bio pointers in cloned requests, leading to issues with use-after-free.

A vulnerability related to APEI/GHES has been resolved in the Linux kernel, which could lead to the allocation of overly large records. The logic in the ghes_new() function checks that records do not exceed the maximum size of GHES_ESTATUS_MAX_SIZE, currently set at 64KB.

In the Linux kernel, a fake timeout has been removed to avoid request leaks. This change requires drivers to be responsible for calling blk_should_fake_timeout() at appropriate code paths.

A vulnerability in the Linux kernel related to exception handling in SCSI for UFS has been resolved. The issue was the lack of proper flushing of exception handling work during system suspend when the runtime power management level is set to zero.

A vulnerability in the Linux kernel has been fixed, which involved a NULL pointer dereference in the process_metadata_update() function. The issue occurred in the wait_event() macro, which improperly handled the 'thread' pointer.

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.

In the Linux kernel's btrfs filesystem, a use-after-free of the block device file occurs in __btrfs_free_extra_devids(). The issue may arise when mounting two btrfs images with the same fsid.

A vulnerability has been identified in the Linux kernel related to the logic in GHES/CPER, which does not detect if the section length is too large. This may lead to improper processing of CPER records for ARM processors.

A vulnerability has been identified in the Linux kernel related to a reference count leak in the of_get_display_timings() function. This issue occurs during the processing of device nodes, potentially leading to improper memory management.

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 the gfs2_fiemap() function, which can lead to recursive inode lock taking. The issue occurs when the fiemap buffer is memory mapped to the same inode.

A vulnerability in the Linux kernel has been fixed that caused sporadic user-space crashes and heap corruption on Alpha systems during memory compaction.

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 that has been resolved. In the error path, the function cx88_alsa_dma_unmap() has been added to release resources acquired by cx88_alsa_dma_map().

A vulnerability in the Linux kernel related to out-of-bounds access in the vfe_isr_reg_update() function has been resolved. The issue occurs during iteration in the vfe_isr() function, where an incorrect loop bound is used, potentially leading to unauthorized memory access.

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 has been identified in the Linux kernel that has been resolved. The issue concerns the xen_9pfs_front_free function, which can be called concurrently by the xenwatch thread, leading to a general protection fault due to double invocation.

A vulnerability has been identified in the Linux kernel that has been resolved. In the tw9906_probe() function, there was a potential memory leak because memory allocated in v4l2_ctrl_handler_init() and v4l2_ctrl_new_std() was not freed.

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.

In the Linux kernel, RCU protection was added for the conventional zones bitmap of a disk (conv_zones_bitmap) in the block layer. This prevents invalid memory references during disk revalidation.

A vulnerability has been identified in the Linux kernel related to a regmap leak on probe failure. The allocated mmio regmap is never freed, which can lead to memory issues.

A vulnerability in the Linux kernel has been resolved that allowed two query interface operations to concurrently update interfaces. A locking mechanism has been introduced to prevent these races.

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 related to use-after-free in drm_crtc_commit after release has been fixed in the Linux kernel. The issue involved improper duplication of the drm_plane_state in the atmel_hlcdc_plane_atomic_duplicate_state() function.

A vulnerability in the Linux kernel has been fixed that allowed for out-of-bounds read in the decode_choice() function. The issue stemmed from improper boundary checking before calling get_len(), which could lead to unexpected behavior.

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.

In the Linux kernel, the bnge driver has a vulnerability where a return statement is missing after auxiliary_device_uninit() in the error path. After auxiliary_device_add() fails, execution continues, potentially leading to use-after-free.

In the Linux kernel, a vulnerability related to use-after-free bugs has been fixed, which occurs during the detachment of the FarSync T-series card. These issues may arise in the fst_remove_one() function, where fst_card_info is deallocated, but fst_tx_task or fst_int_task may still be active.

A vulnerability in the Linux kernel related to RDS connections lacking a proper shortcut in case of connection errors has been resolved.

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 URB leak in the pvr2_send_request_ex function has been fixed in the Linux kernel. The issue occurs when the function successfully submits a write URB but fails to submit the read URB, leading to an immediate return without waiting for the write URB to complete.

A vulnerability in the Linux kernel related to event handler initialization in IPMB has been resolved, which does not use I2C reads but requires a value to be set. Otherwise, an I2C read will return an uninitialized value from the bus driver.

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