CVE-2025-21955: ksmbd: prevent connection release during oplock break notification
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: prevent connection release during oplock break notification
ksmbd_work could be freed when after connection release.
Increment r_count of ksmbd_conn to indicate that requests
are not finished yet and to not release the connection.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw in the ksmbd SMB file-server component can release a connection while related work is still running. A network attacker with low privileges could potentially trigger memory corruption affecting confidentiality, integrity, and availability. Risk is concentrated on systems actively using and exposing ksmbd.
Executive priority
Prioritize exposed ksmbd file servers and systems accessible from untrusted or broadly privileged networks. Remediate promptly because the severity is high and the stated impact spans data confidentiality, integrity, and service availability. Systems not using ksmbd are lower priority after configuration is verified.
Technical view
The flaw is a use-after-free condition: ksmbd_work may remain active after its ksmbd_conn is released during an oplock-break notification. The upstream correction increments the connection reference count while requests remain unfinished. The supplied CVSS 3.1 score is 8.8, with network reachability, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure requires a Linux system using ksmbd, with its SMB service reachable by the attacker. The bundle flags Linux 5.15 and listed 6.x releases through 6.14 as affected. Distribution kernels may contain backported fixes, so version numbers alone are insufficient for confirmation.
Exploitation context
The supplied record is not in KEV, and the source bundle provides no evidence of active exploitation or a public exploit. The CVSS vector indicates that exploitation is network-accessible but requires low privileges. The available evidence does not establish reliable code execution outcomes.
Researcher notes
The core issue is connection lifetime management during oplock-break notification. Review the referenced stable commits and distribution backports for exact branch coverage. The affected-version representation in the supplied bundle is not detailed enough to determine every vulnerable or fixed downstream kernel solely from its release string.
Mitigation direction
Install a vendor-supported kernel containing the applicable upstream stable fix.
Check distribution security guidance because vendors may backport fixes without changing the main kernel version.
Restrict network access to ksmbd services while remediation is pending.
Disable ksmbd where it is not operationally required, following vendor guidance.
Validation and detection
Confirm whether the ksmbd module or service is enabled and actively serving SMB.
Identify every network path that can reach the affected SMB service.
Verify the installed vendor kernel includes the applicable referenced stable commit.
After updating, confirm the fixed kernel is running rather than merely installed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21955 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.