VulnerabilityPublished 23 Oct 2026

CVE-2026-98947: Linux kernel · vsock: Fix memory leak in vmci_transport_recv_dgram_cb()

Source GCVE Database

Authoritative record:CVE-2026-98947

Not known to be exploited · fixed in 9907db2b8e7ba70b442bb9dec86526a6511fac62 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9907db2b8e7ba70b442bb9dec86526a6511fac62, 4835dbcde5cc3ae37e0d0796052056b35fcae8bf, 7c24a4e87e219072e5e106f6791146cbf3b056b3 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-cf52-4qc8-h2h9

What to do

Upgrade Linux kernel to 9907db2b8e7ba70b442bb9dec86526a6511fac62, 4835dbcde5cc3ae37e0d0796052056b35fcae8bf, 7c24a4e87e219072e5e106f6791146cbf3b056b3 or 0f8e2b2045355a0ee2008125e573435504b13cee.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ d021c344051af91f42c5ba9fdedc176740cbd238, < 9907db2b8e7ba70b442bb9dec86526a6511fac62	Fixed in 9907db2b8e7ba70b442bb9dec86526a6511fac62
LinuxLinux	Affected ≥ d021c344051af91f42c5ba9fdedc176740cbd238, < 4835dbcde5cc3ae37e0d0796052056b35fcae8bf	Fixed in 4835dbcde5cc3ae37e0d0796052056b35fcae8bf
LinuxLinux	Affected ≥ d021c344051af91f42c5ba9fdedc176740cbd238, < 7c24a4e87e219072e5e106f6791146cbf3b056b3	Fixed in 7c24a4e87e219072e5e106f6791146cbf3b056b3
LinuxLinux	Affected ≥ d021c344051af91f42c5ba9fdedc176740cbd238, < 0f8e2b2045355a0ee2008125e573435504b13cee	Fixed in 0f8e2b2045355a0ee2008125e573435504b13cee
LinuxLinux	Affected =3.9	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: vsock: Fix memory leak in vmci_transport_recv_dgram_cb() During the closure of a datagram socket, the vmci_transport_recv_dgram_cb() function may be called, which will add the packets to the socket's backlog; then, after the receive queue is cleared, the __release_sock() function will move the packet back from the socket's backlog to the receive queue, which will lead to a memory leak. sock_close __sock_release __vsock_release // take ownership by user-space lock_sock_nested sock_set_flag(sk, SOCK_DEAD) vmci_transport_release vmci_dispatch_dgs vmci_datagram_invoke_guest_handler vmci_transport_recv_dgram_cb sk_receive_skb if (!sock_owned_by_user(sk)) [...] (!) else if sk_add_backlog() [...] (!) skb_queue_purge(&sk->sk_receive_queue) release_sock __release_sock // move all packets from the backlog // to the receive queue (!) sk_backlog_rcv vsock_queue_rcv_skb [...] __sock_queue_rcv_skb if (!sock_flag(sk, SOCK_DEAD)) // Since the socket is "dead", the function will not // be called sk->sk_data_ready(sk) sock_release_ownership(sk); sock_put Add a receive queue cleanup in the socket destructor to fix this. syzkaller report: unreferenced object 0xffff8880117bfb80 (size 240): comm "irq/56-vmw_vmci", pid 205, jiffies 4295064448 (age 73.992s) hex dump (first 32 bytes): 78 dc 26 1e 80 88 ff ff 78 dc 26 1e 80 88 ff ff x.&.....x.&..... 00 00 00 00 00 00 00 00 c0 da 26 1e 80 88 ff ff ..........&..... backtrace: [<ffffffff82be8d97>] __alloc_skb+0x287/0x330 net/core/skbuff.c:505 [<ffffffffa114bcbd>] vmci_transport_recv_dgram_cb+0xbd/0x210 [vmw_vsock_vmci_transport] [<ffffffffa05072c6>] vmci_datagram_invoke_guest_handler+0x366/0x450 [vmw_vmci] [<ffffffffa050ad75>] vmci_dispatch_dgs+0x235/0x490 [vmw_vmci] [<ffffffffa050b025>] vmci_interrupt+0x55/0x290 [vmw_vmci] [<ffffffff8137ad2b>] irq_thread_fn+0x8b/0x1a0 kernel/irq/manage.c:1205 [<ffffffff8137c7ae>] irq_thread+0x28e/0x530 kernel/irq/manage.c:1314 [<ffffffff81253dd6>] kthread+0x2e6/0x3a0 kernel/kthread.c:376 [<ffffffff81004392>] ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:295 Found by InfoTeCS on behalf of Linux Verification Center (linuxtesting.org) with Syzkaller.

References

Community reviews

Loading reviews…