GHSA-HVV6-QVXJ-4XMV
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-23 15:32In the Linux kernel, the following vulnerability has been resolved:
gpio: mt7621: avoid corruption of shared interrupt trigger state
The bank-shared fields like 'rising' and 'falling' are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if 'mediatek_gpio_irq_type()' is called concurrently for different IRQs on the same bank a possible overwrite of each other's configuration is possible. Thus, protect this state with 'gpio_generic_lock_irqsave' lock in the same way it is handled in irp_chip 'mediatek_gpio_irq_mask()' and 'mediatek_gpio_irq_unmask()' callbacks.
{
"affected": [],
"aliases": [
"CVE-2026-72062"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:21:15Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: mt7621: avoid corruption of shared interrupt trigger state\n\nThe bank-shared fields like \u0027rising\u0027 and \u0027falling\u0027 are modified using\nnon-atomic read-modify-write operations. Since every gpio chip instance\nrepresents an entire bank of 32 pins, if \u0027mediatek_gpio_irq_type()\u0027 is\ncalled concurrently for different IRQs on the same bank a possible overwrite\nof each other\u0027s configuration is possible. Thus, protect this state with\n\u0027gpio_generic_lock_irqsave\u0027 lock in the same way it is handled in irp_chip\n\u0027mediatek_gpio_irq_mask()\u0027 and \u0027mediatek_gpio_irq_unmask()\u0027 callbacks.",
"id": "GHSA-hvv6-qvxj-4xmv",
"modified": "2026-08-23T15:32:58Z",
"published": "2026-08-15T06:32:10Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72062"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1781172526d1092323af443fa03f00e6de560401"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/207d3ebf36f654a43a934addeb4d6775cb2dd667"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/877a243006788aaa586b2d087f27c9f3628071b0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a60a40c9ba30edd06d3fb4215fdf430ed968728e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bddf9314a57a243dd11ed945ba11e146e331257e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d3b9026ef78da3018a7d2c5a9c9d611de6d45c47"
}
],
"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.