https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Tue, 05 May 2026 23:12:53 +0000 https://vulnerability.circl.lu/sighting/cdb181e2-4cca-4a49-801a-a4312cd73a81/export {"uuid": "cdb181e2-4cca-4a49-801a-a4312cd73a81", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49980", "type": "seen", "source": "https://t.me/cvedetector/8524", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-49980 - \"vrf Linux Kernel Deadlock Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2024-49980 \nPublished : Oct. 21, 2024, 6:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nvrf: revert \"vrf: Remove unnecessary RCU-bh critical section\" \n \nThis reverts commit 504fc6f4f7f681d2a03aa5f68aad549d90eab853. \n \ndev_queue_xmit_nit is expected to be called with BH disabled. \n__dev_queue_xmit has the following: \n \n /* Disable soft irqs for various locks below. Also \n * stops preemption for RCU. \n */ \n rcu_read_lock_bh(); \n \nVRF must follow this invariant. The referenced commit removed this \nprotection. Which triggered a lockdep warning: \n \n ================================ \n WARNING: inconsistent lock state \n 6.11.0 #1 Tainted: G W \n -------------------------------- \n inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage. \n btserver/134819 [HC0[0]:SC0[0]:HE1:SE1] takes: \n ffff8882da30c118 (rlock-AF_PACKET){+.?.}-{2:2}, at: tpacket_rcv+0x863/0x3b30 \n {IN-SOFTIRQ-W} state was registered at: \n lock_acquire+0x19a/0x4f0 \n _raw_spin_lock+0x27/0x40 \n packet_rcv+0xa33/0x1320 \n __netif_receive_skb_core.constprop.0+0xcb0/0x3a90 \n __netif_receive_skb_list_core+0x2c9/0x890 \n netif_receive_skb_list_internal+0x610/0xcc0 \n [...] \n \n other info that might help us debug this: \n Possible unsafe locking scenario: \n \n CPU0 \n ---- \n lock(rlock-AF_PACKET); \n \n lock(rlock-AF_PACKET); \n \n *** DEADLOCK *** \n \n Call Trace: \n \n dump_stack_lvl+0x73/0xa0 \n mark_lock+0x102e/0x16b0 \n __lock_acquire+0x9ae/0x6170 \n lock_acquire+0x19a/0x4f0 \n _raw_spin_lock+0x27/0x40 \n tpacket_rcv+0x863/0x3b30 \n dev_queue_xmit_nit+0x709/0xa40 \n vrf_finish_direct+0x26e/0x340 [vrf] \n vrf_l3_out+0x5f4/0xe80 [vrf] \n __ip_local_out+0x51e/0x7a0 \n [...] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"21 Oct 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T21:02:16.000000Z"} {"uuid": "cdb181e2-4cca-4a49-801a-a4312cd73a81", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49980", "type": "seen", "source": "https://t.me/cvedetector/8524", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-49980 - \"vrf Linux Kernel Deadlock Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2024-49980 \nPublished : Oct. 21, 2024, 6:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nvrf: revert \"vrf: Remove unnecessary RCU-bh critical section\" \n \nThis reverts commit 504fc6f4f7f681d2a03aa5f68aad549d90eab853. \n \ndev_queue_xmit_nit is expected to be called with BH disabled. \n__dev_queue_xmit has the following: \n \n /* Disable soft irqs for various locks below. Also \n * stops preemption for RCU. \n */ \n rcu_read_lock_bh(); \n \nVRF must follow this invariant. The referenced commit removed this \nprotection. Which triggered a lockdep warning: \n \n ================================ \n WARNING: inconsistent lock state \n 6.11.0 #1 Tainted: G W \n -------------------------------- \n inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage. \n btserver/134819 [HC0[0]:SC0[0]:HE1:SE1] takes: \n ffff8882da30c118 (rlock-AF_PACKET){+.?.}-{2:2}, at: tpacket_rcv+0x863/0x3b30 \n {IN-SOFTIRQ-W} state was registered at: \n lock_acquire+0x19a/0x4f0 \n _raw_spin_lock+0x27/0x40 \n packet_rcv+0xa33/0x1320 \n __netif_receive_skb_core.constprop.0+0xcb0/0x3a90 \n __netif_receive_skb_list_core+0x2c9/0x890 \n netif_receive_skb_list_internal+0x610/0xcc0 \n [...] \n \n other info that might help us debug this: \n Possible unsafe locking scenario: \n \n CPU0 \n ---- \n lock(rlock-AF_PACKET); \n \n lock(rlock-AF_PACKET); \n \n *** DEADLOCK *** \n \n Call Trace: \n \n dump_stack_lvl+0x73/0xa0 \n mark_lock+0x102e/0x16b0 \n __lock_acquire+0x9ae/0x6170 \n lock_acquire+0x19a/0x4f0 \n _raw_spin_lock+0x27/0x40 \n tpacket_rcv+0x863/0x3b30 \n dev_queue_xmit_nit+0x709/0xa40 \n vrf_finish_direct+0x26e/0x340 [vrf] \n vrf_l3_out+0x5f4/0xe80 [vrf] \n __ip_local_out+0x51e/0x7a0 \n [...] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"21 Oct 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T21:02:16.000000Z"} https://vulnerability.circl.lu/sighting/cdb181e2-4cca-4a49-801a-a4312cd73a81/export Mon, 21 Oct 2024 21:02:16 +0000