Export limit exceeded: 412929 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (412929 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2024-54587 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2024-54586 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2024-54585 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2024-54584 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2024-54583 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2024-54582 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2023-42999 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2023-42998 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2023-42997 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2023-42996 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2023-42995 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2023-42994 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2023-42993 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2023-42992 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2023-42991 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2023-42990 | 2026-10-19 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues. | ||||
| CVE-2026-103038 | 1 Streamsoft | 1 Pingtools Network Utilities | 2026-10-19 | N/A |
| PingTools Network Utilities 4.64 contains an OS command injection vulnerability in the Host field of a Watcher ICMP service. The application appends the attacker-controlled Host value to a ping command, serializes the command as a single string, and executes it through sh -c. A local attacker who can create or modify a Watcher service can inject shell syntax and execute arbitrary commands with the PingTools application UID and its granted Android permissions. | ||||
| CVE-2026-97204 | 1 Gitea | 1 Gitea | 2026-10-19 | 3.1 Low |
| Deleting a label compared the ID of the repository in the request against the organization ID of organization labels, and the two ID sequences overlap. A user with write access to the issues of a repository could therefore delete the labels of an organization that has the same numeric ID as that repository. Labels are now deleted only within their own repository or organization. | ||||
| CVE-2026-68290 | 1 Linux | 1 Linux Kernel | 2026-10-19 | 7.8 High |
| In the Linux kernel, the following vulnerability has been resolved: rds: tcp: unregister sysctl before tearing down listen socket rds_tcp_exit_net() frees the per-netns RDS TCP listen socket via rds_tcp_kill_sock() before unregistering the per-netns sysctl table. Since rds_tcp_skbuf_handler() derives the netns from rtn->rds_tcp_listen_sock->sk, a concurrent sysctl write can race with netns teardown and dereference the freed socket/sk. KASAN reports the race as: BUG: KASAN: slab-use-after-free in rds_tcp_skbuf_handler+0x2aa/0x2e0 rds_tcp_skbuf_handler net/rds/tcp.c:721 proc_sys_call_handler fs/proc/proc_sysctl.c vfs_write fs/read_write.c __x64_sys_pwrite64 fs/read_write.c Fix this by unregistering the RDS TCP sysctl table before calling rds_tcp_kill_sock(). unregister_net_sysctl_table() prevents new sysctl handlers from starting and waits for in-flight handlers to finish, so the listen socket can then be released safely. The fix was tested against the linked reproducer. | ||||
| CVE-2026-68284 | 1 Linux | 1 Linux Kernel | 2026-10-19 | 7.8 High |
| In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix cork use-after-free in tcp_bpf_sendmsg() tcp_bpf_sendmsg() keeps msg_tx across sk_stream_wait_memory(), which drops and reacquires the socket lock. Its error path tries to decide whether msg_tx names the local temporary message by comparing it with the current value of psock->cork. This comparison is unsafe when two threads send on the same socket: Thread A Thread B msg_tx = psock->cork sk_msg_alloc() fails sk_stream_wait_memory() releases the socket lock acquires the socket lock completes the cork psock->cork = NULL frees the cork reacquires the socket lock msg_tx != psock->cork sk_msg_free(msg_tx) The stale cork is therefore mistaken for the local temporary message and freed again. KASAN reported: BUG: KASAN: slab-use-after-free in sk_msg_free+0x49/0x50 Read of size 4 at addr ffff88810c908800 by task poc/90 Call Trace: sk_msg_free+0x49/0x50 tcp_bpf_sendmsg+0x14f5/0x1cc0 __sys_sendto+0x32c/0x3a0 __x64_sys_sendto+0xdb/0x1b0 Allocated by task 89: __kasan_kmalloc+0x8f/0xa0 tcp_bpf_sendmsg+0x16b3/0x1cc0 Freed by task 91: __kasan_slab_free+0x43/0x70 kfree+0x131/0x3c0 tcp_bpf_sendmsg+0xec3/0x1cc0 msg_tx can only name the stack-local tmp or the shared cork. Check for tmp directly so a changed psock->cork cannot turn a shared message into an apparent local one. | ||||