https://vulnerability.circl.lu/sightings/feed 2026-05-07T04:44:02.325573+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/44668d9f-c805-4f3f-aab4-fb1a5e209293/export 2026-05-07T04:44:02.725621+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "44668d9f-c805-4f3f-aab4-fb1a5e209293", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-46784", "type": "seen", "source": "https://t.me/cvedetector/5946", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46784 - Intel Mana NAPI Race Condition Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-46784 \nPublished : Sept. 18, 2024, 8:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup \n \nCurrently napi_disable() gets called during rxq and txq cleanup, \neven before napi is enabled and hrtimer is initialized. It causes \nkernel panic. \n \n? page_fault_oops+0x136/0x2b0 \n ? page_counter_cancel+0x2e/0x80 \n ? do_user_addr_fault+0x2f2/0x640 \n ? refill_obj_stock+0xc4/0x110 \n ? exc_page_fault+0x71/0x160 \n ? asm_exc_page_fault+0x27/0x30 \n ? __mmdrop+0x10/0x180 \n ? __mmdrop+0xec/0x180 \n ? hrtimer_active+0xd/0x50 \n hrtimer_try_to_cancel+0x2c/0xf0 \n hrtimer_cancel+0x15/0x30 \n napi_disable+0x65/0x90 \n mana_destroy_rxq+0x4c/0x2f0 \n mana_create_rxq.isra.0+0x56c/0x6d0 \n ? mana_uncfg_vport+0x50/0x50 \n mana_alloc_queues+0x21b/0x320 \n ? skb_dequeue+0x5f/0x80 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"18 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-18T10:53:24.000000Z"} 2024-09-18T10:53:24+00:00