CVE-2026-72220
CVE CVE-2026-72220EUVD EUVD-2026-59119Published 2026-08-15T05:54:13.000ZLast changed 2026-08-17T05:41:41.000ZCVSS 9.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: sunrpc: harden rq_procinfo lifecycle to prevent double-free The svc_release_rqst() function executes the callback inside rqstp->rq_procinfo->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. 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. This guarantees that error flows will not encounter a non-NULL stale rq_procinfo pointer when there is nothing to release.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux d9adbb6e10bf7d4223d3d521ede1b2052903bc5e <66014ab165cb01bfef5836939412a8ef98d5d5ff; patch: 7.1.5; patch: 6.18.40; patch: 0; 6.18; patch: 7.2; d9adbb6e10bf7d4223d3d521ede1b2052903bc5e <31ba490c02d476a5e4f90b8845932ac9db8aa71b; d9adbb6e10bf7d4223d3d521ede1b2052903bc5e <18d216788bef06332ff8901670ecf1ed8f6eb614
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.