CVE-2026-99356: SUNRPC: Do not credit control-record octets to the RPC stream
In the Linux kernel, the following vulnerability has been resolved:
SUNRPC: Do not credit control-record octets to the RPC stream
svctcpsockrecvcmsg() receives up to two octets into a local buffer, and returns that count for any record type other than TLSRECORDTYPEALERT. Nothing reached the caller's buffer, but svctcpreadmarker() adds the count to sktcplen and svctcpreadmsg()'s caller adds it to skdatalen. The RPC stream advances over octets it never received. The fragment marker is assembled from stale skmarker 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->rxlist, so the body drains two octets per svctcprecvfrom() call. Each pair is credited the same way.
Return -EAGAIN for a record that is not an alert. That is what svctcpsockprocesscmsg()'s default arm returned before the receive moved into a local buffer.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.7 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.16 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.17 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2 - Compensating control
Return -EAGAIN for a record that is not an alert.