CVE-2026-93207
CVE CVE-2026-93207EUVD EUVD-2026-85936Published 2026-09-24T15:10:30.000ZLast changed 2026-09-25T05:09:43.000ZCVSS 9.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux b0bc53470d1af01f62a0fe2d405cf56477804863 <0e18641708eaa8bc3c1ff338cd844aeadbd52bac; patch: 6.12.109; patch: 7.3-rc1; patch: 6.6.157; b0bc53470d1af01f62a0fe2d405cf56477804863 <11539e8fcce0b0af062ae5fecf7b3676c2f7aeed; b0bc53470d1af01f62a0fe2d405cf56477804863 <e0778464049b0238f2915a40007a4154f86cf351; patch: 0; b0bc53470d1af01f62a0fe2d405cf56477804863 <0fa8a8acae57e6373962741d5b06d13f44aba6a9; 6.3; patch: 7.2.4; patch: 6.18.50; b0bc53470d1af01f62a0fe2d405cf56477804863 <56b29d62017c7dd1718d060dd5b3a2ce61095d0c
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.