CVE Vulnerability Catalog

A vulnerability related to sync handling in amdgpu has been resolved in the Linux kernel. Invalidating a dmabuf can impact other users of the shared buffer object (BO).

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

Sudo VISudo version 1.6.8 and earlier allows local users to corrupt arbitrary files via a symlink attack on temporary files.

A vulnerability exists in the nodemailer package (npm) affecting versions from 2.7.2 to 10.0.1. Details are not fully described in the provided snippet, but vulnerable versions are confirmed.

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 within the USB pegasus module, which involves filling URBs with hardcoded endpoint pipes without verifying their descriptors. This may lead to improper functioning of USB devices.

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 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 missing initializations in the code handling CIFS request replay. Some parts of the code lacked the necessary initializations, which could lead to improper functioning.

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 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 freemap adjustments when adding extended attributes (xattrs) to leaf blocks has been resolved. This issue caused an assertion failure in the freemap adjustment code after approximately 20 minutes of running on virtual machines.

In the Linux kernel, a vulnerability related to the pstore: ram_core function has been fixed, which incorrectly returned a success pointer when the vmap() function failed.

A vulnerability has been identified in the Linux kernel related to ARM processor errors, occurring when the BIOS generates a very small or incomplete error. This can lead to improper memory dereferencing.

A vulnerability has been identified in the Linux kernel related to the failure to free memory in case of an error. Specifically, the screen buffer fbi->fb.screen_buffer is allocated using dma_alloc_coherent() but is not freed if an error occurs.

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 leads to a General Protection Fault (GPF) in the write_page() function during array resize. This issue is caused by a use-after-free race between bitmap_daemon_work().

In the Linux kernel, a vulnerability related to a resource leak in the cx25821_dev_setup() function has been fixed. The issue occurred when ioremap() failed, leading to the memory region obtained by cx25821_get_resources() not being released.

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