GHSA-84PC-7MXQ-H2J8
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-14 15:32In the Linux kernel, the following vulnerability has been resolved:
NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path
When the server returns a new layout stateid while a valid one is still held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on the on-stack free_me list and jumps to out_forget. Segments whose reference count drops to zero are unlinked from lo->plh_segs and moved to free_me by mark_lseg_invalid(); for an idle cached segment the layout header holds the only reference, so this happens on the first decrement.
out_forget never drains free_me -- only the success path calls pnfs_free_lseg_list().
Commit 814b84971388 ("pNFS/NFSv4: Fix a layout segment leak in pnfs_layout_process()") added the drain; commit 08bd8dbe8882 ("pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()") removed it while switching the destination to lo->plh_return_segs, which is drained elsewhere. Commit fb700ef02676 ("NFSv4.1: Simplify layout return in pnfs_layout_process()") switched the destination back to free_me without restoring the drain.
Restore the pnfs_free_lseg_list() call.
{
"affected": [],
"aliases": [
"CVE-2026-89710"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:19:58Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path\n\nWhen the server returns a new layout stateid while a valid one is still\nheld, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on\nthe on-stack free_me list and jumps to out_forget. Segments whose\nreference count drops to zero are unlinked from lo-\u003eplh_segs and moved\nto free_me by mark_lseg_invalid(); for an idle cached segment the layout\nheader holds the only reference, so this happens on the first decrement.\n\nout_forget never drains free_me -- only the success path calls\npnfs_free_lseg_list().\n\nCommit 814b84971388 (\"pNFS/NFSv4: Fix a layout segment leak in\npnfs_layout_process()\") added the drain; commit 08bd8dbe8882\n(\"pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()\")\nremoved it while switching the destination to lo-\u003eplh_return_segs, which\nis drained elsewhere. Commit fb700ef02676 (\"NFSv4.1: Simplify layout\nreturn in pnfs_layout_process()\") switched the destination back to\nfree_me without restoring the drain.\n\nRestore the pnfs_free_lseg_list() call.",
"id": "GHSA-84pc-7mxq-h2j8",
"modified": "2026-09-14T15:32:34Z",
"published": "2026-09-11T21:31:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89710"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/32ac1b0b7f1cfa0d1a1faf9c72f4154046101070"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/36e3f13bf0728f4ce11ee8904cec82a783222f62"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a080bb69d30f11738d753a60d1eb733d627c2093"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ad3e41855325e55623276660ef20fbc3b8ba087f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ee5a386cfe60f3f8286de16a9db8e1a08f0bc124"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f52188118d319b47d49ee91a897f6afda4879c59"
}
],
"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.