CVE-2026-93228: Linux kernel · svcrdma: Reject Write/Reply chunks with segcount 0
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical · fixed in fe533ae1bed2ef2b3d54ee7ab410da1874ed3d4f : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 20:10 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fe533ae1bed2ef2b3d54ee7ab410da1874ed3d4f, a798714b58041e88716db3bf8fb03ae13eecd54a, 9808eb7656666acc7291bae9ab6b987bd16e47e0 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel commits identified by the fixedVersions hashes. Users should update to a Linux kernel version that includes these fixes to mitigate the vulnerability. No additional mitigation is required as the patch rejects malformed zero-segment chunks and ensures only fully populated chunks are processed.
Description
CVE-2026-93228 is a critical vulnerability in the Linux kernel's svcrdma module where Write or Reply chunks with a segcount of zero were improperly accepted. This flaw allowed malformed chunks with zero segments to be linked into parsed chunk lists, potentially leading to denial of service. The issue was addressed by rejecting such zero-segment chunks at the decode boundary and reordering code to ensure only fully-populated chunks are processed. Legitimate clients are not affected as RFC 8166 does not define Write/Reply chunks with zero segments.
References
- git.kernel.org/stable/c/28c5a3a572f6cf81ac304459cfd515480995d62a (opens in a new tab)
- git.kernel.org/stable/c/fe533ae1bed2ef2b3d54ee7ab410da1874ed3d4f (opens in a new tab)
- git.kernel.org/stable/c/a798714b58041e88716db3bf8fb03ae13eecd54a (opens in a new tab)
- git.kernel.org/stable/c/45dbdb2637b7fc5f1355b588780d2a7fb0516805 (opens in a new tab)
- git.kernel.org/stable/c/9808eb7656666acc7291bae9ab6b987bd16e47e0 (opens in a new tab)