# CVE-2026-72062: gpio: mt7621: avoid corruption of shared interrupt trigger state

> A race condition in the Linux kernel MT7621 GPIO driver allows concurrent interrupt configuration changes to corrupt shared state, potentially causing denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** BELL-CVE-2026-72062, DEBIAN-CVE-2026-72062, GHSA-hvv6-qvxj-4xmv, UBUNTU-CVE-2026-72062

## What is CVE-2026-72062?

CVE-2026-72062 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In 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.

## Which versions are affected by CVE-2026-72062?


## How do I fix CVE-2026-72062?

Apply the vendor's patch.

## Is CVE-2026-72062 being exploited?

There is no known exploitation of CVE-2026-72062 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72062 and fix it if it is affected.

What it is: CVE-2026-72062 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72062 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72062/ (Markdown: https://insights.sbomify.com/CVE-2026-72062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72062
- OSV: https://osv.dev/vulnerability/CVE-2026-72062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72062/
Summaries are generated and may contain mistakes; the official description above is the record.