GHSA-3R6V-V38P-C2R8
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In the Linux kernel, the following vulnerability has been resolved:
sunrpc: fix uninitialized xprt_create_args structure
The xprt_create_args structure is allocated on the stack without initialization in rpc_sysfs_xprt_switch_add_xprt_store(). While some fields are manually populated, critical fields like srcaddr, bc_xps, and flags contain uninitialized stack garbage.
This can lead to: 1. Kernel panic when xs_setup_xprt() dereferences garbage srcaddr 2. Information leak if srcaddr points to sensitive stack data 3. Unpredictable behavior if flags has random bits set
The fix is to zero-initialize the structure to ensure all unused fields are NULL/0, preventing the transport setup code from acting on garbage data.
{
"affected": [],
"aliases": [
"CVE-2026-72150"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:21:32Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsunrpc: fix uninitialized xprt_create_args structure\n\nThe xprt_create_args structure is allocated on the stack without\ninitialization in rpc_sysfs_xprt_switch_add_xprt_store(). While some\nfields are manually populated, critical fields like srcaddr, bc_xps,\nand flags contain uninitialized stack garbage.\n\nThis can lead to:\n1. Kernel panic when xs_setup_xprt() dereferences garbage srcaddr\n2. Information leak if srcaddr points to sensitive stack data\n3. Unpredictable behavior if flags has random bits set\n\nThe fix is to zero-initialize the structure to ensure all unused\nfields are NULL/0, preventing the transport setup code from acting\non garbage data.",
"id": "GHSA-3r6v-v38p-c2r8",
"modified": "2026-08-15T06:32:14Z",
"published": "2026-08-15T06:32:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72150"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/17d90b68c3a3d7d7e95b49e1fe9381a723f637a8"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7d3ce3bd23c062a7c1c6d372d1b08e48b9e17cc3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/933654508b2bc36e2c3c086c0365e2403fb2141f"
}
],
"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.