{"id":"CVE-2026-98947","title":"vsock: Fix memory leak in vmci_transport_recv_dgram_cb()","summary":"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…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= d021c344051af91f42c5ba9fdedc176740cbd238 < 0f8e2b2045355a0ee2008125e573435504b13cee","Linux >= d021c344051af91f42c5ba9fdedc176740cbd238 < 4835dbcde5cc3ae37e0d0796052056b35fcae8bf","Linux >= d021c344051af91f42c5ba9fdedc176740cbd238 < 9907db2b8e7ba70b442bb9dec86526a6511fac62","Linux >= d021c344051af91f42c5ba9fdedc176740cbd238 < 7c24a4e87e219072e5e106f6791146cbf3b056b3","Linux 3.9"],"published":"2026-10-23","updated":"2026-10-23","sourceUpdated":"2026-10-23T12:19:06.146Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-98947","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"}],"tags":["cve.org"],"ingestedAt":"2026-10-23T13:24:55.559Z","slug":"CVE-2026-98947","body":"## Overview\n\nIn 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    [<ffffffff82be8d97>] __alloc_skb+0x287/0x330 net/core/skbuff.c:505\n    [<ffffffffa114bcbd>] vmci_transport_recv_dgram_cb+0xbd/0x210 [vmw_vsock_vmci_transport]\n    [<ffffffffa05072c6>] vmci_datagram_invoke_guest_handler+0x366/0x450 [vmw_vmci]\n    [<ffffffffa050ad75>] vmci_dispatch_dgs+0x235/0x490 [vmw_vmci]\n    [<ffffffffa050b025>] vmci_interrupt+0x55/0x290 [vmw_vmci]\n    [<ffffffff8137ad2b>] irq_thread_fn+0x8b/0x1a0 kernel/irq/manage.c:1205\n    [<ffffffff8137c7ae>] irq_thread+0x28e/0x530 kernel/irq/manage.c:1314\n    [<ffffffff81253dd6>] kthread+0x2e6/0x3a0 kernel/kthread.c:376\n    [<ffffffff81004392>] 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.\n\n## Affected\n\n- `Linux >= d021c344051af91f42c5ba9fdedc176740cbd238 < 0f8e2b2045355a0ee2008125e573435504b13cee`\n- `Linux >= d021c344051af91f42c5ba9fdedc176740cbd238 < 4835dbcde5cc3ae37e0d0796052056b35fcae8bf`\n- `Linux >= d021c344051af91f42c5ba9fdedc176740cbd238 < 9907db2b8e7ba70b442bb9dec86526a6511fac62`\n- `Linux >= d021c344051af91f42c5ba9fdedc176740cbd238 < 7c24a4e87e219072e5e106f6791146cbf3b056b3`\n- `Linux 3.9`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}