Skip to main content

Linux Kernel CVE-2026-63798

| EUVDEUVD-2026-45464 MEDIUM
Memory Leak (CWE-401)
2026-07-19 Linux GHSA-2332-q5fp-53mf
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
4.4 MEDIUM

Driver removal and module unloading require CAP_SYS_MODULE (root-equivalent), warranting PR:H over the assigned PR:L; impact is purely availability with no confidentiality or integrity effect.

3.1 AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 29, 2026 - 22:31 vuln.today
CVSS changed
Jul 29, 2026 - 20:22 NVD
5.5 (MEDIUM)
Patch available
Jul 19, 2026 - 14:17 EUVD
CVE Published
Jul 19, 2026 - 12:02 nvd
MEDIUM 5.5
CVE Published
Jul 19, 2026 - 12:02 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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

AnalysisAI

Resource leak in the Linux kernel irqchip/imgpdc interrupt controller driver allows a local privileged user to induce a kernel use-after-free and system crash by triggering driver removal without proper cleanup. The imgpdc driver, targeting Imagination Technologies PDC hardware on MIPS-based SoCs, fails to free allocated domain generic interrupt chips or clear chained handlers on unbind, leaving dangling pointers on the global gc_list accessible by PM suspend, resume, and shutdown callbacks. No public exploit exists and EPSS is 0.18% (7th percentile), reflecting very low exploitation probability consistent with the niche hardware target.

Technical ContextAI

The imgpdc driver (irqchip/irq-imgpdc.c) manages the Imagination Technologies Power Down Controller interrupt controller. The Linux interrupt domain subsystem tracks generic interrupt chips (irq_domain_generic_chips) on a kernel-global gc_list via irq_alloc_domain_generic_chips(). Without the IRQ_DOMAIN_FLAG_DESTROY_GC flag set in domain->flags, these chips are not freed when irq_domain_remove() is called, leaving stale entries on gc_list. Separately, chained handlers installed for peripheral and syswake interrupts via irq_set_chained_handler_and_data() are not cleared on driver removal. CWE-401 (Missing Release of Memory after Effective Lifetime) captures both failure modes: the freed driver memory remains reachable through interrupt infrastructure callbacks, creating use-after-free conditions exploitable during PM transitions or on spurious interrupt delivery.

RemediationAI

Update the Linux kernel to a version containing the backported fix: 5.10.260 or later, 5.15.211 or later, 6.1.177 or later, 6.6.144 or later, 6.12.95 or later, 6.18.38 or later, or 7.1.3 or later. Individual stable-branch fix commits are indexed at https://git.kernel.org/stable/c/8176773dfceae7978b01c20b233693e072053700 and the seven related commits listed in the references. If patching is not immediately possible on an affected embedded platform, preventing imgpdc module unloading - by building the driver as a built-in (CONFIG_IMGPDC=y rather than =m) or using module blacklisting - eliminates the software-triggered removal path, though this trade-off prevents runtime unbind. Note this does not protect against the physical device removal path if the hardware supports hotplug.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected

Share

CVE-2026-63798 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy