CVE-20XX-?
agent?

CVEs of 2025.

Every CVE published in 2025 that we hold, ranked by exploit odds.

3,423 CVEs · updated 2026-11-20 19:24 UTC

Reset all
  1. CVE-2025-64721

    Sandboxie is a sandbox-based isolation software for 32-bit and 64-bit Windows NT-based operating systems. In versions 1.16.6 and below, the SYSTEM-level service SbieSvc.exe exposes SbieIniServer::RC4Crypt to sandboxed processes. The handler adds a fixed header size to a caller-controlled value_len without overflow checking. A large value_len (e.g., 0xFFFFFFF0) wraps the allocation size, causing a heap overflow when attacker data is copied into the undersized buffer. This allows sandboxed processes to execute arbitrary code as SYSTEM, fully compromising the host. This issue is fixed in version 1.16.7.

    Memory safety OS & kernel sandboxie-plus Sandboxie

    9.9 CRITICAL 0.7% exploit odds Fix listed
  2. CVE-2025-27733

    Out-of-bounds read in Windows NTFS allows an unauthorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1507

    7.8 HIGH 0.7% exploit odds Fix listed
  3. CVE-2025-62691

    Security Point (Windows) of MaLion and MaLionCloud contains a stack-based buffer overflow vulnerability in processing HTTP headers. Receiving a specially crafted request from a remote unauthenticated attacker could lead to arbitrary code execution with SYSTEM privilege.

    Memory safety OS & kernel

    9.3 CRITICAL 0.7% exploit odds No fix listed
  4. CVE-2025-64693

    Security Point (Windows) of MaLion and MaLionCloud contains a heap-based buffer overflow vulnerability in processing Content-Length. Receiving a specially crafted request from a remote unauthenticated attacker could lead to arbitrary code execution with SYSTEM privilege.

    Memory safety OS & kernel

    9.3 CRITICAL 0.7% exploit odds No fix listed
  5. CVE-2025-21257

    Windows WLAN AutoConfig Service Information Disclosure Vulnerability

    Memory safety OS & kernel Microsoft Windows 10 1607

    5.5 MEDIUM 0.7% exploit odds Fix listed
  6. CVE-2025-37879

    In the Linux kernel, the following vulnerability has been resolved: 9p/net: fix improper handling of bogus negative read/write replies In p9_client_write() and p9_client_read_once(), if the server incorrectly replies with success but a negative write/read count then we would consider written (negative) <= rsize (positive) because both variables were signed. Make variables unsigned to avoid this problem. The reproducer linked below now fails with the following error instead of a null pointer deref: 9pnet: bogus RWRITE count (4294967295 > 3)

    Memory safety OS & kernel Linux Kernel

    9.8 CRITICAL 0.7% exploit odds Fix listed
  7. CVE-2025-24157

    A buffer overflow issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. An app may be able to cause unexpected system termination or corrupt kernel memory.

    Memory safety OS & kernel Apple macOS

    5.6 MEDIUM 0.7% exploit odds Fix listed
  8. CVE-2025-24063

    Heap-based buffer overflow in Windows Kernel allows an authorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1507

    7.8 HIGH 0.7% exploit odds Fix listed
  9. CVE-2025-32720

    Out-of-bounds read in Windows Storage Management Provider allows an authorized attacker to disclose information locally.

    Memory safety OS & kernel Microsoft Windows 10 1507

    5.5 MEDIUM 0.7% exploit odds Fix listed
  10. CVE-2025-62220

    Heap-based buffer overflow in Windows Subsystem for Linux GUI allows an unauthorized attacker to execute code over a network.

    Memory safety OS & kernel Microsoft Windows Subsystem For Linux

    8.8 HIGH 0.7% exploit odds Fix listed
  11. CVE-2025-22040

    In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix session use-after-free in multichannel connection There is a race condition between session setup and ksmbd_sessions_deregister. The session can be freed before the connection is added to channel list of session. This patch check reference count of session before freeing it.

    Memory safety OS & kernel Linux Kernel

    8.8 HIGH 0.7% exploit odds Fix listed
  12. CVE-2025-22041

    In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in ksmbd_sessions_deregister() In multichannel mode, UAF issue can occur in session_deregister when the second channel sets up a session through the connection of the first channel. session that is freed through the global session table can be accessed again through ->sessions of connection.

    Memory safety OS & kernel Linux Kernel

    8.8 HIGH 0.7% exploit odds Fix listed
  13. CVE-2025-24066

    Heap-based buffer overflow in Windows Kernel-Mode Drivers allows an authorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1507

    7.8 HIGH 0.7% exploit odds Fix listed
  14. CVE-2025-24067

    Heap-based buffer overflow in Microsoft Streaming Service allows an authorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1507

    7.8 HIGH 0.7% exploit odds Fix listed
  15. CVE-2025-40135

    In the Linux kernel, the following vulnerability has been resolved: ipv6: use RCU in ip6_xmit() Use RCU in ip6_xmit() in order to use dst_dev_rcu() to prevent possible UAF.

    Memory safety OS & kernel

    8.1 HIGH 0.7% exploit odds No fix listed
  16. CVE-2025-49689

    Integer overflow or wraparound in Virtual Hard Disk (VHDX) allows an unauthorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1507

    7.8 HIGH 0.7% exploit odds Fix listed
  17. CVE-2025-21341

    Windows Digital Media Elevation of Privilege Vulnerability

    Memory safety OS & kernel Microsoft Windows 10 1507

    6.6 MEDIUM 0.7% exploit odds Fix listed
  18. CVE-2025-62458

    Heap-based buffer overflow in Windows Win32K - GRFX allows an authorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1607

    7.8 HIGH 0.7% exploit odds Fix listed
  19. CVE-2025-49730

    Time-of-check time-of-use (toctou) race condition in Microsoft Windows QoS scheduler allows an authorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1507

    7.8 HIGH 0.7% exploit odds Fix listed
  20. CVE-2025-27918

    An issue was discovered in AnyDesk for Windows before 9.0.5, AnyDesk for macOS before 9.0.1, AnyDesk for Linux before 7.0.0, AnyDesk for iOS before 7.1.2, and AnyDesk for Android before 8.0.0. It has an integer overflow and resultant heap-based buffer overflow via a UDP packet during processing of an Identity user image within the Discovery feature, or when establishing a connection between any two clients.

    Memory safety OS & kernel Anydesk

    9.8 CRITICAL 0.7% exploit odds No fix listed
  21. CVE-2023-3865

    In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix out-of-bound read in smb2_write ksmbd_smb2_check_message doesn't validate hdr->NextCommand. If ->NextCommand is bigger than Offset + Length of smb2 write, It will allow oversized smb2 write length. It will cause OOB read in smb2_write.

    Memory safety OS & kernel Linux Kernel

    8.1 HIGH 0.7% exploit odds Fix listed
  22. CVE-2025-14180

    In PHP versions 8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1 when using the PDO PostgreSQL driver with PDO::ATTR_EMULATE_PREPARES enabled, an invalid character sequence (such as \x99) in a prepared statement parameter may cause the quoting function PQescapeStringConn to return NULL, leading to a null pointer dereference in pdo_parse_params() function. This may lead to crashes (segmentation fault) and affect the availability of the target server.

    Memory safety OS & kernel PHP

    8.2 HIGH 0.7% exploit odds Fix listed
  23. CVE-2025-31239

    A use-after-free issue was addressed with improved memory management. This issue is fixed in iOS 18.5 and iPadOS 18.5, iPadOS 17.7.7, macOS Sequoia 15.5, macOS Sonoma 14.7.6, macOS Ventura 13.7.6, tvOS 18.5, visionOS 2.5, watchOS 11.5. Parsing a file may lead to an unexpected app termination.

    Memory safety OS & kernel Apple Ipados

    4.3 MEDIUM 0.7% exploit odds Fix listed
  24. CVE-2022-49664

    In the Linux kernel, the following vulnerability has been resolved: tipc: move bc link creation back to tipc_node_create Shuang Li reported a NULL pointer dereference crash: [] BUG: kernel NULL pointer dereference, address: 0000000000000068 [] RIP: 0010:tipc_link_is_up+0x5/0x10 [tipc] [] Call Trace: [] <IRQ> [] tipc_bcast_rcv+0xa2/0x190 [tipc] [] tipc_node_bc_rcv+0x8b/0x200 [tipc] [] tipc_rcv+0x3af/0x5b0 [tipc] [] tipc_udp_recv+0xc7/0x1e0 [tipc] It was caused by the 'l' passed into tipc_bcast_rcv() is NULL. When it creates a node in tipc_node_check_dest(), after inserting the new node into hashtable in tipc_node_create(), it creates the bc link. However, there is a gap between this insert and bc link creation, a bc packet may come in and get the node from the hashtable then try to dereference its bc link, which is NULL. This patch is to fix it by moving the bc link creation before inserting into the hashtable. Note that for a preliminary node becoming "real", the bc link creation should also be called before it's rehashed, as we don't create it for preliminary nodes.

    Memory safety OS & kernel Linux Kernel

    7.5 HIGH 0.7% exploit odds Fix listed
  25. CVE-2025-24988

    Out-of-bounds read in Windows USB Video Driver allows an authorized attacker to elevate privileges with a physical attack.

    Memory safety OS & kernel Microsoft Windows 10 1507

    6.6 MEDIUM 0.7% exploit odds Fix listed
  26. CVE-2025-24987

    Out-of-bounds read in Windows USB Video Driver allows an authorized attacker to elevate privileges with a physical attack.

    Memory safety OS & kernel Microsoft Windows 10 1507

    6.6 MEDIUM 0.7% exploit odds Fix listed
  27. CVE-2022-49084

    In the Linux kernel, the following vulnerability has been resolved: qede: confirm skb is allocated before using qede_build_skb() assumes build_skb() always works and goes straight to skb_reserve(). However, build_skb() can fail under memory pressure. This results in a kernel panic because the skb to reserve is NULL. Add a check in case build_skb() failed to allocate and return NULL. The NULL return is handled correctly in callers to qede_build_skb().

    Memory safety OS & kernel Linux Kernel

    7.5 HIGH 0.7% exploit odds Fix listed
  28. CVE-2022-49356

    In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Trap RDMA segment overflows Prevent svc_rdma_build_writes() from walking off the end of a Write chunk's segment array. Caught with KASAN. The test that this fix replaces is invalid, and might have been left over from an earlier prototype of the PCL work.

    Memory safety OS & kernel Linux Kernel

    9.8 CRITICAL 0.7% exploit odds Fix listed
  29. CVE-2025-26634

    Heap-based buffer overflow in Windows Core Messaging allows an authorized attacker to elevate privileges over a network.

    Memory safety OS & kernel Microsoft Windows 10 1507

    7.5 HIGH 0.7% exploit odds Fix listed
  30. CVE-2022-49075

    In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a 3GiB file. This should fail. echo echo "Try to fallocate a 3GiB file..." fallocate -l 3G $MNT/3G.file # Try to fallocate a 5GiB file. echo echo "Try to fallocate a 5GiB file..." fallocate -l 5G $MNT/5G.file # See we break the qgroup limit. echo sync btrfs qgroup show -r $MNT umount $MNT When running the test: $ ./qgroup-overflow.sh (...) Try to fallocate a 3GiB file... fallocate: fallocate failed: Disk quota exceeded Try to fallocate a 5GiB file... qgroupid         rfer         excl     max_rfer --------         ----         ----     -------- 0/5           5.00GiB      5.00GiB      2.00GiB Since we have no control of how bytes_changed is used, it's better to set it to u64.

    Memory safety OS & kernel Linux Kernel

    8.1 HIGH 0.7% exploit odds Fix listed
  31. CVE-2025-21796

    In the Linux kernel, the following vulnerability has been resolved: nfsd: clear acl_access/acl_default after releasing them If getting acl_default fails, acl_access and acl_default will be released simultaneously. However, acl_access will still retain a pointer pointing to the released posix_acl, which will trigger a WARNING in nfs3svc_release_getacl like this: ------------[ cut here ]------------ refcount_t: underflow; use-after-free. WARNING: CPU: 26 PID: 3199 at lib/refcount.c:28 refcount_warn_saturate+0xb5/0x170 Modules linked in: CPU: 26 UID: 0 PID: 3199 Comm: nfsd Not tainted 6.12.0-rc6-00079-g04ae226af01f-dirty #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 RIP: 0010:refcount_warn_saturate+0xb5/0x170 Code: cc cc 0f b6 1d b3 20 a5 03 80 fb 01 0f 87 65 48 d8 00 83 e3 01 75 e4 48 c7 c7 c0 3b 9b 85 c6 05 97 20 a5 03 01 e8 fb 3e 30 ff <0f> 0b eb cd 0f b6 1d 8a3 RSP: 0018:ffffc90008637cd8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff83904fde RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff88871ed36380 RBP: ffff888158beeb40 R08: 0000000000000001 R09: fffff520010c6f56 R10: ffffc90008637ab7 R11: 0000000000000001 R12: 0000000000000001 R13: ffff888140e77400 R14: ffff888140e77408 R15: ffffffff858b42c0 FS: 0000000000000000(0000) GS:ffff88871ed00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000562384d32158 CR3: 000000055cc6a000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? refcount_warn_saturate+0xb5/0x170 ? __warn+0xa5/0x140 ? refcount_warn_saturate+0xb5/0x170 ? report_bug+0x1b1/0x1e0 ? handle_bug+0x53/0xa0 ? exc_invalid_op+0x17/0x40 ? asm_exc_invalid_op+0x1a/0x20 ? tick_nohz_tick_stopped+0x1e/0x40 ? refcount_warn_saturate+0xb5/0x170 ? refcount_warn_saturate+0xb5/0x170 nfs3svc_release_getacl+0xc9/0xe0 svc_process_common+0x5db/0xb60 ? __pfx_svc_process_common+0x10/0x10 ? __rcu_read_unlock+0x69/0xa0 ? __pfx_nfsd_dispatch+0x10/0x10 ? svc_xprt_received+0xa1/0x120 ? xdr_init_decode+0x11d/0x190 svc_process+0x2a7/0x330 svc_handle_xprt+0x69d/0x940 svc_recv+0x180/0x2d0 nfsd+0x168/0x200 ? __pfx_nfsd+0x10/0x10 kthread+0x1a2/0x1e0 ? kthread+0xf4/0x1e0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x34/0x60 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Kernel panic - not syncing: kernel: panic_on_warn set ... Clear acl_access/acl_default after posix_acl_release is called to prevent UAF from being triggered.

    Memory safety OS & kernel Linux Kernel

    9.8 CRITICAL 0.7% exploit odds Fix listed
  32. CVE-2022-49094

    In the Linux kernel, the following vulnerability has been resolved: net/tls: fix slab-out-of-bounds bug in decrypt_internal The memory size of tls_ctx->rx.iv for AES128-CCM is 12 setting in tls_set_sw_offload(). The return value of crypto_aead_ivsize() for "ccm(aes)" is 16. So memcpy() require 16 bytes from 12 bytes memory space will trigger slab-out-of-bounds bug as following: ================================================================== BUG: KASAN: slab-out-of-bounds in decrypt_internal+0x385/0xc40 [tls] Read of size 16 at addr ffff888114e84e60 by task tls/10911 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report.cold+0x5e/0x5db ? decrypt_internal+0x385/0xc40 [tls] kasan_report+0xab/0x120 ? decrypt_internal+0x385/0xc40 [tls] kasan_check_range+0xf9/0x1e0 memcpy+0x20/0x60 decrypt_internal+0x385/0xc40 [tls] ? tls_get_rec+0x2e0/0x2e0 [tls] ? process_rx_list+0x1a5/0x420 [tls] ? tls_setup_from_iter.constprop.0+0x2e0/0x2e0 [tls] decrypt_skb_update+0x9d/0x400 [tls] tls_sw_recvmsg+0x3c8/0xb50 [tls] Allocated by task 10911: kasan_save_stack+0x1e/0x40 __kasan_kmalloc+0x81/0xa0 tls_set_sw_offload+0x2eb/0xa20 [tls] tls_setsockopt+0x68c/0x700 [tls] __sys_setsockopt+0xfe/0x1b0 Replace the crypto_aead_ivsize() with prot->iv_size + prot->salt_size when memcpy() iv value in TLS_1_3_VERSION scenario.

    Memory safety OS & kernel Linux Kernel

    9.8 CRITICAL 0.7% exploit odds Fix listed
  33. CVE-2024-57973

    In the Linux kernel, the following vulnerability has been resolved: rdma/cxgb4: Prevent potential integer overflow on 32bit The "gl->tot_len" variable is controlled by the user. It comes from process_responses(). On 32bit systems, the "gl->tot_len + sizeof(struct cpl_pass_accept_req) + sizeof(struct rss_header)" addition could have an integer wrapping bug. Use size_add() to prevent this.

    Memory safety OS & kernel Linux Kernel

    8.1 HIGH 0.7% exploit odds Fix listed
  34. CVE-2025-21762

    In the Linux kernel, the following vulnerability has been resolved: arp: use RCU protection in arp_xmit() arp_xmit() can be called without RTNL or RCU protection. Use RCU protection to avoid potential UAF.

    Memory safety OS & kernel Linux Kernel

    8.1 HIGH 0.7% exploit odds Fix listed
  35. CVE-2025-21315

    Microsoft Brokering File System Elevation of Privilege Vulnerability

    Memory safety OS & kernel Microsoft Windows 11 24h2

    7.8 HIGH 0.7% exploit odds Fix listed
  36. CVE-2022-49362

    In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix potential use-after-free in nfsd_file_put() nfsd_file_put_noref() can free @nf, so don't dereference @nf immediately upon return from nfsd_file_put_noref().

    Memory safety OS & kernel Linux Kernel

    9.8 CRITICAL 0.7% exploit odds Fix listed
  37. CVE-2025-21367

    Windows Win32 Kernel Subsystem Elevation of Privilege Vulnerability

    Memory safety OS & kernel Microsoft Windows 10 1809

    7.8 HIGH 0.6% exploit odds Fix listed
  38. CVE-2025-33062

    Out-of-bounds read in Windows Storage Management Provider allows an authorized attacker to disclose information locally.

    Memory safety OS & kernel Microsoft Windows 10 1607

    5.5 MEDIUM 0.6% exploit odds Fix listed
  39. CVE-2025-33055

    Out-of-bounds read in Windows Storage Management Provider allows an authorized attacker to disclose information locally.

    Memory safety OS & kernel Microsoft Windows 10 1507

    5.5 MEDIUM 0.6% exploit odds Fix listed
  40. CVE-2024-36476

    In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs: Ensure 'ib_sge list' is accessible Move the declaration of the 'ib_sge list' variable outside the 'always_invalidate' block to ensure it remains accessible for use throughout the function. Previously, 'ib_sge list' was declared within the 'always_invalidate' block, limiting its accessibility, then caused a 'BUG: kernel NULL pointer dereference'[1]. ? __die_body.cold+0x19/0x27 ? page_fault_oops+0x15a/0x2d0 ? search_module_extables+0x19/0x60 ? search_bpf_extables+0x5f/0x80 ? exc_page_fault+0x7e/0x180 ? asm_exc_page_fault+0x26/0x30 ? memcpy_orig+0xd5/0x140 rxe_mr_copy+0x1c3/0x200 [rdma_rxe] ? rxe_pool_get_index+0x4b/0x80 [rdma_rxe] copy_data+0xa5/0x230 [rdma_rxe] rxe_requester+0xd9b/0xf70 [rdma_rxe] ? finish_task_switch.isra.0+0x99/0x2e0 rxe_sender+0x13/0x40 [rdma_rxe] do_task+0x68/0x1e0 [rdma_rxe] process_one_work+0x177/0x330 worker_thread+0x252/0x390 ? __pfx_worker_thread+0x10/0x10 This change ensures the variable is available for subsequent operations that require it. [1] https://lore.kernel.org/linux-rdma/[email protected]/

    Memory safety OS & kernel Linux Kernel

    9.8 CRITICAL 0.6% exploit odds Fix listed
  41. CVE-2025-40252

    In the Linux kernel, the following vulnerability has been resolved: net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end() The loops in 'qede_tpa_cont()' and 'qede_tpa_end()', iterate over 'cqe->len_list[]' using only a zero-length terminator as the stopping condition. If the terminator was missing or malformed, the loop could run past the end of the fixed-size array. Add an explicit bound check using ARRAY_SIZE() in both loops to prevent a potential out-of-bounds access. Found by Linux Verification Center (linuxtesting.org) with SVACE.

    Memory safety OS & kernel

    9.8 CRITICAL 0.6% exploit odds No fix listed
  42. CVE-2023-52991

    In the Linux kernel, the following vulnerability has been resolved: net: fix NULL pointer in skb_segment_list Commit 3a1296a38d0c ("net: Support GRO/GSO fraglist chaining.") introduced UDP listifyed GRO. The segmentation relies on frag_list being untouched when passing through the network stack. This assumption can be broken sometimes, where frag_list itself gets pulled into linear area, leaving frag_list being NULL. When this happens it can trigger following NULL pointer dereference, and panic the kernel. Reverse the test condition should fix it. [19185.577801][ C1] BUG: kernel NULL pointer dereference, address: ... [19185.663775][ C1] RIP: 0010:skb_segment_list+0x1cc/0x390 ... [19185.834644][ C1] Call Trace: [19185.841730][ C1] <TASK> [19185.848563][ C1] __udp_gso_segment+0x33e/0x510 [19185.857370][ C1] inet_gso_segment+0x15b/0x3e0 [19185.866059][ C1] skb_mac_gso_segment+0x97/0x110 [19185.874939][ C1] __skb_gso_segment+0xb2/0x160 [19185.883646][ C1] udp_queue_rcv_skb+0xc3/0x1d0 [19185.892319][ C1] udp_unicast_rcv_skb+0x75/0x90 [19185.900979][ C1] ip_protocol_deliver_rcu+0xd2/0x200 [19185.910003][ C1] ip_local_deliver_finish+0x44/0x60 [19185.918757][ C1] __netif_receive_skb_one_core+0x8b/0xa0 [19185.927834][ C1] process_backlog+0x88/0x130 [19185.935840][ C1] __napi_poll+0x27/0x150 [19185.943447][ C1] net_rx_action+0x27e/0x5f0 [19185.951331][ C1] ? mlx5_cq_tasklet_cb+0x70/0x160 [mlx5_core] [19185.960848][ C1] __do_softirq+0xbc/0x25d [19185.968607][ C1] irq_exit_rcu+0x83/0xb0 [19185.976247][ C1] common_interrupt+0x43/0xa0 [19185.984235][ C1] asm_common_interrupt+0x22/0x40 ... [19186.094106][ C1] </TASK>

    Memory safety OS & kernel Linux Kernel

    7.5 HIGH 0.6% exploit odds Fix listed
  43. CVE-2022-49065

    In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix the svc_deferred_event trace class Fix a NULL deref crash that occurs when an svc_rqst is deferred while the sunrpc tracing subsystem is enabled. svc_revisit() sets dr->xprt to NULL, so it can't be relied upon in the tracepoint to provide the remote's address. Unfortunately we can't revert the "svc_deferred_class" hunk in commit ece200ddd54b ("sunrpc: Save remote presentation address in svc_xprt for trace events") because there is now a specific check of event format specifiers for unsafe dereferences. The warning that check emits is: event svc_defer_recv has unsafe dereference of argument 1 A "%pISpc" format specifier with a "struct sockaddr *" is indeed flagged by this check. Instead, take the brute-force approach used by the svcrdma_qp_error tracepoint. Convert the dr::addr field into a presentation address in the TP_fast_assign() arm of the trace event, and store that as a string. This fix can be backported to -stable kernels. In the meantime, commit c6ced22997ad ("tracing: Update print fmt check to handle new __get_sockaddr() macro") is now in v5.18, so this wonky fix can be replaced with __sockaddr() and friends properly during the v5.19 merge window.

    Memory safety OS & kernel Linux Kernel

    7.5 HIGH 0.6% exploit odds Fix listed
  44. CVE-2025-27730

    Use after free in Windows Digital Media allows an authorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1809

    7.8 HIGH 0.6% exploit odds Fix listed
  45. CVE-2025-27476

    Use after free in Windows Digital Media allows an authorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1809

    7.8 HIGH 0.6% exploit odds Fix listed
  46. CVE-2025-27467

    Use after free in Windows Digital Media allows an authorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1809

    7.8 HIGH 0.6% exploit odds Fix listed
  47. CVE-2025-26674

    Heap-based buffer overflow in Windows Media allows an authorized attacker to execute code locally.

    Memory safety OS & kernel Microsoft Windows 10 1809

    7.8 HIGH 0.6% exploit odds Fix listed
  48. CVE-2025-26666

    Heap-based buffer overflow in Windows Media allows an authorized attacker to execute code locally.

    Memory safety OS & kernel Microsoft Windows 10 1809

    7.8 HIGH 0.6% exploit odds Fix listed
  49. CVE-2025-23322

    NVIDIA Triton Inference Server for Windows and Linux contains a vulnerability where multiple requests could cause a double free when a stream is cancelled before it is processed. A successful exploit of this vulnerability might lead to denial of service.

    Memory safety OS & kernel Nvidia Triton Inference Server

    7.5 HIGH 0.6% exploit odds Fix listed
  50. CVE-2025-50161

    Heap-based buffer overflow in Windows Win32K - GRFX allows an authorized attacker to elevate privileges locally.

    Memory safety OS & kernel Microsoft Windows 10 1507

    7.3 HIGH 0.6% exploit odds Fix listed

CVE records published in 2025 (ids starting CVE-2025-), sorted by how likely they are to be exploited.