GHSA-44M9-H4RV-5WQG
Vulnerability from github – Published: 2026-11-19 15:31 – Updated: 2026-11-19 15:31In the Linux kernel, the following vulnerability has been resolved:
NFSD: Don't complete a cld upcall the daemon has not read
cld_pipe_downcall() matches a reply to its upcall on the xid alone. A write that arrives before the daemon has read that upcall completes __cld_pipe_upcall() while its struct rpc_pipe_msg is still queued on the pipe. The waiter returns, its stack frame goes away, and the pipe keeps a list_head that points into it. The next rpc_queue_upcall() walks that pointer:
BUG: KASAN: vmalloc-out-of-bounds in __list_add_valid_or_report Read of size 8 at addr ffffc90007027950 by task syz.0.96/13066 __list_add_valid_or_report+0x6a/0x130 rpc_queue_upcall cld_pipe_upcall nfsd4_cld_grace_start nfsd4_cld_tracking_init
The pipe is mode 0600 in rpc_pipefs, so the trigger is a broken or hostile nfsdcld rather than an unprivileged task.
Record whether the daemon has consumed the whole message and complete only when it has. cld_pipe_destroy_msg() runs on every path by which the pipe releases a message, so it can maintain that flag under cn_lock. nfsdcld sends its -EINPROGRESS downcalls only after reading the upcall, so the new check does not break the GraceStart record stream.
{
"affected": [],
"aliases": [
"CVE-2026-99367"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-19T15:17:48Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Don\u0027t complete a cld upcall the daemon has not read\n\ncld_pipe_downcall() matches a reply to its upcall on the xid alone.\nA write that arrives before the daemon has read that upcall\ncompletes __cld_pipe_upcall() while its struct rpc_pipe_msg is still\nqueued on the pipe. The waiter returns, its stack frame goes away,\nand the pipe keeps a list_head that points into it. The next\nrpc_queue_upcall() walks that pointer:\n\n BUG: KASAN: vmalloc-out-of-bounds in __list_add_valid_or_report\n Read of size 8 at addr ffffc90007027950 by task syz.0.96/13066\n __list_add_valid_or_report+0x6a/0x130\n rpc_queue_upcall\n cld_pipe_upcall\n nfsd4_cld_grace_start\n nfsd4_cld_tracking_init\n\nThe pipe is mode 0600 in rpc_pipefs, so the trigger is a broken or\nhostile nfsdcld rather than an unprivileged task.\n\nRecord whether the daemon has consumed the whole message and\ncomplete only when it has. cld_pipe_destroy_msg() runs on every path\nby which the pipe releases a message, so it can maintain that flag\nunder cn_lock. nfsdcld sends its -EINPROGRESS downcalls only after\nreading the upcall, so the new check does not break the GraceStart\nrecord stream.",
"id": "GHSA-44m9-h4rv-5wqg",
"modified": "2026-11-19T15:31:22Z",
"published": "2026-11-19T15:31:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99367"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/226c11eb20042ce4251f50870ce61f86581f8152"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7f4bf851aca4e18940ebf2bddf4ba6783802ee81"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e058341ceb177226fdb20a36d48fa827851d9c81"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f6d1f1072243a1adb1ae15425f6e36f86be94078"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.