GHSA-X3RH-X4GX-M2J8
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 12:30In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak
Several bsg handlers stage their request/reply in an uninitialized 256-byte on-stack buffer (uint8_t bsg[DMA_POOL_SIZE]) and fill it via sg_copy_to_buffer(), which only copies as many bytes as the user-supplied request payload. When the request is shorter than the structure, the remainder of the buffer is left holding stale stack data.
qla2x00_read_fru_status() and qla2x00_read_i2c() then copy the full structure back to the reply payload with sg_copy_from_buffer(), leaking the uninitialized stack bytes to user space. The write/update paths do not copy the buffer back, but can feed uninitialized fields to the device.
Zero the stack buffer at declaration in all five handlers, mirroring the heap kzalloc() approach, so short requests can no longer expose stale memory.
{
"affected": [],
"aliases": [
"CVE-2026-89843"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:16:51Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak\n\nSeveral bsg handlers stage their request/reply in an uninitialized 256-byte\non-stack buffer (uint8_t bsg[DMA_POOL_SIZE]) and fill it via\nsg_copy_to_buffer(), which only copies as many bytes as the user-supplied\nrequest payload. When the request is shorter than the structure, the\nremainder of the buffer is left holding stale stack data.\n\nqla2x00_read_fru_status() and qla2x00_read_i2c() then copy the full\nstructure back to the reply payload with sg_copy_from_buffer(), leaking the\nuninitialized stack bytes to user space. The write/update paths do not copy\nthe buffer back, but can feed uninitialized fields to the device.\n\nZero the stack buffer at declaration in all five handlers, mirroring the\nheap kzalloc() approach, so short requests can no longer expose stale\nmemory.",
"id": "GHSA-x3rh-x4gx-m2j8",
"modified": "2026-09-16T12:30:38Z",
"published": "2026-09-16T12:30:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89843"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1c820d0900e4aacd5020b989159f6b4b2f7d0d6a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/26bc6a2c235a70bfc9b6de412600208aca820e20"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4fe5790674097897a1af1367d1e384f7e5a62fb7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5ab32dff910291b5e6bf6223f8a4003536c1800a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/708c0ec1e09c52fee24b74ce9398bf3f8d1c83fd"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7881faf862ee301ecfe3adc0725bd2fa0021cd95"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/947c6bfcf7f5ec924995bec43e3108b98c75b44e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b93d3bb3afe1b44489927de1eb4e66e8536a5935"
}
],
"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.