GHSA-9698-PW26-H6MC
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In the Linux kernel, the following vulnerability has been resolved:
accel/ivpu: Validate firmware log buffer metadata
The tracing log headers parsed by fw_log_print_buffer() reside in DMA-shared BOs that the NPU firmware can write to.
fw_log_from_bo() validated log->header_size and log->size, but fw_log_print_buffer() re-read those same fields from shared memory afterwards, allowing a TOCTOU where firmware changes them between the check and the use, and making the host dereference out-of-bounds addresses while printing logs.
Snapshot the validated values once with READ_ONCE() and pass them down explicitly in a new struct ivpu_fw_log_desc instead of re-reading them from the shared struct.
{
"affected": [],
"aliases": [
"CVE-2026-97916"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:18Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Validate firmware log buffer metadata\n\nThe tracing log headers parsed by fw_log_print_buffer() reside in\nDMA-shared BOs that the NPU firmware can write to.\n\nfw_log_from_bo() validated log-\u003eheader_size and log-\u003esize, but\nfw_log_print_buffer() re-read those same fields from shared memory\nafterwards, allowing a TOCTOU where firmware changes them between the\ncheck and the use, and making the host dereference out-of-bounds\naddresses while printing logs.\n\nSnapshot the validated values once with READ_ONCE() and pass them down\nexplicitly in a new struct ivpu_fw_log_desc instead of re-reading them\nfrom the shared struct.",
"id": "GHSA-9698-pw26-h6mc",
"modified": "2026-09-25T12:31:28Z",
"published": "2026-09-25T12:31:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97916"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0724afc55c77c36c7feb9a7264b02aa7593c5c2d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/40868f80a89199630b03d4457876f9a1feba0660"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8ec3d6972f1440fae6c8dadd1859892775208759"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b1555f63ee1a680f280bc18e8dac416f250e2ec3"
}
],
"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.