GHSA-F4RX-VF72-PG97
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33In the Linux kernel, the following vulnerability has been resolved:
accel/ivpu: Reject firmware log with size smaller than header
fw_log_from_bo() validates the tracing buffer header_size and that the log fits within the BO, but never checks that log->size is at least log->header_size. fw_log_print_buffer() then computes:
u32 data_size = log->size - log->header_size;
which underflows to a near-U32_MAX value when firmware reports a log whose size is smaller than its header. That huge data_size defeats the log_start/log_end bounds clamps added by commit dd1311bcf0e6 ("accel/ivpu: Add bounds checks for firmware log indices"), so fw_log_print_lines() reads far past the small real data region of the BO. A size of 0 also makes fw_log_from_bo() advance the offset by 0, causing the callers to loop forever on the same header.
Reject logs whose size is smaller than the header (which also rejects size == 0).
{
"affected": [],
"aliases": [
"CVE-2026-72089"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:21:22Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Reject firmware log with size smaller than header\n\nfw_log_from_bo() validates the tracing buffer header_size and that the\nlog fits within the BO, but never checks that log-\u003esize is at least\nlog-\u003eheader_size. fw_log_print_buffer() then computes:\n\n u32 data_size = log-\u003esize - log-\u003eheader_size;\n\nwhich underflows to a near-U32_MAX value when firmware reports a log whose\nsize is smaller than its header. That huge data_size defeats the\nlog_start/log_end bounds clamps added by commit dd1311bcf0e6 (\"accel/ivpu:\nAdd bounds checks for firmware log indices\"), so fw_log_print_lines() reads\nfar past the small real data region of the BO. A size of 0 also makes\nfw_log_from_bo() advance the offset by 0, causing the callers to loop\nforever on the same header.\n\nReject logs whose size is smaller than the header (which also rejects\nsize == 0).",
"id": "GHSA-f4rx-vf72-pg97",
"modified": "2026-08-17T06:33:09Z",
"published": "2026-08-15T06:32:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72089"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/257321a1c036da417f5d9c47b95c7e58f62bf263"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5592a207e158b738d9c1d27f208dbbea13ae7606"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6920e62be4c969a68ce4ebc59da68c6cbc9512e5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dc9a1cda2e46d0254730a6f93cfe48532895f33c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ddb44baed257560f192b145ed36cf8c0a412de47"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
"type": "CVSS_V3"
}
]
}
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.