7 matches found
Ubuntu: Security Advisory (USN-7801-1)
The remote host is missing an update for the SPDX-FileCopyrightText: 2025 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only ifdescription...
Linux Distros Unpatched Vulnerability : CVE-2025-21944
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - ksmbd: fix bug on trap in smb2lock If lock count is greater than 1, flags could be old value. It should be checked with flags of smblock, not flags. It will cau...
CVE-2025-21944
creationtimestamp| type| source ---|---|--- 2025-04-02 12:36:41+00:00| seen| https://t.me/DarkWebInformerCVEAlerts/10052 2026-03-19 00:00:00+00:00| seen| https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/...
CVE-2025-21944
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix bug on trap in smb2lock If lock count is greater than 1, flags could be old value. It should be checked with flags of smblock, not flags. It will cause bug-on trap from locksfreelock in error handling routine...
CVE-2025-21944 ksmbd: fix bug on trap in smb2_lock
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix bug on trap in smb2lock If lock count is greater than 1, flags could be old value. It should be checked with flags of smblock, not flags. It will cause bug-on trap from locksfreelock in error handling routine...
CVE-2025-21944
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix bug on trap in smb2lock If lock count is greater than 1, flags could be old value. It should be checked with flags of smblock, not flags. It will cause bug-on trap from locksfreelock in error handling routine...
CVE-2025-21944 ksmbd: fix bug on trap in smb2_lock
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix bug on trap in smb2lock If lock count is greater than 1, flags could be old value. It should be checked with flags of smblock, not flags. It will cause bug-on trap from locksfreelock in error handling routine...