https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 21:35:23 +0000 https://vulnerability.circl.lu/vuln/cve-2026-72220 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sunrpc: harden rq_procinfo lifecycle to prevent double-free</p> <p>The svc_release_rqst() function executes the callback inside rqstp-&gt;rq_procinfo-&gt;pc_release. However, if a worker thread begins processing a new request and encounters an early error path (e.g., unsupported protocol, short frame, or bad auth) before a valid rq_procinfo is installed, a stale release hook can be re-triggered against reused state from the previous RPC, resulting in a double-free or use-after-free vulnerability.</p> <p>Harden the lifecycle of rq_procinfo by: 1. Ensuring svc_release_rqst() always clears rq_procinfo after the optional pc_release() call, regardless of whether the hook exists. 2. Explicitly clearing rq_procinfo at request entry in svc_process() before any early decode or drop paths. 3. Ensuring svc_process_bc() does the same at backchannel entry.</p> <p>This guarantees that error flows will not encounter a non-NULL stale rq_procinfo pointer when there is nothing to release.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sunrpc: harden rq_procinfo lifecycle to prevent double-free</p> <p>The svc_release_rqst() function executes the callback inside rqstp-&gt;rq_procinfo-&gt;pc_release. However, if a worker thread begins processing a new request and encounters an early error path (e.g., unsupported protocol, short frame, or bad auth) before a valid rq_procinfo is installed, a stale release hook can be re-triggered against reused state from the previous RPC, resulting in a double-free or use-after-free vulnerability.</p> <p>Harden the lifecycle of rq_procinfo by: 1. Ensuring svc_release_rqst() always clears rq_procinfo after the optional pc_release() call, regardless of whether the hook exists. 2. Explicitly clearing rq_procinfo at request entry in svc_process() before any early decode or drop paths. 3. Ensuring svc_process_bc() does the same at backchannel entry.</p> <p>This guarantees that error flows will not encounter a non-NULL stale rq_procinfo pointer when there is nothing to release.</p> https://vulnerability.circl.lu/vuln/cve-2026-72220