CVE Feed
9.8 Critical

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Do not credit control-record octets to the RPC stream…

CVE-2026-99356

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.

Assessment

CVSS
9.8 (v3.1)
Severity
Critical
EPSS
0.21% chance of exploitation in the next 30 days
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
19 November 2026
Last updated
22 November 2026
Affected
Linux · Linux
Assigner
Linux

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99356