CVE-2026-72217 in the critical feed json
SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing
published 2mo ago modified 2mo ago also EUVD-2026-58975
- 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: Bound-check xdr_buf_to_bvec() stores before writing
xdr_buf_to_bvec() writes a bio_vec into the caller's array before testing whether that slot is in range, and the head branch performs the store with no check at all. When the caller's budget is exactly used up, the next store lands one element past the end of the array. The overflow label returns count - 1, which masks the surplus store but cannot undo it.
rq_bvec, the array passed by nfsd_vfs_write(), is allocated to exactly rq_maxpages entries with no slack. The OOB store can land in adjacent slab memory; the bv_len and bv_offset fields written there are derived from client-supplied RPC payload sizes.
Move the in-range check ahead of the store in the head, page-loop, and tail branches. With the check at the top of each sequence, count is incremented only after a successful store, so the overflow label can return count directly.
Patch / fix
- Linux Linux 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2
- linux Debian 13 6.12.100-1
- linux Debian 14 7.1.5-1
debian advisories DEBIAN-CVE-2026-72217
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-34.34
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1013.13
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1013.13
- linux-gke Ubuntu 24.04 LTS 6.8.0-1066.74
- linux-gke Ubuntu 26.04 LTS 7.0.0-1007.8
ubuntu advisories UBUNTU-CVE-2026-72217
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
- kernel-livepatch-SLE16_Update_5 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 12-160000.1.1
- kernel-livepatch-SLE16_Update_9 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 8-160000.1.1
- kernel-livepatch-SLE16_Update_0 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 19-160000.4.3
- kernel-livepatch-SLE16_Update_4 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 13-160000.1.1
- kernel-livepatch-SLE16_Update_3 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 14-160000.1.1
- kernel-livepatch-SLE16_Update_2 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 15-160000.1.1
- kernel-livepatch-SLE16_Update_6 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 11-160000.1.1
- kernel-livepatch-SLE16_Update_1 SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 17-160000.1.1
suse advisories SUSE-SU-2026:24107-1SUSE-SU-2026:24108-1SUSE-SU-2026:24174-1SUSE-SU-2026:24175-1SUSE-SU-2026:24106-1SUSE-SU-2026:24173-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.38.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.38.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.38.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.38.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.38.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.38.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.38.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.38.1
opensuse advisories openSUSE-SU-2026:21910-1
- git.kernel.org/stable/c/4a1148f2739d5089c3ca8ae2e9d1053e219ab5df commit
- git.kernel.org/stable/c/6029e711a818bf34d6c4b90cafee24f3afffa110 commit
- git.kernel.org/stable/c/69e18135e2a004a79505451dbef07314ea16e1eb commit
- git.kernel.org/stable/c/98414b42530af65cb984ffc12685096a3b5e179a commit
- git.kernel.org/stable/c/42f5b80dda6b86e424054baf1475df686c403d5c commit
Is CVE-2026-72217 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 FencerVendor 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-72217 updated cvss 7.0
kernel: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing
-
Red Hat Enterprise Linux 10 kernelaffected: no fix available
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreunder investigation
-
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 morenot 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.64% 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
- git.kernel.org /stable/c/4a1148f2739d5089c3ca8ae2e9d1053e219ab5df
- git.kernel.org /stable/c/6029e711a818bf34d6c4b90cafee24f3afffa110
- git.kernel.org /stable/c/69e18135e2a004a79505451dbef07314ea16e1eb
- git.kernel.org /stable/c/98414b42530af65cb984ffc12685096a3b5e179a
- git.kernel.org /stable/c/42f5b80dda6b86e424054baf1475df686c403d5c
Sources
- CVE List CVE-2026-72217
- NVD CVE-2026-72217
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.