{"uuid": "c93371c2-e958-49a7-a67f-0bd9b7a7ca97", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56694", "type": "seen", "source": "https://t.me/cvedetector/13838", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56694 - Linux Kernel BPF Recursive Lock Deadlock in Stream Verdict Program\", \n  \"Content\": \"CVE ID : CVE-2024-56694 \nPublished : Dec. 28, 2024, 10:15 a.m. | 45\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: fix recursive lock when verdict program return SK_PASS  \n  \nWhen the stream_verdict program returns SK_PASS, it places the received skb  \ninto its own receive queue, but a recursive lock eventually occurs, leading  \nto an operating system deadlock. This issue has been present since v6.9.  \n  \n'''  \nsk_psock_strp_data_ready  \n    write_lock_bh(&sk->sk_callback_lock)  \n    strp_data_ready  \n      strp_read_sock  \n        read_sock -> tcp_read_sock  \n          strp_recv  \n            cb.rcv_msg -> sk_psock_strp_read  \n              # now stream_verdict return SK_PASS without peer sock assign  \n              __SK_PASS = sk_psock_map_verd(SK_PASS, NULL)  \n              sk_psock_verdict_apply  \n                sk_psock_skb_ingress_self  \n                  sk_psock_skb_ingress_enqueue  \n                    sk_psock_data_ready  \n                      read_lock_bh(&sk->sk_callback_lock) <=\nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-28T12:06:04.000000Z"}