{"vulnerability": "CVE-2025-2179", "sightings": [{"uuid": "3efbe5d5-5e24-4bfd-b5d3-c75dd2bcaf6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21797", "type": "seen", "source": "https://bsky.app/profile/omo.bsky.social/post/3ljo4dkyf7k2l", "content": "", "creation_timestamp": "2025-03-05T23:16:11.380672Z"}, {"uuid": "022deca3-d098-4d94-bbfb-148e1cdb4dda", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21796", "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": "16aecbb4-1e28-4397-a2da-e38f4c7535f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21795", "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": "6e6b8764-3fca-4e1e-8a17-b3c0691fccb8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2179", "type": "seen", "source": "https://security.paloaltonetworks.com/CVE-2025-2179", "content": "", "creation_timestamp": "2025-07-28T17:00:00.000000Z"}, {"uuid": "3b56b145-7db9-4447-a792-a918d58855ba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21791", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lwbhky6biw2y", "content": "", "creation_timestamp": "2025-08-13T09:00:04.953229Z"}, {"uuid": "8d36ac59-79ce-4c66-87cb-100c2807ad3a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2179", "type": "seen", "source": "https://bsky.app/profile/ripjyr.bsky.social/post/3lv2pa6kstg27", "content": "", "creation_timestamp": "2025-07-28T23:03:21.652878Z"}, {"uuid": "9a479ab4-4b1d-44cb-994a-2788e7f3a5d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2179", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3lvrnb7vn4224", "content": "", "creation_timestamp": "2025-08-07T01:59:23.727952Z"}, {"uuid": "8b8a2204-30a6-46c0-8d62-09a1ec3eecc5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21796", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lwbhky6biw2y", "content": "", "creation_timestamp": "2025-08-13T09:00:05.030992Z"}, {"uuid": "c65e7ddb-b920-41a3-b3da-e89d1dcf9203", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21799", "type": "seen", "source": "MISP/24306fae-b16b-4478-9297-d2973cdb583c", "content": "", "creation_timestamp": "2025-08-22T14:52:22.000000Z"}, {"uuid": "097a385d-2444-46eb-a948-61ec76324e6c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-21792", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "008e9831-7d7c-4d96-a0d8-2b0f5a952fe3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-21792", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "0dbbc095-3bec-49a8-bd37-cec10e7849e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-21796", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "73e75485-e18e-45f3-b8c3-3d8ce193ec8a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21797", "type": "seen", "source": "https://t.me/cvedetector/19003", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21797 - Corsair Void Linux Kernel Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21797 \nPublished : Feb. 27, 2025, 3:15 a.m. | 1\u00a0hour, 54\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nHID: corsair-void: Add missing delayed work cancel for headset status  \n  \nThe cancel_delayed_work_sync() call was missed, causing a use-after-free  \nin corsair_void_remove(). \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-27T06:11:26.000000Z"}, {"uuid": "5e1858ca-7bc2-4c25-8299-e2ca631b8685", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21795", "type": "seen", "source": "https://t.me/cvedetector/19002", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21795 - Linux Kernel NFS Server RPC Callback Hang Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21795 \nPublished : Feb. 27, 2025, 3:15 a.m. | 1\u00a0hour, 54\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nNFSD: fix hang in nfsd4_shutdown_callback  \n  \nIf nfs4_client is in courtesy state then there is no point to send  \nthe callback. This causes nfsd4_shutdown_callback to hang since  \ncl_cb_inflight is not 0. This hang lasts about 15 minutes until TCP  \nnotifies NFSD that the connection was dropped.  \n  \nThis patch modifies nfsd4_run_cb_work to skip the RPC call if  \nnfs4_client is in courtesy state. \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-27T06:11:23.000000Z"}, {"uuid": "552f58ca-0efc-4536-8a9b-2c957538fc14", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21794", "type": "seen", "source": "https://t.me/cvedetector/19001", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21794 - Thrustmaster HID Stack-Based Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2025-21794 \nPublished : Feb. 27, 2025, 3:15 a.m. | 1\u00a0hour, 54\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nHID: hid-thrustmaster: fix stack-out-of-bounds read in usb_check_int_endpoints()  \n  \nSyzbot[1] has detected a stack-out-of-bounds read of the ep_addr array from  \nhid-thrustmaster driver. This array is passed to usb_check_int_endpoints  \nfunction from usb.c core driver, which executes a for loop that iterates  \nover the elements of the passed array. Not finding a null element at the end of  \nthe array, it tries to read the next, non-existent element, crashing the kernel.  \n  \nTo fix this, a 0 element was added at the end of the array to break the for  \nloop.  \n  \n[1]  \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-27T06:11:22.000000Z"}, {"uuid": "d29b5cf6-6ffe-4cac-9c85-e2fda799d5c7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21796", "type": "seen", "source": "https://t.me/cvedetector/18999", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21796 - Linux Kernel NFSd Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21796 \nPublished : Feb. 27, 2025, 3:15 a.m. | 1\u00a0hour, 54\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnfsd: clear acl_access/acl_default after releasing them  \n  \nIf getting acl_default fails, acl_access and acl_default will be released  \nsimultaneously. However, acl_access will still retain a pointer pointing  \nto the released posix_acl, which will trigger a WARNING in  \nnfs3svc_release_getacl like this:  \n  \n------------[ cut here ]------------  \nrefcount_t: underflow; use-after-free.  \nWARNING: CPU: 26 PID: 3199 at lib/refcount.c:28  \nrefcount_warn_saturate+0xb5/0x170  \nModules linked in:  \nCPU: 26 UID: 0 PID: 3199 Comm: nfsd Not tainted  \n6.12.0-rc6-00079-g04ae226af01f-dirty #8  \nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS  \n1.16.1-2.fc37 04/01/2014  \nRIP: 0010:refcount_warn_saturate+0xb5/0x170  \nCode: cc cc 0f b6 1d b3 20 a5 03 80 fb 01 0f 87 65 48 d8 00 83 e3 01 75  \ne4 48 c7 c7 c0 3b 9b 85 c6 05 97 20 a5 03 01 e8 fb 3e 30 ff <0f0b eb  \ncd 0f b6 1d 8a3  \nRSP: 0018:ffffc90008637cd8 EFLAGS: 00010282  \nRAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff83904fde  \nRDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff88871ed36380  \nRBP: ffff888158beeb40 R08: 0000000000000001 R09: fffff520010c6f56  \nR10: ffffc90008637ab7 R11: 0000000000000001 R12: 0000000000000001  \nR13: ffff888140e77400 R14: ffff888140e77408 R15: ffffffff858b42c0  \nFS:  0000000000000000(0000) GS:ffff88871ed00000(0000)  \nknlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 0000562384d32158 CR3: 000000055cc6a000 CR4: 00000000000006f0  \nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \nCall Trace:  \n   \n ? refcount_warn_saturate+0xb5/0x170  \n ? __warn+0xa5/0x140  \n ? refcount_warn_saturate+0xb5/0x170  \n ? report_bug+0x1b1/0x1e0  \n ? handle_bug+0x53/0xa0  \n ? exc_invalid_op+0x17/0x40  \n ? asm_exc_invalid_op+0x1a/0x20  \n ? tick_nohz_tick_stopped+0x1e/0x40  \n ? refcount_warn_saturate+0xb5/0x170  \n ? refcount_warn_saturate+0xb5/0x170  \n nfs3svc_release_getacl+0xc9/0xe0  \n svc_process_common+0x5db/0xb60  \n ? __pfx_svc_process_common+0x10/0x10  \n ? __rcu_read_unlock+0x69/0xa0  \n ? __pfx_nfsd_dispatch+0x10/0x10  \n ? svc_xprt_received+0xa1/0x120  \n ? xdr_init_decode+0x11d/0x190  \n svc_process+0x2a7/0x330  \n svc_handle_xprt+0x69d/0x940  \n svc_recv+0x180/0x2d0  \n nfsd+0x168/0x200  \n ? __pfx_nfsd+0x10/0x10  \n kthread+0x1a2/0x1e0  \n ? kthread+0xf4/0x1e0  \n ? __pfx_kthread+0x10/0x10  \n ret_from_fork+0x34/0x60  \n ? __pfx_kthread+0x10/0x10  \n ret_from_fork_asm+0x1a/0x30  \n   \nKernel panic - not syncing: kernel: panic_on_warn set ...  \n  \nClear acl_access/acl_default after posix_acl_release is called to prevent  \nUAF from being triggered. \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-27T06:11:20.000000Z"}, {"uuid": "2443ccf5-2af0-48cf-9a84-69ded62068cc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21792", "type": "seen", "source": "https://t.me/cvedetector/18998", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21792 - Linux Kernel AX25 SO_BINDTODEVICE Refcount Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21792 \nPublished : Feb. 27, 2025, 3:15 a.m. | 1\u00a0hour, 54\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nax25: Fix refcount leak caused by setting SO_BINDTODEVICE sockopt  \n  \nIf an AX25 device is bound to a socket by setting the SO_BINDTODEVICE  \nsocket option, a refcount leak will occur in ax25_release().  \n  \nCommit 9fd75b66b8f6 (\"ax25: Fix refcount leaks caused by ax25_cb_del()\")  \nadded decrement of device refcounts in ax25_release(). In order for that  \nto work correctly the refcounts must already be incremented when the  \ndevice is bound to the socket. An AX25 device can be bound to a socket  \nby either calling ax25_bind() or setting SO_BINDTODEVICE socket option.  \nIn both cases the refcounts should be incremented, but in fact it is done  \nonly in ax25_bind().  \n  \nThis bug leads to the following issue reported by Syzkaller:  \n  \n================================================================  \nrefcount_t: decrement hit 0; leaking memory.  \nWARNING: CPU: 1 PID: 5932 at lib/refcount.c:31 refcount_warn_saturate+0x1ed/0x210 lib/refcount.c:31  \nModules linked in:  \nCPU: 1 UID: 0 PID: 5932 Comm: syz-executor424 Not tainted 6.13.0-rc4-syzkaller-00110-g4099a71718b0 #0  \nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014  \nRIP: 0010:refcount_warn_saturate+0x1ed/0x210 lib/refcount.c:31  \nCall Trace:  \n   \n __refcount_dec include/linux/refcount.h:336 [inline]  \n refcount_dec include/linux/refcount.h:351 [inline]  \n ref_tracker_free+0x710/0x820 lib/ref_tracker.c:236  \n netdev_tracker_free include/linux/netdevice.h:4156 [inline]  \n netdev_put include/linux/netdevice.h:4173 [inline]  \n netdev_put include/linux/netdevice.h:4169 [inline]  \n ax25_release+0x33f/0xa10 net/ax25/af_ax25.c:1069  \n __sock_release+0xb0/0x270 net/socket.c:640  \n sock_close+0x1c/0x30 net/socket.c:1408  \n ...  \n do_syscall_x64 arch/x86/entry/common.c:52 [inline]  \n do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83  \n entry_SYSCALL_64_after_hwframe+0x77/0x7f  \n ...  \n   \n================================================================  \n  \nFix the implementation of ax25_setsockopt() by adding increment of  \nrefcounts for the new device bound, and decrement of refcounts for  \nthe old unbound device. \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-27T06:11:20.000000Z"}, {"uuid": "cbfd56fc-5785-4d0a-b7b9-9871da9d933c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21793", "type": "seen", "source": "https://t.me/cvedetector/19000", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21793 - Linux Kernel SPI Division By Zero Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21793 \nPublished : Feb. 27, 2025, 3:15 a.m. | 1\u00a0hour, 54\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nspi: sn-f-ospi: Fix division by zero  \n  \nWhen there is no dummy cycle in the spi-nor commands, both dummy bus cycle  \nbytes and width are zero. Because of the cpu's warning when divided by  \nzero, the warning should be avoided. Return just zero to avoid such  \ncalculations. \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-27T06:11:21.000000Z"}, {"uuid": "a08b9b3b-6552-4dad-8c45-eefbcb9469fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21791", "type": "seen", "source": "https://t.me/cvedetector/19011", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21791 - Linux Kernel RCU Protection Vulnerability in VRF l3mdev_l3_out()\", \n  \"Content\": \"CVE ID : CVE-2025-21791 \nPublished : Feb. 27, 2025, 3:15 a.m. | 1\u00a0hour, 54\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nvrf: use RCU protection in l3mdev_l3_out()  \n  \nl3mdev_l3_out() can be called without RCU being held:  \n  \nraw_sendmsg()  \n ip_push_pending_frames()  \n  ip_send_skb()  \n   ip_local_out()  \n    __ip_local_out()  \n     l3mdev_ip_out()  \n  \nAdd rcu_read_lock() / rcu_read_unlock() pair to avoid  \na potential UAF. \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-27T06:11:35.000000Z"}, {"uuid": "307d695d-91af-4290-87dd-905b7ac8a93c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21790", "type": "seen", "source": "https://t.me/cvedetector/19010", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21790 - Linux Kernel Vxlan Null Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2025-21790 \nPublished : Feb. 27, 2025, 3:15 a.m. | 1\u00a0hour, 54\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nvxlan: check vxlan_vnigroup_init() return value  \n  \nvxlan_init() must check vxlan_vnigroup_init() success  \notherwise a crash happens later, spotted by syzbot.  \n  \nOops: general protection fault, probably for non-canonical address 0xdffffc000000002c: 0000 [#1] PREEMPT SMP KASAN NOPTI  \nKASAN: null-ptr-deref in range [0x0000000000000160-0x0000000000000167]  \nCPU: 0 UID: 0 PID: 7313 Comm: syz-executor147 Not tainted 6.14.0-rc1-syzkaller-00276-g69b54314c975 #0  \nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014  \n RIP: 0010:vxlan_vnigroup_uninit+0x89/0x500 drivers/net/vxlan/vxlan_vnifilter.c:912  \nCode: 00 48 8b 44 24 08 4c 8b b0 98 41 00 00 49 8d 86 60 01 00 00 48 89 c2 48 89 44 24 10 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <803c 02 00 0f 85 4d 04 00 00 49 8b 86 60 01 00 00 48 ba 00 00 00  \nRSP: 0018:ffffc9000cc1eea8 EFLAGS: 00010202  \nRAX: dffffc0000000000 RBX: 0000000000000001 RCX: ffffffff8672effb  \nRDX: 000000000000002c RSI: ffffffff8672ecb9 RDI: ffff8880461b4f18  \nRBP: ffff8880461b4ef4 R08: 0000000000000001 R09: 0000000000000000  \nR10: 0000000000000001 R11: 0000000000000000 R12: 0000000000020000  \nR13: ffff8880461b0d80 R14: 0000000000000000 R15: dffffc0000000000  \nFS:  00007fecfa95d6c0(0000) GS:ffff88806a600000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 00007fecfa95cfb8 CR3: 000000004472c000 CR4: 0000000000352ef0  \nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \nCall Trace:  \n   \n  vxlan_uninit+0x1ab/0x200 drivers/net/vxlan/vxlan_core.c:2942  \n  unregister_netdevice_many_notify+0x12d6/0x1f30 net/core/dev.c:11824  \n  unregister_netdevice_many net/core/dev.c:11866 [inline]  \n  unregister_netdevice_queue+0x307/0x3f0 net/core/dev.c:11736  \n  register_netdevice+0x1829/0x1eb0 net/core/dev.c:10901  \n  __vxlan_dev_create+0x7c6/0xa30 drivers/net/vxlan/vxlan_core.c:3981  \n  vxlan_newlink+0xd1/0x130 drivers/net/vxlan/vxlan_core.c:4407  \n  rtnl_newlink_create net/core/rtnetlink.c:3795 [inline]  \n  __rtnl_newlink net/core/rtnetlink.c:3906 [inline] \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-27T06:11:34.000000Z"}]}