{"vulnerability": "CVE-2021-47671", "sightings": [{"uuid": "0c1fb941-5907-486e-b591-62596d584de8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-47671", "type": "seen", "source": "https://t.me/cvedetector/23279", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2021-47671 - Canal (CAN) Linux Kernel Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2021-47671 \nPublished : April 17, 2025, 6:15 p.m. | 2\u00a0hours, 7\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncan: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path  \n  \nIn es58x_rx_err_msg(), if can-&gt;do_set_mode() fails, the function  \ndirectly returns without calling netif_rx(skb). This means that the  \nskb previously allocated by alloc_can_err_skb() is not freed. In other  \nterms, this is a memory leak.  \n  \nThis patch simply removes the return statement in the error branch and  \nlet the function continue.  \n  \nIssue was found with GCC -fanalyzer, please follow the link below for  \ndetails. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T23:01:22.000000Z"}, {"uuid": "4901144f-c63e-4ff3-92a8-349bbec05cb4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-47671", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12328", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2021-47671\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncan: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path\n\nIn es58x_rx_err_msg(), if can-&gt;do_set_mode() fails, the function\ndirectly returns without calling netif_rx(skb). This means that the\nskb previously allocated by alloc_can_err_skb() is not freed. In other\nterms, this is a memory leak.\n\nThis patch simply removes the return statement in the error branch and\nlet the function continue.\n\nIssue was found with GCC -fanalyzer, please follow the link below for\ndetails.\n\ud83d\udccf Published: 2025-04-17T18:01:31.459Z\n\ud83d\udccf Modified: 2025-04-17T19:49:36.575Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4f389e1276a5389c92cef860c9fde8e1c802a871\n2. https://git.kernel.org/stable/c/7eb0881aec26099089f12ae850aebd93190b1dfe\n3. https://git.kernel.org/stable/c/d9447f768bc8c60623e4bb3ce65b8f4654d33a50", "creation_timestamp": "2025-04-17T19:58:00.000000Z"}, {"uuid": "b2fae32b-2973-4119-b04e-eac07886ed8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-47671", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lmzrqyzvbs2b", "content": "", "creation_timestamp": "2025-04-17T18:54:25.635998Z"}]}