Answer in brief
CVE-2026-72220 records a Critical severity (CVSS 9.8) vulnerability in sunrpc: harden rq_procinfo lifecycle to prevent double-free. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d9adbb6e10bf7d4223d3d521ede1b2052903bc5e <66014ab165cb01bfef5836939412a8ef98d5d5ff || >=d9adbb6e10bf7d4223d3d521ede1b2052903bc5e <31ba490c02d476a5e4f90b8845932ac9db8aa71b || >=d9adbb6e10bf7d4223d3d521ede1b2052903bc5e <18d216788bef06332ff8901670ecf1ed8f6eb614 | 66014ab165cb01bfef5836939412a8ef98d5d5ff, 31ba490c02d476a5e4f90b8845932ac9db8aa71b, 18d216788bef06332ff8901670ecf1ed8f6eb614 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.