Kernel crash and stream corruption via packet replay
Published Sep 17, 2026 · Updated Sep 18, 2026
Race condition in Linux kernel RDMA/rxe allows remote attackers to corrupt application streams and crash the host via RoCE traffic. In do_complete(), an error-state return sends an already completed packet back through check_resource() and send_data_in(), duplicating completions until a null receive work queue entry is dereferenced. Exploitation requires an established RoCEv2 reliable-connected queue pair and a disconnect or negative acknowledgment racing with receive completion; the result is repeated application delivery, stream corruption, and a kernel crash.
Summary
What happened
Race condition in Linux kernel RDMA/rxe allows remote attackers to corrupt application streams and crash the host via RoCE traffic. In do_complete(), an error-state return sends an already completed packet back through check_resource() and send_data_in(), duplicating completions until a null receive work queue entry is dereferenced. Exploitation requires an established RoCEv2 reliable-connected queue pair and a disconnect or negative acknowledgment racing with receive completion; the result is repeated application delivery, stream corruption, and a kernel crash.
The record
- CVE
- CVE-2026-93107
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=49dc9c1f0c7e396654a31a480328fffd902fa494 <0d37e2503efd1069a74be740eadf63ea17c96810
- Affected versionversion=49dc9c1f0c7e396654a31a480328fffd902fa494 <15ae32c4a3551c4c9da457370bdfdd65d171e512
- Affected versionversion=49dc9c1f0c7e396654a31a480328fffd902fa494 <399713f1f0eac641351c8ceaec0ab8244ddcf78c
- Affected versionversion=49dc9c1f0c7e396654a31a480328fffd902fa494 <62a4b48767e06fdd64548450fae2b1ffc6ff5d69
- Affected versionversion=49dc9c1f0c7e396654a31a480328fffd902fa494 <c319b986a88cedf600c4497cd7814a891b2f9e7c
- Affected versionversion=6.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started