CVE-2026-93207SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry
- 9.8CriticalCVSS base score
- 0.47%Exploitation in 30 daysEPSS · top 59% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry svcauth_gss_decode_credbody() writes the caller's rpc_gss_wire_cred field by field and assigns gc_ctx.len only on the success tail. The caller storage is svcdata->clcred, which lives in the per-svc_rqst gss_svc_data and is reused across requests. Early decode failures leave partially decoded state mixed with residue from the prior request. The trailing body_len tightness check is the sharpest case: xdr_stream_decode_opaque_inline() has already written gc_ctx.data with a borrowed inline pointer into the current request's XDR pages, but gc_ctx.len retains its prior value. Once the request pages are released the pooled clcred carries a dangling pointer paired with a stale length. Zero the caller's rpc_gss_wire_cred at function entry so that every early-return path leaves a deterministic all-zero cred. On the trailing tightness-check path, gc_ctx.len is now zero instead of stale, which neuters length-driven consumers such as gss_svc_searchbyctx() that would otherwise walk the dangling data pointer.
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 25 days later
· 25 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.47% · top 59% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected b0bc53470d1af01f62a0fe2d405cf56477804863 – < 56b29d62017c7dd1718d060dd5b3a2ce61095d0c
- affected b0bc53470d1af01f62a0fe2d405cf56477804863 – < 0e18641708eaa8bc3c1ff338cd844aeadbd52bac
- affected b0bc53470d1af01f62a0fe2d405cf56477804863 – < e0778464049b0238f2915a40007a4154f86cf351
- affected b0bc53470d1af01f62a0fe2d405cf56477804863 – < 0fa8a8acae57e6373962741d5b06d13f44aba6a9
- affected b0bc53470d1af01f62a0fe2d405cf56477804863 – < 11539e8fcce0b0af062ae5fecf7b3676c2f7aeed
- affected 6.3
- unaffected < 6.3
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.109 – ≤ 6.12.*
- unaffected 6.18.50 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/56b29d62017c7dd1718d060dd5b3a2ce61095d0c (opens in a new tab)
- https://git.kernel.org/stable/c/0e18641708eaa8bc3c1ff338cd844aeadbd52bac (opens in a new tab)
- https://git.kernel.org/stable/c/e0778464049b0238f2915a40007a4154f86cf351 (opens in a new tab)
- https://git.kernel.org/stable/c/0fa8a8acae57e6373962741d5b06d13f44aba6a9 (opens in a new tab)
- https://git.kernel.org/stable/c/11539e8fcce0b0af062ae5fecf7b3676c2f7aeed (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-85936 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93207)Record last updated .