GHSA-8J89-GR3P-JPP8
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
perf: arm_pmuv3: Zero initialize hw_id branch stack field
PERF_SAMPLE_BRANCH_HW_INDEX is supported by BRBE so hw_id is passed to userspace, but it's never set by the BRBE driver. Zero initialize it as it should be according to the docs:
- For the architectures whose raw branch records are
- already stored in age order, the hw_idx should be 0.
It's probably too risky to remove PERF_SAMPLE_BRANCH_HW_INDEX from BRBE now in case anyone is setting it and reading the value, but zero initializing the whole struct also protects against the same issue with new fields that are added in the future.
{
"affected": [],
"aliases": [
"CVE-2026-90272"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:23Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nperf: arm_pmuv3: Zero initialize hw_id branch stack field\n\nPERF_SAMPLE_BRANCH_HW_INDEX is supported by BRBE so hw_id is passed to\nuserspace, but it\u0027s never set by the BRBE driver. Zero initialize it as\nit should be according to the docs:\n\n * For the architectures whose raw branch records are\n * already stored in age order, the hw_idx should be 0.\n\nIt\u0027s probably too risky to remove PERF_SAMPLE_BRANCH_HW_INDEX from BRBE\nnow in case anyone is setting it and reading the value, but zero\ninitializing the whole struct also protects against the same issue with\nnew fields that are added in the future.",
"id": "GHSA-8j89-gr3p-jpp8",
"modified": "2026-09-17T18:31:58Z",
"published": "2026-09-17T18:31:58Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90272"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/57b72442c1672963fd51ab441ca1b71f6dc79b66"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7c3b63386c27bed8d59a4b4c283d02860420eb0a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/988e11b69ef9d4034e19c64407030fa948580c3d"
}
],
"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.