CVE-2026-72062 in Linux
Summary
by MITRE • 08/15/2026
In the Linux kernel, the following vulnerability has been resolved:
gpio: mt7621: avoid corruption of shared interrupt trigger state
The bank-shared fields like 'rising' and 'falling' are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if 'mediatek_gpio_irq_type()' is called concurrently for different IRQs on the same bank a possible overwrite of each other's configuration is possible. Thus, protect this state with 'gpio_generic_lock_irqsave' lock in the same way it is handled in irp_chip 'mediatek_gpio_irq_mask()' and 'mediatek_gpio_irq_unmask()' callbacks.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 08/15/2026
This vulnerability exists within the Linux kernel's gpio subsystem specifically affecting the MediaTek mt7621 platform implementation. The issue stems from improper handling of shared interrupt trigger state configuration across multiple gpio chip instances that represent the same hardware bank containing 32 pins. When concurrent calls to the mediatek_gpio_irq_type() function occur for different IRQs within the same bank, the non-atomic read-modify-write operations used to modify bank-shared fields such as 'rising' and 'falling' create a race condition that can result in configuration corruption.
The technical flaw manifests when multiple processes or threads attempt to configure interrupt trigger types simultaneously on different gpio lines within the same 32-pin bank. Since these operations are not protected by atomic mechanisms, one thread's modification can overwrite another thread's configuration changes before they are properly committed. This creates a scenario where interrupt trigger settings become inconsistent and unpredictable, potentially leading to missed interrupts or incorrect interrupt handling behavior. The vulnerability directly relates to CWE-362 which describes concurrent execution issues such as race conditions in multithreaded applications.
The operational impact of this vulnerability extends beyond simple configuration corruption to potentially compromise system stability and security. If an attacker can predict or control the timing of gpio interrupt configuration operations, they might be able to manipulate interrupt behavior to bypass security mechanisms or create denial-of-service conditions. The affected platform represents a common embedded architecture used in networking equipment and IoT devices where reliable interrupt handling is critical for proper system operation. This vulnerability affects systems using the MediaTek mt7621 SoC where gpio interrupt handling relies on shared bank state management without proper synchronization.
The recommended mitigation involves implementing proper locking mechanisms around the shared interrupt trigger state modifications, specifically using the existing gpio_generic_lock_irqsave lock that is already employed in the mediatek_gpio_irq_mask() and mediatek_gpio_irq_unmask() callback functions. This approach ensures atomic access to the bank-shared configuration fields and prevents concurrent modification conflicts. The fix aligns with standard security practices for protecting shared resources in kernel space operations and follows ATT&CK technique T1068 which relates to exploit development for privilege escalation through race conditions and concurrency issues. The solution maintains compatibility while ensuring data integrity in multi-threaded interrupt handling scenarios typical of embedded systems.