{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90138 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90138 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90138 and fix it if it is affected.\n\nWhat it is: CVE-2026-90138 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90138 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-90138/ (Markdown: https://insights.sbomify.com/CVE-2026-90138/index.md)","id":"CVE-2026-90138","markdown":"https://insights.sbomify.com/CVE-2026-90138/index.md","name":"CVE-2026-90138","record":{"aliases":["AZL-101975","BELL-CVE-2026-90138","DEBIAN-CVE-2026-90138","GHSA-r47p-87c6-4p5v","UBUNTU-CVE-2026-90138"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel vsock","requires_auth":"none","summary":"A logic error in the Linux kernel vsock implementation causes resource leaks and connection rejections, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","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: don't check the listener's sk_err in vsock_accept()\n\nSyzbot reported an issue which can be reproduced with these steps:\n\tr0 = socket(AF_VSOCK, SOCK_STREAM, 0)\n\tbind(r0, {VMADDR_CID_ANY, PORT})\n\tconnect(r0, {VMADDR_CID_LOCAL, PORT}) -\u003e -1, EPROTO (self-connect)\n\tlisten(r0, backlog)                   -\u003e 0\n\tr1 = socket(AF_VSOCK, SOCK_STREAM, 0)\n\tconnect(r1, {VMADDR_CID_LOCAL, PORT}) -\u003e 0\n\taccept(r0)                            -\u003e -1, EPROTO (stale sk_err)\n\nBasically, it creates a socket (r0) and triggers a self-connect after\nbinding it. This self-connect fails with EPROTO because it loops back\nto r0 while the socket is still in the TCP_SYN_SENT state, causing it\nto be incorrectly dispatched to the connecting-client path. The\nunexpected packet type encountered there sets sk_err to EPROTO.\n\nAfter that, it invokes a listen() call on the same socket. This\nlisten() call succeeds because the kernel's listening path never\ninspects or clears sk_err. Then, a new socket (r1) is created as a\nnormal client and connects to r0. However, vsock_accept() rejects this\nincoming connection because the listener's sk_err still holds the\nEPROTO error from the earlier failed self-connect.\n\nThis rejection causes the child socket created for r1's connection to\nnever be freed on virtio or hyperv transports; only the VMCI transport\nimplements pending_work to revisit and clean up a rejected socket.\n\nFor a non-blocking connect(), vsock_connect() may return -EINPROGRESS\nimmediately, and vsock_connect_timeout() can later set sk-\u003esk_err\nasynchronously.\n\nSince no vsock transport ever sets sk_err on a socket while it is in\nTCP_LISTEN state, checking it in vsock_accept() serves no purpose and\nonly carries forward errors left behind by earlier, unrelated\nconnection attempts on the same socket. Remove the checks so accept()\nno longer rejects valid incoming connections because of a stale\nerror, which also avoids the resource leak described above.","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: don't check the listener's sk_err in vsock_accept()","id":"CVE-2026-90138","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"fuse: check for NULL root inode in fuse_fill_super_submount","id":"CVE-2026-90139"},"packages":[],"prev":{"headline":"platform/x86: hp-bioscfg: fix password encoding bounds check","id":"CVE-2026-90137"},"products":["Linux"],"published":"2026-09-17","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-21","vendors":["Linux"]},"summary":"A logic error in the Linux kernel vsock implementation causes resource leaks and connection rejections, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-90138/"}