{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99213 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99213 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99213 and fix it if it is affected.\n\nWhat it is: CVE-2026-99213 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99213 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-99213/ (Markdown: https://insights.sbomify.com/CVE-2026-99213/index.md)","id":"CVE-2026-99213","markdown":"https://insights.sbomify.com/CVE-2026-99213/index.md","name":"CVE-2026-99213","record":{"aliases":["AZL-111380","BELL-CVE-2026-99213","DEBIAN-CVE-2026-99213","GHSA-5hph-w22r-x9jx","UBUNTU-CVE-2026-99213"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"vsock: treat TCP_CLOSING as once-established","id":"CVE-2026-99213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"drm/vc4: hdmi: Move packet RAM enable to PM runtime","id":"CVE-2026-99214"},"packages":[],"prev":{"headline":"net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure","id":"CVE-2026-99212"},"products":["Linux"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99213/"}