Skip to content
Fencer Intel
critical 9.8

CVE-2026-72220 in the critical feed json

sunrpc: harden rq_procinfo lifecycle to prevent double-free

published 2mo ago modified 2mo ago also EUVD-2026-59119

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 6.18.40, 7.1.5, 7.2
  • linux Debian 14 7.1.5-1

debian advisories DEBIAN-CVE-2026-72220

  • linux Ubuntu 26.04 LTS 7.0.0-34.34
  • linux-aws Ubuntu 26.04 LTS 7.0.0-1013.13
  • linux-gcp Ubuntu 26.04 LTS 7.0.0-1013.13
  • linux-gke Ubuntu 26.04 LTS 7.0.0-1007.8
  • linux-ibm Ubuntu 26.04 LTS 7.0.0-1014.14
  • linux-azure Ubuntu 26.04 LTS 7.0.0-1017.17
  • linux-raspi Ubuntu 26.04 LTS 7.0.0-1020.20
  • linux-riscv Ubuntu 26.04 LTS 7.0.0-34.34.1

ubuntu advisories UBUNTU-CVE-2026-72220

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-72220 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-72220 updated cvss 7.0

kernel: sunrpc: harden rq_procinfo lifecycle to prevent double-free

  • Red Hat Enterprise Linux 10 kernel
    affected: workaround, no fix available “To reduce exposure to this vulnerability, disable the kernel NFS server if it is not required in your environment: # systemctl stop nfs-server.service # systemctl disable nfs-server.service”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.