CVE-2026-89551

SUNRPC: xdr_buf_trim: clamp buf->len to avoid underflow

State
Published
Severity
9.8 Critical
Published
Sep 11, 2026
Updated
Oct 19, 2026
Reserved
Sep 11, 2026

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

SUNRPC: xdr_buf_trim: clamp buf->len to avoid underflow

xdr_buf_trim() trims `len` bytes from the tail of an xdr_buf by walking the tail, pages, and head iovecs. Each per-section step uses min_t() so it never removes more bytes than that section holds, but the final accounting at the fix_len label subtracts the total bytes actually consumed from buf->len without any clamp:

fix_len: buf->len -= (len - trim);

When the caller has set buf->len to a value smaller than the sum of the iov_lens, (len - trim) can exceed buf->len and the unsigned subtraction wraps to near UINT_MAX. gss_krb5_unwrap_v2() reaches xdr_buf_trim() in exactly that state:

buf->head[0].iov_len -= GSS_KRB5_TOK_HDR_LEN + headskip; buf->len = len - (GSS_KRB5_TOK_HDR_LEN + headskip); xdr_buf_trim(buf, ec + GSS_KRB5_TOK_HDR_LEN + tailskip);

buf->len is a small wire-derived value while the iov_lens are at page scale, so the per-section loops legitimately consume far more bytes than buf->len records. The wrapped buf->len then propagates as the authoritative stream bound into every downstream XDR decoder.

Fix by clamping the decrement so buf->len bottoms out at zero:

buf->len -= min_t(unsigned int, buf->len, len - trim);

On the normal path where the iov_lens sum to buf->len, (len - trim) is always <= buf->len and the result is identical to before. No callers change behavior outside the underflow case.

Scores

CVSSScoreVectorSource
3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 4c190e2f913f038c9c91ee63b59cd037260ba353 to before a3d77bcd974b8625d16bddf448cb3a1b5e37049cAffected
  • 4c190e2f913f038c9c91ee63b59cd037260ba353 to before fa16bbe987b47e771e52eeb1b4540f18d92496acAffected
  • 4c190e2f913f038c9c91ee63b59cd037260ba353 to before a924ac4c78afab71bf82641afa3b62e0c4a8b55eAffected
  • 4c190e2f913f038c9c91ee63b59cd037260ba353 to before 4bf59cb0ea5b0ddfbc46a1dc2fa78fc8b9986ce4Affected
  • 4c190e2f913f038c9c91ee63b59cd037260ba353 to before e6267cccd7b05cc514e57f2160aa8db85f5c2701Affected
  • 4c190e2f913f038c9c91ee63b59cd037260ba353 to before ad0cce80d4af2f74674e8b635d97aa3880e83da8Affected
  • 4c190e2f913f038c9c91ee63b59cd037260ba353 to before 85e9602650e9df07190abe817cee3b4d9bc3df17Affected
  • 4c190e2f913f038c9c91ee63b59cd037260ba353 to before 3f491306dcb673ff5e78e1044ba450c58978774eAffected
LinuxLinux
  • 3.9Affected
  • before 3.9Not affected
  • 5.10.270 through 5.10.*Not affected
  • 5.15.221 through 5.15.*Not affected
  • 6.1.188 through 6.1.*Not affected
  • 6.6.157 through 6.6.*Not affected
  • 6.12.109 through 6.12.*Not affected
  • 6.18.50 through 6.18.*Not affected
  • 7.2.4 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.