In the Linux kernel, the following vulnerability has been resolved: vsock: treat TCPCLOSING as once-established Handle the TCPESTABLISHED…
CVE-2026-99213
In the Linux kernel, the following vulnerability has been resolved: vsock: treat TCPCLOSING as once-established Handle the TCPESTABLISHED -> TCPCLOSING transition on OPRST, which can race with the connect loop. Immediately break and return 0 on ESTABLISHED/CLOSING. The return value of connect() should reflect what happened up to the point the connection was established or failed. Events that occur afterwards must not affect it. E.g. even if OPRW has already set skerr, connect() should still return 0, not ENOBUFS because of it. Adapt the inaccurate comment above signalpending(). Resetting a socket that is still present in connectedtable can lead to memory corruption. The reporter noted lost transports for in-flight skbs, and I have reproduced crashes caused by re-insertion into connectedtable. listadd double add: new=, prev=, next=. kernel BUG at lib/listdebug.c:35! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI Workqueue: vsock-loopback vsockloopbackwork RIP: 0010:listaddvalidorreport+0x11f/0x130 Call Trace: vsockinsertconnected.cold+0xe/0x13 virtiotransportrecvpkt+0x10e9/0x1460 vsockloopbackwork+0x305/0x480 processonework+0xe4c/0x1560 workerthread+0x4f1/0xd60 kthread+0x36e/0x470…
Assessment
- CVSS
- 7.8 (v3.1)
- Severity
- High
- EPSS
- 0.16% 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
- 28 October 2026
- Last updated
- 31 October 2026
- Affected
- Linux
- Assigner
- Linux
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
At the source
References
- https://git.kernel.org/stable/c/ea36ef3c229d54b552432d1290aee1d807f67fd5
- https://git.kernel.org/stable/c/5f2ab77028602a22f0cc33cac063a313787cbeae
- https://git.kernel.org/stable/c/f89770c7365748d9d6a2ae07d1c23497ca21ec07
- https://git.kernel.org/stable/c/deb972c7eea8d0bc3109c35c30a1c86d4939f811
- https://git.kernel.org/stable/c/baf1b5715640e434249ce7f63f94bd1a00938ef9
- https://git.kernel.org/stable/c/c2c5359ef2c33684fa3f3652fd761a483db8d1e7
- https://git.kernel.org/stable/c/44d1ca05d6094a5d75c671a0545249186d790b8d
- https://git.kernel.org/stable/c/4f6ac74fa594a918d41255c941256e1d51592d3b
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
Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-99213