Threat Feed

CVE-2026-99356: SUNRPC: Do not credit control-record octets to the RPC stream

Exploitation: None known · CVSS 9.8 Critical · Unauthenticated · Published 2026-11-19

Description

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Do not credit control-record octets to the RPC stream svc_tcp_sock_recv_cmsg() receives up to two octets into a local buffer, and returns that count for any record type other than TLS_RECORD_TYPE_ALERT. Nothing reached the caller's buffer, but svc_tcp_read_marker() adds the count to sk_tcplen and svc_tcp_read_msg()'s caller adds it to sk_datalen. The RPC stream advances over octets it never received. The fragment marker is assembled from stale sk_marker octets. The message body comes from pages nothing wrote. A conforming client reaches this. RFC 8446 Section 4.6.3 lets either peer send KeyUpdate once it has sent its Finished, and svcsock has no rekey path. kTLS leaves the partially consumed record on ctx->rx_list, so the body drains two octets per svc_tcp_recvfrom() call. Each pair is credited the same way. Return -EAGAIN for a record that is not an alert. That is what svc_tcp_sock_process_cmsg()'s default arm returned before the receive moved into a local buffer.

Enclave's analysis

A Linux kernel nfsd bug miscounts bytes from TLS control records in the RPC-with-TLS (kTLS) transport. A fully standards-compliant client can trigger it just by sending a normal TLS 1.3 KeyUpdate record, desyncing the server's byte accounting and potentially corrupting heap memory or crashing nfsd. It only fires when nfsd has kTLS/RPC-with-TLS explicitly enabled, a non-default, fairly new NFS feature most servers don't use. No PoC exists, it isn't in KEV, and EPSS is near zero — patch on your normal cycle unless you run NFS-over-TLS, then prioritize it.

Fix

Upgrade Linux kernel to 6.7 or 6.12.117 or 6.16 or 6.17 or 6.18.61 or 7.3.2; Google Container-Optimized OS kernel packages (cos-kernel-6_12 family) to 19506.625.45 (COS 129) / 19216.801.52 (COS 125). No fixed version is listed for Linux; follow the vendor advisory.

Affected versions

ProductVulnerableFixed in
Linux25bb3647d30a20486b5fe7cff2b0e503c16c9692 before d784d46e19b52a553d5c772a18e13b4c6dc84708Not listed
Linuxbee47cb026e762841f3faece47b51f985e215edb before 67d36b376f76a71e52a5f8ed4a4d9d90b8b68133Not listed
Linuxbee47cb026e762841f3faece47b51f985e215edb before 99eb91d68e73a08bfc784eff6f5c02ecb6ea58baNot listed
Linuxbee47cb026e762841f3faece47b51f985e215edb before 129e7107b971009bc81643d23f3ab949f540d321Not listed
Linuxb1df394621710b312f0393e3f240fdac0764f968Not listed
Linux3b549da875414989f480b66835d514be80a0bd9cNot listed
Linux6b33c31cc788073bfbed9297e1f4486ed73d87daNot listed
Linux6.12.42 before 6.12.117Not listed
Linux6.6.102 before 6.7Not listed
Linux6.15.10 before 6.16Not listed
Linux6.16.1 before 6.17Not listed
Linux6.17Not listed
Linux kernel>=6.6.102, <6.76.7
Linux kernel>=6.12.42, <6.12.1176.12.117
Linux kernel>=6.15.10, <6.166.16
Linux kernel>=6.16.1, <6.176.17
Linux kernel>=6.17, <6.18.616.18.61
Linux kernel>=6.19, <7.3.2 (mainline fixed at 7.4-rc1)7.3.2
Google Container-Optimized OS kernel packages (cos-kernel-6_12 family)<19506.625.45 (COS 129); <19216.801.52 (COS 125)19506.625.45 (COS 129) / 19216.801.52 (COS 125)

Seen in 2 sources