Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99356

Not known to be exploited · fixed in d784d46e19b52a553d5c772a18e13b4c6dc84708 : update Linux kernel when convenient.

Data as of 19 Nov 2026, 16:20 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in d784d46e19b52a553d5c772a18e13b4c6dc84708, 129e7107b971009bc81643d23f3ab949f540d321, 99eb91d68e73a08bfc784eff6f5c02ecb6ea58ba +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.12.42 <6.12.117
  • >=6.6.102 <6.7
  • >=6.15.10 <6.16
  • >=6.16.1 <6.17
Fixed in
  • d784d46e19b52a553d5c772a18e13b4c6dc84708
  • 129e7107b971009bc81643d23f3ab949f540d321
  • 99eb91d68e73a08bfc784eff6f5c02ecb6ea58ba
  • 67d36b376f76a71e52a5f8ed4a4d9d90b8b68133
  • 6.17
  • 6.16
  • 6.12.117
  • 6.7
LinuxLinuxAffected
  • =6.17
Fixed in–

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.

References

Community reviews

Loading reviews…