- Veröffentlicht
- 19.11.2026 15:45
- Zuletzt geändert
- 19.11.2026
- EPSS (30 Tage)
- unbekannt
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Beschreibung
Originaltext der Quelle, nicht übersetzt.
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.
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 1 betroffen, 6 nicht betroffen.
Red Hat Enterprise Linux 10
BetroffenFix ausstehend
kernel
Nicht betroffen (6)
Red Hat Enterprise Linux 6Nicht betroffenverwundbarer Code nicht enthaltenkernel, kernel-abi-whitelists, kernel-bootwrapper, kernel-debug, kernel-debug-devel, kernel-devel, kernel-doc, kernel-firmware, kernel-headers, kernel-kdump, kernel-kdump-devel, perf, python-perf
Red Hat Enterprise Linux 7Nicht betroffenverwundbarer Code nicht enthaltenbpftool, kernel, kernel-abi-whitelists, kernel-bootwrapper, kernel-debug, kernel-debug-devel, kernel-devel, kernel-doc, kernel-headers, kernel-kdump, kernel-kdump-devel, kernel-rt, kernel-rt-debug, kernel-rt-debug-devel, kernel-rt-debug-kvm, kernel-rt-devel, kernel-rt-doc, kernel-rt-kvm, kernel-rt-trace, kernel-rt-trace-devel, kernel-rt-trace-kvm, kernel-tools, kernel-tools-libs, kernel-tools-libs-devel, perf und 1 weitere
Red Hat Enterprise Linux 8Nicht betroffenverwundbarer Code nicht enthaltenbpftool, kernel, kernel-abi-stablelists, kernel-abi-whitelists, kernel-core, kernel-cross-headers, kernel-debug, kernel-debug-core, kernel-debug-devel, kernel-debug-modules, kernel-debug-modules-extra, kernel-debug-modules-internal, kernel-devel, kernel-doc, kernel-headers, kernel-ipaclones-internal, kernel-modules, kernel-modules-extra, kernel-modules-internal, kernel-rt, kernel-rt-core, kernel-rt-debug, kernel-rt-debug-core, kernel-rt-debug-devel, kernel-rt-debug-kvm und 21 weitere
Red Hat Enterprise Linux 9Nicht betroffenverwundbarer Code nicht enthaltenbpftool, kernel, kernel-64k, kernel-64k-core, kernel-64k-debug, kernel-64k-debug-core, kernel-64k-debug-devel, kernel-64k-debug-devel-matched, kernel-64k-debug-modules, kernel-64k-debug-modules-core, kernel-64k-debug-modules-extra, kernel-64k-debug-modules-internal, kernel-64k-debug-modules-partner, kernel-64k-devel, kernel-64k-devel-matched, kernel-64k-modules, kernel-64k-modules-core, kernel-64k-modules-extra, kernel-64k-modules-internal, kernel-64k-modules-partner, kernel-abi-stablelists, kernel-core, kernel-cross-headers, kernel-debug, kernel-debug-core und 82 weitere
Red Hat OpenShift Container Platform 4Nicht betroffenverwundbarer Code nicht enthaltenopenshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9
Red Hat OpenShift Container Platform 5Nicht betroffenverwundbarer Code nicht enthaltenopenshift/ose-rhel-coreos-10, openshift/ose-rhel-coreos-9
Betroffene Pakete im beobachteten Stack
Debian:14linux7.2.15-1DEBIAN-CVE-2026-99563
Red Hat:enterprise_linux:10kernelkein Fix bekanntCVE-2026-99563
Weitere betroffene Pakete (3)
CVELinux/Linuxkein Fix bekanntCVE-2026-99563
CVELinux/Linuxkein Fix bekanntCVE-2026-99563
LinuxKernel7.1.0 → 7.2.15, 7.3.0 → 7.3.2CVE-2026-99563
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.
Referenzen
- git.kernel.org/stable/c/c13279523ed5da31ca7bba761115afdbd40e06eb
- git.kernel.org/stable/c/df7e97ff4f114e1dc2188d11339b8d0299c4a77f
- git.kernel.org/stable/c/328c7e307e8411899e2f90beae83da9e4c45d700
- git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99563.json
- nvd.nist.gov/vuln/detail/CVE-2026-99563
- security-tracker.debian.org/tracker/CVE-2026-99563
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99563.json
- access.redhat.com/security/cve/CVE-2026-99563
- bugzilla.redhat.com/show_bug.cgi
- www.cve.org/CVERecord