GHSA-46J9-HJXG-9FF5
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In the Linux kernel, the following vulnerability has been resolved:
fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header()
mpf_ops_parse_header() reads header_size from the bitstream at MPF_HEADER_SIZE_OFFSET (24). When header_size is zero, the expression *(buf + header_size - 1) reads one byte before the buffer start.
Since initial_header_size is set to 71 in mpf_ops, the fpga-mgr core guarantees the buffer is large enough to reach MPF_HEADER_SIZE_OFFSET. The only real gap is the zero header_size case, which cannot be resolved by providing a larger buffer, so return -EINVAL.
{
"affected": [],
"aliases": [
"CVE-2026-72156"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:21:33Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header()\n\nmpf_ops_parse_header() reads header_size from the bitstream at\nMPF_HEADER_SIZE_OFFSET (24). When header_size is zero, the expression\n*(buf + header_size - 1) reads one byte before the buffer start.\n\nSince initial_header_size is set to 71 in mpf_ops, the fpga-mgr core\nguarantees the buffer is large enough to reach MPF_HEADER_SIZE_OFFSET.\nThe only real gap is the zero header_size case, which cannot be\nresolved by providing a larger buffer, so return -EINVAL.",
"id": "GHSA-46j9-hjxg-9ff5",
"modified": "2026-08-15T06:32:14Z",
"published": "2026-08-15T06:32:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72156"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0d3766fecd9b2db39a18b48021c15c522997ec25"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3da8eaf5469eda2353b72038d644fabddb848ce1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/43a1974da6bc7ce8f4d1dc1d03d56997428c29c3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a1baee24df72ec8fd1d6925c1d5162ffff4ee3bf"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c9ef79e34bc1eac4fd59051e5c7b96a74e59d46f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e45ec24d8e986d79a8e07f49a816c414ad283622"
}
],
"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.