9 matches found
ksmbd: prevent connection release during oplock break notification
...
EUVD-2025-9365
Malicious code in bioql PyPI...
Linux Distros Unpatched Vulnerability : CVE-2025-21955
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - ksmbd: prevent connection release during oplock break notification ksmbdwork could be freed when after connection release. Increment rcount of ksmbdconn to...
CVE-2025-21955
In the Linux kernel, the following vulnerability has been resolved: ksmbd: prevent connection release during oplock break notification ksmbdwork could be freed when after connection release. Increment rcount of ksmbdconn to indicate that requests are not finished yet and to not release the...
CVE-2025-21955
CVE-2025-21955 affects the Linux kernel’s ksmbd component. The issue occurs when ksmbd_work could be freed after a connection release during an oplock break notification, risking use-after-release. The fix increments the ksmbd_conn r_count to indicate ongoing requests and prevents releasing the c...
PT-2025-14336
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A vulnerability in the Linux kernel has been resolved, specifically in the ksmbd component. The issue involved the potential freeing of ksmbd work after connection release during oplock...
Design/Logic Flaw
smbd in Samba 3.0 before 3.0.37, 3.2 before 3.2.15, 3.3 before 3.3.8, and 3.4 before 3.4.2 allows remote authenticated users to cause a denial of service infinite loop via an unanticipated oplock break notification reply packet...
CVE-2009-2906
smbd in Samba 3.0 before 3.0.37, 3.2 before 3.2.15, 3.3 before 3.3.8, and 3.4 before 3.4.2 allows remote authenticated users to cause a denial of service infinite loop via an unanticipated oplock break notification reply packet...
CVE-2009-2906
smbd in Samba 3.0 before 3.0.37, 3.2 before 3.2.15, 3.3 before 3.3.8, and 3.4 before 3.4.2 allows remote authenticated users to cause a denial of service infinite loop via an unanticipated oplock break notification reply packet...