{"vulnerability": "CVE-2025-22005", "sightings": [{"uuid": "5b6900d7-5ac1-4787-a733-6d48b83fdbb4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22005", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3llvrfe6gl326", "content": "", "creation_timestamp": "2025-04-03T11:12:07.038591Z"}, {"uuid": "a045d18f-0e2a-4159-9fa7-70a397ac56b4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22005", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10178", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22005\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().\n\nfib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything\nwhen it fails.\n\nCommit 7dd73168e273 (\"ipv6: Always allocate pcpu memory in a fib6_nh\")\nmoved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()\nbut forgot to add cleanup for fib6_nh->nh_common.nhc_pcpu_rth_output in\ncase it fails to allocate fib6_nh->rt6i_pcpu, resulting in memleak.\n\nLet's call fib_nh_common_release() and clear nhc_pcpu_rth_output in the\nerror path.\n\nNote that we can remove the fib6_nh_release() call in nh_create_ipv6()\nlater in net-next.git.\n\ud83d\udccf Published: 2025-04-03T07:19:06.716Z\n\ud83d\udccf Modified: 2025-04-03T07:19:06.716Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/77c41cdbe6bce476e08d3251c0d501feaf10a9f3\n2. https://git.kernel.org/stable/c/119dcafe36795a15ae53351cbbd6177aaf94ffef\n3. https://git.kernel.org/stable/c/29d91820184d5cbc70f3246d4911d96eaeb930d6\n4. https://git.kernel.org/stable/c/d3d5b4b5ae263c3225db363ba08b937e2e2b0380\n5. https://git.kernel.org/stable/c/9740890ee20e01f99ff1dde84c63dcf089fabb98", "creation_timestamp": "2025-04-03T07:34:09.000000Z"}, {"uuid": "6007499f-d777-430f-a3c5-4a4eec2cd221", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22005", "type": "seen", "source": "https://t.me/cvedetector/21951", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22005 - Linux Kernel IPv6 Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22005 \nPublished : April 3, 2025, 8:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().  \n  \nfib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything  \nwhen it fails.  \n  \nCommit 7dd73168e273 (\"ipv6: Always allocate pcpu memory in a fib6_nh\")  \nmoved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()  \nbut forgot to add cleanup for fib6_nh->nh_common.nhc_pcpu_rth_output in  \ncase it fails to allocate fib6_nh->rt6i_pcpu, resulting in memleak.  \n  \nLet's call fib_nh_common_release() and clear nhc_pcpu_rth_output in the  \nerror path.  \n  \nNote that we can remove the fib6_nh_release() call in nh_create_ipv6()  \nlater in net-next.git. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T11:03:06.000000Z"}]}