Skip to content
Threat Brief

← All advisories

CVE-2026-99563

Severity unknownNo known exploitationFix available

smb: smbdirect: release failed pending sockets of a listener

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 5% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: smb: smbdirect: release failed pending sockets of a listener A child of a listener only left the listen.pending or listen.ready list via smbdirect_socket_accept() or when the listener was destroyed. So every connection that failed before it was accepted (negotiate timeout, peer disconnect, invalid negotiate request, ...) stayed on the list and counted against the backlog until the listener was destroyed. After about backlog (10 for ksmbd) such connections smbdirect_listen_connect_request() rejected every new connection with -EBUSY, so an unauthenticated peer was able to permanently stop ksmbd from accepting SMB-Direct connections. Now a failed child moves itself to a new listen.orphaned list at the end of smbdirect_socket_cleanup_work(), after the disconnect was started, and queues listen.purge_orphaned_work, which releases it with smbdirect_socket_release(), without holding the listener's rdma_lock_handler() lock, in the same way smbdirect_socket_destroy() does for the remaining children. Orphaned sockets still count against the backlog until they are released. sc->accept.listener is now only changed under listener->listen.lock and whoever clears it is responsible for releasing the socket: smbdirect_socket_accept(), purge_orphaned_work or the destroy of the listener. In order to make that work: - a struct smbdirect_socket that is a listener is now freed via kfree_rcu(), so that a child can dereference sc->accept.listener under rcu_read_lock(), even if the listener is released concurrently. - smbdirect_listen_connect_request() adds nsc to the listen.pending list and sets nsc->accept.listener before it calls smbdirect_accept_connect_request(), and always returns 0 so the rdma_cm core keeps the connection id and nsc owns it. On a non-zero return it schedules nsc's teardown with smbdirect_socket_schedule_cleanup(), which orphans it off the listener so that purge_orphaned_work releases it; nsc destroys its own connection id with rdma_destroy_id() in that teardown. The teardown has to be deferred because the rdma_cm core holds nsc's id_priv->handler_mutex across the handler, so nsc->rdma.cm_id must not be destroyed synchronously from here. That same handler_mutex (and the listener's) also guarantees nsc can't go away under us, so setting the listener before the call is safe and lets a failure orphan nsc. - smbdirect_accept_negotiate_recv_work() no longer moves a socket to the ready list if it already failed or no longer belongs to the listener. Every accepting socket has a listener, so if sc->accept.listener is already cleared, it no longer sends a negotiate response, as the socket is about to be released. - smbdirect_socket_destroy() of the listener disables purge_orphaned_work and also releases the orphaned sockets.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom dc691b91ad1677def14582a279e56fd943b52f94 before df7e97ff4f114e1dc2188d11339b8d0299c4a77fdf7e97ff4f114e1dc2188d11339b8d0299c4a77fCVE Program
LinuxLinuxfrom dc691b91ad1677def14582a279e56fd943b52f94 before 328c7e307e8411899e2f90beae83da9e4c45d700328c7e307e8411899e2f90beae83da9e4c45d700CVE Program
LinuxLinuxfrom dc691b91ad1677def14582a279e56fd943b52f94 before c13279523ed5da31ca7bba761115afdbd40e06ebc13279523ed5da31ca7bba761115afdbd40e06ebCVE Program
LinuxLinux7.1Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.15 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 7.1Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references