CVE-2026-99356
What it is
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.
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < d784d46e19b52a553d5c772a18e13b4c6dc84708
- Linux < 67d36b376f76a71e52a5f8ed4a4d9d90b8b68133
- Linux < 99eb91d68e73a08bfc784eff6f5c02ecb6ea58ba
- Linux < 129e7107b971009bc81643d23f3ab949f540d321
- Linux b1df394621710b312f0393e3f240fdac0764f968
- Linux 3b549da875414989f480b66835d514be80a0bd9c
- Linux 6b33c31cc788073bfbed9297e1f4486ed73d87da
- Linux < 6.12.117
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99356.md and follow it. Check whether this project is affected by CVE-2026-99356. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.