GHSA-X3MW-3VXW-G4F9
Vulnerability from github – Published: 2026-07-19 15:30 – Updated: 2026-07-19 15:30In the Linux kernel, the following vulnerability has been resolved:
PCI: mediatek-gen3: Prevent leaking IRQ domains when IRQ not found
In mtk_pcie_setup_irq(), the IRQ domains are allocated before the controller's IRQ is fetched. If the latter fails, the function directly returns an error, without cleaning up the allocated domains.
Hence, reverse the order so that the IRQ domains are allocated after the controller's IRQ is found.
This was flagged by Sashiko during a review of "[PATCH v6 0/7] PCI: mediatek-gen3: add power control support".
{
"affected": [],
"aliases": [
"CVE-2026-63862"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-19T15:16:53Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nPCI: mediatek-gen3: Prevent leaking IRQ domains when IRQ not found\n\nIn mtk_pcie_setup_irq(), the IRQ domains are allocated before the\ncontroller\u0027s IRQ is fetched. If the latter fails, the function\ndirectly returns an error, without cleaning up the allocated domains.\n\nHence, reverse the order so that the IRQ domains are allocated after the\ncontroller\u0027s IRQ is found.\n\nThis was flagged by Sashiko during a review of \"[PATCH v6 0/7] PCI:\nmediatek-gen3: add power control support\".",
"id": "GHSA-x3mw-3vxw-g4f9",
"modified": "2026-07-19T15:30:27Z",
"published": "2026-07-19T15:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63862"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/07a5ecb94768cbf76fe659e9924000e9ced0c8a6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0a2d60edc3e57c9512e239ebdfd12204d3368560"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/215d4273347b9010a9deae378b0df79c163f707d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5573c44cb3fd01a9f62d569ae9ac870ef5f0e0ba"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/946b31b5a699a2760ee52af0055e5ebf29c5f4cb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/abd3c1927d33766aef39c4640880e3d2637429c2"
}
],
"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.