All CVEs — page 610 of 631
The complete archive, 25 per page, newest first. 15775 records. Search instead.
This flaw allows an attacker to cause adjacency flapping and packet loss in OSPFv2-configured networks, disrupting routing within the OSPF domain.
This flaw in the Linux kernel allows a local unprivileged user to perform a use-after-free attack on a perf mmap object, leading to potential local privilege escalation to root.
This vulnerability allows for a use-after-free condition in the Linux kernel's GTP module, which can lead to memory corruption or a denial of service.
This flaw involves a use-after-free vulnerability in the Linux kernel's ksmbd module, where a concurrent session logoff can free a tree connection object while it is still being used by a handler, leading to potential kernel crashes or exploits.
This vulnerability in the ext4 file system of the Linux kernel allows an attacker to trigger a slab-out-of-bounds read, potentially leading to information disclosure.
This vulnerability in the Linux kernel allows an attacker to perform an out-of-bounds write, potentially leading to a kernel panic or other severe issues.
The flaw allows an attacker to cause an out-of-bounds access by mounting a crafted NTFS image, leading to a potential use-after-free condition and kernel crash.
The flaw is an out-of-bounds read vulnerability in the Linux kernel's NTFS3 file system driver, which can lead to memory corruption and potential privilege escalation if exploited.
The flaw allows an attacker to read out-of-bounds heap memory via a crafted EA record, leading to potential heap memory leaks to userspace.
The flaw involves an out-of-bounds page array access in the Linux kernel's isofs module, specifically in the handling of empty zisofs blocks. This can lead to a kernel crash or potentially arbitrary code execution if an attacker can craft a malicious ISO9660 image.
This flaw involves a use-after-free condition in the Linux kernel's vfio/pci subsystem, where the vdev->msi_perm pointer is left dangling after a memory allocation failure, leading to potential reuse and double-free issues.