GHSA-6GP8-RR63-M2RJ
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
ksmbd: retain connection for pending notify work
Deferred CHANGE_NOTIFY work keeps an async message ID after the original request work is released. A durable handle can outlive its connection, so the connection teardown can destroy its async IDA before the handle close releases the pending notify work.
Give the synthetic deferred work a connection reference. Release it after the async ID in ksmbd_free_work_struct(). This keeps the async IDA alive until the deferred work is released, even when the original connection has already left the connection list.
During server shutdown there is no client to receive a cleanup response. Skip the write and only release the pending work.
{
"affected": [],
"aliases": [
"CVE-2026-90168"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:10Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: retain connection for pending notify work\n\nDeferred CHANGE_NOTIFY work keeps an async message ID after the original\nrequest work is released. A durable handle can outlive its connection, so\nthe connection teardown can destroy its async IDA before the handle close\nreleases the pending notify work.\n\nGive the synthetic deferred work a connection reference. Release it after\nthe async ID in ksmbd_free_work_struct(). This keeps the async IDA alive\nuntil the deferred work is released, even when the original connection has\nalready left the connection list.\n\nDuring server shutdown there is no client to receive a cleanup response.\nSkip the write and only release the pending work.",
"id": "GHSA-6gp8-rr63-m2rj",
"modified": "2026-09-17T18:31:53Z",
"published": "2026-09-17T18:31:53Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90168"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/50be5e96c381ae995b7de3869eecdc84476be7f2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f495154703cbcc0050cfd53469bd56965791616b"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.