CVE-2026-63798
Received Received - Intake

Resource Leak and Use-After-Free in Linux Kernel irqchip/imgpdc

Publication date: 2026-07-19

Last updated on: 2026-07-19

Assigner: kernel.org

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()

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-19
Last Modified
2026-07-19
Generated
2026-07-20
AI Q&A
2026-07-19
EPSS Evaluated
N/A
NVD
CVE-2026-63798
EUVD
EUVD-2026-45464

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a resource leak in the irqchip/imgpdc driver. During driver initialization, generic interrupt chips are allocated and chained handlers are set up. However, during driver removal, these resources are not properly cleaned up. The generic chips remain on a global list and chained handlers are left dangling, which can lead to use-after-free scenarios and kernel crashes when the freed memory is accessed later.

Detection Guidance

This vulnerability is specific to the Linux kernel's irqchip/imgpdc driver and does not have network-based detection methods. Detection requires checking kernel logs for crashes or spurious interrupts related to the imgpdc driver. Monitor dmesg or system logs for errors like 'use-after-free' or 'kernel crash' after driver removal.

Impact Analysis

This vulnerability can cause system instability by triggering kernel crashes due to use-after-free conditions. It may also lead to spurious interrupts accessing freed memory, potentially causing data corruption or unexpected behavior in the system.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a Linux kernel driver issue causing resource leaks and potential kernel crashes due to improper cleanup of interrupt handlers and generic chips. Compliance impacts would only occur if the vulnerability leads to system instability or data corruption in systems handling sensitive data.

Mitigation Strategies

Apply the kernel patch that resolves this issue by updating to a version containing the fix. Ensure the imgpdc driver is properly removed without leaving dangling handlers or generic chips. Reboot the system after applying the patch to ensure changes take effect.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-63798. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart