← Back to the live CVE advisory feed

CVE-2026-93207: Linux

Severity

9.8 (CRITICAL)

Vendor

LINUX

Affected versions

b0bc53470d1af01f62a0fe2d405cf56477804863 through before 56b29d62017c7dd1718d060dd5b3a2ce61095d0c; b0bc53470d1af01f62a0fe

Patch status

Patched

Published

2026-09-24T16:17:15.357

Modified

2026-09-25T05:16:58.630

Why it matters

Critical vulnerability requiring immediate validation against your environment.

Recommended admin actions

• Prioritize validation immediately due to critical CVSS severity.

Technical summary

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.

View the official NVD record for CVE-2026-93207

CVE data is sourced from NVD/CNA records and optional enrichment. Validate against the vendor advisory before taking production action.