GHSA-2259-3WPH-4X6G
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In the Linux kernel, the following vulnerability has been resolved:
gpio: cdev: fix kernel stack leak to user-space in error path
If we fail to acquire the GPIO chip guard in gpio_desc_to_lineinfo(), we return immediately before zeroing the info struct we'll end up passing to the user-space later in lineinfo_get_v1(). This may leak the kernel stack contents. Make gpio_desc_to_lineinfo() return int so that the -ENODEV returned on failure to acquire the guard can be propagated to the callers.
While not strictly necessary: move the memset() before trying to acquire the SRCU read lock too for good measure.
{
"affected": [],
"aliases": [
"CVE-2026-98528"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:04Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: cdev: fix kernel stack leak to user-space in error path\n\nIf we fail to acquire the GPIO chip guard in gpio_desc_to_lineinfo(), we\nreturn immediately before zeroing the info struct we\u0027ll end up passing\nto the user-space later in lineinfo_get_v1(). This may leak the kernel\nstack contents. Make gpio_desc_to_lineinfo() return int so that the\n-ENODEV returned on failure to acquire the guard can be propagated to\nthe callers.\n\nWhile not strictly necessary: move the memset() before trying to acquire\nthe SRCU read lock too for good measure.",
"id": "GHSA-2259-3wph-4x6g",
"modified": "2026-10-18T18:31:52Z",
"published": "2026-10-18T18:31:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98528"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1feb5d39b05afd902ed9fc902ec5b15be03a4bdb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/60a466f231905cd96ae6f0f3c44a710c97873dac"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8460ee5216ab9a38263b01dca4b0a27e083f70f3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cf3d043582e106a0e57002bec8a6de8929ba3e1c"
}
],
"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
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.