GHSA-HW67-72FP-VF5F
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
clk: mediatek: pllfh: Fix IO remapping leak in register_pllfhs error path
When mtk_clk_register_pllfhs function fails to register a PLL, it unregisters all PLLs and cleans up itself in its error path before returning, so the function callers don't need to do it.
But contrary to mtk_clk_unregister_pllfhs function, that does almost the same sequence, it does not free the IO memory mapped on fhctl node, leading to a leak.
Fix this leak by factorizing the cleanup sequence in a new private function and use it both mtk_clk_register_pllfhs and mtk_clk_unregister_pllfhs functions.
Also, change the loop index start value to avoid the -1 operation on index at each loop.
{
"affected": [],
"aliases": [
"CVE-2026-90422"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:46Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: mediatek: pllfh: Fix IO remapping leak in register_pllfhs error path\n\nWhen mtk_clk_register_pllfhs function fails to register a PLL, it\nunregisters all PLLs and cleans up itself in its error path before\nreturning, so the function callers don\u0027t need to do it.\n\nBut contrary to mtk_clk_unregister_pllfhs function, that does almost\nthe same sequence, it does not free the IO memory mapped on fhctl node,\nleading to a leak.\n\nFix this leak by factorizing the cleanup sequence in a new private\nfunction and use it both mtk_clk_register_pllfhs and\nmtk_clk_unregister_pllfhs functions.\n\nAlso, change the loop index start value to avoid the -1 operation on\nindex at each loop.",
"id": "GHSA-hw67-72fp-vf5f",
"modified": "2026-09-17T18:32:04Z",
"published": "2026-09-17T18:32:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90422"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/540d91480bcb1b28a62d7023aa70947ea44c55b9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d35e45e5bad4fabcf122126402b6c6dcb4379672"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fea0b4fd891a2af77b55e05b950e7ea55b5d234e"
}
],
"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.