Skip to content
Threat Brief

← All advisories

CVE-2026-99356

Severity unknownNo known exploitationFix available

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

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 11% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 25bb3647d30a20486b5fe7cff2b0e503c16c9692 before d784d46e19b52a553d5c772a18e13b4c6dc84708d784d46e19b52a553d5c772a18e13b4c6dc84708CVE Program
LinuxLinuxfrom 6.12.42 before 6.12.1176.12.117CVE Program
LinuxLinuxfrom 6.15.10 before 6.166.16CVE Program
LinuxLinuxfrom 6.16.1 before 6.176.17CVE Program
LinuxLinuxfrom 6.6.102 before 6.76.7CVE Program
LinuxLinuxfrom bee47cb026e762841f3faece47b51f985e215edb before 99eb91d68e73a08bfc784eff6f5c02ecb6ea58ba99eb91d68e73a08bfc784eff6f5c02ecb6ea58baCVE Program
LinuxLinuxfrom bee47cb026e762841f3faece47b51f985e215edb before 67d36b376f76a71e52a5f8ed4a4d9d90b8b6813367d36b376f76a71e52a5f8ed4a4d9d90b8b68133CVE Program
LinuxLinuxfrom bee47cb026e762841f3faece47b51f985e215edb before 129e7107b971009bc81643d23f3ab949f540d321129e7107b971009bc81643d23f3ab949f540d321CVE Program
LinuxLinux3b549da875414989f480b66835d514be80a0bd9cNot documentedCVE Program
LinuxLinux6.17Not documentedCVE Program
LinuxLinux6b33c31cc788073bfbed9297e1f4486ed73d87daNot documentedCVE Program
LinuxLinuxb1df394621710b312f0393e3f240fdac0764f968Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.17Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references