https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 21:12:38 +0000 https://vulnerability.circl.lu/vuln/cve-2022-49732 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sock: redo the psock vs ULP protection check</p> <p>Commit 8a59f9d1e3d4 (&#34;sock: Introduce sk-&gt;sk_prot-&gt;psock_update_sk_prot()&#34;) has moved the inet_csk_has_ulp(sk) check from sk_psock_init() to the new tcp_bpf_update_proto() function. I&#39;m guessing that this was done to allow creating psocks for non-inet sockets.</p> <p>Unfortunately the destruction path for psock includes the ULP unwind, so we need to fail the sk_psock_init() itself. Otherwise if ULP is already present we&#39;ll notice that later, and call tcp_update_ulp() with the sk_proto of the ULP itself, which will most likely result in the ULP looping its callbacks.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sock: redo the psock vs ULP protection check</p> <p>Commit 8a59f9d1e3d4 (&#34;sock: Introduce sk-&gt;sk_prot-&gt;psock_update_sk_prot()&#34;) has moved the inet_csk_has_ulp(sk) check from sk_psock_init() to the new tcp_bpf_update_proto() function. I&#39;m guessing that this was done to allow creating psocks for non-inet sockets.</p> <p>Unfortunately the destruction path for psock includes the ULP unwind, so we need to fail the sk_psock_init() itself. Otherwise if ULP is already present we&#39;ll notice that later, and call tcp_update_ulp() with the sk_proto of the ULP itself, which will most likely result in the ULP looping its callbacks.</p> https://vulnerability.circl.lu/vuln/cve-2022-49732