GHSA-5HPH-W22R-X9JX
Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-31 15:30In 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.
{
"affected": [],
"aliases": [
"CVE-2026-99213"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-28T11:17:42Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nvsock: treat TCP_CLOSING as once-established\n\nHandle the TCP_ESTABLISHED -\u003e TCP_CLOSING transition on OP_RST, which can\nrace with the connect loop. Immediately break and return 0 on\nESTABLISHED/CLOSING. The return value of connect() should reflect what\nhappened up to the point the connection was established or failed. Events\nthat occur afterwards must not affect it. E.g. even if OP_RW has already\nset sk_err, connect() should still return 0, not ENOBUFS because of it.\nAdapt the inaccurate comment above signal_pending().\n\nResetting a socket that is still present in connected_table can lead to\nmemory corruption. The reporter noted lost transports for in-flight skbs,\nand I have reproduced crashes caused by re-insertion into connected_table.\n\n list_add double add: new=, prev=, next=.\n kernel BUG at lib/list_debug.c:35!\n Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n Workqueue: vsock-loopback vsock_loopback_work\n RIP: 0010:__list_add_valid_or_report+0x11f/0x130\n Call Trace:\n vsock_insert_connected.cold+0xe/0x13\n virtio_transport_recv_pkt+0x10e9/0x1460\n vsock_loopback_work+0x305/0x480\n process_one_work+0xe4c/0x1560\n worker_thread+0x4f1/0xd60\n kthread+0x36e/0x470\n ret_from_fork+0x47b/0x6b0\n ret_from_fork_asm+0x1a/0x30\n\nThis fix is supplementary to commit 002541ef650b (\"vsock: Ignore\nsignal/timeout on connect() if already established\"). Details under Link.",
"id": "GHSA-5hph-w22r-x9jx",
"modified": "2026-10-31T15:30:23Z",
"published": "2026-10-28T12:31:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99213"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/44d1ca05d6094a5d75c671a0545249186d790b8d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4f6ac74fa594a918d41255c941256e1d51592d3b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5f2ab77028602a22f0cc33cac063a313787cbeae"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/baf1b5715640e434249ce7f63f94bd1a00938ef9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c2c5359ef2c33684fa3f3652fd761a483db8d1e7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/deb972c7eea8d0bc3109c35c30a1c86d4939f811"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ea36ef3c229d54b552432d1290aee1d807f67fd5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f89770c7365748d9d6a2ae07d1c23497ca21ec07"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.