Show filters
142 Total Results
Displaying 111-120 of 142
Sort by:
Attacker Value
Unknown

CVE-2019-19069

Disclosure Date: November 18, 2019 (last updated November 27, 2024)
A memory leak in the fastrpc_dma_buf_attach() function in drivers/misc/fastrpc.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption) by triggering dma_get_sgtable() failures, aka CID-fc739a058d99.
Attacker Value
Unknown

CVE-2019-19050

Disclosure Date: November 18, 2019 (last updated November 08, 2023)
A memory leak in the crypto_reportstat() function in crypto/crypto_user_stat.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering crypto_reportstat_alg() failures, aka CID-c03b04dcdba1.
Attacker Value
Unknown

CVE-2019-19057

Disclosure Date: November 18, 2019 (last updated November 08, 2023)
Two memory leaks in the mwifiex_pcie_init_evt_ring() function in drivers/net/wireless/marvell/mwifiex/pcie.c in the Linux kernel through 5.3.11 allow attackers to cause a denial of service (memory consumption) by triggering mwifiex_map_pci_memory() failures, aka CID-d10dcb615c8e.
Attacker Value
Unknown

CVE-2019-19054

Disclosure Date: November 18, 2019 (last updated November 08, 2023)
A memory leak in the cx23888_ir_probe() function in drivers/media/pci/cx23885/cx23888-ir.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering kfifo_alloc() failures, aka CID-a7b2df76b42b.
Attacker Value
Unknown

CVE-2019-18805

Disclosure Date: November 07, 2019 (last updated November 27, 2024)
An issue was discovered in net/ipv4/sysctl_net_ipv4.c in the Linux kernel before 5.0.11. There is a net/ipv4/tcp_input.c signed integer overflow in tcp_ack_update_rtt() when userspace writes a very large integer to /proc/sys/net/ipv4/tcp_min_rtt_wlen, leading to a denial of service or possibly unspecified other impact, aka CID-19fad20d15a6.
Attacker Value
Unknown

CVE-2019-18683

Disclosure Date: November 04, 2019 (last updated June 07, 2024)
An issue was discovered in drivers/media/platform/vivid in the Linux kernel through 5.3.8. It is exploitable for privilege escalation on some Linux distributions where local users have /dev/video0 access, but only if the driver happens to be loaded. There are multiple race conditions during streaming stopping in this driver (part of the V4L2 subsystem). These issues are caused by wrong mutex locking in vivid_stop_generating_vid_cap(), vivid_stop_generating_vid_out(), sdr_cap_stop_streaming(), and the corresponding kthreads. At least one of these race conditions leads to a use-after-free.
Attacker Value
Unknown

CVE-2019-17498

Disclosure Date: October 21, 2019 (last updated November 08, 2023)
In libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an integer overflow in a bounds check, enabling an attacker to specify an arbitrary (out-of-bounds) offset for a subsequent memory read. A crafted SSH server may be able to disclose sensitive information or cause a denial of service condition on the client system when a user connects to the server.
Attacker Value
Unknown

CVE-2019-15166

Disclosure Date: October 03, 2019 (last updated November 08, 2023)
lmp_print_data_link_subobjs() in print-lmp.c in tcpdump before 4.9.3 lacks certain bounds checks.
Attacker Value
Unknown

CVE-2019-5481

Disclosure Date: September 16, 2019 (last updated November 08, 2023)
Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.
Attacker Value
Unknown

CVE-2019-13272

Disclosure Date: July 17, 2019 (last updated July 25, 2024)
In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to create a ptrace relationship, which allows local users to obtain root access by leveraging certain scenarios with a parent-child process relationship, where a parent drops privileges and calls execve (potentially allowing control by an attacker). One contributing factor is an object lifetime issue (which can also cause a panic). Another contributing factor is incorrect marking of a ptrace relationship as privileged, which is exploitable through (for example) Polkit's pkexec helper with PTRACE_TRACEME. NOTE: SELinux deny_ptrace might be a usable workaround in some environments.