{"api_version":"1","generated_at":"2026-10-24T07:56:24+00:00","cve":"CVE-2026-98947","urls":{"html":"https://cve.report/CVE-2026-98947","api":"https://cve.report/api/cve/CVE-2026-98947.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98947","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98947"},"summary":{"title":"vsock: Fix memory leak in vmci_transport_recv_dgram_cb()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix memory leak in vmci_transport_recv_dgram_cb()\n\nDuring the closure of a datagram socket, the vmci_transport_recv_dgram_cb()\nfunction may be called, which will add the packets\nto the socket's backlog; then, after the receive queue is cleared,\nthe __release_sock() function will move the packet back from the socket's\nbacklog to the receive queue, which will lead to a memory leak.\n\nsock_close\n __sock_release\n __vsock_release\n // take ownership by user-space\n lock_sock_nested\n sock_set_flag(sk, SOCK_DEAD)\n vmci_transport_release\n vmci_dispatch_dgs\n vmci_datagram_invoke_guest_handler\n vmci_transport_recv_dgram_cb\n sk_receive_skb\n if (!sock_owned_by_user(sk))\n [...]\n (!) else if sk_add_backlog()\n [...]\n (!) skb_queue_purge(&sk->sk_receive_queue)\n\n release_sock\n __release_sock\n // move all packets from the backlog\n // to the receive queue\n (!) sk_backlog_rcv\n vsock_queue_rcv_skb\n [...]\n __sock_queue_rcv_skb\n if (!sock_flag(sk, SOCK_DEAD))\n // Since the socket is \"dead\", the function will not\n // be called\n sk->sk_data_ready(sk)\n sock_release_ownership(sk);\n sock_put\n\nAdd a receive queue cleanup in the socket destructor to fix this.\n\nsyzkaller report:\n\nunreferenced object 0xffff8880117bfb80 (size 240):\n comm \"irq/56-vmw_vmci\", pid 205, jiffies 4295064448 (age 73.992s)\n hex dump (first 32 bytes):\n 78 dc 26 1e 80 88 ff ff 78 dc 26 1e 80 88 ff ff x.&.....x.&.....\n 00 00 00 00 00 00 00 00 c0 da 26 1e 80 88 ff ff ..........&.....\n backtrace:\n [] __alloc_skb+0x287/0x330 net/core/skbuff.c:505\n [] vmci_transport_recv_dgram_cb+0xbd/0x210 [vmw_vsock_vmci_transport]\n [] vmci_datagram_invoke_guest_handler+0x366/0x450 [vmw_vmci]\n [] vmci_dispatch_dgs+0x235/0x490 [vmw_vmci]\n [] vmci_interrupt+0x55/0x290 [vmw_vmci]\n [] irq_thread_fn+0x8b/0x1a0 kernel/irq/manage.c:1205\n [] irq_thread+0x28e/0x530 kernel/irq/manage.c:1314\n [] kthread+0x2e6/0x3a0 kernel/kthread.c:376\n [] ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:295\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with Syzkaller.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-23 13:17:15","updated_at":"2026-10-23 13:17:15"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/7c24a4e87e219072e5e106f6791146cbf3b056b3","name":"https://git.kernel.org/stable/c/7c24a4e87e219072e5e106f6791146cbf3b056b3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9907db2b8e7ba70b442bb9dec86526a6511fac62","name":"https://git.kernel.org/stable/c/9907db2b8e7ba70b442bb9dec86526a6511fac62","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0f8e2b2045355a0ee2008125e573435504b13cee","name":"https://git.kernel.org/stable/c/0f8e2b2045355a0ee2008125e573435504b13cee","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/4835dbcde5cc3ae37e0d0796052056b35fcae8bf","name":"https://git.kernel.org/stable/c/4835dbcde5cc3ae37e0d0796052056b35fcae8bf","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98947","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98947","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d021c344051af91f42c5ba9fdedc176740cbd238 0f8e2b2045355a0ee2008125e573435504b13cee git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d021c344051af91f42c5ba9fdedc176740cbd238 4835dbcde5cc3ae37e0d0796052056b35fcae8bf git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d021c344051af91f42c5ba9fdedc176740cbd238 9907db2b8e7ba70b442bb9dec86526a6511fac62 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d021c344051af91f42c5ba9fdedc176740cbd238 7c24a4e87e219072e5e106f6791146cbf3b056b3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3.9","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 3.9 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.113 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.57 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.11 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/vmw_vsock/af_vsock.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"0f8e2b2045355a0ee2008125e573435504b13cee","status":"affected","version":"d021c344051af91f42c5ba9fdedc176740cbd238","versionType":"git"},{"lessThan":"4835dbcde5cc3ae37e0d0796052056b35fcae8bf","status":"affected","version":"d021c344051af91f42c5ba9fdedc176740cbd238","versionType":"git"},{"lessThan":"9907db2b8e7ba70b442bb9dec86526a6511fac62","status":"affected","version":"d021c344051af91f42c5ba9fdedc176740cbd238","versionType":"git"},{"lessThan":"7c24a4e87e219072e5e106f6791146cbf3b056b3","status":"affected","version":"d021c344051af91f42c5ba9fdedc176740cbd238","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/vmw_vsock/af_vsock.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"3.9"},{"lessThan":"3.9","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.113","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.57","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.11","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.113","versionStartIncluding":"3.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.57","versionStartIncluding":"3.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.11","versionStartIncluding":"3.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"3.9","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix memory leak in vmci_transport_recv_dgram_cb()\n\nDuring the closure of a datagram socket, the vmci_transport_recv_dgram_cb()\nfunction may be called, which will add the packets\nto the socket's backlog; then, after the receive queue is cleared,\nthe __release_sock() function will move the packet back from the socket's\nbacklog to the receive queue, which will lead to a memory leak.\n\nsock_close\n __sock_release\n __vsock_release\n // take ownership by user-space\n lock_sock_nested\n sock_set_flag(sk, SOCK_DEAD)\n vmci_transport_release\n vmci_dispatch_dgs\n vmci_datagram_invoke_guest_handler\n vmci_transport_recv_dgram_cb\n sk_receive_skb\n if (!sock_owned_by_user(sk))\n [...]\n (!) else if sk_add_backlog()\n [...]\n (!) skb_queue_purge(&sk->sk_receive_queue)\n\n release_sock\n __release_sock\n // move all packets from the backlog\n // to the receive queue\n (!) sk_backlog_rcv\n vsock_queue_rcv_skb\n [...]\n __sock_queue_rcv_skb\n if (!sock_flag(sk, SOCK_DEAD))\n // Since the socket is \"dead\", the function will not\n // be called\n sk->sk_data_ready(sk)\n sock_release_ownership(sk);\n sock_put\n\nAdd a receive queue cleanup in the socket destructor to fix this.\n\nsyzkaller report:\n\nunreferenced object 0xffff8880117bfb80 (size 240):\n comm \"irq/56-vmw_vmci\", pid 205, jiffies 4295064448 (age 73.992s)\n hex dump (first 32 bytes):\n 78 dc 26 1e 80 88 ff ff 78 dc 26 1e 80 88 ff ff x.&.....x.&.....\n 00 00 00 00 00 00 00 00 c0 da 26 1e 80 88 ff ff ..........&.....\n backtrace:\n [] __alloc_skb+0x287/0x330 net/core/skbuff.c:505\n [] vmci_transport_recv_dgram_cb+0xbd/0x210 [vmw_vsock_vmci_transport]\n [] vmci_datagram_invoke_guest_handler+0x366/0x450 [vmw_vmci]\n [] vmci_dispatch_dgs+0x235/0x490 [vmw_vmci]\n [] vmci_interrupt+0x55/0x290 [vmw_vmci]\n [] irq_thread_fn+0x8b/0x1a0 kernel/irq/manage.c:1205\n [] irq_thread+0x28e/0x530 kernel/irq/manage.c:1314\n [] kthread+0x2e6/0x3a0 kernel/kthread.c:376\n [] ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:295\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with Syzkaller."}],"providerMetadata":{"dateUpdated":"2026-10-23T12:19:06.146Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/0f8e2b2045355a0ee2008125e573435504b13cee"},{"url":"https://git.kernel.org/stable/c/4835dbcde5cc3ae37e0d0796052056b35fcae8bf"},{"url":"https://git.kernel.org/stable/c/9907db2b8e7ba70b442bb9dec86526a6511fac62"},{"url":"https://git.kernel.org/stable/c/7c24a4e87e219072e5e106f6791146cbf3b056b3"}],"title":"vsock: Fix memory leak in vmci_transport_recv_dgram_cb()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98947","datePublished":"2026-10-23T12:19:06.146Z","dateReserved":"2026-09-25T10:25:14.381Z","dateUpdated":"2026-10-23T12:19:06.146Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-23 13:17:15","lastModifiedDate":"2026-10-23 13:17:15","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98947","Ordinal":"1","Title":"vsock: Fix memory leak in vmci_transport_recv_dgram_cb()","CVE":"CVE-2026-98947","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98947","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix memory leak in vmci_transport_recv_dgram_cb()\n\nDuring the closure of a datagram socket, the vmci_transport_recv_dgram_cb()\nfunction may be called, which will add the packets\nto the socket's backlog; then, after the receive queue is cleared,\nthe __release_sock() function will move the packet back from the socket's\nbacklog to the receive queue, which will lead to a memory leak.\n\nsock_close\n __sock_release\n __vsock_release\n // take ownership by user-space\n lock_sock_nested\n sock_set_flag(sk, SOCK_DEAD)\n vmci_transport_release\n vmci_dispatch_dgs\n vmci_datagram_invoke_guest_handler\n vmci_transport_recv_dgram_cb\n sk_receive_skb\n if (!sock_owned_by_user(sk))\n [...]\n (!) else if sk_add_backlog()\n [...]\n (!) skb_queue_purge(&sk->sk_receive_queue)\n\n release_sock\n __release_sock\n // move all packets from the backlog\n // to the receive queue\n (!) sk_backlog_rcv\n vsock_queue_rcv_skb\n [...]\n __sock_queue_rcv_skb\n if (!sock_flag(sk, SOCK_DEAD))\n // Since the socket is \"dead\", the function will not\n // be called\n sk->sk_data_ready(sk)\n sock_release_ownership(sk);\n sock_put\n\nAdd a receive queue cleanup in the socket destructor to fix this.\n\nsyzkaller report:\n\nunreferenced object 0xffff8880117bfb80 (size 240):\n comm \"irq/56-vmw_vmci\", pid 205, jiffies 4295064448 (age 73.992s)\n hex dump (first 32 bytes):\n 78 dc 26 1e 80 88 ff ff 78 dc 26 1e 80 88 ff ff x.&.....x.&.....\n 00 00 00 00 00 00 00 00 c0 da 26 1e 80 88 ff ff ..........&.....\n backtrace:\n [] __alloc_skb+0x287/0x330 net/core/skbuff.c:505\n [] vmci_transport_recv_dgram_cb+0xbd/0x210 [vmw_vsock_vmci_transport]\n [] vmci_datagram_invoke_guest_handler+0x366/0x450 [vmw_vmci]\n [] vmci_dispatch_dgs+0x235/0x490 [vmw_vmci]\n [] vmci_interrupt+0x55/0x290 [vmw_vmci]\n [] irq_thread_fn+0x8b/0x1a0 kernel/irq/manage.c:1205\n [] irq_thread+0x28e/0x530 kernel/irq/manage.c:1314\n [] kthread+0x2e6/0x3a0 kernel/kthread.c:376\n [] ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:295\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with Syzkaller.","Type":"Description","Title":"vsock: Fix memory leak in vmci_transport_recv_dgram_cb()"}]}}}