https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:10:07 +0000 https://vulnerability.circl.lu/vuln/cve-2026-72062 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>gpio: mt7621: avoid corruption of shared interrupt trigger state</p> <p>The bank-shared fields like &#39;rising&#39; and &#39;falling&#39; are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if &#39;mediatek_gpio_irq_type()&#39; is called concurrently for different IRQs on the same bank a possible overwrite of each other&#39;s configuration is possible. Thus, protect this state with &#39;gpio_generic_lock_irqsave&#39; lock in the same way it is handled in irp_chip &#39;mediatek_gpio_irq_mask()&#39; and &#39;mediatek_gpio_irq_unmask()&#39; callbacks.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>gpio: mt7621: avoid corruption of shared interrupt trigger state</p> <p>The bank-shared fields like &#39;rising&#39; and &#39;falling&#39; are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if &#39;mediatek_gpio_irq_type()&#39; is called concurrently for different IRQs on the same bank a possible overwrite of each other&#39;s configuration is possible. Thus, protect this state with &#39;gpio_generic_lock_irqsave&#39; lock in the same way it is handled in irp_chip &#39;mediatek_gpio_irq_mask()&#39; and &#39;mediatek_gpio_irq_unmask()&#39; callbacks.</p> https://vulnerability.circl.lu/vuln/cve-2026-72062