Answer in brief
CVE-2026-63798 records a Unknown severity vulnerability in irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-63798 records a Unknown severity vulnerability in irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <8176773dfceae7978b01c20b233693e072053700 || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <c2c7733101bb8c0b29ac9ee41073eaf602821a59 || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <83d7ec14b0938ad8cae008058fd6f912f4a9a312 || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <44567537a2623dcd2b4018a7f043cf8069579e5d || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <41826e5297e67cd96a0a46fde06a5069a8ce436a || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <b3a3831b2eb884641906fc5e46207b205b6aea13 || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <0405a65e4ebd9eac13a765f9f02ac05851ca5421 || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <37738fdf2ab1e504d1c63ce5bc0aeb6452d8f057 | 8176773dfceae7978b01c20b233693e072053700, c2c7733101bb8c0b29ac9ee41073eaf602821a59, 83d7ec14b0938ad8cae008058fd6f912f4a9a312, 44567537a2623dcd2b4018a7f043cf8069579e5d, 41826e5297e67cd96a0a46fde06a5069a8ce436a, b3a3831b2eb884641906fc5e46207b205b6aea13, 0405a65e4ebd9eac13a765f9f02ac05851ca5421, 37738fdf2ab1e504d1c63ce5bc0aeb6452d8f057 |
| Linux/Linuxgeneric | 3.12 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
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()
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <8176773dfceae7978b01c20b233693e072053700 || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <c2c7733101bb8c0b29ac9ee41073eaf602821a59 || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <83d7ec14b0938ad8cae008058fd6f912f4a9a312 || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <44567537a2623dcd2b4018a7f043cf8069579e5d || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <41826e5297e67cd96a0a46fde06a5069a8ce436a || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <b3a3831b2eb884641906fc5e46207b205b6aea13 || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <0405a65e4ebd9eac13a765f9f02ac05851ca5421 || >=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <37738fdf2ab1e504d1c63ce5bc0aeb6452d8f057 | 8176773dfceae7978b01c20b233693e072053700, c2c7733101bb8c0b29ac9ee41073eaf602821a59, 83d7ec14b0938ad8cae008058fd6f912f4a9a312, 44567537a2623dcd2b4018a7f043cf8069579e5d, 41826e5297e67cd96a0a46fde06a5069a8ce436a, b3a3831b2eb884641906fc5e46207b205b6aea13, 0405a65e4ebd9eac13a765f9f02ac05851ca5421, 37738fdf2ab1e504d1c63ce5bc0aeb6452d8f057 |
| Linux/Linuxgeneric | 3.12 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
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()
Quoted source text, attributed separately from HOL analysis.