GHSA-6GQW-GW67-F4RG
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
smb/server: abort initialization when proc setup fails
ksmbd_server_init() calls ksmbd_proc_init() before creating the remaining proc entries and server subsystems. ksmbd_proc_init() tears down partial state on a procfs or percpu_counter allocation failure, but returns void, so ksmbd_server_init() continues as if the counters were usable.
Once userspace starts the server, server_ctrl_handle_init() calls ksmbd_proc_reset(), which reaches percpu_counter_set() with a NULL per-CPU counters pointer on SMP systems. The later ksmbd_proc_create() calls also receive a NULL parent and may create entries in the /proc root; ksmbd_proc_cleanup() cannot remove those entries because ksmbd_proc_fs is NULL.
{
"affected": [],
"aliases": [
"CVE-2026-90164"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:09Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: abort initialization when proc setup fails\n\nksmbd_server_init() calls ksmbd_proc_init() before creating the\nremaining proc entries and server subsystems. ksmbd_proc_init() tears\ndown partial state on a procfs or percpu_counter allocation failure,\nbut returns void, so ksmbd_server_init() continues as if the counters\nwere usable.\n\nOnce userspace starts the server, server_ctrl_handle_init() calls\nksmbd_proc_reset(), which reaches percpu_counter_set() with a NULL\nper-CPU counters pointer on SMP systems. The later ksmbd_proc_create()\ncalls also receive a NULL parent and may create entries in the /proc\nroot; ksmbd_proc_cleanup() cannot remove those entries because\nksmbd_proc_fs is NULL.",
"id": "GHSA-6gqw-gw67-f4rg",
"modified": "2026-09-17T18:31:53Z",
"published": "2026-09-17T18:31:53Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90164"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/db97f3763727d652112ae70038d4e17b3ce277bb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fb4ba2bdfc1de8866e7c8e00df99f4b03ff42f09"
}
],
"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.