# CVE-2026-53226: gpio: rockchip: fix generic IRQ chip leak on remove

> A use-after-free vulnerability in the Rockchip GPIO driver can cause a kernel crash during device removal, leading to denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-90414, BELL-CVE-2026-53226, DEBIAN-CVE-2026-53226, GHSA-fw97-88cp-67m9, ROOT-OS-DEBIAN-12-CVE-2026-53226, ROOT-OS-DEBIAN-13-CVE-2026-53226, ROOT-OS-UBUNTU-2204-CVE-2026-53226, ROOT-OS-UBUNTU-2404-CVE-2026-53226, UBUNTU-CVE-2026-53226

## What is CVE-2026-53226?

CVE-2026-53226 is a medium-severity use after free vulnerability in Linux kernel, published on 25 Jun 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: rockchip: fix generic IRQ chip leak on remove

The driver allocates domain generic chips using
irq_alloc_domain_generic_chips() during probe. However, on driver
remove/teardown, the generic chips are not automatically freed when the
IRQ domain is removed because the domain flags do not include
IRQ_DOMAIN_FLAG_DESTROY_GC.

This causes both the domain generic chips structure and the associated
generic chips to be leaked. Additionally, the generic chips remain on
the global gc_list and may later be visited by generic IRQ chip suspend,
resume, or shutdown callbacks after the GPIO bank has been removed,
potentially resulting in a use-after-free and kernel crash.

Fix the resource leak by explicitly calling
irq_domain_remove_generic_chips() before removing the IRQ domain in
rockchip_gpio_remove().

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-53226 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53226 is a medium-severity use after free vulnerability in Linux kernel, published on 25 Jun 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-53226 in the wild and no public exploit code.

Affected product: Linux kernel. 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-53226/ (Markdown: https://insights.sbomify.com/CVE-2026-53226/index.md)
```

## Sources

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

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