CVE-2026-72220

CVE-2026-72220 · sunrpc: harden rq_procinfo lifecycle to prevent double-free

CVSS 9.8 · Critique · EPSS 0,6% · Correctif disponible

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="linux"'

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="linux-hwe-edge"'

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="linux-aws-5.0"'

curl -fsSL https://patchfirst.dev/check.sh | sh

Cette page présente des faits issus de sources publiques. Consultez l’avis original avant toute mise à jour.

Cette page présente une partie des faits des sources. Consultez les avis liés pour la description complète et les versions concernées.

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.

Publication

2026-08-15T05:54:13.800Z

Mise à jour

2026-08-17T05:41:41.598Z

Pile logicielle: system

Vérifiez votre serveur →