CVE Vulnerability Catalog

A vulnerability in the Linux kernel related to error handling during initialization in the HID: hid-pl module has been resolved. Errors must be reported to avoid dereferencing a NULL pointer when FF is first used.

A vulnerability has been identified in the Linux kernel related to the initialization of subdevice before setting controls in the ov5647 module. The issue arises because the v4l2_get_subdevdata function is called before its initialization, which may lead to malfunction.

A vulnerability has been identified and resolved in the Linux kernel. The issue concerns the fbcon_open() function, which, if it fails, does not set the info->fbcon_par pointer, leading to later dereferencing of a NULL pointer.

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 has been identified and resolved in the Linux kernel. It concerns the HID Magic Mouse, which can cause system crashes when the input pointer is missing.

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 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.

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 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 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 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 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 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.