Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99356

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

No exploitation reported by the sources we read.

  • Published2026-11-19
  • Fixed in7.3.2 · 6.18.61 · 6.17 · 6.16 · 6.12.117 · 6.7

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-1914:22CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.27.3.2
6.x≥ 6.17.0, < 6.18.616.18.61
6.x≥ 6.16.1, < 6.176.17
6.x≥ 6.15.10, < 6.166.16
6.12≥ 6.12.42, < 6.12.1176.12.117
6.x≥ 6.6.102, < 6.76.7

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 25bb3647d30a20486b5fe7cff2b0e503c16c9692, < d784d46e19b52a553d5c772a18e13b4c6dc84708fixed in d784d46e19b52a553d5c772a18e13b4c6dc84708git
    • ≥ bee47cb026e762841f3faece47b51f985e215edb, < 67d36b376f76a71e52a5f8ed4a4d9d90b8b68133fixed in 67d36b376f76a71e52a5f8ed4a4d9d90b8b68133git
    • ≥ bee47cb026e762841f3faece47b51f985e215edb, < 99eb91d68e73a08bfc784eff6f5c02ecb6ea58bafixed in 99eb91d68e73a08bfc784eff6f5c02ecb6ea58bagit
    • ≥ bee47cb026e762841f3faece47b51f985e215edb, < 129e7107b971009bc81643d23f3ab949f540d321fixed in 129e7107b971009bc81643d23f3ab949f540d321git
    • = b1df394621710b312f0393e3f240fdac0764f968no fix statedgit
    • = 3b549da875414989f480b66835d514be80a0bd9cno fix statedgit
    • = 6b33c31cc788073bfbed9297e1f4486ed73d87dano fix statedgit
    • ≥ 6.12.42, < 6.12.117fixed in 6.12.117semver

    3 more version lines in the CVE record.

  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 6.17no fix stated

    Not affected < 6.17 · ≥ 6.12.117, ≤ 6.12.* · ≥ 6.18.61, ≤ 6.18.* · ≥ 7.3.2, ≤ 7.3.* · ≥ 7.4-rc1

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-19

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • linuxDebian:14all versions · fixed in 7.3.3-1
  • linuxDebian:13all versions · fixed in 6.12.117-1
  • linux-6.12Debian:12all versions · fixed in 6.12.117-1~deb12u1
  • linux-ltsAlpaquita:streamfrom 6.18.58-r0 · fixed in 6.18.62-r0
  • linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed

Vendor advisories

  • CVE-2026-99356 Red Hat Product Security125 known affected

    kernel: kernel: denial of service via improper handling of TLS control messages in SUNRPC

    kernel.src as a component of Red Hat Enterprise Linux 10 · kernel as a component of Red Hat Enterprise Linux 6 · kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6 · +122 more

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.2 · 6.18.61 · 6.17 · 6.16 · 6.12.117 · 6.7
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-99356 · 111 productsFix deferred
  3. No fix planned, says the vendor Red Hat Product Security CVE-2026-99356 · 14 productsOut of support scope

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-19
Last modified
2026-11-22
NVD status
Received
GitHub advisory
GHSA-8c64-89jh-jj83

Frequently asked questions

What is CVE-2026-99356?

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.

Is CVE-2026-99356 actively exploited?

Active exploitation of CVE-2026-99356 has not been confirmed. Its EPSS score was 0.2% on 2026-11-21, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99356?

CVE-2026-99356 has a CVSS v3 base score of 9.8 (Critical severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website checks · 250 API requests/month

Sources for this record