https://vulnerability.circl.lu/sightings/feed 2026-05-05T22:24:16.722069+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/92d1e34d-6e09-43ad-9899-43e9794d1b56/export 2026-05-05T22:24:17.246305+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "92d1e34d-6e09-43ad-9899-43e9794d1b56", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-49732", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/5509", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-49732\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nsock: redo the psock vs ULP protection check\n\nCommit 8a59f9d1e3d4 (\"sock: Introduce sk->sk_prot->psock_update_sk_prot()\")\nhas moved the inet_csk_has_ulp(sk) check from sk_psock_init() to\nthe new tcp_bpf_update_proto() function. I'm guessing that this\nwas done to allow creating psocks for non-inet sockets.\n\nUnfortunately the destruction path for psock includes the ULP\nunwind, so we need to fail the sk_psock_init() itself.\nOtherwise if ULP is already present we'll notice that later,\nand call tcp_update_ulp() with the sk_proto of the ULP\nitself, which will most likely result in the ULP looping\nits callbacks.\n\ud83d\udccf Published: 2025-02-26T14:57:24.827Z\n\ud83d\udccf Modified: 2025-02-26T14:57:24.827Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/72fa0f65b56605b8a9ae9fba2082f2123f7fe017\n2. https://git.kernel.org/stable/c/922309e50befb0cfa5cb65e4989b7706d6578846\n3. https://git.kernel.org/stable/c/e34a07c0ae3906f97eb18df50902e2a01c1015b6", "creation_timestamp": "2025-02-26T15:26:12.000000Z"} 2025-02-26T15:26:12+00:00