All CVEs — page 601 of 631
The complete archive, 25 per page, newest first. 15775 records. Search instead.
This flaw involves a return type mismatch in the `dma_direct_alloc_from_pool` function, leading to incorrect handling of `struct page *`. It matters because it could allow an attacker to manipulate memory allocations, potentially leading to privilege escalation or other severe consequences.
This flaw allows an attacker to trigger a kernel crash by injecting an event that dereferences a stale pointer, potentially leading to a denial of service.
The vulnerability in the Linux kernel's cpuidle module allows for a potential out-of-bounds free error, leading to a denial of service or possibly other kernel memory issues.
The flaw allows a use-after-free condition in the Ceph MDS session handling, which can lead to kernel crashes or arbitrary code execution if exploited.
The flaw allows an attacker to dereference freed memory by concurrently accessing the kprobe_blacklist while a module is being unloaded, leading to potential kernel crashes or arbitrary code execution.
The flaw allows a task with a specific memory policy to allocate memory in an atomic context, potentially leading to a kernel crash or denial of service.
This vulnerability in the Linux kernel allows for potential race conditions during folio migration, leading to incorrect memory control group (memcg) handling and potential privilege escalation or denial of service.
The vulnerability in the Linux kernel's ALSA subsystem allows an attacker to exploit uninitialized locks, potentially leading to a system crash or privilege escalation.
The flaw lies in the race condition between non-atomic PCM operations and atomic trigger-start operations in the Linux kernel's ALSA subsystem, leading to potential inconsistencies and operational issues.
The vulnerability in the Linux kernel's nvme-tcp module allows a malicious controller to trigger a kernel warning by sending a C2HData PDU for a non-read command, potentially causing a system panic due to the panic_on_warn setting.
This flaw in the Linux kernel's NVMe driver allows concurrent readers to hold a reference to a namespace structure that is being freed, potentially leading to a use-after-free condition.