https://vulnerability.circl.lu/sightings/feed 2026-05-05T23:13:37.129312+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/260d1ddc-0cbd-4f40-946a-4ec544fe1d23/export 2026-05-05T23:13:37.505199+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "260d1ddc-0cbd-4f40-946a-4ec544fe1d23", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-49918", "type": "seen", "source": "https://t.me/cvedetector/24248", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-49918 - Linux Kernel ipvs proc_entry Double Free\", \n \"Content\": \"CVE ID : CVE-2022-49918 \nPublished : May 1, 2025, 3:16 p.m. | 1\u00a0hour, 9\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nipvs: fix WARNING in __ip_vs_cleanup_batch() \n \nDuring the initialization of ip_vs_conn_net_init(), if file ip_vs_conn \nor ip_vs_conn_sync fails to be created, the initialization is successful \nby default. Therefore, the ip_vs_conn or ip_vs_conn_sync file doesn't \nbe found during the remove. \n \nThe following is the stack information: \nname 'ip_vs_conn_sync' \nWARNING: CPU: 3 PID: 9 at fs/proc/generic.c:712 \nremove_proc_entry+0x389/0x460 \nModules linked in: \nWorkqueue: netns cleanup_net \nRIP: 0010:remove_proc_entry+0x389/0x460 \nCall Trace: \n \n__ip_vs_cleanup_batch+0x7d/0x120 \nops_exit_list+0x125/0x170 \ncleanup_net+0x4ea/0xb00 \nprocess_one_work+0x9bf/0x1710 \nworker_thread+0x665/0x1080 \nkthread+0x2e4/0x3a0 \nret_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\": \"01 May 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T19:01:41.000000Z"} 2025-05-01T19:01:41+00:00