CVE-2026-93207

SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry

  • Critical 9.8

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.

Key facts

Published
24 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.467% likely to be exploited in the next 30 days, higher than 40.99% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 9.8CVSS 3.1, Criticalfrom the CNA (Linux)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • b0bc53470d1af01f62a0fe2d405cf56477804863 up to but excluding 56b29d62017c7dd1718d060dd5b3a2ce61095d0c (affected)
  • b0bc53470d1af01f62a0fe2d405cf56477804863 up to but excluding 0e18641708eaa8bc3c1ff338cd844aeadbd52bac (affected)
  • b0bc53470d1af01f62a0fe2d405cf56477804863 up to but excluding e0778464049b0238f2915a40007a4154f86cf351 (affected)
  • b0bc53470d1af01f62a0fe2d405cf56477804863 up to but excluding 0fa8a8acae57e6373962741d5b06d13f44aba6a9 (affected)
  • b0bc53470d1af01f62a0fe2d405cf56477804863 up to but excluding 11539e8fcce0b0af062ae5fecf7b3676c2f7aeed (affected)
LinuxLinux
  • Default status: affected
  • 6.3 (affected)
  • 0 up to but excluding 6.3 (unaffected)
  • 6.6.157 up to and including 6.6.* (unaffected)
  • 6.12.109 up to and including 6.12.* (unaffected)
  • 6.18.50 up to and including 6.18.* (unaffected)
  • 7.2.4 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 24 Sep 2026 Published

References