CVE-2026-99213

Source
https://cve.org/CVERecord?id=CVE-2026-99213
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99213.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99213
Downstream
Published
2026-10-28T10:36:06Z
Modified
2026-11-02T02:30:57Z
Severity
  • 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
vsock: treat TCP_CLOSING as once-established
Details

In the Linux kernel, the following vulnerability has been resolved:

vsock: treat TCP_CLOSING as once-established

Handle the TCP_ESTABLISHED -> TCP_CLOSING transition on OP_RST, 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 OP_RW has already set sk_err, connect() should still return 0, not ENOBUFS because of it. Adapt the inaccurate comment above signal_pending().

Resetting a socket that is still present in connected_table can lead to memory corruption. The reporter noted lost transports for in-flight skbs, and I have reproduced crashes caused by re-insertion into connected_table.

list_add double add: new=, prev=, next=. kernel BUG at lib/list_debug.c:35! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI Workqueue: vsock-loopback vsock_loopback_work RIP: 0010:__list_add_valid_or_report+0x11f/0x130 Call Trace: vsock_insert_connected.cold+0xe/0x13 virtio_transport_recv_pkt+0x10e9/0x1460 vsock_loopback_work+0x305/0x480 process_one_work+0xe4c/0x1560 worker_thread+0x4f1/0xd60 kthread+0x36e/0x470 ret_from_fork+0x47b/0x6b0 ret_from_fork_asm+0x1a/0x30

This fix is supplementary to commit 002541ef650b ("vsock: Ignore signal/timeout on connect() if already established"). Details under Link.

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99213.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
d021c344051af91f42c5ba9fdedc176740cbd238
Fixed
ea36ef3c229d54b552432d1290aee1d807f67fd5
Fixed
5f2ab77028602a22f0cc33cac063a313787cbeae
Fixed
f89770c7365748d9d6a2ae07d1c23497ca21ec07
Fixed
deb972c7eea8d0bc3109c35c30a1c86d4939f811
Fixed
baf1b5715640e434249ce7f63f94bd1a00938ef9
Fixed
c2c5359ef2c33684fa3f3652fd761a483db8d1e7
Fixed
44d1ca05d6094a5d75c671a0545249186d790b8d
Fixed
4f6ac74fa594a918d41255c941256e1d51592d3b

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99213.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
3.9.0
Fixed
5.10.273
Type
ECOSYSTEM
Events
Introduced
5.11.0
Fixed
5.15.224
Type
ECOSYSTEM
Events
Introduced
5.16.0
Fixed
6.1.191
Type
ECOSYSTEM
Events
Introduced
6.2.0
Fixed
6.6.161
Type
ECOSYSTEM
Events
Introduced
6.7.0
Fixed
6.12.115
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.59
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.2.13

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99213.json"