GHSA-PWWP-XV6G-3R4C
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 15:31In the Linux kernel, the following vulnerability has been resolved:
ksmbd: safely drain sessions during logoff
SMB3 multichannel allows requests for one session to run on multiple connections. Wait for all channels bound to a session before freeing shared session objects.
A deferred byte-range lock remains counted as a running request and only wakes when its file closes. Wake blocked locks during the drain without unpublishing or modifying their file objects. Synchronous CANCEL requests must invoke their cancellation callback to wake pending operations, while CHANGE_NOTIFY completion remains specific to the asynchronous path.
Serialize session teardown with channel registration and previous-session cleanup, and use atomic work-state transitions so LOGOFF, CANCEL, and connection teardown invoke cancellation callbacks only once.
{
"affected": [],
"aliases": [
"CVE-2026-98115"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:42Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: safely drain sessions during logoff\n\nSMB3 multichannel allows requests for one session to run on multiple\nconnections. Wait for all channels bound to a session before freeing\nshared session objects.\n\nA deferred byte-range lock remains counted as a running request and only\nwakes when its file closes. Wake blocked locks during the drain without\nunpublishing or modifying their file objects. Synchronous CANCEL requests\nmust invoke their cancellation callback to wake pending operations, while\nCHANGE_NOTIFY completion remains specific to the asynchronous path.\n\nSerialize session teardown with channel registration and previous-session\ncleanup, and use atomic work-state transitions so LOGOFF, CANCEL, and\nconnection teardown invoke cancellation callbacks only once.",
"id": "GHSA-pwwp-xv6g-3r4c",
"modified": "2026-09-25T15:31:45Z",
"published": "2026-09-25T12:31:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98115"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a7e6df0bb92642bee4431b2b85c69ada1e463b21"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d12168084c8c1b6d883c8eca5853929ac5136a9e"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.