GHSA-7WFC-WFH5-RXRH
Vulnerability from github – Published: 2026-07-19 18:31 – Updated: 2026-07-19 18:31In the Linux kernel, the following vulnerability has been resolved:
iio: pressure: bmp280: fix stack leak in bmp580 trigger handler
bmp580_trigger_handler() declares its scan buffer on the stack without an initializer and then memcpy()s 3 bytes of 24-bit sensor data into each 4-byte __le32 field. The high byte of comp_temp and comp_press is left uninitialized, and the channel storagebits is 32, so two bytes of stack are pushed to userspace per scan.
This is a regression from when the buffer lived in the private data, the move to a stack-local struct dropped the implicit zeroing. bme280_trigger_handler() was fixed up to handle this bug, but this driver was not fixed because there was no padding hole, but rather a short-fill issue.
Fix this all by just zero-initializing the structure on the stack.
{
"affected": [],
"aliases": [
"CVE-2026-63965"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-19T16:17:15Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\niio: pressure: bmp280: fix stack leak in bmp580 trigger handler\n\nbmp580_trigger_handler() declares its scan buffer on the stack without\nan initializer and then memcpy()s 3 bytes of 24-bit sensor data into\neach 4-byte __le32 field. The high byte of comp_temp and comp_press is\nleft uninitialized, and the channel storagebits is 32, so two bytes of\nstack are pushed to userspace per scan.\n\nThis is a regression from when the buffer lived in the private data, the\nmove to a stack-local struct dropped the implicit zeroing.\nbme280_trigger_handler() was fixed up to handle this bug, but this\ndriver was not fixed because there was no padding hole, but rather a\nshort-fill issue.\n\nFix this all by just zero-initializing the structure on the stack.",
"id": "GHSA-7wfc-wfh5-rxrh",
"modified": "2026-07-19T18:31:47Z",
"published": "2026-07-19T18:31:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63965"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/387c86b582e0782ab332e7bfcd4e6e3f93922961"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/58dfb6fe9dc80270cf7cc014837af4cbf928e3aa"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a58400f58f82f3d8de9c067aa7cda690228c1ecc"
}
],
"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.