{"vulnerability": "cve-2025-2171", "sightings": [{"uuid": "13fbb3e9-91ea-4eb1-b621-7bb49bb29a57", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-21712", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "0f955110-40bd-492f-b94c-7506f68a1b93", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2171", "type": "seen", "source": "https://bsky.app/profile/thedailytechfeed.com/post/3lseesejnmc2a", "content": "", "creation_timestamp": "2025-06-24T15:07:46.508699Z"}, {"uuid": "9959162c-84ff-4034-9200-b824d94c0ba6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-21714", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "770f5918-f7c2-4222-b9cb-dde5af33d44e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21717", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114074812998194265", "content": "", "creation_timestamp": "2025-02-27T08:05:09.315872Z"}, {"uuid": "914670f5-84d5-448b-9b43-256d5c9b9236", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21712", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-162-05", "content": "", "creation_timestamp": "2025-06-12T10:00:00.000000Z"}, {"uuid": "7d594e18-691a-4894-9760-88ded3bef51f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2171", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3lsdkoak7ob2m", "content": "", "creation_timestamp": "2025-06-24T07:20:07.924360Z"}, {"uuid": "87a422e2-7dc5-4f63-b4e5-44b2bc7de4c4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2171", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lsdlqeefxhn2", "content": "", "creation_timestamp": "2025-06-24T07:39:55.847272Z"}, {"uuid": "16e03220-b533-4194-8ee1-200f15f39cef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21715", "type": "seen", "source": "MISP/af1fbe07-e10c-40c4-844e-d4419bdf6f80", "content": "", "creation_timestamp": "2025-08-22T13:26:18.000000Z"}, {"uuid": "043790da-f404-4500-ba93-e82b6ed3f2a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21716", "type": "seen", "source": "MISP/af1fbe07-e10c-40c4-844e-d4419bdf6f80", "content": "", "creation_timestamp": "2025-08-22T13:26:18.000000Z"}, {"uuid": "53156a7e-b51c-4152-b1f7-8fe69703e174", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21719", "type": "seen", "source": "MISP/af1fbe07-e10c-40c4-844e-d4419bdf6f80", "content": "", "creation_timestamp": "2025-08-22T13:26:18.000000Z"}, {"uuid": "fd282ae2-12b0-4f07-92d1-d96e667558ab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21718", "type": "seen", "source": "MISP/af1fbe07-e10c-40c4-844e-d4419bdf6f80", "content": "", "creation_timestamp": "2025-08-22T13:26:18.000000Z"}, {"uuid": "8ad52944-fbb5-4068-8464-c4fd5595f9eb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21717", "type": "seen", "source": "MISP/af1fbe07-e10c-40c4-844e-d4419bdf6f80", "content": "", "creation_timestamp": "2025-08-22T13:26:18.000000Z"}, {"uuid": "25839f7d-1fbf-4c0b-af40-44f239b44e92", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21717", "type": "seen", "source": "https://t.me/cvedetector/18984", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21717 - Mellanox Technologies mlx5e Node ID Validation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21717 \nPublished : Feb. 27, 2025, 2:15 a.m. | 50\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet/mlx5e: add missing cpu_to_node to kvzalloc_node in mlx5e_open_xdpredirect_sq  \n  \nkvzalloc_node is not doing a runtime check on the node argument  \n(__alloc_pages_node_noprof does have a VM_BUG_ON, but it expands to  \nnothing on !CONFIG_DEBUG_VM builds), so doing any ethtool/netlink  \noperation that calls mlx5e_open on a CPU that's larger that MAX_NUMNODES  \ntriggers OOB access and panic (see the trace below).  \n  \nAdd missing cpu_to_node call to convert cpu id to node id.  \n  \n[  165.427394] mlx5_core 0000:5c:00.0 beth1: Link up  \n[  166.479327] BUG: unable to handle page fault for address: 0000000800000010  \n[  166.494592] #PF: supervisor read access in kernel mode  \n[  166.505995] #PF: error_code(0x0000) - not-present page  \n...  \n[  166.816958] Call Trace:  \n[  166.822380]    \n[  166.827034]  ? __die_body+0x64/0xb0  \n[  166.834774]  ? page_fault_oops+0x2cd/0x3f0  \n[  166.843862]  ? exc_page_fault+0x63/0x130  \n[  166.852564]  ? asm_exc_page_fault+0x22/0x30  \n[  166.861843]  ? __kvmalloc_node_noprof+0x43/0xd0  \n[  166.871897]  ? get_partial_node+0x1c/0x320  \n[  166.880983]  ? deactivate_slab+0x269/0x2b0  \n[  166.890069]  ___slab_alloc+0x521/0xa90  \n[  166.898389]  ? __kvmalloc_node_noprof+0x43/0xd0  \n[  166.908442]  __kmalloc_node_noprof+0x216/0x3f0  \n[  166.918302]  ? __kvmalloc_node_noprof+0x43/0xd0  \n[  166.928354]  __kvmalloc_node_noprof+0x43/0xd0  \n[  166.938021]  mlx5e_open_channels+0x5e2/0xc00  \n[  166.947496]  mlx5e_open_locked+0x3e/0xf0  \n[  166.956201]  mlx5e_open+0x23/0x50  \n[  166.963551]  __dev_open+0x114/0x1c0  \n[  166.971292]  __dev_change_flags+0xa2/0x1b0  \n[  166.980378]  dev_change_flags+0x21/0x60  \n[  166.988887]  do_setlink+0x38d/0xf20  \n[  166.996628]  ? ep_poll_callback+0x1b9/0x240  \n[  167.005910]  ? __nla_validate_parse.llvm.10713395753544950386+0x80/0xd70  \n[  167.020782]  ? __wake_up_sync_key+0x52/0x80  \n[  167.030066]  ? __mutex_lock+0xff/0x550  \n[  167.038382]  ? security_capable+0x50/0x90  \n[  167.047279]  rtnl_setlink+0x1c9/0x210  \n[  167.055403]  ? ep_poll_callback+0x1b9/0x240  \n[  167.064684]  ? security_capable+0x50/0x90  \n[  167.073579]  rtnetlink_rcv_msg+0x2f9/0x310  \n[  167.082667]  ? rtnetlink_bind+0x30/0x30  \n[  167.091173]  netlink_rcv_skb+0xb1/0xe0  \n[  167.099492]  netlink_unicast+0x20f/0x2e0  \n[  167.108191]  netlink_sendmsg+0x389/0x420  \n[  167.116896]  __sys_sendto+0x158/0x1c0  \n[  167.125024]  __x64_sys_sendto+0x22/0x30  \n[  167.133534]  do_syscall_64+0x63/0x130  \n[  167.141657]  ? __irq_exit_rcu.llvm.17843942359718260576+0x52/0xd0  \n[  167.155181]  entry_SYSCALL_64_after_hwframe+0x4b/0x53 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T04:30:18.000000Z"}, {"uuid": "df8ca7e4-3e11-4971-a1c8-6c499db234e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-21711", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "871f7a42-a462-495d-a0b8-5c9dc138dc2d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-21712", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "387d8e37-d759-4300-843d-3a61e1eea760", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21719", "type": "seen", "source": "https://t.me/cvedetector/18994", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21719 - Linux Kernel IPMR Unres Entries Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21719 \nPublished : Feb. 27, 2025, 2:15 a.m. | 50\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nipmr: do not call mr_mfc_uses_dev() for unres entries  \n  \nsyzbot found that calling mr_mfc_uses_dev() for unres entries  \nwould crash [1], because c->mfc_un.res.minvif / c->mfc_un.res.maxvif  \nalias to \"struct sk_buff_head unresolved\", which contain two pointers.  \n  \nThis code never worked, lets remove it.  \n  \n[1]  \nUnable to handle kernel paging request at virtual address ffff5fff2d536613  \nKASAN: maybe wild-memory-access in range [0xfffefff96a9b3098-0xfffefff96a9b309f]  \nModules linked in:  \nCPU: 1 UID: 0 PID: 7321 Comm: syz.0.16 Not tainted 6.13.0-rc7-syzkaller-g1950a0af2d55 #0  \nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024  \npstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  \n pc : mr_mfc_uses_dev net/ipv4/ipmr_base.c:290 [inline]  \n pc : mr_table_dump+0x5a4/0x8b0 net/ipv4/ipmr_base.c:334  \n lr : mr_mfc_uses_dev net/ipv4/ipmr_base.c:289 [inline]  \n lr : mr_table_dump+0x694/0x8b0 net/ipv4/ipmr_base.c:334  \nCall trace:  \n  mr_mfc_uses_dev net/ipv4/ipmr_base.c:290 [inline] (P)  \n  mr_table_dump+0x5a4/0x8b0 net/ipv4/ipmr_base.c:334 (P)  \n  mr_rtm_dumproute+0x254/0x454 net/ipv4/ipmr_base.c:382  \n  ipmr_rtm_dumproute+0x248/0x4b4 net/ipv4/ipmr.c:2648  \n  rtnl_dump_all+0x2e4/0x4e8 net/core/rtnetlink.c:4327  \n  rtnl_dumpit+0x98/0x1d0 net/core/rtnetlink.c:6791  \n  netlink_dump+0x4f0/0xbc0 net/netlink/af_netlink.c:2317  \n  netlink_recvmsg+0x56c/0xe64 net/netlink/af_netlink.c:1973  \n  sock_recvmsg_nosec net/socket.c:1033 [inline]  \n  sock_recvmsg net/socket.c:1055 [inline]  \n  sock_read_iter+0x2d8/0x40c net/socket.c:1125  \n  new_sync_read fs/read_write.c:484 [inline]  \n  vfs_read+0x740/0x970 fs/read_write.c:565  \n  ksys_read+0x15c/0x26c fs/read_write.c:708 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T04:30:32.000000Z"}, {"uuid": "200d019a-8bf5-4bbb-b94e-87bd002a3b17", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21715", "type": "seen", "source": "https://t.me/cvedetector/18992", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21715 - \"Qualcomm Emac and Davicom DM9000 Linux Kernel UAF Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-21715 \nPublished : Feb. 27, 2025, 2:15 a.m. | 50\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: davicom: fix UAF in dm9000_drv_remove  \n  \ndm is netdev private data and it cannot be  \nused after free_netdev() call. Using dm after free_netdev()  \ncan cause UAF bug. Fix it by moving free_netdev() at the end of the  \nfunction.  \n  \nThis is similar to the issue fixed in commit  \nad297cd2db89 (\"net: qcom/emac: fix UAF in emac_remove\").  \n  \nThis bug is detected by our static analysis tool. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T04:30:30.000000Z"}, {"uuid": "406ddb9e-9bf1-473a-8e39-b38ba5a64a7c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21718", "type": "seen", "source": "https://t.me/cvedetector/18985", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21718 - Here is the title: \"Rose Linux Kernel Timer Use-After-Free Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-21718 \nPublished : Feb. 27, 2025, 2:15 a.m. | 50\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: rose: fix timer races against user threads  \n  \nRose timers only acquire the socket spinlock, without  \nchecking if the socket is owned by one user thread.  \n  \nAdd a check and rearm the timers if needed.  \n  \nBUG: KASAN: slab-use-after-free in rose_timer_expiry+0x31d/0x360 net/rose/rose_timer.c:174  \nRead of size 2 at addr ffff88802f09b82a by task swapper/0/0  \n  \nCPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.13.0-rc5-syzkaller-00172-gd1bf27c4e176 #0  \nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024  \nCall Trace:  \n   \n  __dump_stack lib/dump_stack.c:94 [inline]  \n  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120  \n  print_address_description mm/kasan/report.c:378 [inline]  \n  print_report+0x169/0x550 mm/kasan/report.c:489  \n  kasan_report+0x143/0x180 mm/kasan/report.c:602  \n  rose_timer_expiry+0x31d/0x360 net/rose/rose_timer.c:174  \n  call_timer_fn+0x187/0x650 kernel/time/timer.c:1793  \n  expire_timers kernel/time/timer.c:1844 [inline]  \n  __run_timers kernel/time/timer.c:2418 [inline]  \n  __run_timer_base+0x66a/0x8e0 kernel/time/timer.c:2430  \n  run_timer_base kernel/time/timer.c:2439 [inline]  \n  run_timer_softirq+0xb7/0x170 kernel/time/timer.c:2449  \n  handle_softirqs+0x2d4/0x9b0 kernel/softirq.c:561  \n  __do_softirq kernel/softirq.c:595 [inline]  \n  invoke_softirq kernel/softirq.c:435 [inline]  \n  __irq_exit_rcu+0xf7/0x220 kernel/softirq.c:662  \n  irq_exit_rcu+0x9/0x30 kernel/softirq.c:678  \n  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1049 [inline]  \n  sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1049 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T04:30:22.000000Z"}, {"uuid": "26fadf38-a7b3-4ec7-bffc-965151ee5c75", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21716", "type": "seen", "source": "https://t.me/cvedetector/18991", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21716 - Linux Kernel Vxlan Uninit-Value Access Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21716 \nPublished : Feb. 27, 2025, 2:15 a.m. | 50\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nvxlan: Fix uninit-value in vxlan_vnifilter_dump()  \n  \nKMSAN reported an uninit-value access in vxlan_vnifilter_dump() [1].  \n  \nIf the length of the netlink message payload is less than  \nsizeof(struct tunnel_msg), vxlan_vnifilter_dump() accesses bytes  \nbeyond the message. This can lead to uninit-value access. Fix this by  \nreturning an error in such situations.  \n  \n[1]  \nBUG: KMSAN: uninit-value in vxlan_vnifilter_dump+0x328/0x920 drivers/net/vxlan/vxlan_vnifilter.c:422  \n vxlan_vnifilter_dump+0x328/0x920 drivers/net/vxlan/vxlan_vnifilter.c:422  \n rtnl_dumpit+0xd5/0x2f0 net/core/rtnetlink.c:6786  \n netlink_dump+0x93e/0x15f0 net/netlink/af_netlink.c:2317  \n __netlink_dump_start+0x716/0xd60 net/netlink/af_netlink.c:2432  \n netlink_dump_start include/linux/netlink.h:340 [inline]  \n rtnetlink_dump_start net/core/rtnetlink.c:6815 [inline]  \n rtnetlink_rcv_msg+0x1256/0x14a0 net/core/rtnetlink.c:6882  \n netlink_rcv_skb+0x467/0x660 net/netlink/af_netlink.c:2542  \n rtnetlink_rcv+0x35/0x40 net/core/rtnetlink.c:6944  \n netlink_unicast_kernel net/netlink/af_netlink.c:1321 [inline]  \n netlink_unicast+0xed6/0x1290 net/netlink/af_netlink.c:1347  \n netlink_sendmsg+0x1092/0x1230 net/netlink/af_netlink.c:1891  \n sock_sendmsg_nosec net/socket.c:711 [inline]  \n __sock_sendmsg+0x330/0x3d0 net/socket.c:726  \n ____sys_sendmsg+0x7f4/0xb50 net/socket.c:2583  \n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2637  \n __sys_sendmsg net/socket.c:2669 [inline]  \n __do_sys_sendmsg net/socket.c:2674 [inline]  \n __se_sys_sendmsg net/socket.c:2672 [inline]  \n __x64_sys_sendmsg+0x211/0x3e0 net/socket.c:2672  \n x64_sys_call+0x3878/0x3d90 arch/x86/include/generated/asm/syscalls_64.h:47  \n do_syscall_x64 arch/x86/entry/common.c:52 [inline]  \n do_syscall_64+0xd9/0x1d0 arch/x86/entry/common.c:83  \n entry_SYSCALL_64_after_hwframe+0x77/0x7f  \n  \nUninit was created at:  \n slab_post_alloc_hook mm/slub.c:4110 [inline]  \n slab_alloc_node mm/slub.c:4153 [inline]  \n kmem_cache_alloc_node_noprof+0x800/0xe80 mm/slub.c:4205  \n kmalloc_reserve+0x13b/0x4b0 net/core/skbuff.c:587  \n __alloc_skb+0x347/0x7d0 net/core/skbuff.c:678  \n alloc_skb include/linux/skbuff.h:1323 [inline]  \n netlink_alloc_large_skb+0xa5/0x280 net/netlink/af_netlink.c:1196  \n netlink_sendmsg+0xac9/0x1230 net/netlink/af_netlink.c:1866  \n sock_sendmsg_nosec net/socket.c:711 [inline]  \n __sock_sendmsg+0x330/0x3d0 net/socket.c:726  \n ____sys_sendmsg+0x7f4/0xb50 net/socket.c:2583  \n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2637  \n __sys_sendmsg net/socket.c:2669 [inline]  \n __do_sys_sendmsg net/socket.c:2674 [inline]  \n __se_sys_sendmsg net/socket.c:2672 [inline]  \n __x64_sys_sendmsg+0x211/0x3e0 net/socket.c:2672  \n x64_sys_call+0x3878/0x3d90 arch/x86/include/generated/asm/syscalls_64.h:47  \n do_syscall_x64 arch/x86/entry/common.c:52 [inline]  \n do_syscall_64+0xd9/0x1d0 arch/x86/entry/common.c:83  \n entry_SYSCALL_64_after_hwframe+0x77/0x7f  \n  \nCPU: 0 UID: 0 PID: 30991 Comm: syz.4.10630 Not tainted 6.12.0-10694-gc44daa7e3c73 #29  \nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T04:30:30.000000Z"}, {"uuid": "da1c0a5e-63d5-4047-85f1-a755bb19fa3b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21714", "type": "seen", "source": "https://t.me/cvedetector/18990", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21714 - \"IBM mlx5 Use-After-Free Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-21714 \nPublished : Feb. 27, 2025, 2:15 a.m. | 50\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nRDMA/mlx5: Fix implicit ODP use after free  \n  \nPrevent double queueing of implicit ODP mr destroy work by using  \n__xa_cmpxchg() to make sure this is the only time we are destroying this  \nspecific mr.  \n  \nWithout this change, we could try to invalidate this mr twice, which in  \nturn could result in queuing a MR work destroy twice, and eventually the  \nsecond work could execute after the MR was freed due to the first work,  \ncausing a user after free and trace below.  \n  \n   refcount_t: underflow; use-after-free.  \n   WARNING: CPU: 2 PID: 12178 at lib/refcount.c:28 refcount_warn_saturate+0x12b/0x130  \n   Modules linked in: bonding ib_ipoib vfio_pci ip_gre geneve nf_tables ip6_gre gre ip6_tunnel tunnel6 ipip tunnel4 ib_umad rdma_ucm mlx5_vfio_pci vfio_pci_core vfio_iommu_type1 mlx5_ib vfio ib_uverbs mlx5_core iptable_raw openvswitch nsh rpcrdma ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_cm ib_core xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry overlay zram zsmalloc fuse [last unloaded: ib_uverbs]  \n   CPU: 2 PID: 12178 Comm: kworker/u20:5 Not tainted 6.5.0-rc1_net_next_mlx5_58c644e #1  \n   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014  \n   Workqueue: events_unbound free_implicit_child_mr_work [mlx5_ib]  \n   RIP: 0010:refcount_warn_saturate+0x12b/0x130  \n   Code: 48 c7 c7 38 95 2a 82 c6 05 bc c6 fe 00 01 e8 0c 66 aa ff 0f 0b 5b c3 48 c7 c7 e0 94 2a 82 c6 05 a7 c6 fe 00 01 e8 f5 65 aa ff <0f0b 5b c3 90 8b 07 3d 00 00 00 c0 74 12 83 f8 01 74 13 8d 50 ff  \n   RSP: 0018:ffff8881008e3e40 EFLAGS: 00010286  \n   RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027  \n   RDX: ffff88852c91b5c8 RSI: 0000000000000001 RDI: ffff88852c91b5c0  \n   RBP: ffff8881dacd4e00 R08: 00000000ffffffff R09: 0000000000000019  \n   R10: 000000000000072e R11: 0000000063666572 R12: ffff88812bfd9e00  \n   R13: ffff8881c792d200 R14: ffff88810011c005 R15: ffff8881002099c0  \n   FS:  0000000000000000(0000) GS:ffff88852c900000(0000) knlGS:0000000000000000  \n   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \n   CR2: 00007f5694b5e000 CR3: 00000001153f6003 CR4: 0000000000370ea0  \n   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \n   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \n   Call Trace:  \n      \n    ? refcount_warn_saturate+0x12b/0x130  \n    free_implicit_child_mr_work+0x180/0x1b0 [mlx5_ib]  \n    process_one_work+0x1cc/0x3c0  \n    worker_thread+0x218/0x3c0  \n    kthread+0xc6/0xf0  \n    ret_from_fork+0x1f/0x30 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T04:30:29.000000Z"}, {"uuid": "53a9b775-1ab1-4308-b3ba-bbd682f744f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21715", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/5642", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21715\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: davicom: fix UAF in dm9000_drv_remove\n\ndm is netdev private data and it cannot be\nused after free_netdev() call. Using dm after free_netdev()\ncan cause UAF bug. Fix it by moving free_netdev() at the end of the\nfunction.\n\nThis is similar to the issue fixed in commit\nad297cd2db89 (\"net: qcom/emac: fix UAF in emac_remove\").\n\nThis bug is detected by our static analysis tool.\n\ud83d\udccf Published: 2025-02-27T02:07:26.174Z\n\ud83d\udccf Modified: 2025-02-27T02:07:26.174Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/c94ab07edc2843e2f3d46dbd82e5c681503aaadf\n2. https://git.kernel.org/stable/c/c411f9a5fdc9158e8f7c57eac961d3df3eb4d8ca\n3. https://git.kernel.org/stable/c/5a54367a7c2378c65aaa4d3cfd952f26adef7aa7\n4. https://git.kernel.org/stable/c/2013c95df6752d9c88221d0f0f37b6f197969390\n5. https://git.kernel.org/stable/c/19e65c45a1507a1a2926649d2db3583ed9d55fd9", "creation_timestamp": "2025-02-27T02:25:29.000000Z"}, {"uuid": "bfda266b-0ad2-4018-a89e-26b04b5a8037", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21716", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/5641", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21716\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: Fix uninit-value in vxlan_vnifilter_dump()\n\nKMSAN reported an uninit-value access in vxlan_vnifilter_dump() [1].\n\nIf the length of the netlink message payload is less than\nsizeof(struct tunnel_msg), vxlan_vnifilter_dump() accesses bytes\nbeyond the message. This can lead to uninit-value access. Fix this by\nreturning an error in such situations.\n\n[1]\nBUG: KMSAN: uninit-value in vxlan_vnifilter_dump+0x328/0x920 drivers/net/vxlan/vxlan_vnifilter.c:422\n vxlan_vnifilter_dump+0x328/0x920 drivers/net/vxlan/vxlan_vnifilter.c:422\n rtnl_dumpit+0xd5/0x2f0 net/core/rtnetlink.c:6786\n netlink_dump+0x93e/0x15f0 net/netlink/af_netlink.c:2317\n __netlink_dump_start+0x716/0xd60 net/netlink/af_netlink.c:2432\n netlink_dump_start include/linux/netlink.h:340 [inline]\n rtnetlink_dump_start net/core/rtnetlink.c:6815 [inline]\n rtnetlink_rcv_msg+0x1256/0x14a0 net/core/rtnetlink.c:6882\n netlink_rcv_skb+0x467/0x660 net/netlink/af_netlink.c:2542\n rtnetlink_rcv+0x35/0x40 net/core/rtnetlink.c:6944\n netlink_unicast_kernel net/netlink/af_netlink.c:1321 [inline]\n netlink_unicast+0xed6/0x1290 net/netlink/af_netlink.c:1347\n netlink_sendmsg+0x1092/0x1230 net/netlink/af_netlink.c:1891\n sock_sendmsg_nosec net/socket.c:711 [inline]\n __sock_sendmsg+0x330/0x3d0 net/socket.c:726\n ____sys_sendmsg+0x7f4/0xb50 net/socket.c:2583\n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2637\n __sys_sendmsg net/socket.c:2669 [inline]\n __do_sys_sendmsg net/socket.c:2674 [inline]\n __se_sys_sendmsg net/socket.c:2672 [inline]\n __x64_sys_sendmsg+0x211/0x3e0 net/socket.c:2672\n x64_sys_call+0x3878/0x3d90 arch/x86/include/generated/asm/syscalls_64.h:47\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xd9/0x1d0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n slab_post_alloc_hook mm/slub.c:4110 [inline]\n slab_alloc_node mm/slub.c:4153 [inline]\n kmem_cache_alloc_node_noprof+0x800/0xe80 mm/slub.c:4205\n kmalloc_reserve+0x13b/0x4b0 net/core/skbuff.c:587\n __alloc_skb+0x347/0x7d0 net/core/skbuff.c:678\n alloc_skb include/linux/skbuff.h:1323 [inline]\n netlink_alloc_large_skb+0xa5/0x280 net/netlink/af_netlink.c:1196\n netlink_sendmsg+0xac9/0x1230 net/netlink/af_netlink.c:1866\n sock_sendmsg_nosec net/socket.c:711 [inline]\n __sock_sendmsg+0x330/0x3d0 net/socket.c:726\n ____sys_sendmsg+0x7f4/0xb50 net/socket.c:2583\n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2637\n __sys_sendmsg net/socket.c:2669 [inline]\n __do_sys_sendmsg net/socket.c:2674 [inline]\n __se_sys_sendmsg net/socket.c:2672 [inline]\n __x64_sys_sendmsg+0x211/0x3e0 net/socket.c:2672\n x64_sys_call+0x3878/0x3d90 arch/x86/include/generated/asm/syscalls_64.h:47\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xd9/0x1d0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 0 UID: 0 PID: 30991 Comm: syz.4.10630 Not tainted 6.12.0-10694-gc44daa7e3c73 #29\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014\n\ud83d\udccf Published: 2025-02-27T02:07:26.779Z\n\ud83d\udccf Modified: 2025-02-27T02:07:26.779Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/cb1de9309a48cc5b771115781eec05075fd67039\n2. https://git.kernel.org/stable/c/a84d511165d6ba7f331b90ae6b6ce180ec534daa\n3. https://git.kernel.org/stable/c/f554bce488605d2f70e06eeab5e4d2448c813713\n4. https://git.kernel.org/stable/c/1693d1fade71646a0731b6b213298cb443d186ea\n5. https://git.kernel.org/stable/c/5066293b9b7046a906eff60e3949a887ae185a43", "creation_timestamp": "2025-02-27T02:25:28.000000Z"}, {"uuid": "e60eb876-f5f6-4b79-81cd-96e4670c7e1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21711", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/5643", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21711\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet/rose: prevent integer overflows in rose_setsockopt()\n\nIn case of possible unpredictably large arguments passed to\nrose_setsockopt() and multiplied by extra values on top of that,\ninteger overflows may occur.\n\nDo the safest minimum and fix these issues by checking the\ncontents of 'opt' and returning -EINVAL if they are too large. Also,\nswitch to unsigned int and remove useless check for negative 'opt'\nin ROSE_IDLE case.\n\ud83d\udccf Published: 2025-02-27T02:07:23.746Z\n\ud83d\udccf Modified: 2025-02-27T02:07:23.746Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/9bdee49ad6bbd26ab5e13cc6731e54fb1b6c1dca\n2. https://git.kernel.org/stable/c/352daa50946c3bbb662432e8daf54d6760796589\n3. https://git.kernel.org/stable/c/d08f4074f9c69f7e95502587eb1b258a965ba7f0\n4. https://git.kernel.org/stable/c/e5338930a29d0ab2a5af402f5f664aeba0d1a676\n5. https://git.kernel.org/stable/c/d640627663bfe7d8963c7615316d7d4ef60f3b0b", "creation_timestamp": "2025-02-27T02:25:31.000000Z"}, {"uuid": "4965c0ad-0a8b-4041-87a0-9a80e70f533f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21719", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/5640", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21719\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nipmr: do not call mr_mfc_uses_dev() for unres entries\n\nsyzbot found that calling mr_mfc_uses_dev() for unres entries\nwould crash [1], because c->mfc_un.res.minvif / c->mfc_un.res.maxvif\nalias to \"struct sk_buff_head unresolved\", which contain two pointers.\n\nThis code never worked, lets remove it.\n\n[1]\nUnable to handle kernel paging request at virtual address ffff5fff2d536613\nKASAN: maybe wild-memory-access in range [0xfffefff96a9b3098-0xfffefff96a9b309f]\nModules linked in:\nCPU: 1 UID: 0 PID: 7321 Comm: syz.0.16 Not tainted 6.13.0-rc7-syzkaller-g1950a0af2d55 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024\npstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : mr_mfc_uses_dev net/ipv4/ipmr_base.c:290 [inline]\n pc : mr_table_dump+0x5a4/0x8b0 net/ipv4/ipmr_base.c:334\n lr : mr_mfc_uses_dev net/ipv4/ipmr_base.c:289 [inline]\n lr : mr_table_dump+0x694/0x8b0 net/ipv4/ipmr_base.c:334\nCall trace:\n  mr_mfc_uses_dev net/ipv4/ipmr_base.c:290 [inline] (P)\n  mr_table_dump+0x5a4/0x8b0 net/ipv4/ipmr_base.c:334 (P)\n  mr_rtm_dumproute+0x254/0x454 net/ipv4/ipmr_base.c:382\n  ipmr_rtm_dumproute+0x248/0x4b4 net/ipv4/ipmr.c:2648\n  rtnl_dump_all+0x2e4/0x4e8 net/core/rtnetlink.c:4327\n  rtnl_dumpit+0x98/0x1d0 net/core/rtnetlink.c:6791\n  netlink_dump+0x4f0/0xbc0 net/netlink/af_netlink.c:2317\n  netlink_recvmsg+0x56c/0xe64 net/netlink/af_netlink.c:1973\n  sock_recvmsg_nosec net/socket.c:1033 [inline]\n  sock_recvmsg net/socket.c:1055 [inline]\n  sock_read_iter+0x2d8/0x40c net/socket.c:1125\n  new_sync_read fs/read_write.c:484 [inline]\n  vfs_read+0x740/0x970 fs/read_write.c:565\n  ksys_read+0x15c/0x26c fs/read_write.c:708\n\ud83d\udccf Published: 2025-02-27T02:07:28.573Z\n\ud83d\udccf Modified: 2025-02-27T02:07:28.573Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/57177c5f47a8da852f8d76cf6945cf803f8bb9e5\n2. https://git.kernel.org/stable/c/b379b3162ff55a70464c6a934ae9bf0497478a62\n3. https://git.kernel.org/stable/c/a099834a51ccf9bbba3de86a251b3433539abfde\n4. https://git.kernel.org/stable/c/26bb7d991f04eeef47dfad23e533834995c26f7a\n5. https://git.kernel.org/stable/c/15a901361ec3fb1c393f91880e1cbf24ec0a88bd", "creation_timestamp": "2025-02-27T02:25:26.000000Z"}, {"uuid": "ea05a409-c266-4851-88c1-23144bf6ff8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2171", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/19213", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-2171\n\ud83d\udd25 CVSS Score: 8.8 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:H/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: Aviatrix Controller versions prior to 7.1.4208, 7.2.5090, and 8.0.0 do not enforce rate limiting on password reset attempts, allowing adversaries to brute force guess the 6-digit password reset PIN\n\ud83d\udccf Published: 2025-06-23T14:01:07.690Z\n\ud83d\udccf Modified: 2025-06-23T14:01:07.690Z\n\ud83d\udd17 References:\n1. https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2025/MNDT-2025-0003.md\n2. https://cloud.google.com/blog/topics/threat-intelligence/remote-code-execution-aviatrix-controller", "creation_timestamp": "2025-06-23T14:45:35.000000Z"}, {"uuid": "1d00c5e7-1c6a-4359-a26c-dc51f872fa91", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2171", "type": "published-proof-of-concept", "source": "Telegram/S7RPzkaVu9rMwdZrCAlLyJw5bBMvrbhCFuoMTi2UNDrM6ko", "content": "", "creation_timestamp": "2025-06-23T15:31:00.000000Z"}, {"uuid": "34b74789-610b-47f5-9e46-71644db48d93", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21711", "type": "seen", "source": "Telegram/_1HXxncZJ4Dq8KnPdt_mdR1JDgyUZQZFMh1c-fdqIkEGTUrE", "content": "", "creation_timestamp": "2025-03-08T04:34:56.000000Z"}]}