Bug 2576161 (CVE-2026-104357) - CVE-2026-104357 libtirpc: libtirpc: SunRPC UDP datagram-boundary violation (stale buffer bytes decoded as current request)
Summary: CVE-2026-104357 libtirpc: libtirpc: SunRPC UDP datagram-boundary violation (s...
Keywords:
Status: NEW
Alias: CVE-2026-104357
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-19 03:01 UTC by OSIDB Bzimport
Modified: 2026-11-19 04:35 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-19 03:01:54 UTC
A flaw was found in libtirpc. The SunRPC UDP/datagram server transport (svc_dg_recv / svcudp_create) reuses a single XDR decode stream sized to the allocated receive buffer. On each datagram, the receive path resets the stream position and calls xdr_callmsg, but it does not rebind the decode bound (x_handy) to the actual received length rlen. Because the XDR memory backend uses x_handy as the remaining length, a shorter request can be decoded together with stale bytes left by a prior datagram. Florian Weimer reproduced this with tst-udp-stale: a full request leaves argument bytes at the tail of the buffer after a shorter reply is encoded; a follow-up truncated AUTH_NONE call with no arguments then has svc_getargs consume those leftover bytes and echo them back. A correctly bounded decoder would fail with GARBAGE_ARGS. This is a logical datagram-boundary violation, not a read past the allocated buffer. The same inherited SunRPC pattern exists in glibc sunrpc/svc_udp.c (legacy ABI compatibility; glibc is expected to assign a separate CVE) and in other copies such as krb5 GSSRPC. CVE-2026-104357 is assigned to the libtirpc implementation. Reported by Aisle Research against glibc; Red Hat confirmed the bug is present in libtirpc. Related tracking: OSIM-77274 / RHEL-217046 (glibc report), PSIRTSUPT-22635 (coordination).


Note You need to log in before you can comment on or make changes to this bug.