GHSA-62GJ-QM4M-4RG3
Vulnerability from github – Published: 2026-08-10 15:33 – Updated: 2026-08-10 15:33In the Linux kernel, the following vulnerability has been resolved:
arm_mpam: guard MBWU state before adding it to garbage
__destroy_component_cfg() adds each RIS mbwu_state object to the MPAM garbage list when destroying component configuration.
However, mbwu_state is allocated per RIS and only for RISes with MBWU monitors. A component can therefore have comp->cfg allocated while some RISes still have ris->mbwu_state set to NULL.
Passing a NULL mbwu_state to add_to_garbage() dereferences the NULL pointer inside the macro.
Skip RISes that do not have an mbwu_state object before adding them to the garbage list.
{
"affected": [],
"aliases": [
"CVE-2026-68345"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-10T13:20:25Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\narm_mpam: guard MBWU state before adding it to garbage\n\n__destroy_component_cfg() adds each RIS mbwu_state object to the MPAM\ngarbage list when destroying component configuration.\n\nHowever, mbwu_state is allocated per RIS and only for RISes with MBWU\nmonitors. A component can therefore have comp-\u003ecfg allocated while some\nRISes still have ris-\u003embwu_state set to NULL.\n\nPassing a NULL mbwu_state to add_to_garbage() dereferences the NULL\npointer inside the macro.\n\nSkip RISes that do not have an mbwu_state object before adding them to\nthe garbage list.",
"id": "GHSA-62gj-qm4m-4rg3",
"modified": "2026-08-10T15:33:47Z",
"published": "2026-08-10T15:33:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68345"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/977f52909c624210178a1247fab0b02b110c1106"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ca1f96334267ab8d47b2c9d535cdc9920fdde269"
}
],
"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.